Messages in this thread | | | Date | Thu, 6 Sep 2007 09:35:51 -0400 | From | Bill Nottingham <> | Subject | Re: origin of __tmp1930643048 network device name: kernel-space or user-space |
| |
Jan Engelhardt (jengelh@computergmbh.de) said: > >dear all, > >I'm trying to track down a problem on a Sun V40Z server with 4 network > >devices grabbing random ethX device names. now, trying to force the > >device names to what I want, I got a __tmpXXXXX form of device name, > >which I think is a half-configured device... but which piece of > >software is to blame ??? kernel, udev, hotplug > > Look into dmesg. If the device was once known as ethX or similar, > then it is userspace to blame.
It's userspace.
<off-topic for l-k, but while I'm here...>
I'm assuming you're running some sort of Fedora/RHEL/ derivative; this is what you get when you have a device that starts out named ethX, but which needed to be renamed so that an already configured ethX could be changed to that name.
For the new device, either add a HWADDR in a ifcfg-ethX file for that interface, add something to /etc/mactab, or add a udev rule.
Bill - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |