On Sat, Aug 29, 2015 at 12:17 PM, Michel Catudal <mcatu...@comcast.net> wrote: > You have to be able to boot the os that grub is installed on to be able to > fix booting issues. If the OS that has control of grub2 is wacked you are > screwed. > At least with a bootloader that independant of any operating system and with > a nice graphic interface it is a piece of cake to fix things since you do > not ever lose your bootloader unless you let grub write on the MBR or on > your bootloader partition. > > I know that you can boot on grub if it is not wiped but the interface is not > friendly at all and if you do not remember the syntax you are screwed. Until > grub becomes a nice real bootloader with a friendly user interface it cannot > be allowed to be the sole controller of booting.
The grub config syntax is not really that bad; the main issue is that grub-mkconfig generates a very complex config file to try and cover a lot of possible systems. grub is pretty much designed to be able to boot any OS you have installed on any filesystem. That flexibility carries with it a level of complexity as well. If you don't need that flexibility, a simpler boot loader is always an option for you. If you want an "OS-independent" boot loader, the syslinux family of boot loaders might be a good choice for you. Or keep using grub legacy. Just don't expect either of them to be able to boot Linux from ZFS, or ext4 on lvm on luks. That's where grub2 comes in handy.
