From owner-freebsd-current Mon Jan 4 21:14:57 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA29390 for freebsd-current-outgoing; Mon, 4 Jan 1999 21:14:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles182.castles.com [208.214.165.182]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA29385 for ; Mon, 4 Jan 1999 21:14:54 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id VAA00479; Mon, 4 Jan 1999 21:11:30 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901050511.VAA00479@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: rsss@melbpc.org.au cc: current@FreeBSD.ORG Subject: Re: Panic: Changing default root with the elf loader/kernel In-reply-to: Your message of "Tue, 05 Jan 1999 01:15:40 GMT." <369166ce.6856128@smtp.melbpc.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 04 Jan 1999 21:11:29 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Following the helpful discussions recently, I converted my > recent 3.0 kernel which I thought was elf (but in fact was > aout) to genuine elf. Installed the boot loader OK as per > Robert Nordier's helpful instructions and booted the > kernel. > > Now one big problem, the boot disk is in fact the 2nd scsi > disk (da1) (as well as an IDE disk). It boots OK from what > in fact is the 3rd disk, but root always defaults back to > the first scsi (da0) and of course the kernel panics when it > can't find root. > > The perturbation which resulted in a default root change > with the aout loader/kernel, 2:da(1,a)kernel, is rejected > by the new loader. > > So to avoid a panic with the system and myself (as presently > I can't run the elf kenel), how does one change the default > root with the new loader. Even better, how does one save > this information so it boots automatically and does not > require manual input. Start by breaking to the loader commandline, and say set num_ide_disks=1 boot You may need: set currdev=disk3s1a: if it hasn't already set the current device correctly. Please let me know how you go with this; I don't have such a senario to test with at the moment, but will definitely do whatever is required to make it work properly. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message