Bug 36695 - bad lilo.conf after upgrade
bad lilo.conf after upgrade
Status: CLOSED WORKSFORME
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
7.1
i386 Linux
high Severity medium
: ---
: ---
Assigned To: Brent Fox
Brock Organ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-04-19 18:00 EDT by mw
Modified: 2007-03-26 23:43 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-05-09 15:15:14 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description mw 2001-04-19 18:00:03 EDT
After upgrade (from wolverine to 7.1, but I saw the same from 7.0 to
wolverine), I am left with a syntactically incorrect lilo.conf.

Original lilo.conf
=============

boot=/dev/hda
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
message=/boot/message
default=linux

image=/boot/vmlinuz
        label=linux
        read-only
        root=/dev/hda1

But after installtion, I had

# cat /etc/lilo.conf
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
message=/boot/message
default
linear

image=/boot/vmlinuz
        label=linux
        read-only
        root=/dev/hda1

image=/boot/vmlinuz-2.4.2-2
        label
        read-only
        root=/dev/hda1

The error is in the stale `default' and `label', I believe.
Comment 1 Brent Fox 2001-04-26 15:54:57 EDT
Did you modify the label in the LILO configuration screen?
Comment 2 mw 2001-05-01 13:58:22 EDT
Nope. I am not even sure I got a lilo configuration screen.  The reason I know I
did not modify it even if I had one is because I always test the first upgrade
by not changing anything (including the list of upgradable packages).
Comment 3 Brent Fox 2001-05-01 15:34:56 EDT
We have not seen this in our internal testing.  Was the system bootable after
the upgrade?
Comment 4 mw 2001-05-03 12:09:19 EDT
Nope.  But luckily I had my 7.0 bootfloppy, so I could fix lilo.conf.

Comment 5 Brent Fox 2001-05-09 15:15:09 EDT
I can't explain why that happened.  We have not seen this in our internal
testing.  I just tried this on my test machine and things worked fine.

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