From owner-freebsd-current Sun Aug 27 12:35:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 89F8C37B422; Sun, 27 Aug 2000 12:35:31 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e7RJZQN02015; Sun, 27 Aug 2000 21:35:26 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: gjohnson@gs.verio.net Cc: current@FreeBSD.ORG, questions@FreeBSD.ORG Subject: Re: devfs In-Reply-To: Your message of "Sun, 27 Aug 2000 14:32:19 CDT." <39A96CC3.F47414B4@gs.verio.net> Date: Sun, 27 Aug 2000 21:35:26 +0200 Message-ID: <2013.967404926@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <39A96CC3.F47414B4@gs.verio.net>, Tony Johnson writes: >I'm sure you know this already, but I just want to reiterate. I have >done a make world on Fridays and Saturday's Freebsd 5.0-CURRENT. I did >a cvsup in the "wee" hours in the morning. I then did make world in >/usr/src to rebuild the system, rebuild kernel, and mergemaster -sv. >The system should be clean. Correct me if I am wrong. If I put "option >DEVFS" in my kernel , build/install that kernel, my computer will not >bot up completely. I will have to enter single user with an errr >message stating "/dev: no such file or directory" Mounting of fstab >filesystems fails. press enter for /bin/sh > >My /dev directory exists. Once I rebuild the kernel with no DEVFS it >all works, but I like devfs as it makes all the device files that i need >for my sound card as an example. Do you have devfs in /etc/fstab ? That is *not* needed, /sbin/init will mount devfs on /dev automatically. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message