4 ms·
Personally I prefer syslinux, where the config resides in a easy-to-understand textfile, /boot/syslinux/syslinux.cfg, which can be on FAT or ext2/3/4 or btrfs.
by semi-extrinsic 11y ago
Personally I prefer syslinux, where the config resides in a easy-to-understand textfile, /boot/syslinux/syslinux.cfg, which can be on FAT or ext2/3/4 or btrfs. The only limitation is that all files that syslinux reads must be on the same partition.
Grub2 OTOH is definitely an abomination. Whoever thought it a good idea to require compiling the bootloader config into a binary should be given a thorough slapping with a medium-sized trout. That thing is an overengineered solution looking for a problem.
- arebours 11y agoAre you sure that GRUB2 saves the config as a binary? I think on my Arch update-grub generates /boot/grub/grub.cfg which looks somewhat similar to good old menu.lst.
- digi_owl 11y agoThe binary part may be a bit harsh. But if i recall correctly grub2 compiles one config into another, and the result is topped with a "do not edit!" warning.
- lloeki 11y agoIf you poke into the resulting config, you'll notice that it's just convenience†, and you could write the file by hand. † in the same way that autotools is "convenience" saving you from writing makefiles and configure scripts.
- semi-extrinsic 11y agoYes you can write the file by hand, but what you write is going to get overwritten on the next system update to grub2.
- vetinari 11y agoHowever, it is not due to fault of grub2, but due to distro-specific scripts that "helpfully" generate grub config.