On Sep 14, 2014, at 3:37 PM, Chris Murphy <lists(a)colorremedies.com> wrote:
Now what are the odds that grubby touches grub.cfg at 17:26:41 and
has touched grubenv at the exact same time? I think the odds are high grubby is doing
this. But for whatever reason there's a state change that causes it to not do it
subsequently when I manually run newkernelpkg. And I'll bet the reason why is because
grub.cfg as written from grub2-mkconfig is incomplete because the 3.16.1-301.fc21.i686
initramfs isn't finished building. And it's grubby that cleans up that missing
part of the grub.cfg entry. I bet only when it has to modify grub.cfg does it also modify
grubenv.
OK another TC7 install, another chroot of /mnt/sysimage while in the post-install live
media environment:
# grub2-set-default 0
# grub2-editenv list
saved_entry=0
# rm -f /boot/initramfs-3.16.1-301.fc21.i686.img
# grub2-mkconfig -o /boot/grub2/grub.cfg
## the grub.cfg is now in the state it was in during installation, with a boot entry that
lacks an initrd line
# grub2-editenv list
saved_entry=0
# new-kernel-pkg --mkinitrd --dracut --depmod --update 3.16.1-301.fc21.i686
# grub2-editenv list
saved_entry=Fedora, with Linux 3.16.1-301.fc21.i686
AHA! GOTCHA! TAKE THAT BUG!
Chris Murphy