Bug 47264 – bad /etc/lilo.conf

Bug 47264 - bad /etc/lilo.conf

Summary:	bad /etc/lilo.conf

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	anaconda (Show other bugs)
Sub Component:
Version:	7.3
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Jeremy Katz
QA Contact:	Brock Organ
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2001-07-04 05:35 EDT by Gene Czarcinski
Modified:	2007-04-18 12:34 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2001-07-06 08:12:06 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
as created by install (390 bytes, text/plain) 2001-07-06 08:11 EDT, Gene Czarcinski	no flags	Details
after manually editing to delete last two entries (329 bytes, text/plain) 2001-07-06 08:12 EDT, Gene Czarcinski	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Gene Czarcinski 2001-07-04 05:35:40 EDT

Description of Problem:
This is related to #47891 but different.

With two ide drives already partitioned with a vfat partitions at hda1 and
hdb1, the /etc/lilo.conf was still bad even after changing the label from
"Red Hat Linux" to "Linux" so that lilo could handle it.  The problem
seemed to be that it wanted to make a boot entry fro hdb1 but with no label
at all.  Formally, having no label removed that entry.

How Reproducible:
always

Steps to Reproduce:
1. have two prepartitioned disks with vfat partitions as the first ones.
2. do an install with lilo as the boot loader and fixing the label
3.

Actual Results:


Expected Results:


Additional Information:

Comment 1 Jeremy Katz 2001-07-06 00:48:44 EDT

Do you still have (or can you get another of) the lilo.conf before and after
fixing it?  If not, can you the after lilo.conf and try to point out the difference?

Comment 2 Gene Czarcinski 2001-07-06 08:09:37 EDT

Without changing the "Red Hat Linux" label, no /etc/lilo.conf is created.

I am attaching fix1 (change label to Linux) and fix2 (manually deleting the last
two entries).

In previous versions, a partition without a label did NOT create an entry in
/etc/lilo.conf.

Comment 3 Gene Czarcinski 2001-07-06 08:11:09 EDT

Created attachment 22847 [details]
as created by install

Comment 4 Gene Czarcinski 2001-07-06 08:12:03 EDT

Created attachment 22848 [details]
after manually editing to delete last two entries

Comment 5 Jeremy Katz 2001-07-06 13:00:22 EDT

Aha, thanks.  Fixed in cvs

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