Date: Tue, 2 Jul 2002 00:23:16 -0400 (EDT) From: Andrew Gallatin <gallatin@cs.duke.edu> To: Chan Tur Wei <twchan@singnet.com.sg> Cc: freebsd-hackers@freebsd.org Subject: Re: dual booting current/stable on x86? Message-ID: <15649.10932.4485.446071@grasshopper.cs.duke.edu> In-Reply-To: <20020702080738.Q19609-100000@zaapth.twnet.org> References: <15648.54278.323659.18641@grasshopper.cs.duke.edu> <20020702080738.Q19609-100000@zaapth.twnet.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15649.10932.4485.446071>