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

[Stuart Lynne <sl@fireplug.net>]

>  >>> Lets assume that eth0-eth3 are not initialized at boot time and
>  >>> your init scripts attempt to initialize eth4 ...
> 
> I gather that I misunderstood what you were saying above, so let me
> clarify what I now understand by your comments:
> 
>  1. You are assuming a broken set of init scripts. Specifically,
>     they load the individual modules manually by the name of the
>     module, rather than stating that you wish to initialise a
>     particular interface and letting kmod sort out the correct
>     module.
> 
>     If this is your assumption, then you've created an artificial
>     situation that by its very nature is broken and unreliable.
> 

>  >>> To avoid such problems one probably should add a lot of
>  >>> pre-install parameters in modules.conf.
> 
>  >> What problems?
> 
>  > Described above.
> 
> What KERNEL problems then? I don't see any yet.

So not being able to reliable map ethernet devices to names is a feature
not a bug .... 

It *should* be possible to reliably name devices without having to rely
on order dependant initialization.

-- 
                                            __O 
Lineo - For Embedded Linux Solutions      _-\<,_ 
PGP Fingerprint: 28 E2 A0 15 99 62 9A 00 (_)/ (_) 88 EC A3 EE 2D 1C 15 68
Stuart Lynne <sl@fireplug.net>         www.lineo.com         604-461-7532