Re: dual booting current/stable on x86?
> As far as I know, Grub is one of the best bootloaders around. It supports > IBM JFS (OS/2 and Linux version), ReiserFS, Ext3, Ext2FS, and UFS. > it does not do PXE. danny To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: dual booting current/stable on x86?
Chan Tur Wei writes: > So unless someone specifically sets the active partition, the 1st FreeBSD > one, usually -stable, will get loaded. Since boot1+boot2 is loaded by the > partition boot boot0, or the standard DOS boot (or, even MS's multi boot > selector), the above may cause the 2nd FreeBSD slice to never get loaded. > > Incidentally, our booteasy (boot0.s) is one such someone. Maybe if lilo > or liloboot does the same thing, it will work too. Yep, it turns out that you can make lilo set a partition active and/or deactivate a partition via lilo's "change" keyword: other = /dev/hde2 label=stable alias=s table=/dev/hde loader=/boot/chain.b change partition=/dev/hde2 activate partition=/dev/hde3 deactivate other = /dev/hde3 label=current alias=c table=/dev/hde loader=/boot/chain.b change partition=/dev/hde3 activate partition=/dev/hde2 deactivate Thanks again for the pointer; I'm now booting directly to -current. Perhaps this should be a FAQ entry.. Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: dual booting current/stable on x86?
Chan Tur Wei writes: > > I'm not sure how booting with lilo will work (never played with it). > > Instead, I dug around a bit previously, and I found that boot1.s reads: > # > # If we are on a hard drive, then load the MBR and look for the first > # FreeBSD slice. We use the fake partition entry below that points to > # the MBR when we call nread. The first pass looks for the first active > # FreeBSD slice. The second pass looks for the first non-active FreeBSD > # slice if the first one fails. > # > > So unless someone specifically sets the active partition, the 1st FreeBSD > one, usually -stable, will get loaded. Since boot1+boot2 is loaded by the > partition boot boot0, or the standard DOS boot (or, even MS's multi boot > selector), the above may cause the 2nd FreeBSD slice to never get loaded. > > Incidentally, our booteasy (boot0.s) is one such someone. Maybe if lilo > or liloboot does the same thing, it will work too. Excellent. Thanks for the pointer. Now I at least have some understanding of what's happening. Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: dual booting current/stable on x86?
On Mon, 1 Jul 2002, Andrew Gallatin wrote: > Date: Mon, 1 Jul 2002 18:13:26 -0400 (EDT) > From: Andrew Gallatin <[EMAIL PROTECTED]> > To: Cyrille Lefevre <[EMAIL PROTECTED]> > Cc: [EMAIL PROTECTED] > Subject: Re: dual booting current/stable on x86? > > > Cyrille Lefevre writes: > > On Sun, Jun 30, 2002 at 09:23:22PM -0400, Andrew Gallatin wrote: > > > > > > How do I dual boot -current and -stable from different slices on the > > > same IDE disk? (and linux too.) > > > > > > When I tell lilo to boot "hde3", I get the -stable boot2 and > > > /boot/loader from "hde2" (ad4s2a). I can then monkey around setting > > > currdev and hints and unloading the -stable kernel & then boot > > > -current, but I'd like to just pop right into -current on ad4s3a if I > > > choose it. > > > > > > Is there a magic bullet? I'd like to continue using lilo so that I > > > can choose what OS to load via a serial console.. > > > > what is the problem w/ the following entries ? > > > > other=/dev/hde2 > > label=stable > > alias=s > > table=/dev/hde > > loader=/boot/chain.b > > other=/dev/hde3 > > label=current > > alias=c > > table=/dev/hde > > loader=/boot/chain.b > > > Just that it behaves exactly as described above -- they both boot > -stable. > > > what is the content of /boot/loader.conf and /boot/loader.conf.local > > for each FreeBSD ? > > /boot/loader.conf: > > -stable: > hw.ata.wc=1 > > -current: > console="comconsole" > > /boot/loader.conf.local is empty both places. > > > > > did you tryed grub which is far better than lilo :P > > > x86 bootloaders terrify me, so I have not tried grub. Does grub > understand reiserfs? > > > you could also take a look at /usr/share/examples/bootforth then > > have something like : > > > > /boot/stable.conf > > currdev="disk1s2a" > > rootdev="disk1s2a" > > > > /boot/current.conf > > currdev="disk1s3a" > > rootdev="disk1s3a" > > > > hope this help ? > > Thanks.. it did help. > > I just discovered liloboot. I may just hack myself together a custom > liloboot and forget about it. That seems to be the most > straightforward solution. > > Drew > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message > I'm not sure how booting with lilo will work (never played with it). Instead, I dug around a bit previously, and I found that boot1.s reads: # # If we are on a hard drive, then load the MBR and look for the first # FreeBSD slice. We use the fake partition entry below that points to # the MBR when we call nread. The first pass looks for the first active # FreeBSD slice. The second pass looks for the first non-active FreeBSD # slice if the first one fails. # So unless someone specifically sets the active partition, the 1st FreeBSD one, usually -stable, will get loaded. Since boot1+boot2 is loaded by the partition boot boot0, or the standard DOS boot (or, even MS's multi boot selector), the above may cause the 2nd FreeBSD slice to never get loaded. Incidentally, our booteasy (boot0.s) is one such someone. Maybe if lilo or liloboot does the same thing, it will work too. Regards -T.W.Chan- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: dual booting current/stable on x86?
: x86 bootloaders terrify me, so I have not tried grub. Does grub : understand reiserfs? --- Kip Macy <[EMAIL PROTECTED]> wrote: > Yes. If you had ever worked with the source to LILO it would terrify you > too. As far as I know, Grub is one of the best bootloaders around. It supports IBM JFS (OS/2 and Linux version), ReiserFS, Ext3, Ext2FS, and UFS. -- Hiten Pandya http://storm.uk.FreeBSD.org/~hiten Finger [EMAIL PROTECTED] for PGP public key -- 4FB9 C4A9 4925 CF97 9BF3 ADDA 861D 5DBD E4E3 03C3 msg35438/pgp0.pgp Description: PGP signature
Re: dual booting current/stable on x86?
Kip Macy writes: > > > > > > > x86 bootloaders terrify me, so I have not tried grub. Does grub > > understand reiserfs? > > Yes. If you had ever worked with the source to LILO it would terrify you too. Lilo is what initially terrified me.. ;-) Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: dual booting current/stable on x86?
> > > x86 bootloaders terrify me, so I have not tried grub. Does grub > understand reiserfs? Yes. If you had ever worked with the source to LILO it would terrify you too. -Kip To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: dual booting current/stable on x86?
Cyrille Lefevre writes: > On Sun, Jun 30, 2002 at 09:23:22PM -0400, Andrew Gallatin wrote: > > > > How do I dual boot -current and -stable from different slices on the > > same IDE disk? (and linux too.) > > > > When I tell lilo to boot "hde3", I get the -stable boot2 and > > /boot/loader from "hde2" (ad4s2a). I can then monkey around setting > > currdev and hints and unloading the -stable kernel & then boot > > -current, but I'd like to just pop right into -current on ad4s3a if I > > choose it. > > > > Is there a magic bullet? I'd like to continue using lilo so that I > > can choose what OS to load via a serial console.. > > what is the problem w/ the following entries ? > > other=/dev/hde2 > label=stable > alias=s > table=/dev/hde > loader=/boot/chain.b > other=/dev/hde3 > label=current > alias=c > table=/dev/hde > loader=/boot/chain.b Just that it behaves exactly as described above -- they both boot -stable. > what is the content of /boot/loader.conf and /boot/loader.conf.local > for each FreeBSD ? /boot/loader.conf: -stable: hw.ata.wc=1 -current: console="comconsole" /boot/loader.conf.local is empty both places. > did you tryed grub which is far better than lilo :P x86 bootloaders terrify me, so I have not tried grub. Does grub understand reiserfs? > you could also take a look at /usr/share/examples/bootforth then > have something like : > > /boot/stable.conf > currdev="disk1s2a" > rootdev="disk1s2a" > > /boot/current.conf > currdev="disk1s3a" > rootdev="disk1s3a" > > hope this help ? Thanks.. it did help. I just discovered liloboot. I may just hack myself together a custom liloboot and forget about it. That seems to be the most straightforward solution. Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: dual booting current/stable on x86?
On Sun, Jun 30, 2002 at 09:23:22PM -0400, Andrew Gallatin wrote: > > How do I dual boot -current and -stable from different slices on the > same IDE disk? (and linux too.) > > When I tell lilo to boot "hde3", I get the -stable boot2 and > /boot/loader from "hde2" (ad4s2a). I can then monkey around setting > currdev and hints and unloading the -stable kernel & then boot > -current, but I'd like to just pop right into -current on ad4s3a if I > choose it. > > Is there a magic bullet? I'd like to continue using lilo so that I > can choose what OS to load via a serial console.. what is the problem w/ the following entries ? other=/dev/hde2 label=stable alias=s table=/dev/hde loader=/boot/chain.b other=/dev/hde3 label=current alias=c table=/dev/hde loader=/boot/chain.b what is the content of /boot/loader.conf and /boot/loader.conf.local for each FreeBSD ? did you tryed grub which is far better than lilo :P you could also take a look at /usr/share/examples/bootforth then have something like : /boot/stable.conf currdev="disk1s2a" rootdev="disk1s2a" /boot/current.conf currdev="disk1s3a" rootdev="disk1s3a" hope this help ? Cyrille. -- Cyrille Lefevre mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
