Date: Tue, 26 Nov 2002 00:16:53 +0100 From: Marcin Dalecki <mdcki@gmx.net> To: Terry Lambert <tlambert2@mindspring.com> Cc: Kris Kennaway <kris@obsecurity.org>, Robert Watson <rwatson@FreeBSD.ORG>, Mikhail Teterin <mi+mx@aldan.algebra.com>, current@FreeBSD.ORG Subject: Re: -current unusable after a crash Message-ID: <3DE2AF65.9000502@gmx.net> References: <200211250959.39594.mi%2Bmx@aldan.algebra.com> <Pine.NEB.3.96L.1021125102358.33619A-100000@fledge.watson.org> <20021125172445.GA8953@rot13.obsecurity.org> <3DE29DE6.CDD96F3F@mindspring.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Terry Lambert wrote: > Kris Kennaway wrote: > >>On Mon, Nov 25, 2002 at 10:24:46AM -0500, Robert Watson wrote: >> >>>>I thought, this might be due to the priority of the background fsck and >>>>have once left it alone for several hours -- with no effect. The usual >>>>fsck takes a few minutes. >>> >>We really need to disable background fsck if the system panicked. >>I've seen far too much bizarre filesystem behaviour that went away the >>next time I did a full fsck. > > > I don't think this is really possible. > > I went looking for a generic "application use" CMOS are for this > sort of thing a while back, and I was unable to find one. > Well you should please take a look at the "fast boot" option of moderately modern BIOS-es. Somthing along those lines went right now in to the linux kernel. Seems pretty adequate to me, since you would be even able to controll it through the BIOS setup... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3DE2AF65.9000502>