From owner-freebsd-hackers Sat Jan 5 15:37:39 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id 4210E37B400 for ; Sat, 5 Jan 2002 15:37:36 -0800 (PST) Received: from whizzo.transsys.com (#6@localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.11.6/8.11.6) with ESMTP id g05NbY701185; Sat, 5 Jan 2002 18:37:34 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <200201052337.g05NbY701185@whizzo.transsys.com> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Doug White Cc: freebsd-hackers@FreeBSD.ORG X-Image-URL: http://www.transsys.com/louie/images/louie-mail.jpg From: "Louis A. Mamakos" Subject: Re: what slice did I boot from? References: <20020105105058.U5794-100000@resnet.uoregon.edu> In-reply-to: Your message of "Sat, 05 Jan 2002 10:52:34 PST." <20020105105058.U5794-100000@resnet.uoregon.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 05 Jan 2002 18:37:34 -0500 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: > > > Hmm.. I'm running a 4.4-STABLE based system on the hardware, and > > don't seem to have any problem booting off the other slice. Right > > now, it's runnong on the second slice of ATA Compact Flash disk: > > > > # kenv > > LINES="24" > > console="vidconsole" > > currdev="disk0s2a:" > > interpret="ok" > > kernel="/kernel" > > kernel_options="" > > kernelname="/kernel" > > loaddev="disk0s2a:" > > root_disk_unit="0" > > vfs.root.mountfrom="ufs:/dev/ad0s2a" > > # > > You're playing the same trick I am, just in more words :) Which slice is > loader.conf on? 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. > > 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 :=) louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message