From owner-freebsd-current Sun Mar 21 18:25:43 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 03BE114BE9 for ; Sun, 21 Mar 1999 18:25:40 -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 NAA29947; Mon, 22 Mar 1999 13:25:20 +1100 Date: Mon, 22 Mar 1999 13:25:20 +1100 From: Bruce Evans Message-Id: <199903220225.NAA29947@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 >> >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. Driver name changes are implementation bugs. So are driver numbering changes. The latter are more serious, since you can't work around them by linking files in /dev if the new or old numbering is dynamic. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message