grub leagcy about average open source code quality, however with "huge mess" I don't talk about source code quality, it's the config system.
legacy grub as *one* simple config. grub2 has such complicated config file that a script is needed to create it. That's a big step forward in the correct direction...
Posted Jun 12, 2011 22:02 UTC (Sun) by mjg59 (subscriber, #23239)
[Link]
grub leagcy about average open source code quality
Yeah, not really.
grub support?
Posted Jun 15, 2011 23:51 UTC (Wed) by HelloWorld (guest, #56129)
[Link]
legacy grub as *one* simple config. grub2 has such complicated config file that a script is needed to create it. That's a big step forward in the correct direction...
The grub2 configuration file isn't complicated. A typical config for grub legacy may look like this:
timeout 5
default 0
title Arch Linux
root (hd0,0)
kernel /vmlinuz26 root=/dev/sda3 ro
initrd /kernel26.img
set timeout=5
set default=0
menuentry "Arch Linux" {
set root=(hd0,1)
linux /vmlinuz26 root=/dev/sda3 ro
initrd /kernel26.img
}
(examples taken from the Arch Linux wiki). As you can see, the differences are trivial.
The reason that the grub2 configuration is created by a script is that the configuration needs to be changed when your distro ships a new kernel. Of course, this applies to grub legacy as well, so distros like Debian shipped code that does just that: generate a configuration file for grub legacy. The only difference is that grub2 actually ships the code that the distributors used to write for grub legacy (update-grub on debian, grubby on Fedora etc.). So please, stop trolling already.