Bug 2420 - edit lilo defaults fails to add quotes
edit lilo defaults fails to add quotes
Status: CLOSED ERRATA
Product: Red Hat Linux
Classification: Retired
Component: linuxconf (Show other bugs)
6.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Michael K. Johnson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-04-29 14:48 EDT by Marty Shannon
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-12-15 15:55:49 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)

  None (edit)
Description Marty Shannon 1999-04-29 14:48:29 EDT
Not a big deal, but it would be nice if, when changing
(adding) additional parameters to lilo.conf, linuxconf would
both preserve indentation, and add quotes around the
additional parameters (i.e., "mem=80m" for my laptop).
Comment 1 Joe Acosta 1999-07-05 18:34:59 EDT
this happened on my machine too, it is a bug in linuxconf. It happens
with all version of linux conf. in my case it was the append line:

the append line should look like append = "xtpic=3" but was showing up
as append = xtpic=3 this cause errors when running lilo it would fail,
thank goodness I always have a boot disk.
the xtpic=3 is a SMP kernel patch that I have just voluntered to be an
alpha tester for. It may provide a workaround for a suspected APIC
bug.
Comment 2 Joe Acosta 1999-07-05 18:35:59 EDT
by versio I ment linuxconf, gnomeconf, linuxweb based, etc tyhat are
included in RH 6.0
Comment 3 Michael K. Johnson 1999-08-28 15:43:59 EDT
Added Jacques to the Cc line so that he can fix this.
Comment 4 Dale Lovelace 1999-12-03 14:54:59 EST
This is fixed in linuxconf-1.16r10 which will be released as an errata when
testing is completed. I suggest upgrading when it is available.
Comment 5 Michael K. Johnson 1999-12-15 15:55:59 EST
1.16r10-2 released.

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