Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!elroy!david
From: david@elroy.Jpl.Nasa.Gov (David Robinson)
Newsgroups: comp.unix.questions
Subject: Re: umount, and SunOS 3.X
Summary: "-b" option
Message-ID: <9192@elroy.Jpl.Nasa.Gov>
Date: 9 Sep 88 01:54:02 GMT
References: <27262@neabbs.UUCP> <520@cra2.apctrc.UUCP> <13448@mimsy.UUCP>
Organization: Image Analysis Systems Grp, JPL
Lines: 23

In article <13448@mimsy.UUCP>, chris@mimsy.UUCP (Chris Torek) writes:
< In article <520@cra2.apctrc.UUCP> zjat02@apctrc.UUCP (Jon A. Tankersley)
< writes:
< >rc.boot trashes /etc/mtab before running /etc/umount -at nfs.  This leaves
< >potential garbage on remote systems /etc/rmtab (remote mtab).
< 
< It does more than just that.  rc.boot is always run, even on a single-
< user boot.  If your root file system gets corrupted---and as most of us
< know, anything that *can* go wrong *will* go wrong (someone at Sun
< seems to have forgotten)---the code that clobbers /etc/mtab will cause
< a continuous series of crashes and auto-reboots.  The only way to
< recover is to boot from another machine, or from the distribution
< tapes.  But if this is the first machine on your network, or the only
< one with source . . . ?  (Praise to Aule for mini-roots.)

Or you could use the totally undocumented "-b" option to cause the
Sun to boot without running /etc/rc.boot and hope you are not
too corrupted.

-- 
	David Robinson		elroy!david@csvax.caltech.edu     ARPA
				david@elroy.jpl.nasa.gov	  ARPA
				{cit-vax,ames}!elroy!david	  UUCP
Disclaimer: No one listens to me anyway!