Bug 90821

Summary:	no lilo installed -> lilo still gets messed up
Product:	[Retired] Red Hat Linux	Reporter:	Göran Schultz <goran.schultz>
Component:	lilo	Assignee:	Jeremy Katz <katzj>
Status:	CLOSED RAWHIDE	QA Contact:	Brock Organ <borgan>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	9	CC:	mitr
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2003-05-16 22:14:31 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 Göran Schultz 2003-05-14 10:54:57 UTC

Description of problem:
New RH9 installion / on empty partition, /boot shared with other RH versions:
choose NOT to install LILO, still lilo gets messed up (solution:
boot machine with boot rescue disk, rerun lilo -C /oldetc/lilo.conf )

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

How reproducible:
done 4 removable disk partitions with new RH9, always same problem 

Steps to Reproduce:
1. make new installation without installing lilo, new boot disk works fine
2. old lilo installed on /boot partition gets messed up (needs to "lilo")
3.
    
Actual results:


Expected results:
if I don't install lilo, nothing in that respect should be touched even if I
share the
/boot partition with other RH versions

Additional info:
if a hard disk has had grub previously, all old partitions seem to get messed up
(only one hard disk experience, no desire to use grub further!)

Comment 1 Jeremy Katz 2003-05-16 22:14:31 UTC

Unfortunately, with the way that lilo does boot sectors, this doesn't work.   We
don't install lilo unless you specifically request installing lilo as your boot
loader with our current codebase, though, so that should work around the problem.