From owner-freebsd-current@FreeBSD.ORG Fri Mar 28 16:22:53 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DE57C37B401; Fri, 28 Mar 2003 16:22:53 -0800 (PST) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3369643FBD; Fri, 28 Mar 2003 16:22:53 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.12.8/8.12.8) with SMTP id h2T0MljK013507; Fri, 28 Mar 2003 19:22:47 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Fri, 28 Mar 2003 19:22:46 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Sean Chittenden In-Reply-To: <20030328235106.GA10799@perrin.int.nxad.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@FreeBSD.org Subject: Re: init not loading? why? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Mar 2003 00:22:55 -0000 On Fri, 28 Mar 2003, Sean Chittenden wrote: > > > Ah! Figured it out after reading through init's src: /dev didn't > > > exist therefore the machine wouldn't start. No good. I may find > > > a place to stick this got'cha in the docs or add an mkdir() call > > > to init. > > > > mkdir(2) on / is not going to work if / is readonly. The kernel > > actually tries to do a vop_mkdir() already, I think. The eventual > > solution is probably a rootfs (blaim mux). > > Well, I haven't tested this, but I think you're right that it's nmount() > that's failing and the lack of a check on it's return value. I haven't > tested this beyond compiling it, but I suspect it'll work and fix this > corner case. -sc Per our out-of-band conversation, it looks like this won't work because of a lack of /dev. It seems like the most reasonable solution is to generate a kernel warning message if the kernel-side devfs mount attempt fails. If we cause init to fail, the kernel will panic, and I can't quite decide if (a) the system hanging, or (b) the kernel panicking is a better answer. :-) Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories