Description of problem: When updating kernel* packages, grubby activates the wrong variant as default, i.e. xen0 instead of UP on one machine (Athlon 1400) and smp instead of UP on another (Athlon 700). Version-Release number of selected component (if applicable): mkinitrd-5.0.32-1 How reproducible: Easy Steps to Reproduce: 1. Update kernel* packages 2. check "default" in /boot/grub/grub.conf Actual results: default kernel from a different variant Expected results: default kernel from same variant
I've seen this again with the update to 2.6.16-1.2107_FC5, it defaulted to the xen0 variant even though it defaulted to the UP variant previously.
Fedora apologizes that these issues have not been resolved yet. We're sorry it's taken so long for your bug to be properly triaged and acted on. We appreciate the time you took to report this issue and want to make sure no important bugs slip through the cracks. If you're currently running a version of Fedora Core between 1 and 6, please note that Fedora no longer maintains these releases. We strongly encourage you to upgrade to a current Fedora release. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained and closing them. http://fedoraproject.org/wiki/LifeCycle/EOL If this bug is still open against Fedora Core 1 through 6, thirty days from now, it will be closed 'WONTFIX'. If you can reporduce this bug in the latest Fedora version, please change to the respective version. If you are unable to do this, please add a comment to this bug requesting the change. Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we are following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again. And if you'd like to join the bug triage team to help make things better, check out http://fedoraproject.org/wiki/BugZappers
It seems to me that grubby activates whatever is configured in /etc/sysconfig/kernel.