From owner-freebsd-current Sun Dec 5 18: 6:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from cypherpunks.ai (cypherpunks.ai [209.88.68.47]) by hub.freebsd.org (Postfix) with ESMTP id 96C8214E16; Sun, 5 Dec 1999 18:06:12 -0800 (PST) (envelope-from jeroen@vangelderen.org) Received: from vangelderen.org (cc.publicdata.com.ai [209.88.68.29]) by cypherpunks.ai (Postfix) with ESMTP id 00D353B; Sun, 5 Dec 1999 22:06:10 -0400 (AST) Message-ID: <384B19D9.E77F7E21@vangelderen.org> Date: Sun, 05 Dec 1999 22:05:13 -0400 From: "Jeroen C. van Gelderen" X-Mailer: Mozilla 4.61 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: David Malone Cc: Warner Losh , current@FreeBSD.ORG, phk@FreeBSD.ORG Subject: Re: Should UPDATING tell you to rerun MAKEDEV now? References: <199912051813.aa78561@salmon.maths.tcd.ie> <199912052118.OAA29838@harmony.village.org> <19991205221941.A27611@walton.maths.tcd.ie> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Malone wrote: > I just had the same problem as someone else on the list where I > booted after a make world and new kernel, and then fsck reported > the filesystems clean but mount said they were dirty. I booted > from the old kernel, installed and ran the new MAKEDEV and the > new kernel ran fine. This is on a 386. Being the other person, I basically had the same problem. I had run MAKEDEV but an IDE disk did go bad which caused a crash which caused /dev corruption which caused the problem I posted... > Phk just recommended running MAKEDEV to the othe person with this > problem. I had to boot a kernel and /dev off a floppy to fix the /dev. Cheers, Jeroen -- Jeroen C. van Gelderen - jeroen@vangelderen.org Interesting read: http://www.vcnet.com/bms/ JLF To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message