On Fri, Dec 18, 2015 at 2:01 PM, Eric Griffith <egriffith92@xxxxxxxxx> wrote: > Grub2-mkconfig works fine on F23. Maybe not for complex operations but for > general modifications to /etc/default/grub it creates a perfectly working > grub.cfg The default menu entries for other OS's is definitely suboptimal. OS X and Windows+Secure Boot entries don't work. [1] And other Linux OS installations get generic menu entries rather than pointing to the distro specific grub.cfg instance using the GRUB 'configfile' command. There are many different implementations of GRUB2 by the distros, including grub.cfg location, what and where the 1st stage bootloader (jump code) goes. And Fedora atomic builds manage all the bootloader stuff internally, leveraging some of grub2-mkconfig but not all of it. So that's a 3rd variation for producing a grub.cfg, on a single distro. If you care about understanding how systems boot, in particular to know how to fix booting when it breaks, good luck with that. It's a lot of work. Most search results will be polluted with the misleading irrelevancies of how other distros do things. [1] Automatic MacOSX grub entries are broken (and weird) https://bugzilla.redhat.com/show_bug.cgi?id=893179 SecureBoot enabled causes Win 8 UEFI to not start from grub https://bugzilla.redhat.com/show_bug.cgi?id=1170245 -- Chris Murphy -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx http://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx
