From owner-freebsd-current Sat Oct 27 2:27:32 2001 Delivered-To: freebsd-current@freebsd.org Received: from silby.com (cb34181-a.mdsn1.wi.home.com [24.14.173.39]) by hub.freebsd.org (Postfix) with ESMTP id 5590237B401 for ; Sat, 27 Oct 2001 02:27:30 -0700 (PDT) Received: (qmail 92273 invoked by uid 1000); 27 Oct 2001 09:27:29 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 27 Oct 2001 09:27:29 -0000 Date: Sat, 27 Oct 2001 04:27:29 -0500 (CDT) From: Mike Silbersack To: Poul-Henning Kamp Cc: Subject: Re: devfs question In-Reply-To: <10460.1004168165@critter.freebsd.dk> Message-ID: <20011027042527.T88536-100000@achilles.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 27 Oct 2001, Poul-Henning Kamp wrote: > >Oops, error on my part; /proc does need to exist. So, I guess the > >question is this: Can devfs's error handling in the case of /dev being > >non-existant be improved? > > Barely, because without /dev, how do you plan to open the console ? > > Mkdir(/dev) isn't an option because the rootfs is mounted R/O. > > About the only thing one could do is make init exit(bla) and get > a diagnostic from the kernel. It may make sense to do that. An error message would be sufficient; my concern was that someone might run into this and spend hours trying to figure out which of X variables was the problem. Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message