Bug 82442 - device name missing number for network card
device name missing number for network card
Product: Red Hat Public Beta
Classification: Retired
Component: hwbrowser (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Brent Fox
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2003-01-22 01:35 EST by Tammy Fox
Modified: 2007-04-18 12:50 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-01-22 16:56:55 EST
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 Tammy Fox 2003-01-22 01:35:33 EST
On the Network devices page, the device name for my ethernet
card says /dev/eth instead of /dev/eth0.
Comment 1 Brent Fox 2003-01-22 16:24:22 EST
Actually, this is the data that kudzu provides.  Try this from a python interpreter:

d = kudzu.probe(kudzu.BUS_UNSPEC, kudzu.CLASS_UNSPEC, kudzu.PROBE_SAFE)
print d

The network section will look something like this:

, Desc:           Lite-On|LNE100TX
Driver:         tulip
Device:         eth

Shouldn't kudzu should return 'eth0', 'eth1', etc the same way that it returns
'fd0', or 'hdb'?  Changing component to kudzu.
Comment 2 Bill Nottingham 2003-01-22 16:26:36 EST
No, the 'device' field is just an indication of the device prefix;
'eth' for ethernet, 'tr' for token-ring.
Comment 3 Brent Fox 2003-01-22 16:56:55 EST
But doesn't something like 'hdc' tell you more than the device prefix?  It's
telling you not just that the device is a hard drive, but that it is the third
hard drive on the IDE bus.  

Although I guess that 'eth0' isn't really the hardware device name the way that
'hdc' is.  Rather, it's just the interface name that the OS has assigned to that
hardware device.  

I don't think that there's much I can do about this in any kind of clean way.  I
could take the data that kudzu provides and then try to find a match on the
driver in /etc/modules.conf, but what if I have two cards that use the same
driver?  /etc/modules.conf can't tell me then which card is eth0 and which is
eth1.  I'm reluctantly closing as 'wontfix'.  This bothers me, but I don't see
what I can really do about it.  If you have a better idea, please reopen this

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