Bug 2831

Summary:	LILO installation choices are too limited.
Product:	[Retired] Red Hat Linux	Reporter:	deane
Component:	installer	Assignee:	Matt Wilson <msw>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.0
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:	2000-02-10 19:42:07 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 deane 1999-05-15 05:29:02 UTC

I have a system with an ATAPI CDROM as hda, an Sparq
removable drive as hdb1, and a SCSI drive on sda with sda7
being my root Linux filesystem and sda1 being a Win95
partition. I have LILO installed on the SCSI drive's main
boot record and use it to boot either Win95 or Linux.

When upgrading from 5.2 to 6.0 the installer only offered me
the choices of putting LILO on either hdb1 (the Sparq) or
sda7 (my Linux root). I wanted it to go onto sda's main boot
record, just like it did before. That's the first problem: I
should be able to do that.

Not having that choice, I selected sda7 for LILO and sure
enough, on reboot it got as far as `LI' before hanging.

I fixed the problem by booting from floppy, modifying
/etc/lilo.conf and then running lilo by hand.

Comment 1 Jay Turner 2000-02-10 19:42:59 UTC

This issue is fixed in the 6.1 installer.