Bug 82323 - trivial typo prevents boot-time selection of network profile
trivial typo prevents boot-time selection of network profile
Status: CLOSED DUPLICATE of bug 79203
Product: Red Hat Linux
Classification: Retired
Component: initscripts (Show other bugs)
8.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Brock Organ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-01-21 04:56 EST by Ben Liblit
Modified: 2014-03-16 22:33 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-08-17 01:49:21 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)
fix: add "$" for proper variable expansion (509 bytes, patch)
2003-01-21 05:01 EST, Ben Liblit
no flags Details | Diff

  None (edit)
Description Ben Liblit 2003-01-21 04:56:55 EST
Description of problem:

One is supposed to be able to put "netprofile=<foo>" on the kernel command line
to select network profile <foo> when booting.  However, a trivial typo in
"/etc/rc.d/rc.sysinit" 

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

initscripts-6.95-1

How reproducible:

Easily, every time.

Steps to Reproduce:
1. Create at least two network profiles using "neat".
2. Using GRUB or LILO, add "netprofile=foo" to the kernel command line,
replacing "foo" with the name of one of the network profiles.
3. Boot.
    
Actual results:

Named network profile is not activated.

Expected results:

Named network profile should have been activated.

Additional info:

The bug is on line 766 of "/etc/rc.d/rc.sysinit", where a loop iterates over
"cmdline" instead of "$cmdline".  I will attach a diffs to this report showing
the correction.
Comment 1 Ben Liblit 2003-01-21 05:01:13 EST
Created attachment 89456 [details]
fix: add "$" for proper variable expansion
Comment 2 Bill Nottingham 2003-01-21 12:20:03 EST

*** This bug has been marked as a duplicate of 79203 ***
Comment 3 Ben Liblit 2004-08-17 01:49:21 EDT
Marking as CLOSED: the duplicate designation is correct, and
furthermore the bug has long since been fixed.

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