Bug 58063 - Low robustness when installing LILO
Summary: Low robustness when installing LILO
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda   
(Show other bugs)
Version: 7.2
Hardware: i386 Linux
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Brock Organ
Depends On:
TreeView+ depends on / blocked
Reported: 2002-01-07 16:49 UTC by Juan Jose Amor
Modified: 2007-04-18 16:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-03-19 00:44:47 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Juan Jose Amor 2002-01-07 16:49:55 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.78 [es] (X11; U; Linux 2.2.20BS1 i586)

Description of problem:
When installing LILO, anaconda is not robust. May crash in a scenary where it
may not (trivially) be created the /etc/lilo.conf file.

For example, when I upgraded Redhat linux from 7.1 to 7.2, if /etc/lilo.conf
is a symbolic link to /boot/lilo.conf, anaconda does not check why it can not
/etc/lilo.conf, anaconda simply halts the installation process.

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

How reproducible:

Steps to Reproduce:
1. Install a Redhat Linux release, with LILO as boot loader.
2. Move /etc/lilo.conf to another place and then symlink to this file from /etc
3. Upgrade Redhat Linux and choose LILO install. anaconda will crash when
trying to create lilo.conf file.

Additional info:

Comment 1 Jeremy Katz 2002-01-07 17:23:31 UTC
It should be moving the old lilo.conf (even if a symlink) to be
lilo.conf.rpmsave;  if you're getting a crash, the full backtrace would be very

Comment 2 Juan Jose Amor 2002-01-07 18:44:11 UTC
I've not a python backtrace because it occurred during installation phase and I
did not saved it.

However, I remember anaconda stderr said "cannot open /etc/lilo.conf for
writing", and
when I booted my system again with a diskette, both the symlink and the "real"
lilo.conf files
are untouched.

Comment 3 Brent Fox 2002-01-17 15:43:04 UTC
katzj: do you think lilo.conf might be set to immutable?

Comment 4 Jeremy Katz 2002-03-07 21:48:22 UTC
It's possible ... without the backtrace, it's really difficult to say what
happened :(

Comment 5 Jeremy Katz 2002-03-15 04:49:54 UTC
Was this an absolute symlink or a relative symlink (ie was it to
../etc/lilo.conf or /boot/lilo.conf)

Comment 6 Juan Jose Amor 2002-03-15 08:50:19 UTC
Yes, if it was a relative symlink, I assume it would work. However,
I did an absolute link, so when anaconda mounts existing partitions under
/mnt, it does not check this issue.

Comment 7 Jeremy Katz 2002-03-19 00:44:42 UTC
Fixed in CVS

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