Re: howto Name eth[0 .. n-1] in kernel 2.4.18 vs earlier kernels?

[Isaac To <kkto@csis.hku.hk>]

>>>>> "Stephen" == Stephen Gran <gashuffer09@comcast.net> writes:

    Stephen> It's the same as in earlier kernels - you create a file under
    Stephen> /etc/modutils/ (mine is ethernet) with lines like: alias eth0
    Stephen> 3c59x alias eth1 8139too

But... this is not an entirely satisfactory answer.  The problem is that if
somehow the kernel load the 8139too first, it will take eth0 as the network
address.  This happens to one of a Redhat system that I've installed.  I
don't know whether it will happen on Debian as well, because after that I've
made a work-around.

You can imagine the following situation: when there were no network (and no
network module loaded), somehow eth1 is needed (probably because
/etc/init.d/ppp and /etc/init.d/network are executed in the reverse order,
but really dunno why this can happen).  In the above config, "modprobe eth1"
is invoked, 8139too.o gets loaded, but it loads into eth0!  And after that,
eth1 is still unavailable...

My workaround is a module dependency:

  alias eth0 3c59x
  alias eth1 8139too
  below 8139too 3c59x

But this is ugly... why I always need 3c59x when I need 8139too?  Anyway,
this is something that will happen for 99.999999% of the time, so after
making the workaround I ignored that.  It seems that "nameif" can be used to
name network interfaces based on MAC addresses, which would be much more
reasonable.  However, I didn't find the correct place to call the script.
If anyone can, please enlighten me on that one...

Regards,
Isaac.


-- 
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org