From owner-freebsd-current Fri Mar 19 14:34:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (Postfix) with ESMTP id 94A4615CBD for ; Fri, 19 Mar 1999 14:34:40 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id PAA15884; Fri, 19 Mar 1999 15:24:55 -0700 (MST) Date: Fri, 19 Mar 1999 15:24:55 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199903192224.PAA15884@narnia.plutotech.com> To: Robert Nordier Cc: current@FreeBSD.org Subject: Re: How to add a new bootdevice to the new boot code ??? X-Newsgroups: pluto.freebsd.current In-Reply-To: <199903171103.NAA13749@ceia.nordier.com> User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/4.0-CURRENT (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199903171103.NAA13749@ceia.nordier.com> you wrote: > Søren Schmidt wrote: > >> OK, easy enough, this is what I want to do: >> >> Boot from an ata disk on major# 30, device name "ad", plain and simple. > > I'd be inclined to handle this outside the boot code, by treating the > passed in major# as describing the device rather than specifying > the driver. Why not have the boot blocks pass in a device 'name' rather than a major number. If the goal is to ditch major numbers entirely with a properly working DEVFS, then using major numbers in the new boot loader seems to be the wrong way to go. Until DEVFS is a reality, the kernel will still need to perform a name to major number translation, but it should be left up to the kernel. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message