On Sun, May 24, 2020 at 7:48 PM James Cassell <fedoraproject@xxxxxxxxxxxxx> wrote: > > > On Sun, May 24, 2020, at 9:39 PM, Chris Murphy wrote: > > On Sun, May 24, 2020 at 6:42 PM Paul Dufresne via devel > > <devel@xxxxxxxxxxxxxxxxxxxxxxx> wrote: > > > > > > Le 20-05-24 à 19 h 34, Naheem Zaffar a écrit : > > > > The change record for this states that we are not following the BLS at > > > > https://www.freedesktop.org/wiki/Specifications/BootLoaderSpec/ but > > > > the proposed update at > > > > https://www.freedesktop.org/wiki/MatthewGarrett/BootLoaderSpec/ . > > > > > > Thanks for remembering me this alternative specification! > > > > > > That said, Fedora does not seems to follow this alternative spec, > > > because we use: > > > > > > $BOOT/loader directory, and not $BOOT/org/freedesktop/bls directory as > > > indicated in this standard. > > > > > > The point is that as the $BOOT is shared among distributions, there must > > > be a way to detect if it is already there, to be able to re-use it. For > > > that, the specification (whatever the exact version if chosen) must be > > > relatively well followed. > > > > Yep. > > > > But an additional difficulty to fully implementing the spec is so far > > upstream GRUB don't want to follow it. So that means Fedora has to > > carry patches for GRUB to support it. And it's just yet another of > > 100+ patches Fedora carries for GRUB, and makes it difficult for the > > Fedora and RH boot teams. The resources so far implement some of the > > parts of BLS that help make things better on Fedora, but it's not a > > complete implementation. Drop-in snippets to add new kernels is crash > > safe, worst case the previous kernel is booted and you just reinstall > > the kernel; but writing out a new grub.cfg or modifying it, wasn't > > ever crash safe. Also, modifying the snippets is easier, they're just > > a few lines and fairly self-describing compared to what users often > > did, which was wade neck deep into editing grub.cfg. Or the Rube > > Goldberg machine that is editing /etc/default/grub, running a script > > (grub-mkconfig), which then runs 20 other scripts to create a > > configuration file that is actually a script. > > > > Even so, isn't the canonical way of persistently updating kernel args, still, to edit /etc/default/grub and run the script? (If not, are there docs for the new way?) It does still work, but by indirection. You set it in /etc/default/grub but grub2-mkconfig puts it into grub.cfg first and then it goes into grubenv. The grubenv variables are loaded by GRUB at boot time, and the BLS snippets reference those variables. I've resorted to using 'grub2-editenv' to directly modify grubenv. But as grubenv is fragile, using it will be abandoned. -- Chris Murphy _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
