4 ms·

Slackware still uses LILO. Although most people will look at you like you're a fossil for using it these days, I've found it quite simple to configure and it ha

Slackware still uses LILO. Although most people will look at you like you're a fossil for using it these days, I've found it quite simple to configure and it has generally worked without a hitch.

digi_owl 11y ago
Grub1 was not so bad to configure either, but Grub2 looks like a real stinker. The biggest gotcha with LILO is that thing about writing the config to the boot sector. But then i have not used it in some years...
- 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 ago
    Are 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 ago
      The 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 ago
        If 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 ago
        Yes 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 ago
        However, it is not due to fault of grub2, but due to distro-specific scripts that "helpfully" generate grub config.

Slackware still uses LILO. Although most people will look at you like you're a fossil for using it these days, I've found it quite simple to configure and it has generally worked without a hitch.

digi_owl 11y ago

Grub1 was not so bad to configure either, but Grub2 looks like a real stinker. The biggest gotcha with LILO is that thing about writing the config to the boot sector. But then i have not used it in some years...

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 ago
  Are 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 ago
    The 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 ago
      If 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 ago
        Yes 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 ago
        However, it is not due to fault of grub2, but due to distro-specific scripts that "helpfully" generate grub config.