Date: Tue, 18 Sep 2007 09:54:01 -0400 From: "Andrey Shuvikov" <mr.hyro@gmail.com> To: freebsd-questions@freebsd.org Subject: Re: Multi BSD boot loader Message-ID: <24393ae80709180654v2822876al4517ce8a9dfd9c33@mail.gmail.com> In-Reply-To: <b87efac85973104a355a6d43ea1606b2@gmail.com> References: <b87efac85973104a355a6d43ea1606b2@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 9/18/07, Joshua Isom <jrisom@gmail.com> wrote: > I've brought back to life a P3 I got at a school auction years back to > use for testing software under various operating systems(presently all > bsd) on i386. My main "server" is FreeBSD/amd64. The P3 has a 10 gig > hard drive I'm not intending to upgrade(unless I buy an sata hard drive > and find that the bootloader works for atapi sata hard drives in 7.0). > I've currently partitioned it into four partitions, with FreeBSD, > OpenBSD, and DragonFlyBSD. The fourth is unused at the moment, and I > left it open for a fourth system to test on, but I partitioned it as > "FreeBSD". Here comes the problem. The boot menu currently looks like > this. > > F1: FreeBSD > F2: BSD > F3: FreeBSD > F4: FreeBSD > Based on my experience FreeBSD loader (slice boot-sector) tries to load the system from the first FreeBSD (A5) slice it can find. So even is you press F3 you will load FreeBSD rather than DragonFlyBSD. I resolved this issue by installing GRUB and temporarily changing the slice type of the slices I didn't want to boot from. In addition you can edit menu.lst before rebooting to specify which entry should be booted next.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?24393ae80709180654v2822876al4517ce8a9dfd9c33>