Bug 87617 - Installing kernel-2.4.18-27.8.0.i686.rpm on a LILO system gives "grubby" error
Installing kernel-2.4.18-27.8.0.i686.rpm on a LILO system gives "grubby" error
Status: CLOSED WONTFIX
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
8.0
i686 Linux
medium Severity low
: ---
: ---
Assigned To: Arjan van de Ven
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-03-30 16:52 EST by Phil Holden
Modified: 2007-04-18 12:52 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-09-30 11:40:42 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Phil Holden 2003-03-30 16:52:01 EST
From Bugzilla Helper: 
User-Agent: Mozilla/5.0 (compatible; Konqueror/3; Linux) 
 
Description of problem: 
Installed kernel-2.4.18-27.8.0.i686.rpm on a system which uses 
LILO as the boot loader.  The message  
  grubby fatal error: unable to find a suitable template 
was reported.  No entry was added to /etc/lilo.conf for the new 
kernel.   
 
Version-Release number of selected component (if applicable): 
kernel-2.4.18-27.8.0.i686.rpm 
 
How reproducible: 
Didn't try 
 
Steps to Reproduce: 
1. 
2. 
3. 
     
 
Additional info: 
 
Added entry in lilo.conf myself and it booted OK, so the only  
problem seems to be the failure to set up lilo.conf.   
 
Kernel is from your security advisory RHSA-2003:098
Comment 1 Bugzilla owner 2004-09-30 11:40:42 EDT
Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem
persists.

The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, 
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/

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