From owner-freebsd-small Mon Mar 20 16:59:55 2000 Delivered-To: freebsd-small@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 15ED237BC18 for ; Mon, 20 Mar 2000 16:59:48 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id RAA04271; Mon, 20 Mar 2000 17:02:03 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003210102.RAA04271@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: chad@DCFinc.com Cc: Ctdm1@brisbane.qld.gov.au (David Elkin), freebsd-small@FreeBSD.ORG Subject: Re: M-systems DiskOnChip In-reply-to: Your message of "Mon, 20 Mar 2000 16:22:23 MST." <200003202322.QAA13417@freeway.dcfinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 20 Mar 2000 17:02:03 -0800 From: Mike Smith Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The "kernel" config option in the config file seems to be being > ignored, and I can't grok the disk naming conventions in > /boot/loader.rc for the "rootdev" variable. It won't help, unfortunately. > So we get as far as the kernel trying to change root to wd0a and > panicing. > > I'll bet this is easy for someone who's done it. And not to hard for > someone who knows his way completely around the 3.4 boot mechanisms. 3.x is a little too stupid when it comes to finding the root device. If at all possible, I'd recommend using 4.0. If you can't, you'll need to hack the loader or bootblocks up to supply a correct major device number for the root device. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message