LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
* Device naming randomness (udev?)
@ 2006-12-03 22:39 Martin J. Bligh
  2006-12-03 23:12 ` Björn Steinbrink
  2006-12-03 23:23 ` Tony Breeds
  0 siblings, 2 replies; 5+ messages in thread
From: Martin J. Bligh @ 2006-12-03 22:39 UTC (permalink / raw)
  To: Linux Kernel Mailing List; +Cc: Greg Kroah-Hartman

This PC has 1 ethernet interface, an e1000. Ubuntu Dapper.

On 2.6.14, my e1000 interface appears as eth0.
On 2.6.15 to 2.6.18, my e1000 interface appears as eth1.

In both cases, there are no other ethX interfaces listed in
"ifconfig -a". There are no modules involved, just a static
kernel build.

Is this a bug in udev, or the kernel? I'm presuming udev,
but seems odd it changes over a kernel release boundary.
Any ideas on how I get rid of it? Makes automatic switching
between kernel versions a royal pain in the ass.

M.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Device naming randomness (udev?)
  2006-12-03 22:39 Device naming randomness (udev?) Martin J. Bligh
@ 2006-12-03 23:12 ` Björn Steinbrink
  2006-12-06  5:49   ` Greg KH
  2006-12-03 23:23 ` Tony Breeds
  1 sibling, 1 reply; 5+ messages in thread
From: Björn Steinbrink @ 2006-12-03 23:12 UTC (permalink / raw)
  To: Martin J. Bligh; +Cc: Linux Kernel Mailing List, Greg Kroah-Hartman

On 2006.12.03 14:39:44 -0800, Martin J. Bligh wrote:
> This PC has 1 ethernet interface, an e1000. Ubuntu Dapper.
> 
> On 2.6.14, my e1000 interface appears as eth0.
> On 2.6.15 to 2.6.18, my e1000 interface appears as eth1.
> 
> In both cases, there are no other ethX interfaces listed in
> "ifconfig -a". There are no modules involved, just a static
> kernel build.
> 
> Is this a bug in udev, or the kernel? I'm presuming udev,
> but seems odd it changes over a kernel release boundary.
> Any ideas on how I get rid of it? Makes automatic switching
> between kernel versions a royal pain in the ass.

Just a wild guess here... Debian's (and I guess Ubuntu's) udev rules
contain a generator for persistent interface name rules. Maybe these
start working with 2.6.15 and thus the switch (ie. the kernel would call
it eth0, but udev renames it to eth1).
The generated rules are written to
/etc/udev/rules.d/z25_persistent-net.rules on Debian, not sure if its
the same for Ubuntu. Editing/removing the rules should fix your problem.

HTH
Björn

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Device naming randomness (udev?)
  2006-12-03 22:39 Device naming randomness (udev?) Martin J. Bligh
  2006-12-03 23:12 ` Björn Steinbrink
@ 2006-12-03 23:23 ` Tony Breeds
  1 sibling, 0 replies; 5+ messages in thread
From: Tony Breeds @ 2006-12-03 23:23 UTC (permalink / raw)
  To: Martin J. Bligh; +Cc: Linux Kernel Mailing List, Greg Kroah-Hartman

On Sun, Dec 03, 2006 at 02:39:44PM -0800, Martin J. Bligh wrote:
> This PC has 1 ethernet interface, an e1000. Ubuntu Dapper.
> 
> On 2.6.14, my e1000 interface appears as eth0.
> On 2.6.15 to 2.6.18, my e1000 interface appears as eth1.
> 
> In both cases, there are no other ethX interfaces listed in
> "ifconfig -a". There are no modules involved, just a static
> kernel build.
> 
> Is this a bug in udev, or the kernel? I'm presuming udev,
> but seems odd it changes over a kernel release boundary.
> Any ideas on how I get rid of it? Makes automatic switching
> between kernel versions a royal pain in the ass.

Have a look at /etc/iftab.

Yours Tony

   linux.conf.au       http://linux.conf.au/ || http://lca2007.linux.org.au/
   Jan 15-20 2007      The Australian Linux Technical Conference!


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Device naming randomness (udev?)
  2006-12-03 23:12 ` Björn Steinbrink
@ 2006-12-06  5:49   ` Greg KH
  2006-12-06  6:05     ` Martin J. Bligh
  0 siblings, 1 reply; 5+ messages in thread
From: Greg KH @ 2006-12-06  5:49 UTC (permalink / raw)
  To: Bj?rn Steinbrink, Martin J. Bligh, Linux Kernel Mailing List

On Mon, Dec 04, 2006 at 12:12:06AM +0100, Bj?rn Steinbrink wrote:
> On 2006.12.03 14:39:44 -0800, Martin J. Bligh wrote:
> > This PC has 1 ethernet interface, an e1000. Ubuntu Dapper.
> > 
> > On 2.6.14, my e1000 interface appears as eth0.
> > On 2.6.15 to 2.6.18, my e1000 interface appears as eth1.
> > 
> > In both cases, there are no other ethX interfaces listed in
> > "ifconfig -a". There are no modules involved, just a static
> > kernel build.
> > 
> > Is this a bug in udev, or the kernel? I'm presuming udev,
> > but seems odd it changes over a kernel release boundary.
> > Any ideas on how I get rid of it? Makes automatic switching
> > between kernel versions a royal pain in the ass.
> 
> Just a wild guess here... Debian's (and I guess Ubuntu's) udev rules
> contain a generator for persistent interface name rules. Maybe these
> start working with 2.6.15 and thus the switch (ie. the kernel would call
> it eth0, but udev renames it to eth1).
> The generated rules are written to
> /etc/udev/rules.d/z25_persistent-net.rules on Debian, not sure if its
> the same for Ubuntu. Editing/removing the rules should fix your problem.

Yes, I'd place odds on this one.

Martin, any followup?

thanks,

greg k-h

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Device naming randomness (udev?)
  2006-12-06  5:49   ` Greg KH
@ 2006-12-06  6:05     ` Martin J. Bligh
  0 siblings, 0 replies; 5+ messages in thread
From: Martin J. Bligh @ 2006-12-06  6:05 UTC (permalink / raw)
  To: Greg KH; +Cc: Bj?rn Steinbrink, Linux Kernel Mailing List, tony

Greg KH wrote:
> On Mon, Dec 04, 2006 at 12:12:06AM +0100, Bj?rn Steinbrink wrote:
>> On 2006.12.03 14:39:44 -0800, Martin J. Bligh wrote:
>>> This PC has 1 ethernet interface, an e1000. Ubuntu Dapper.
>>>
>>> On 2.6.14, my e1000 interface appears as eth0.
>>> On 2.6.15 to 2.6.18, my e1000 interface appears as eth1.
>>>
>>> In both cases, there are no other ethX interfaces listed in
>>> "ifconfig -a". There are no modules involved, just a static
>>> kernel build.
>>>
>>> Is this a bug in udev, or the kernel? I'm presuming udev,
>>> but seems odd it changes over a kernel release boundary.
>>> Any ideas on how I get rid of it? Makes automatic switching
>>> between kernel versions a royal pain in the ass.
>> Just a wild guess here... Debian's (and I guess Ubuntu's) udev rules
>> contain a generator for persistent interface name rules. Maybe these
>> start working with 2.6.15 and thus the switch (ie. the kernel would call
>> it eth0, but udev renames it to eth1).
>> The generated rules are written to
>> /etc/udev/rules.d/z25_persistent-net.rules on Debian, not sure if its
>> the same for Ubuntu. Editing/removing the rules should fix your problem.
> 
> Yes, I'd place odds on this one.

Huh. Somehow there was this entry in /etc/iftab:

eth0 mac 00:0d:61:44:90:12 arp 1

But that's not my mac address. Damned if I know how that got there, but
if the persistent rules only work on later kernels, that'd explain it.
And indeed ... removing that entry makes it work more normally.

Thanks for the pointers - most helpful.

M.



^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2006-12-06  6:09 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2006-12-03 22:39 Device naming randomness (udev?) Martin J. Bligh
2006-12-03 23:12 ` Björn Steinbrink
2006-12-06  5:49   ` Greg KH
2006-12-06  6:05     ` Martin J. Bligh
2006-12-03 23:23 ` Tony Breeds

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).