All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Neakums <sneakums@zork.net>
To: linux-kernel@vger.kernel.org
Subject: Re: NICs trading places ?
Date: Fri, 28 Mar 2003 23:42:51 +0000	[thread overview]
Message-ID: <6ud6kbcb2c.fsf@zork.zork.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0303281626260.20589-100000@mooru.gurulabs.com> (Dax Kelson's message of "Fri, 28 Mar 2003 16:30:20 -0700 (MST)")

commence  Dax Kelson quotation:

> On Fri, 28 Mar 2003, Dave Jones wrote:
>
>> I just upgraded a box with 2 NICs in it to 2.5.66, and found
>> that what was eth0 in 2.4 is now eth1, and vice versa.
>> Is this phenomenon intentional ? documented ?
>> What caused it to do this ?
>
> I've seen the same thing for 5+ years.  Multiple things can 
> trigger it, eg:
>
> Always having your NIC drivers compiled in, and then moving between 
> different kernel versions.
>
> Going from modular NIC drivers to compiled in drivers can bite you.
>
> Isn't life fun.

Something I have been meaning to write as soon as I get bitten by this
myself is a script that uses the "ip link set X name Y" command
(possibly in conjuction with a MAC-to-name map, or else just a simple
sort) to name the interfaces consistently.

-- 
Sean Neakums - <sneakums@zork.net>

  reply	other threads:[~2003-03-28 23:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-28 22:10 NICs trading places ? Dave Jones
2003-03-28 22:14 ` Jeff Garzik
2003-03-28 22:15 ` jjs
2003-03-28 22:25 ` Joel Becker
2003-03-28 22:27   ` Randy.Dunlap
2003-03-28 22:34   ` Dave Jones
2003-03-28 22:48 ` Andries Brouwer
2003-03-28 23:02   ` Andrew Morton
2003-03-28 23:20     ` Andries Brouwer
2003-03-28 23:41       ` Greg KH
2003-03-28 23:56         ` Jeff Garzik
2003-03-29  0:03           ` Greg KH
2003-03-29  9:20   ` Marc Zyngier
2003-03-28 23:30 ` Dax Kelson
2003-03-28 23:42   ` Sean Neakums [this message]
     [not found] <20030328221037.GB25846@suse.de.suse.lists.linux.kernel>
2003-03-29  4:47 ` Andi Kleen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6ud6kbcb2c.fsf@zork.zork.net \
    --to=sneakums@zork.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.