From owner-freebsd-current Sat Aug 21 13:35:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 7837814C17 for ; Sat, 21 Aug 1999 13:35:47 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id WAA00478; Sat, 21 Aug 1999 22:32:25 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Mike Smith Cc: Soren Schmidt , geoffr@is.co.za, brian@pobox.com, current@FreeBSD.ORG Subject: Re: ATA - Trouble mounting secondary master In-reply-to: Your message of "Sat, 21 Aug 1999 13:14:43 PDT." <199908212014.NAA00959@dingo.cdrom.com> Date: Sat, 21 Aug 1999 22:32:25 +0200 Message-ID: <476.935267545@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199908212014.NAA00959@dingo.cdrom.com>, Mike Smith writes: >> So I still stick with my statement that the -current bootblocks/loader >> doesn't have the computrons needed to use the ad device (or any non >> wd/da/fd device for that matter) for anything usefull :) > >The loader is fine; the problem is just that Poul never finished fixing >the mountroot code. All the loader does is read /etc/fstab and pass in >the entry for /. It's up to the kernel to work it out from there, and >that's where it's falling down. Excuse me! I fixed boot -a, and you came rushing in and said that the boot code could use the same thing, so obviously I expected you to do that, since the boot code is your baby... I don't even know where to look for the cookies left by the bootcode... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message