Bug 375

Summary: Setup provides lilo boot label for non-bootable disks, and fails
Product: [Retired] Red Hat Linux Reporter: Nick Urbanik <nicku>
Component: setuptoolAssignee: David Lawrence <dkl>
Status: CLOSED NOTABUG QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 5.2   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 1998-12-29 21:06:43 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Nick Urbanik 1998-12-10 03:19:52 UTC
When install/upgrade, lilo fails.

This is because setup has written a lilo.conf that tries
to start up non-bootable partitions.

Lilo fails, leaving lilo.conf to be edited manually,
(the non-bootable parititions to be commented out) and lilo
to be re-run.

A problem for newcomers to Linux.

Comment 1 Jay Turner 1998-12-10 15:58:59 UTC
Need more information about where you installed Lilo and what
partitition Lilo sets to boot.

Comment 2 David Lawrence 1998-12-10 19:35:59 UTC
Also a dump of what the lilo.conf file that is getting written
contains would be helpful.

Comment 3 David Lawrence 1998-12-29 21:06:59 UTC
This report has been closed due to lack of responce from user.

It may be reopned if needed.