Bug 13491

Summary: lilo.conf not updated with new kernel choice
Product: [Retired] Red Hat Linux Reporter: paulw
Component: up2dateAssignee: Preston Brown <pbrown>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2001-02-21 17:30:13 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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.