Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!agate.berkeley.edu!cgd From: cgd@erewhon.CS.Berkeley.EDU (Chris G. Demetriou) Newsgroups: comp.os.386bsd.questions Subject: Re: skipping fsck on boot Date: 28 Mar 93 09:26:19 Organization: Kernel Hackers 'r' Us Lines: 28 Message-ID: <CGD.93Mar28092619@erewhon.CS.Berkeley.EDU> References: <C4JzM1.19C@rokkaku.atl.ga.us> <C4LvFs.2pG@chinet.chi.il.us> NNTP-Posting-Host: erewhon.cs.berkeley.edu In-reply-to: randy@chinet.chi.il.us's message of Sun, 28 Mar 1993 15:38:15 GMT In article <C4LvFs.2pG@chinet.chi.il.us> randy@chinet.chi.il.us (Randy Suess) writes: >Use fastboot and fasthalt. Won't run fsck on startup. they create a file named /fastboot, and /etc/rc (which deals with things like fsck'ing the disk on startup), upon seeing it, doesn't fsck the disk. >You can trace down what those programs do, I guess to make >it permanent. umm, it's *really* a good idea to do this *ONLY* if you know the disks were unmounted cleanly (for an example of why, say "fastboot" but reset the machine before it syncs the disks). even so, you don't want to *always* not fsck your disks, because, while the FFS has been around for ages, it still might have a few bugs in it... so use fastboot whenever you can, but make *sure* that things get fsck'd after crashes... chris -- Chris G. Demetriou cgd@cs.berkeley.edu In case you didn't know: There are blondes and bogons in the VM system!