Le 20/01/2016 13:14, Simon Hobson a écrit :
Didier Kryn <k...@in2p3.fr> wrote:
I don't think Grub2 is all about pretty colours though. The veteran admin likes
to have a bootloader which is easy to configure, but the random admin, likes to
have a working multi-boot bootloader at the end of the installation.
Indeed, and when ${random_admin} has a mix of md raid and lvm (and possibly
other stuff as well), then either the bootloader has to support that - or
${random_admin} starts asking WTF? type questions.
AIUI, if you use md and raid1, with metadata version 0.9, for /boot - then each
member of the raid set contains a complete image of /boot which is safe to use
read-only. So the bootloader doesn't need to understand md, and the rest can be
taken care of in the initramfs/initrd (it's OK if said quickly and I slam the
lid back down before the worms crawl out !)
But try explaining the specific steps needed to achieve that to someone who is just
"clicking the options" for an install.
Dunno enough about metadata version, but, yes, I experimented this
setup with md1 and it worked. If boot fails from the first disk, you can
ask the BIOS to boot from the other one and it works. It worked for
Grub-0.9 as well.
Didier
_______________________________________________
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
