From owner-freebsd-current Sat Oct 27 2:32:45 2001 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 8C99D37B407 for ; Sat, 27 Oct 2001 02:32:42 -0700 (PDT) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id f9R9W7S12049; Sat, 27 Oct 2001 11:32:07 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Mike Silbersack Cc: current@FreeBSD.ORG Subject: Re: devfs question In-Reply-To: Your message of "Sat, 27 Oct 2001 04:27:29 CDT." <20011027042527.T88536-100000@achilles.silby.com> Date: Sat, 27 Oct 2001 11:32:07 +0200 Message-ID: <12047.1004175127@critter.freebsd.dk> From: Poul-Henning Kamp 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 In message <20011027042527.T88536-100000@achilles.silby.com>, Mike Silbersack w rites: > >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. Right, but the only way to get an error message is to let /sbin/init die and have the kernel print the message. /sbin/init cannot print the message when there is no "/dev/console" can it ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | 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