Re: How does "alias ethX drivername" in modules.conf work?

[Mark Atwood <mra@pobox.com>]

Riley Williams <rhw@MemAlpha.CX> writes:
> 
>  > Described above.
> 
> What KERNEL problems then? I don't see any yet.

I smell the stench of finger pointing. It's a pity that it stinks jsut
as bad in the open source world as it is I am "privileged" when closed
source shops, or (even worse) telco/network folks start playing
"blameball".

Userspace init scripts point the finger at kernel, saying "there is no
good and no well documented mapping method". Kernel points its finger
at userspace, saying "this is the way we do it" and "we cant guarantee
a perfect 100% mapping solution, so we're not even going to try for
90%" and "futz with your drivers and modules.conf and init scripts
till you get something that works".

Fingers back and forth, fingers pointing all around

and those of us with lots of different interfaces, and
those of us with several hot-plug interfaces

What happens to us?

We get the finger.

-- 
Mark Atwood   | I'm wearing black only until I find something darker.
mra@pobox.com | http://www.pobox.com/~mra