On Tue, Feb 12, 2019 at 5:08 AM Javier Martinez Canillas <javier@xxxxxxxxxxxx> wrote: > You are correct, we will work on more documentation and also better > tooling to manage the BLS snippets, grubenv file, etc. For example > grub2-editenv is very fragile as was mentioned in this thread. I'm looking at this: https://docs.fedoraproject.org/en-US/fedora/f29/system-administrators-guide/kernel-module-driver-configuration/Working_with_the_GRUB_2_Boot_Loader/ I'm noticing that grubby on F30 is actually grubby-bls. On the one hand: # grubby --set-default /boot/vmlinuz-5.0.0-0.rc5.git0.1.fc30.x86_64 # cat /boot/efi/EFI/fedora/grubenv # GRUB Environment Block saved_entry=8a6804fc8b1447b49bf2b522e419f2ae-5.0.0-0.rc5.git0.1.fc30.x86_64 [snip] That appears to work. However, [chris@localhost ~]$ sudo grubby --remove-args=quiet [chris@localhost ~]$ sudo cat /boot/efi/EFI/fedora/grubenv [snip] kernelopts=root=/dev/mapper/fedora_localhost--live-root ro resume=/dev/mapper/fedora_localhost--live-swap rd.lvm.lv=fedora_localhost-live/root rd.luks.uuid=luks-8dc728e5-4420-4f90-a1c5-aaf87a69d88b rd.lvm.lv=fedora_localhost-live/swap rhgb quiet boot_indeterminate=0 That doesn't work. Nor does --remove-args="quiet" - nor is there an error message. It just fails silently. And the --args argument doesn't appear to add arguments to the grubenv (or the bls snippets), also fails silently. Is it a bug? Is grubby-bls intended as the primary tool for changing these things? Long term or short term? -- Chris Murphy _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
