Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!seismo!gatech!bloom-beacon!bu-cs!m2c!ulowell!page From: page@ulowell.cs.ulowell.edu (Bob Page) Newsgroups: comp.sys.amiga Subject: Re: Wishlist for 1.3 Executive. Message-ID: <1539@ulowell.cs.ulowell.edu> Date: Sat, 18-Jul-87 14:29:27 EDT Article-I.D.: ulowell.1539 Posted: Sat Jul 18 14:29:27 1987 Date-Received: Sun, 19-Jul-87 01:11:48 EDT References: <396@mdbs.UUCP> Reply-To: page@swan.cs.ulowell.edu (Bob Page) Distribution: comp Organization: University of Lowell Lines: 30 cs@mdbs.UUCP wrote: >since Control-Amiga-Amiga is not a system crash but rather a very >friendly reboot, why didn't the system wait for the disks to synchronize?? >This is what I would like the 1.3 executive to do for me, and hurry! No way. I want to ensure that I can IMMEDIATELY stop writes to the disk (or the serial port, or whatever) on command without powering the system down. That's what Control Uh Uh is for. Sure the file system is fragile, and your disk might get trashed, but that's the price you pay for the ability to STOP the system. For user sanity, there should be a 'reboot' command that will flush I/O buffers, send messages to any processes/daemons, and do whatever other cleanup is necessary. Then it could warm restart the machine, or write "Type Control Uh Uh now" and loop in high priority with interrupts and multitasking disabled so nothing else gets run on the system. Another option would be to have a program that revectors the warm restart location and replaces it with a subroutine that flushes the disk buffers before it calls the REAL warm restart routine. So, what you want is possible, but altering the OS to automatically (by default, built into the kernel) do it for you is the wrong approach. In the meantime, remember that your machine multitasks. The disk driver runs when it can get the CPU slice to. ..Bob -- Bob Page, U of Lowell CS Dept. page@ulowell.{uucp,edu,csnet}