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
