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 - 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/
This archive was generated by hypermail 2b29 : Mon Mar 31 2003 - 22:00:33 EST