Bug 99301 - lilo won't install without redhat-logos
Summary: lilo won't install without redhat-logos
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: lilo   
(Show other bugs)
Version: 8.0
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Brock Organ
Depends On:
TreeView+ depends on / blocked
Reported: 2003-07-17 10:41 UTC by Cipriano Groenendal
Modified: 2007-04-18 16:55 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-08-04 20:39:50 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Cipriano Groenendal 2003-07-17 10:41:46 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 

Description of problem:
Installing lilo with a kickstart, installs it with a default lilo.conf file, 
which includes this line:


However, said file is owned by the redhat-logos packages. If you don't install 
that rpm, and the file is not present, lilo will refuse to install with the 
following error:

Fatal: open /boot/message: No such file or directory

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Install redhat with a kickstart that specificly excludes the redhat-logos 
2. Install lilo


Actual Results:  After installation, there is no lilo installed and linux will 
refuse to start.

Expected Results:  Lilo / Anaconda should not install the message line in the 
lilo.conf if the messagefile is not there, or lilo-[...].rpm should Depend on 

Additional info:

Comment 1 Jeremy Katz 2003-07-26 02:53:21 UTC
Fixed in CVS to only put the message line there if the image exists.

Comment 2 Bill Nottingham 2006-08-04 20:39:50 UTC
Red Hat Linux and Red Hat Powertools are currently no longer supported by Red
Hat, Inc. In an effort to clean up bugzilla, we are closing all bugs in MODIFIED
state for these products.

However, we do want to make sure that nothing important slips through the
cracks. If, in fact, these issues are not resolved in a current Fedora Core
Release (such as Fedora Core 5), please open a new issues stating so. Thanks.

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