From owner-freebsd-current  Sun Mar 21 17:47: 8 1999
Delivered-To: freebsd-current@freebsd.org
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9])
	by hub.freebsd.org (Postfix) with ESMTP id 7A7BD14BCD
	for <current@FreeBSD.ORG>; Sun, 21 Mar 1999 17:46:39 -0800 (PST)
	(envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id MAA23082;
	Mon, 22 Mar 1999 12:46:17 +1100
Date: Mon, 22 Mar 1999 12:46:17 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199903220146.MAA23082@godzilla.zeta.org.au>
To: bde@zeta.org.au, mike@smith.net.au
Subject: Re: How to add a new bootdevice to the new boot code ???
Cc: current@FreeBSD.ORG, dcs@newsguy.com
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>> >> I pass "foo" from 1:foo(2s1a)kernel in my version of the old boot blocks.
>> >
>> >And you determine "foo" how?
>> 
>> I type it into the config file or the command line.
>
>And you submit that this is an acceptable solution?

Of course.  The FreeBSD device name won't change (modulo implementation
bugs), and even when it does, changing the config file is easier than
changing /etc/fstab.

Note that there is, or should be, no problem here with the BIOS drive
number.  My example has "1:" in it to switch from the default BIOS
drive of hard disk 0.  The boot blocks should read the config file on
the new drive[,slice,partition] to determine the FreeBSD device name
(drive and unit number, but not slice or partition).  Leave out "1:"
from my example.  Then booting will not be affected by changes in the
BIOS drive number.

Bruce


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