From owner-freebsd-current Wed May 12 1:25:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from peedub.muc.de (newpc.muc.ditec.de [194.120.126.33]) by hub.freebsd.org (Postfix) with ESMTP id 8E0FB14C12 for ; Wed, 12 May 1999 01:25:27 -0700 (PDT) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.3/8.6.9) with ESMTP id KAA03627; Wed, 12 May 1999 10:23:01 +0200 (CEST) Message-Id: <199905120823.KAA03627@peedub.muc.de> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith Cc: freebsd-current@freebsd.org Subject: Re: the new config and booting Reply-To: Gary Jennejohn In-reply-to: Your message of "Wed, 12 May 1999 03:09:51 +0200." <199905120109.SAA02741@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 12 May 1999 10:23:01 +0200 From: Gary Jennejohn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith writes: >> I switched to the new config(8) today, where the ``config kernel root on..'' >> line is no longer tolerated in the config file. >> >> I now have to ``boot -r'' to avoid a `can't mount root' panic. This wasn't >> necessary before. >> >> I know I can probably put something into /boot/ to automate this. >> Just thought I'd report my (negative) experience. > >Can you tell us what it's trying to mount vs. what it should be >mounting? > >I'm in the process of rewriting parts of this code again to fix the >mess that's been made of it. I'm not sure I'll get all the way, but in >conjunction with some small changes in the loader it *should* make >problems like yours history. > Sorry, all I see is the panic message. As I wrote in another mail, the loader sees the floppy as DISK A and the SCSI disk as DISK B. But then again, it saw that before. Since I'm leaving shortly on a trip and won't be back for 2 weeks I won't be able to pursue this further. --- Gary Jennejohn Home - garyj@muc.de Work - garyj@fkr.dec.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message