On Tue, 13 Feb 2001, Andrew Morton wrote:
Thanks Andrew, I appreciate your note. I'll try it again with 509 as a module.
I had forgotten about linkage order problems.
> al goldstein wrote:
> >
> > I have 2 ether cards 59x (eth0) and 509 (eth1). I have been adding 509
> > at boot in lilo.conf. Using this same config in 2.4.1 results in
> > the hardware addresses for the cards to be swapped. If I remove 509 from
> > Lilo I get the same result. Suggestions would be appreciated
>
> 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 [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
