On Sun, Dec 06, 2015 at 06:25:09PM +0100, drago01 wrote: > >> Well mkconfig can produce a configuration that does not actually work > >> when grub2 itself gets updated (in which case the bootloader does not > >> get rewritten). > >> Until this is fixed grub2-mkconfig is dangerous and should not be used. > > > > I have never seen this happen on any distro. In any event, even if > > there's a case in which mkconfig screws up, Fedora is unlikely to be > > able to install in the first place. > > No that has nothing to do with the installation process. > > The events are: > > 1) You install Fedora -- grub2-mkconfig creates a config that matches > the bootloader > 2) The grub package gets updated / upgraded --- grub2-mkconfig is no > longer guaranted to generate a config file that works with the grub > that is actually installed (i.e you'd have to rerun grub2-install to > be sure). > > Yes in most of the cases that works but it is fragile and therefore > dangerous to do that by default. Can you list specific cases? It sounds awfully theoretical. -- Tomasz Torcz "Never underestimate the bandwidth of a station xmpp: zdzichubg@xxxxxxxxx wagon filled with backup tapes." -- Jim Gray -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx http://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx
