From owner-freebsd-current  Sat Mar 20 12:21:17 1999
Delivered-To: freebsd-current@freebsd.org
Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16])
	by hub.freebsd.org (Postfix) with ESMTP id B149314CE4
	for <current@FreeBSD.ORG>; Sat, 20 Mar 1999 12:21:15 -0800 (PST)
	(envelope-from crossd@cs.rpi.edu)
Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2])
	by cs.rpi.edu (8.9.1/8.9.1) with ESMTP id PAA08940;
	Sat, 20 Mar 1999 15:19:08 -0500 (EST)
Message-Id: <199903202019.PAA08940@cs.rpi.edu>
To: Mike Smith <mike@smith.net.au>
Cc: "Daniel C. Sobral" <dcs@newsguy.com>,
	=?iso-8859-1?Q?S=F8ren?= Schmidt <sos@freebsd.dk>,
	current@FreeBSD.ORG, crossd@cs.rpi.edu
Subject: Re: How to add a new bootdevice to the new boot code ??? 
In-Reply-To: Message from Mike Smith <mike@smith.net.au> 
   of "Sat, 20 Mar 1999 11:44:20 PST." <199903201944.LAA12569@dingo.cdrom.com> 
Date: Sat, 20 Mar 1999 15:19:07 -0500
From: "David E. Cross" <crossd@cs.rpi.edu>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


> > The major number passed to the kernel is a product of a lot of
> > guesswork, because the loader has simply not enough information. I
> > have added a bit of code to my version of loader so you can use the
> > variable root_device_major_number to override the major number to be
> > passed to the kernel. I'm inclined to commit it, but I expect strong
> > objections from Mike, who wants the right thing done before we go
> > too far with these hacks.
> 
> Correct.
> 
> I'm currently leaning heavily towards a tunable which can be set to 
> explicitly control the device the root filesystem is loaded from, eg.
> 
>  set kern.rootdev.device=da0s1a

How hard would it be to have /boot/loader get the major number from the
filesystem itself?  Just have it read the node entry for /dev/$rootdev
(or similiar).

--
David Cross


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