Bug 55380 - initscripts doesn't work with nicknames
initscripts doesn't work with nicknames
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: initscripts (Show other bugs)
7.2
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Brock Organ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-10-30 11:58 EST by Trond Eivind Glomsrxd
Modified: 2014-03-16 22:24 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-10-31 03:09:54 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 Trond Eivind Glomsrxd 2001-10-30 11:58:17 EST
neat creates network devices with nicknames. The initscripts uses some of
the information to guess other filenames, which breaks device init.
Comment 1 Gert Dewit 2001-10-31 03:09:48 EST
In the is_available function in the network-functions file the network
device gets modprobed with the module name.
This way one can't assing specific options to an interface using
"options alias module_options" notation in /etc/modules.conf

If one has 2 NIC's using the same module, one can't for instance force
100Mbit FDX on one interface and 100Mbit HDX on the other because only
options to the module are available.

Try this setup:
alias eth0 eepro100
alias eth1 eepro100
options eth0 options=48
options eth1 options=32
Comment 2 Bill Nottingham 2002-01-25 00:25:41 EST
modprobe call fixed in 6.51-1; the use of $DEVICE/$REALDEVICE should have all
been fixed in 6.40.2-1.

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