Red Hat Bugzilla – Bug 476565
yum update of kernel doesn't make the newly installed kernel the default
Last modified: 2014-09-24 17:51:52 EDT
Every since F10-Preview, when I install a new kernel, it gets added to grub.conf to the top of list, but "default" option is changed from 0 to 1, making my current kernel the default. I have to manually correct this mistake after the installation. In F9 and below, updating kernel made it the default. This is no longer the case. Is this on purpose?
I did a clean install of F10, and when I installed the new kernel-2.6.27.7-134.fc10, grub made it the default as usual.
Yeah, this isn't a clean install - it was upgraded with yum and I have an old grub.conf (still has a menu). Should I attach it? Or maybe it does that only for kernel-PAE?
What do you have in /etc/sysconfig/kernel ?
Oh... DEFAULTKERNEL=kernel I moved to kernel-PAE a month before upgrading to Rawhide (at Preview timeframe), it's totally possible that I haven't updated the kernel during that month, or haven't noticed the problem back then. Okay, so let's say it's my fault, but on the other hand, I have no "kernel" in my system and the currently running kernel is always kernel-PAE. Can't new-kernel-pkg be a little more automatic? I guess using something like rpm -qf `grubby --default-kernel` --qf '%{name}' should be enough for most of people anyhow, not to mention checking if my "DEFAULTKERNEL" is installed at all... Can I at least ask for it to print a warning if DEFAULTKERNEL is different that the one currently being the default? This would be harmless (no possible system breakage due to no behavior change, no PackageKit users even noticing...), at the same time providing some insight into what's going to happen for the brave ones like me, who install different kernels with yum :) Thanks and sorry for not knowing about /etc/sysconfig/kernel.
Closing as notabug per comment #4.