Bug 63240 - Anaconda upgrade wrote invalid lilo.conf
Anaconda upgrade wrote invalid lilo.conf
Product: Red Hat Public Beta
Classification: Retired
Component: anaconda (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2002-04-11 12:27 EDT by Stephen Tweedie
Modified: 2007-04-18 12:41 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-04-11 15:17:57 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Stephen Tweedie 2002-04-11 12:27:44 EDT
Description of Problem:

Upgrading from 7.2 to a recent Skipjack build (internal 0409.1 isos) wrote an
invalid lilo.conf.  I had a custom lilo entry for a non-rpm kernel, which
included a kernel append of the form


and the lilo.conf rewrite stripped out the quote marks leaving


This breaks lilo --- an append line with an "=" in it must be quoted.

This resulted in the lilo run aborting when the boot loader was updated, so on
the next reboot, I ended up with an old kernel being loaded, despite the fact
that anaconda had already deleted the /lib/modules for that old kernel.

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

How Reproducible:

Steps to Reproduce:
1. Install 7.2
2. Add an append="key=value" item to /etc/lilo.conf
3. upgrade to Skipjack.

Actual Results:
Broken lilo.conf is written with the "key=value" unquoted.

Expected Results:
lilo.conf should be usable.

Additional Information:
Comment 1 Jeremy Katz 2002-04-11 15:17:52 EDT
Yep, thanks.  Fixed in CVS.

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