On Fri, Sep 7, 2018 at 5:09 PM, Jason L Tibbitts III <tibbs(a)math.uh.edu> wrote:
>>>>> "CM" == Chris Murphy
<lists(a)colorremedies.com> writes:
CM> But also the first new-kernel-pkg with --install calls grubby with
CM> makedefault, which is what I think is setting grubenv with the new
CM> kernel variable before the initramfs and final grub.cfg modification
CM> are done.
Right, which is why I wonder if switching the two lines wouldn't work.
Given the complexity I assume it's being done this way for a reason; I
just don't know what the reason is.
As I think about it, new-kernel-pkg is part of grubby. And some time
ago I heard new-kernel-pkg was either going away or being refactored.
I don't know the status of that, but if grubby is going away, then
new-kernel-pkg is either going away or being moved. My understanding
of the BLS by default change, is that grubby don't be installed. While
I see it in the upstream grubby project...
$ sudo dnf provides /usr/sbin/new-kernel-pkg
[sudo] password for chris:
Last metadata expiration check: 2:43:04 ago on Fri 07 Sep 2018 02:59:45 PM MDT.
Error: No Matches found
*shrug*
--
Chris Murphy