Bug 5737 – lilo configuration in linuxconf does not accept valid root partition.

Bug 5737 - lilo configuration in linuxconf does not accept valid root partition.

Summary:	lilo configuration in linuxconf does not accept valid root partition.

Status:	CLOSED ERRATA

Aliases:	None

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

Priority	high Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Michael K. Johnson
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Duplicates:	6985 (view as bug list)
Depends On:
Blocks:
	Show dependency tree / graph

Reported:	1999-10-08 15:15 EDT by mmclure
Modified:	2008-05-01 11:37 EDT (History)
CC List:	3 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	1999-12-15 15:59:10 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description mmclure 1999-10-08 15:15:29 EDT

I have a configuration where my /boot directory is
on /dev/hda1, with my / directory on /dev/hda7. If I try to
set this up in the linuxconf lilo configuration, it does
not let me specify /dev/hda7 as root - it says that this is
not a Linux partition (even though fdisk shows it as type
83 and it's mounted just fine as my root). I have to edit
the lilo.conf file by hand (this works fine).

What's worse is that the installation created a fine
lilo.conf file with /dev/hda7 as root. All I wanted to do
was change the vga setting.

Comment 1 Michael K. Johnson 1999-11-18 13:17:59 EST

Jacques, are there any known bugs regarding parsing fdisk output?

Comment 2 Michael K. Johnson 1999-11-19 16:36:59 EST

*** Bug 6985 has been marked as a duplicate of this bug. ***

Comment 3 jack 1999-11-30 11:24:59 EST

Solved in 1.16r7 and further enhanced in 1.16r8

Comment 4 Michael K. Johnson 1999-12-02 13:43:59 EST

We'll be making an errata release of 1.16r10 or later soon that will
include this fix, after we do appropriate testing.

Comment 5 jskline 1999-12-04 08:12:59 EST

I also have verified this issue but also testing it with several different types
and even the "stock" workstation installation on 2 different machines here. Also
the same conditions happen if you compile your own kernel and try to install it
via linuxconf. It will not accept a valid root partition on any drive.

Comment 6 Michael K. Johnson 1999-12-15 15:59:59 EST

1.16r10-2 released

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