From owner-freebsd-current Wed Mar 17 12:57: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from ceia.nordier.com (m2-2-dbn.dial-up.net [196.34.155.66]) by hub.freebsd.org (Postfix) with ESMTP id CE99714D38 for ; Wed, 17 Mar 1999 12:56:06 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id WAA01481; Wed, 17 Mar 1999 22:50:29 +0200 (SAT) From: Robert Nordier Message-Id: <199903172050.WAA01481@ceia.nordier.com> Subject: Re: How to add a new bootdevice to the new boot code ??? In-Reply-To: <36F000B5.E87D2BF3@newsguy.com> from "Daniel C. Sobral" at "Mar 18, 99 04:21:25 am" To: dcs@newsguy.com (Daniel C. Sobral) Date: Wed, 17 Mar 1999 22:50:27 +0200 (SAT) Cc: sos@freebsd.dk, rnordier@nordier.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (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 Daniel C. Sobral wrote: > "Søren Schmidt" wrote: > > > 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 :) > > Ok, I have a clue... bootdev can be different from rootdev. I don't > know where this makes a difference, but it makes... :-) In loader, you can have a default device (currdev), but load from a different device (loaddev) and pass a third device to the kernel (rootdev). In the simple case of booting from ad0, all the default settings would be correct, though. > Also, make sure you don't have any root_disk_unit or num_ide_disks > set. A num_ide_disks setting is used only where the major# indicates a SCSI device, so it wouldn't affect things. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message