Date: Thu, 21 Mar 1996 10:17:54 -0600 (CST) From: Joe Greco <jgreco@brasil.moneng.mei.com> To: davidg@root.com Cc: phk@critter.tfs.com, terry@lambert.org, julian@ref.tfs.com, scrappy@ki.net, current@FreeBSD.org Subject: Re: DEVFS vs "regular /dev" Message-ID: <199603211618.KAA02588@brasil.moneng.mei.com> In-Reply-To: <199603211331.FAA05288@Root.COM> from "David Greenman" at Mar 21, 96 05:31:11 am
next in thread | previous in thread | raw e-mail | index | archive | help
> If we do the mount in /sbin/init and it fails for some reason (like the > mount point doesn't exist), then we'll have no way to inform the operator > (there isn't a /dev/console to write to). If we do it in the kernel, we can > emit a message saying "/dev: not found" or something. They just got through arguing this in NetBSD's port-sun3 list (folks tend to forget to do the MAKEDEV every once in a while). It would seem to me that a little "special handling" for init would not be so bad, i.e. pass init file descriptors 0, 1, and 2 already pointing at the console, so that the console does not have to be accessible via the filesystem immediately. I know that there is some "ugh" associated with this, but it would seem the most robust method to provide USEFUL error trapping and reporting. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/546-7968
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199603211618.KAA02588>