From owner-freebsd-current Wed Mar 17 0: 5:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 500AF152B6 for ; Wed, 17 Mar 1999 00:05:42 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id JAA25289; Wed, 17 Mar 1999 09:05:00 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903170805.JAA25289@freebsd.dk> Subject: Re: How to add a new bootdevice to the new boot code ??? In-Reply-To: <199903162322.BAA07920@ceia.nordier.com> from Robert Nordier at "Mar 17, 1999 1:22:10 am" To: rnordier@nordier.com (Robert Nordier) Date: Wed, 17 Mar 1999 09:05:00 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Robert Nordier wrote: > If the problem is the bootblocks, why not send a message to Robert > Nordier, or if it's loader, to Mike Smith or Daniel Sobral? And > say, "This is what I want to do, what are we going to do about it?" > or something similar? OK, easy enough, this is what I want to do: Boot from an ata disk on major# 30, device name "ad", plain and simple. As the bootcode is now this wont work. If its as simple as me adding the pair 30 & "ad" somewhere, I'm satisfied, if not, I'm dissapointed :) -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message