From owner-freebsd-current Sat Dec 25 14:17: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 9101214D72 for ; Sat, 25 Dec 1999 14:17:03 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 25 Dec 1999 22:17:02 +0000 (GMT) Date: Sat, 25 Dec 1999 22:17:02 +0000 From: David Malone To: Poul-Henning Kamp Cc: freebsd-current@FreeBSD.ORG, iedowse@maths.tcd.ie Subject: Re: fsck not cleaning on first try Message-ID: <19991225221702.A39844@walton.maths.tcd.ie> References: <199912241058.aa42494@salmon.maths.tcd.ie> <30130.946066441@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <30130.946066441@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 24, 1999 at 09:14:01PM +0100, Poul-Henning Kamp wrote: > In message <199912241058.aa42494@salmon.maths.tcd.ie>, David Malone writes: > > >Should fsck be changed to set the hotroot flag if the block device > >is given? > > I deliberately didn't do this for several reasons: > > 1. It would need to know the bmajor -> cmajor translation table. > > 2. we need some carrot/stick to get people to update their /dev. Might it be better to make it fix the filesystem, but always return failure if it found a block device. That way it fails too boot after you upgrade and not some weeks later when you don't expect it. POLA and all that. I guess printing/logging a message would be another option. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message