From owner-freebsd-current Sun Mar 21 18:10: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles212.castles.com [208.214.165.212]) by hub.freebsd.org (Postfix) with ESMTP id 395861524D for ; Sun, 21 Mar 1999 18:10:06 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id SAA02358; Sun, 21 Mar 1999 18:03:52 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903220203.SAA02358@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Bruce Evans Cc: mike@smith.net.au, current@FreeBSD.ORG, dcs@newsguy.com Subject: Re: How to add a new bootdevice to the new boot code ??? In-reply-to: Your message of "Mon, 22 Mar 1999 12:46:17 +1100." <199903220146.MAA23082@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 21 Mar 1999 18:03:51 -0800 From: Mike Smith 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. Since this entire thread came about due to a device name change, and given that the last major upheaval in this domain was over a similar change, I'd say that was wishful thinking in the least. > 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. This presupposes that the configuration file is always right, ie. that it correctly describes the location of the disk. This isn't really a valid premise, and in any case does no better than to duplicate the 'last mounted on' field in the filesystem itself. I'm not sold, sorry. This isn't sufficiently automatable, nor does it remove the room for massive user error that I for one fear greatly. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message