On Thu, 2014-01-09 at 08:11 -0500, Robert Moskowitz wrote:
> > The other place you can change the parameters is in /etc/default/grub .
>
> Finally took the time to make the change and.... NO /etc/default/grub!!!!
If it doesn't exist, you can create it and settings in it will be
respected.
> Perhaps there are other interesting files that did not get on the
> system? But then how did grub2-mkconfig work when I ran it from
> rescue? It used what was on the CD?
/etc/defaults/grub doesn't have to exist for grub2-mkconfig to work.
grub2-mkconfig has built-in defaults for all settings; you
write /etc/defaults/grub if you want to change any of them.
So for both BIOS and UEFI, anaconda does this when installing the
bootloader:
self.install()
...
self.write_config()
i.e., it tries to install the bootloader before writing the
configuration file. That sounds odd, but it's actually the right way
around. The write_config() step does grub2-mkconfig but it also
creates /etc/default/grub . So if your bootloader install fails (or you
skip bootloader installation), you won't have a grub2.cfg and you won't
have /etc/defaults/grub .
grub2-mkconfig does work without a /etc/defaults/grub, though, as noted.
Our /etc/defaults/grub changes various settings to be more Fedora-y, so
your bootloader will look and behave a bit differently from a 'regular'
Fedora one, but none of the differences is critical.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
--
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
