From owner-freebsd-current Wed Nov 11 14:35:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA11742 for freebsd-current-outgoing; Wed, 11 Nov 1998 14:35:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles249.castles.com [208.214.165.249]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA11726 for ; Wed, 11 Nov 1998 14:35:37 -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 OAA05716; Wed, 11 Nov 1998 14:33:01 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811112233.OAA05716@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Kevin Street cc: Mike Smith , current@FreeBSD.ORG Subject: Re: boot loader problems with mix of wd and da In-reply-to: Your message of "Wed, 11 Nov 1998 17:28:43 EST." <13898.3995.612543.848374@kstreet.interlog.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 11 Nov 1998 14:33:01 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mike Smith writes: > >This is the same as the old problem that required you to prefix a BIOS > >unit number offset to the 'sd' in the old loader. You need to > >explicitly set $rootdev: > > > > set rootdev=da0s2a > > In boot/boot.conf ? It does not help. The kernel still tries to > mount da2s2a as root. This is without anything in boot.config, so > hopefully it's not confused about the bios unit numbers. currdev is > disk3s2a, so it's correct. Oops, sorry, that should be: set rootdev=disk0s2a The syntax is stupid because this is a stupid problem that's very difficult to solve. > >> Why does /boot/loader confuse the kernel into thinking there's a da2 on > >> which it might find root? > >Because you haven't told it not to. > > well I tried shouting "Yo, kernel, please don't mount root from > devices we don't have" while it was booting, but this didn't seem to help > either :-> 8) The problem is that we don't have a unified disk naming space, so it's extremely difficult to discern that "disk2" in BIOS lingo is in fact "da0" when you go to pass it to the kernel. Probing is Bad and Evil and I didn't want to go that way. Maybe it's the only way to go though. 8( -- \\ 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