From owner-freebsd-mobile Mon Nov 12 8: 8:40 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from mail5.speakeasy.net (mail5.speakeasy.net [216.254.0.205]) by hub.freebsd.org (Postfix) with ESMTP id 93DA137B416 for ; Mon, 12 Nov 2001 08:08:37 -0800 (PST) Received: (qmail 22301 invoked from network); 12 Nov 2001 16:08:35 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([64.81.54.73]) (envelope-sender ) by mail5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 12 Nov 2001 16:08:35 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3BEF1290.2663.3F79F2@localhost> Date: Mon, 12 Nov 2001 08:08:33 -0800 (PST) From: John Baldwin To: Torfinn Ingolfsen Subject: Re: Two FreeBSDs on same disk, booting secondary slice? Cc: freebsd-mobile@FreeBSD.ORG Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On 11-Nov-01 Torfinn Ingolfsen wrote: >> No, neither did I experience this just like David never did. :) You >> might be tricked into thinking this when sysinstall's disk editor >> prevents you from creating two root partitions. > > sysinstall wasn't a problem, see below. > >> I can understand your reasons (self chosen labels, additional >> parameters - for those kernels to understand them - plus boot >> menus with cursor navigation and maybe even graphics screens if >> you feel like it). > > My main point is that I can have lilo always boot the same partition > as default. And of course, that I can use it to boot Linux. boot0 can boot Linux, but it is the 'same by default' problem that is killing you here. If you used that feature with boot0, this would break as well. The problem is that when boot1 is loaded, it has no idea where it was loaded from, so it has to have a way of finding the slice it came from. As I explained earlier, we use the active slice over other slices to help in the case of multiple FreeBSD slices. However, LILO and boot0 both use the active slice as their default slice, so for the default slice to always be the same, it has to not change the active slice in teh MBR when it boots. Thus the bootblocks have no way of knowing which slice was booted. If you turn off the 'same by default' feature then this will work fine. If you know Forth, you can write a Forth function and put it in /boot/loader.rc that does the work of switching to the 44 slice and call it boot44 or some such to make this easier. The other question is why you are putting 4.3 and 4.4 on separate slices. Why not just go with 4.4? That's about like trying to run Windows 95 and Windows 98 on the system in two different partitions. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message