From owner-freebsd-current Fri Dec 24 2:59:45 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 D554015197 for ; Fri, 24 Dec 1999 02:58:59 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from gosset.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 24 Dec 1999 10:58:58 +0000 (GMT) To: Poul-Henning Kamp Cc: freebsd-current@FreeBSD.ORG, iedowse@maths.tcd.ie Subject: Re: fsck not cleaning on first try In-reply-to: Your message of "Thu, 23 Dec 1999 12:35:31 +0100." <24807.945948931@critter.freebsd.dk> X-Request-Do: Date: Fri, 24 Dec 1999 10:58:58 +0000 From: David Malone Message-ID: <199912241058.aa42494@salmon.maths.tcd.ie> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > So running > > ls -l /dev | grep '^b' > > gives no output ? Appologies - I must have cocked up. I can't tell what devices I had there, but there must have been some block devices left. I'd guess I accidently ran "./MAKEDEV all" twice instead of "./MAKEDEV *", (either that or I had some files with really weird names in /dev). I checked out a copy of MAKEDEV from September and experimented a bit. I made all the devices I use usually and tried "MAKEDEV *". This resulted in most, but not all of the block devices being replaced. Then doing a "MAKEDEV all" with the new MAKEDEV seemed to leave me with only od and ft block devices - which sounds about right. Should fsck be changed to set the hotroot flag if the block device is given? Failing to boot only in the case where the root filesystem is dirty is a failure people are likely to miss when testing after an upgrade. (Even if they deserve everything they get for not updating their /dev correctly ;-) David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message