Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: $Revision: 1.6.2.16 $; site inmet.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!gamma!epsilon!zeta!sabre!bellcore!decvax!cca!inmet!bhyde
From: bhyde@inmet.UUCP
Newsgroups: net.micro.mac
Subject: Re: Re: System Beep on power on. FLAME
Message-ID: <26700013@inmet.UUCP>
Date: Mon, 6-May-85 16:52:00 EDT
Article-I.D.: inmet.26700013
Posted: Mon May  6 16:52:00 1985
Date-Received: Fri, 10-May-85 01:38:06 EDT
References: <6689@ucbvax.UUCP>
Lines: 12
Nf-ID: #R:ucbvax:-668900:inmet:26700013:000:718
Nf-From: inmet!bhyde    May  6 16:52:00 1985


Writing a resume procedure is no mean feat.  Since exit to finder
doesn't rebuild the system heap from scratch your takings some risks in
letting the finder attack on your disks at that point.  Consider what
happens if it rewrites a disk's directory without checking that the
directory is absolutly pure and noble, bye bye data...
  I'd be interested in what other people have done to create a reset
procedure that is reasonably safe.  For example do you forcably dismount
the disks?  Do you reinit everybody?  Do you check the consistency of some
read only data structures and use them as a vote of confidence?
  My only use of this feature is to get some oportunity to look at
things prior to the machine rebooting.