Bug 598596 - kernel upgrade messes up default grub.conf selection
Summary: kernel upgrade messes up default grub.conf selection
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 13
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-01 17:14 UTC by Henrique Martins
Modified: 2010-06-08 14:23 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-06-08 14:08:34 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Henrique Martins 2010-06-01 17:14:09 UTC
Description of problem:
Whenever I install a new kernel some script updates my /boot/grub/grub.conf file, as it should. However, it makes the new kernel the default boot kernel, even if the old kernel was not the default, i.e. on my company provided laptop I boot on WindowsXP for work, the default, and under Linux, by manually interaction with grub, whenever I'm at home.
The net result is that I have to re-edit grub.conf and change the default back to WindowsXP, which is a very minor annoyance, but one that could be avoided if the grub update script would only make the new kernel the default if the old (current) kernel was already the default.


Version-Release number of selected component (if applicable):
any for a while now

How reproducible:
after every single kernel update


Steps to Reproduce:
1. yum update whenever there's a new kernel
2.
3.
  
Actual results:
default on /etc/grub.conf always points to the new kernel


Expected results:
More like desired results.  Default to be kept if other than current kernel.

Additional info:

Comment 1 Chuck Ebbert 2010-06-08 14:08:34 UTC
Edit /etc/sysconfig/kernel and change UPDATEDEFAULT=yes to UPDATEDEFAULT=no

Comment 2 Henrique Martins 2010-06-08 14:23:13 UTC
Guess that will do it in my case, though short of a
  UPDATEDEFAULT="if default"
option. 

Thanks.


Note You need to log in before you can comment on or make changes to this bug.