eth1 getting moved to eth0

[Michal Jaegermann]

On Fri, Sep 17, 2004 at 10:54:08AM -0700, Martin wrote:
> Sep 17 12:37:45 laptop ifup:
> Sep 17 12:37:45 laptop ifup: cannot change name of eth0 to eth1: Device
> or resource busy

I run into that in another context.  Some modules have a code which
prevents them from beeing unloaded.  If your statup will try first
the "wrong" module then you are stuck.

See
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=125916
and what Bill had then to say. :-)

One possible workaround is to put in /etc/modprobe.conf an 'install'
directive which looks somewhat like that

install "wrong module" modprobe eth0 && modprobe -i "wrong module"

where "wrong module" is that thing you want to see for eth1.
I had actually a situation of four network interfaces with three
different drivers where I wanted to ensure a particular order
and what was coming up was definitely not that; and confused.

I do not see a reason why 'install' directives similar to the
above could not be written in /etc/modprobe.conf "automagically",
as this does not harm anything when they are not strictly needed
and prevents a "ping-pong" of network interfaces on a startup,
but apparently the problem is not widespread enough.

Another possibility is to use 'nameif' and your own names for
network interfaces instead of eth0 and eth1.  See 'man nameif'
for details.  The catch is that you cannot rename interfaces
after they were brought up, so you have drop in your own startup
script which runs early enough (it would be nice if a support for
that was already present) and I have no idea how various 'sysconfig'
tools will react on "strange" names.  But you have an editor.


   Michal