Date: Mon, 12 Nov 2001 00:06:40 +0100 From: "Torfinn Ingolfsen" <torfinn.ingolfsen@oslo.online.no> To: freebsd-mobile@FreeBSD.ORG Subject: Re: Two FreeBSDs on same disk, booting secondary slice? Message-ID: <3BEF1290.2663.3F79F2@localhost> In-Reply-To: <20011111201007.F39804@shell.gsinet.sittig.org> References: <3BEE8243.1115.97AA66@localhost>; from torfinn.ingolfsen@oslo.online.no on Sun, Nov 11, 2001 at 01:50:59PM %2B0100
next in thread | previous in thread | raw e-mail | index | archive | help
> 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. > But I don't quite get how much of installation already happened on > your machine. Do you already have two FreeBSD systems on it? How Yes, I have. > did you get there? And if it's only one, how can you state that Easy ;) I already had FreeBSD 4.3-release installed on slice ad0s3. When I decided to try my "two-FreeBSDs-on-one-disk" scheme, I had FreeBSD-4.4-release on a CD. So I just installed that one. I had no problems what so ever in making sysinstall use ad0s4 to install on, even if ados3 was there. There is only one swap partition, but that's fine with me. > Do your normal installation (with the hiding mentioned above > between the two runs) and instruct the installer to *not* touch > the MBR. I take it LILO lives there or the standard (DOS?) MBR Lilo lives in the MBR, yes. > lives there and the Linux partition with LILO in it is the active > "partition". As soon as LILO has gotten control, you should be Actually, the first partition (Win2K) is the active one, but that doesn't matter. > FreeBSD's -STABLE or -CURRENT root fs (hda3 and hda4 in your Yes, I'm able to choose the one I would like to start. But, when the FreeBSD bootblock (boot0?) starts, it always loads the kernel from ad0s3, even when I boot from ad0s4. How do I know this? Easy, one kernel is 4.3-release, the other is 4.4-release. How do I *know* that I have 4.4 on ad0s4? Well, I press space to abort the loader, use 'set currdev=disk1s4a:' (or something like that), use 'unload', 'load kernel' and 'boot'. The only thing that remains is to automate this task, preferably in a way that don't require updating. > BTW: Many thanks to David Wolfskill whom I was discussing this > very topic with via PM back in April. I suggest you visit his > website for another description and many more BSD hints. I've already been there. ;-) Thanks for the hint. -- Torfinn Ingolfsen, Norway To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3BEF1290.2663.3F79F2>