Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!munnari.OZ.AU!news.ecn.uoknor.edu!news.cis.okstate.edu!col.hp.com!usenet.eel.ufl.edu!news.mathworks.com!news.kei.com!sundog.tiac.net!gary
From: gary@wheel.tiac.net (Gary D. Duzan)
Newsgroups: comp.unix.bsd.misc
Subject: Re: Not doing fsck on reboot
Date: 4 Jan 1996 13:07:29 GMT
Organization: Brain Dead Innovations
Lines: 19
Message-ID: <4cgjeh$2fl@sundog.tiac.net>
References: <4cfdum$oqo@picasso.op.net> <4cfhuf$q0b@picasso.op.net>
NNTP-Posting-Host: wheel.tiac.net
In article <4cfhuf$q0b@picasso.op.net>,
Bruce Momjian <root@candle.pha.pa.us> wrote:
=>Bruce Momjian (root@candle.pha.pa.us) wrote:
=>: If my unix machine was brought down cleanly, I don't understand why an
=>: fsck is performed upon reboot.
=>
=>I see now that there is an option to shutdown that allows for fastboots.
=>
=>I guess I am now wondering why I would not always want to use that flag.
You didn't mention which Unix in particular you are using recent
versions of NetBSD, at least, do exactly what you want, marking file
systems clean when unmounted normally and not checking them on boot.
Gary D. Duzan
Humble Practitioner of the Computer Arts