As I was booting my system after today's Rawhide update, I noticed that there were no Fedora kernels on offer at all. It seems like, once again, grubby is going weird and refusing to add lines for new kernels to grub.conf as they are installed.
Is this, perhaps, a subtle hint that I should switch the system to grub2? :)
Thanks,
jon
On 29/09/11 21:07, Jonathan Corbet wrote:
As I was booting my system after today's Rawhide update, I noticed that there were no Fedora kernels on offer at all.
No problem adding a kernel today, also removed one. grub1.
On Thu, Sep 29, 2011 at 02:07:23PM -0600, Jonathan Corbet wrote:
As I was booting my system after today's Rawhide update, I noticed that there were no Fedora kernels on offer at all. It seems like, once again, grubby is going weird and refusing to add lines for new kernels to grub.conf as they are installed.
Is this, perhaps, a subtle hint that I should switch the system to grub2? :)
Chuck bumped the NVR requires on grubby for the next kernel build. That should fix this.
Dave
On Thu, 2011-09-29 at 22:46 -0400, Dave Jones wrote:
On Thu, Sep 29, 2011 at 02:07:23PM -0600, Jonathan Corbet wrote:
As I was booting my system after today's Rawhide update, I noticed that there were no Fedora kernels on offer at all. It seems like, once again, grubby is going weird and refusing to add lines for new kernels to grub.conf as they are installed.
Is this, perhaps, a subtle hint that I should switch the system to grub2? :)
Chuck bumped the NVR requires on grubby for the next kernel build. That should fix this.
it doesn't sound like exactly the same issue. the bug fixed in the grubby update was missing initrd= lines, not entirely missing entries. iirc.