Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!usc!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!destroyer!cs.ubc.ca!newsserver.sfu.ca!sfu.ca!vanepp From: vanepp@fraser.sfu.ca (Peter Van Epp) Subject: Re: skipping fsck on boot Message-ID: <vanepp.733333504@sfu.ca> Sender: news@sfu.ca Organization: Simon Fraser University, Burnaby, B.C., Canada References: <C4JzM1.19C@rokkaku.atl.ga.us> Date: Sun, 28 Mar 1993 15:45:04 GMT Lines: 28 kml@rokkaku.atl.ga.us (Kevin Lahey) writes: >I'm getting pretty tired of waiting for 386BSD to finish fsck'ing my >partitions on boot up. [Some would suggest that I should ditch some >disk; I'll ignore 'em.] I have used other modern UNIXes that don't >bother with the fsck if the partition has been cleanly unmounted. >How dangerous (and tough) would it be for me to set up 386BSD to skip >the fsck's at boot? >I assume that I'd have to change some of the filesystem code to set a flag >on umount, and that I'd have to add some code to fsck to check for that >flag and skip on to the next partition. Are there some other hidden >pitfalls? Is this a religious issue? >Thanks, >Kevin >kml@rokkaku.atl.ga.us >Again, it's one thing to be fun, entertaining and wrong, and quite another >to be boring, self-important and wrong. -- Vince Gibboni Both fastboot and fasthalt work (at least for me) on 386bsd, marking the file system as properly shutdown and therefore skipping the fsck on reboot. Peter Van Epp / Operations and Technical Support Simon Fraser University, Burnaby, B.C. Canada