If both drivers are statically linked into the kernel then
I guess this is entirely dependent upon the linkage order of
net/core/dev.o and drivers/net/3c59x.o.
If you make the drivers modular then you can force the order
within your boot scripts.
If you make just one driver modular then that one will be
"eth1".
You can grab Andi's "nameif" app which allows you to rename
interfaces based on their MAC address, which will certainly
put and end to the issue. I'm not sure whether this
app is in net-tools yet.
Finally, you can wait until the Linux hotplug architecture
is fully implemented, after which the naming order will
be nicely randomised each time you boot :)
It's fun, isn't it?
-
-
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/