Date: Mon, 25 Nov 2002 14:17:48 -0800 From: Kris Kennaway <kris@obsecurity.org> 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: <20021125221748.GA11747@rot13.obsecurity.org> In-Reply-To: <3DE29DE6.CDD96F3F@mindspring.com> 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
On Mon, Nov 25, 2002 at 02:02:14PM -0800, Terry Lambert wrote: > I don't think this is really possible. Yeah :( > If you made system dumps mandatory (or marked swap with a non-dump > header in case of panic), this still would not handle the "silent > reboot", "double panic", or "single panic with disk I/O trashed" > cases. 8-(. And the panics that affect the disk/filesystem are likely to not give a crashdump, but at the same time are likely to cause FS problems for bgfsck :-( Kris 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?20021125221748.GA11747>