Bug 116602 - new kernel doesn't automatically become default
Summary: new kernel doesn't automatically become default
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: grub
Version: rawhide
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-02-23 18:08 UTC by David Jansen
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2004-02-23 23:20:44 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description David Jansen 2004-02-23 18:08:08 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1)
Gecko/20031114

Description of problem:
After upgrading the FC2test1 kernel to the latest version from rawhide
(2.6.3-1.97), this kernel is added to grub.conf, but the previous
kernel is still the default

Version-Release number of selected component (if applicable):
grub- kernel-2.6.3-1.97

How reproducible:
Didn't try

Steps to Reproduce:
1. install FC2test1
2. install all available updates
3.
    

Actual Results:  grub's default is still the original 2.6.1-1.65 that
shipped with FC2test1

Expected Results:  The latest updated kernel should be the default (as
it was in FC1)

Additional info:

In a way, this is a security issue: a user may asume his system is
completely up to date after up2date + reboot, but if this user didn't
pay close attemtion to the boot, his system would still be running the
old kernel (which may have a security hole)

Comment 1 Jeremy Katz 2004-02-23 23:20:44 UTC
This is intentional.  The various updating tools handle doing the
updating of the default themselves (if they don't, bugs should be
filed against them, not grub)


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