Bug 13491 - lilo.conf not updated with new kernel choice
Summary: lilo.conf not updated with new kernel choice
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: up2date
Version: 6.2
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Preston Brown
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-07-05 10:32 UTC by paulw
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2001-02-21 17:30:13 UTC
Embargoed:


Attachments (Terms of Use)

Description paulw 2000-07-05 10:32:38 UTC
The lilo.conf file is installed referencing the 
specific kernel to boot, not vmlinuz; therefore 
lilo.conf needs to be updated when installing a 
new kernel.

This is not happening when the Update Agent loads 
a new kernel. Furthermore, is it a good idea to 
delete the old kernel before the new one is tested 
on a machine, because this is happening.

I'd like to add, the folks at RedHat are doing great work.

Sincerely,
Paul Warriner

Comment 1 Ross Johnson 2001-02-20 06:04:09 UTC
This bug is still present in the latest RedHat 7.0 update kernel-*i686.rpm
downloaded 20/02/2001. Can the priority be raised please so that updates
don't continue to fail. Updates work very nicely except for this.

Comment 2 Preston Brown 2001-02-26 23:39:06 UTC
we don't support kernel upgrades with up2date as of now; that is why kernel is
in the exclude list as shipped.


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