From owner-freebsd-alpha Sun Dec 30 17:36: 8 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id BCB1937B405 for ; Sun, 30 Dec 2001 17:36:03 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.3) with ESMTP id fBV1iKI01874; Sun, 30 Dec 2001 17:44:21 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200112310144.fBV1iKI01874@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: naddy@mips.inka.de (Christian Weisgerber) Cc: freebsd-alpha@freebsd.org Subject: Re: -CURRENT boot1 broken? In-reply-to: Your message of "Mon, 31 Dec 2001 00:50:20 GMT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 30 Dec 2001 17:44:20 -0800 From: Mike Smith Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > John Baldwin wrote: > > > > This suggests that boot1 is broken. > > > > Ugh, it shouldn't be. :( > > Well, I guess it isn't. When I moved my system to a new disk, I > created all filesystems with 16384/2048. Pretty useless for the > root filesystem, I admit, except for consistency's sake. Turns out > that boot1 doesn't handle this. Jumping through some hoops I have > moved / back to 8192/1024 and it works fine now. *Sigh* > > As a side effect of experimenting with various boot combinations, > I'm confused about where the different components are loaded from. > Experimental evidence suggests this: > > 1. At the SRM prompt, booting from a particular drive will load the > bootstrap (boot1) from there. > 2. boot1 proceeds to load /boot/loader from the same drive. You > can specify a different file name, but there appears to be no > way to qualify this with a drive. Phases 1 and 2 use SRM, which gives you an anonymous "device you booted from". This is why you can't eg. load drivers from floppy when booting from CDROM. > 3. loader pulls in the kernel from da0, even if booted from a > different drive. This isn't correct; the loader also uses SRM, and has no way of accessing anything other than "the device you booted from". > 4. The kernel mounts da0a as root device. > > I'm surprised by the step from any drive (1, 2) to the fixed(?) > assumption of da0 (3, 4). There is no way for the kernel to work out what "the device you booted from" was. The loader reads /etc/fstab and tells the kernel what it should mount / from based on the contents therof. I'm not sure what system you were using to get the results in 3 and 4 above, but I don't think it was FreeBSD. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message