mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Joel Becker <Joel.Becker@oracle.com>
Cc: davej@codemonkey.org.uk, linux-kernel@vger.kernel.org
Subject: Re: NICs trading places ?
Date: Fri, 28 Mar 2003 14:27:28 -0800	[thread overview]
Message-ID: <20030328142728.4f242f80.rddunlap@osdl.org> (raw)
In-Reply-To: <20030328222524.GK32000@ca-server1.us.oracle.com>

On Fri, 28 Mar 2003 14:25:25 -0800 Joel Becker <Joel.Becker@oracle.com> wrote:

| On Fri, Mar 28, 2003 at 10:10:37PM +0000, 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 ?
| 
| 	Is this a Red Hat system?  I encountered the same thing on a
| RHAS system.  Basically, Anaconda had controlled the module load order
| in /etc/modules.conf for 2.4.  Because my network drivers were built in
| in 2.5, they loaded in the order of the compile-in.  This turned out to
| be the reverse order.
| 	Swapping eth0 and eth1 in /etc/modules.conf fixed the problem
| for me.  This is not to say it is "Red Hat's fault" or that this is
| entirely the same situation, but I figured this would make a good
| datapoint.

I saw this same problem at home last night, not on a RH system,
so I think it's just a 2.5.lately thing.

--
~Randy

  reply	other threads:[~2003-03-28 22:20 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-28 22:10 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 [this message]
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
     [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=20030328142728.4f242f80.rddunlap@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=Joel.Becker@oracle.com \
    --cc=davej@codemonkey.org.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®