From owner-freebsd-current Wed Mar 17 11:13:38 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 0D49B14D10 for ; Wed, 17 Mar 1999 11:13:35 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id UAA26701; Wed, 17 Mar 1999 20:13:01 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199903171913.UAA26701@freebsd.dk> Subject: Re: How to add a new bootdevice to the new boot code ??? In-Reply-To: <36EFF139.7F2E3AD7@newsguy.com> from "Daniel C. Sobral" at "Mar 18, 1999 3:15:21 am" To: dcs@newsguy.com (Daniel C. Sobral) Date: Wed, 17 Mar 1999 20:13:01 +0100 (CET) Cc: rnordier@nordier.com, 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 Daniel C. Sobral wrote: > "Søren Schmidt" wrote: > > > > Well, that breaks somewhere else, as the mount code is clever enough > > to look at the name of the driver in this case "ad" which doesn't > > match the specified #0 ie "wd". > > I kindof tried this by having my driver put itself in both the > > wd & ad majors in the table, but that doesn't work, because the mount > > stuff gets confused on the root name somehow, and fails to mount > > root because the names dont match... > > I know you most certainly could not possibly have forgotten that, > but it's the kind of thing that just *must* be mentioned... > /etc/fstab? Nope thats not it, been there too :) -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message