Am 02.12.2015 um 20:35 schrieb Andrew Lutomirski:
On Wed, Dec 2, 2015 at 9:50 AM, Josh Boyer <jwboyer@xxxxxxxxxxxxxxxxx> wrote:And you would do that via a single command how? By wrapping it in an architecture/bootloader agnostic wrapper. Which is what grubby is.But it's not. grubby does things like adding kernels and removing kernels. grub2-mkconfig enumerates kernels and generates a config.
and if it has a bug you are lot with *all* entries borked
# # DO NOT EDIT THIS FILE # # It is automatically generated by grub2-mkconfig using templates # from /etc/grub.d and settings from /etc/default/grub # That's grossly misleading. It *was* automatically generated, but it is certainly not automatically generated on an ongoing basis. If I change settings in /etc/default/grub, nothing happens. If I actually want to change boot options, I have to either manually edit every instance (or somehow, magically, the correct subset of copies) in /etc/grub2-efi.cfg, which is a real pain and easy to screw up
no - if you want them all identically just run grub2-mkconfig manually but don't expect that i am happy when something put's the same error into every entry
https://bugzilla.redhat.com/show_bug.cgi?id=840204 is probably the best example - with grubby you where able to add the needed option to the most recent entry and survived kernel updates
with grub2-mkconfig *every* single kernel update without edit the config before reboot meant go to your car and drive 300 miles to the remote machine or explain somebody how to get screen and keyboard on the headless machine and hand out the password
Attachment:
signature.asc
Description: OpenPGP digital signature
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx http://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx
