Date: Thu, 21 Mar 1996 10:56:31 -0800 (PST) From: "Rodney W. Grimes" <rgrimes@GndRsh.aac.dev.com> To: scrappy@ki.net (Marc G. Fournier) Cc: current@FreeBSD.org Subject: Re: DEVFS vs "regular /dev" Message-ID: <199603211856.KAA24142@GndRsh.aac.dev.com> In-Reply-To: <Pine.BSF.3.91.960321134250.29201C-100000@ki.net> from "Marc G. Fournier" at Mar 21, 96 01:45:30 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > On Thu, 21 Mar 1996, Rodney W. Grimes wrote: > > > rm /dev/log > > rm /dev/klog > > Since I don't really want to find out I'm wrong by actually > testing this...but so far as I can tell, /dev/log and /dev/klog are used > by syslogd only. > > When I started doing the modifications to the devfs code, /dev/klog > wasn't being created, yet the system was booting up to a login prompt without > any problems. As well, /dev/log itself was being created as a device instead > of as a socket, again causing syslogd to not run, but not seeming to affect > anything else. 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. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199603211856.KAA24142>