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
