From owner-freebsd-current Thu Mar 21 11:13:23 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA19439 for current-outgoing; Thu, 21 Mar 1996 11:13:23 -0800 (PST) Received: from ki.net (root@ki.net [142.77.249.8]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id LAA19431 for ; Thu, 21 Mar 1996 11:13:10 -0800 (PST) Received: (from scrappy@localhost) by ki.net (8.7.4/8.7.4) id OAA00208; Thu, 21 Mar 1996 14:12:45 -0500 (EST) Date: Thu, 21 Mar 1996 14:12:44 -0500 (EST) From: "Marc G. Fournier" To: "Rodney W. Grimes" cc: current@FreeBSD.org Subject: Re: DEVFS vs "regular /dev" In-Reply-To: <199603211856.KAA24142@GndRsh.aac.dev.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 21 Mar 1996, Rodney W. Grimes wrote: > These problems may have been corrected. I do know for certain that certain > /dev/ entries missing causes the system to hang very early in init, and you > can not even get up single user to fix it. This _needs_ fixed badly, you > should be able to > rm -r /dev > reboot > and get the system up single user, if not you have a chicken and egg > problem as to how to repair a damaged or loss /dev tree. > That's what got me started playing with the DEVFS code. I figured I'd try to boot the system using devfs instead of the "normal /dev", and found that /dev/ttyv* wasn't being created, so I couldn't login. I've got my system now to the point that I could do 'rm -r /dev' and be able to book without any problems. Marc G. Fournier | POP Mail Telnet Acct DNS Hosting System | WWW Services Database Services | Knowledge, Administrator | | Information and scrappy@ki.net | WWW: http://www.ki.net | Communications, Inc