Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!bloom-beacon!oberon!orion.cf.uci.edu!ucsd!ucsbcsl!banana!panzer
From: panzer@banana.ucsb.edu (Panzer, John Robert)
Newsgroups: comp.sys.amiga
Subject: Re: More 1.4 whishes
Message-ID: <1291@hub.ucsb.edu>
Date: 2 Mar 89 23:30:33 GMT
References: <5442@abo.fi> <2020@cps3xx.UUCP> <1265@hub.ucsb.edu> <Mar.1.17.50.06.1989.9522@topaz.rutgers.edu>
Sender: news@hub.ucsb.edu
Reply-To: panzer@banana.UUCP (Panzer)
Organization: University of California, Santa Barbara
Lines: 14

In article <Mar.1.17.50.06.1989.9522@topaz.rutgers.edu> armhold@topaz.rutgers.edu (George Armhold) writes:
>>have the resident commands survive a warm-reboot.
>
>I don't think that would be a good idea- the reason for warm-booting is
>usually to clear all ram, no?
>

Yes, it should be an option, like remounting a recoverable RAM disk.  It would
save a LOT of time when you have an involuntary reboot (a.k.a. Guru) and want
to go back and try again.  (Most of my reboots are involuntary :^)

- John Panzer
(panzer@cornu.ucsb.edu)
(panzer@apple.UUCP)