Bug 89072 - Installation generates invalid lilo.conf (disks start mounted)
Summary: Installation generates invalid lilo.conf (disks start mounted)
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: lilo
Version: 9
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Brock Organ
Depends On:
TreeView+ depends on / blocked
Reported: 2003-04-17 06:03 UTC by Maciej Michno
Modified: 2007-04-18 16:53 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2003-07-28 23:59:33 UTC

Attachments (Terms of Use)
lilo.conf created by the installer (281 bytes, text/plain)
2003-04-17 06:06 UTC, Maciej Michno
no flags Details
My working lilo.conf (306 bytes, text/plain)
2003-04-17 06:07 UTC, Maciej Michno
no flags Details

Description Maciej Michno 2003-04-17 06:03:02 UTC
Red Hat inux 8 + ext2 disks + upgrade to Red Hat Linux 9 + LILO 
During installation (upgrading process) leave the disks in ext2 (don't migrate to ext3) 
Don't migrate to grub, select the recomended option (update the existing boot 
manager -- LILO) 
At boot time the disks will have to be checked by e2fsck and this will not be 
possible: partitions are mounted read-write at startup -- the installation produced an 
erroneous lilo.conf file.

Comment 1 Maciej Michno 2003-04-17 06:06:08 UTC
Created attachment 91169 [details]
lilo.conf created by the installer

This is the file produced by the installation.
There was one more line in the linux section pointing to the initrd file, but I
have deleted it accidentally and don't have a backup version...

Comment 2 Maciej Michno 2003-04-17 06:07:34 UTC
Created attachment 91170 [details]
My working lilo.conf

Comment 3 Jeremy Katz 2003-04-23 02:00:50 UTC
There's a read-only in the section for the new kernel, so it should be right. 
Could you please attach the complete kernel messages for booting with the
original lilo.conf?

Comment 4 Maciej Michno 2003-04-30 11:38:03 UTC
Please, tell me exactly what do you need and how can I save these kernel 

Comment 5 Jeremy Katz 2003-07-28 23:59:33 UTC
Fixed in current code.

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