From owner-freebsd-bugs  Mon Oct 26 01:30:08 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id BAA21653
          for freebsd-bugs-outgoing; Mon, 26 Oct 1998 01:30:08 -0800 (PST)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA21555;
          Mon, 26 Oct 1998 01:29:45 -0800 (PST)
          (envelope-from bde@FreeBSD.org)
From: Bruce Evans <bde@FreeBSD.ORG>
Received: (from bde@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id BAA21832;
	Mon, 26 Oct 1998 01:29:42 -0800 (PST)
Date: Mon, 26 Oct 1998 01:29:42 -0800 (PST)
Message-Id: <199810260929.BAA21832@freefall.freebsd.org>
To: cmetz@inner.net, bde@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG
Subject: Re: kern/8417
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Synopsis: 3.0 config(8) doesn't check that root fs device driver is present

State-Changed-From-To: open-suspended
State-Changed-By: bde
State-Changed-When: Mon Oct 26 01:24:35 PST 1998
State-Changed-Why: 
Mostly fixed, mostly in rev.1.167 of kern/vfs_subr.c.  Related null pointer
panics for non-root mounts fixed in all affected vfs's.

Not fixed in config(8).  It's hardly worth fixing there, since the root device
specified there is rarely used.  It's easier to [mis]configure the root device
at boot time and there is no way for the boot loader to check it.

A nonexistent root device now causes an obscure panic in vfs_mountrootfs()
instead of a null pointer panic.  Not fixed.  vfs_mountrootfs() should
prompt for the root device if none is found.

Not fixed in 2.2.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message