This is an issue with how GRUB deals with a FUBAR BIOS, and not
necessarily a core GRUB design flaw.
Syslinux, seems to win hands down (IMO) when it comes to dealing with
flacky BIOS's, but it's not because it's a dynamic loading design; it's
because HPA knew enough and spent the time refining that 1% of the
program that deals with bad BIOSes.
Should HPA and Werner take a day of their time to review and
correct GRUB, I'm sure this issue would vanish overnight.
> Lilo has the virtue that its extremely
> simple in what it does and how it does it. It works in a suprisingly large
> number of cases and can handle interesting setups that GRUB really
> struggles with.
Where GRUB struggles LILO throws up brickwalls.
Coolest thing is the world you can do with grub:
Load a *partition* as your initrd
With this in mind it makes using images/archives for initrd for
non-embedded systems seem rather clunky. It's much cleaner
to just have an 8/16/32MB partition you dedicate to initrd. Users of
GRUB have been able to do this for YEARS.
And something to say here: Yes I hate lilo, but not because I think
Werner coded it lousy. A boot loader that uses a static block offset
to find it's target is a bad idea, that should have died with M$-DOS.
That said, it's still a wonder to me why GRUB, or another loader similar
in approach, was not adopted as the 'prefered' linux loader years ago.
-- The time is now 22:54 (Totalitarian) - http://www.ccops.org/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to firstname.lastname@example.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/