From owner-freebsd-hackers Sun Jan 6 16:28:56 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id 36B4437B41E for ; Sun, 6 Jan 2002 16:28:54 -0800 (PST) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.11.3/8.10.1) with ESMTP id g070THa90714; Sun, 6 Jan 2002 16:29:17 -0800 (PST) Date: Sun, 6 Jan 2002 16:29:16 -0800 (PST) From: Doug White To: "Louis A. Mamakos" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: what slice did I boot from? In-Reply-To: <200201052337.g05NbY701185@whizzo.transsys.com> Message-ID: <20020106162811.Y90176-100000@resnet.uoregon.edu> X-All-Your-Base: are belong to us MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 5 Jan 2002, Louis A. Mamakos wrote: > Sorry, I wasn't clear. I don't have any explicit configuration in > my loader.conf; this is just the environment that the loader cooked > up all by itself. Each slice has it's own own loader along with a > complete root file system. Oops I didn't notice the kenv :) > > > It would be just fine to have the boot0 boot manager be the mechanism > > > to do all this. That's an easy toggle between the two alternatives, > > > though harder to do an automatic fallback, perhaps. > > > > You try boot0 ... that's where my problem showed up. One would boot but > > the other says "Invalid partition." This is a heavily hacked install > > though (since sysinstall won't let you put a second / into a second slice > > when a first FreeBSD slice already exists). > > What you might try is making sure that the other partition starts on > a cylinder boundary. I've noticed that the BIOS on some machines have > real heartburn when the slice starts at some random location not > coincident with a cylinder boundary. I don't know why, and I'm pretty > sure I don't want to know :=) That's a distinct possibility. I made it with sysinstall but I made the previous slice a wierd size (not a power of 2). sysinstall probably didn't quite justify it to the BIOS's want. I'll have to check the boot0 code though... Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message