Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!seismo!husc6!necntc!ames!ucbcad!ucbvax!COGSCI.BERKELEY.EDU!bryce From: bryce@COGSCI.BERKELEY.EDU (Bryce Nesbitt) Newsgroups: comp.sys.amiga Subject: Re: Wishlist for 1.3 Executive. Message-ID: <8707180817.AA05716@cogsci.berkeley.edu> Date: Sat, 18-Jul-87 04:17:09 EDT Article-I.D.: cogsci.8707180817.AA05716 Posted: Sat Jul 18 04:17:09 1987 Date-Received: Sat, 18-Jul-87 20:52:22 EDT Sender: daemon@ucbvax.BERKELEY.EDU Lines: 23 > The other day I made a change to my sys:s/startup-sequence file using > the editor "ed". Well, I wrote the file out and then immediately rebooted | via Control-Amiga-Amiga to see if it would work. Well, many can guess | that the file was never written out because of the 1 to 2 second delay | it takes to "sync" the disk. What I want to know is,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! Not debating the merits of the idea itself... but this would be a very easy thing to do under the current system. A little program would need to be written that adds a RESET handler to the keyboard.device and on activation sends a FLUSH to each mounted device. Of course the software may be in a somewhat suspect state if the user decides to hit the 'old Vulcan nerve pinch (CTRL-Amiga-Amiga or, for A500 users CTRL-whaddayacallthatkey- whaddayoucalltheotherkey). Care would needed to be taken as to the integerety of the devices you plan to FLUSH. ----------------------------- |\ /| . Ack! (NAK, EOT, SOH) {o O} . ( " ) bryce@cogsci.berkeley.EDU -or- ucbvax!cogsci!bryce U "Success leads to stagnation; stagnation leads to failure."