From owner-freebsd-current Wed Mar 17 20:40:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 49A821516C for ; Wed, 17 Mar 1999 20:40:40 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.3/8.8.5) id VAA36978; Wed, 17 Mar 1999 21:40:07 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199903180440.VAA36978@panzer.plutotech.com> Subject: Re: How to add a new bootdevice to the new boot code ??? In-Reply-To: <19990317192545.A41444@relay.nuxi.com> from "David O'Brien" at "Mar 17, 1999 7:25:45 pm" To: obrien@NUXI.com Date: Wed, 17 Mar 1999 21:40:07 -0700 (MST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David O'Brien wrote... > > And it's not like anyone had to upgrade their fstab -- all of the sd > > devices still work, since the major number is the same. So there's not > > a lot of room for complaint here. > > Only if sysinstall goes back to creating the /dev/sd* devices and > matching fstab w/``sd''. What does that have to do anything? If sysinstall is doing the work, the user doesn't have to. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message