From owner-freebsd-current Sat Oct 27 2:41: 6 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 AE34837B401 for ; Sat, 27 Oct 2001 02:41:04 -0700 (PDT) Received: (qmail 92324 invoked by uid 1000); 27 Oct 2001 09:41:04 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 27 Oct 2001 09:41:04 -0000 Date: Sat, 27 Oct 2001 04:41:04 -0500 (CDT) From: Mike Silbersack To: Poul-Henning Kamp Cc: Subject: Re: devfs question In-Reply-To: <12047.1004175127@critter.freebsd.dk> Message-ID: <20011027043704.F88536-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: > >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 I'm in over my head on this one; I really don't know anything about the boot process. Having init die if there's no /dev sounds acceptable to me. After all, if there's no /dev, the system looks like it's in trouble. (If this does not make sense, reference above paragraph.) Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message