Bug#224645: netcfg wishlists, udhcpc|pump, intend /etc/network/interfaces

[Gaudenz Steinlin <gaudenz@soziologie.ch>]

reassign 224645 discover
severity 224645 normal
retitle 224645 do not sort modules before loading
Thanks

Am Die, den 23.12.2003 schrieb Martin Michlmayr um 11:03:
> * Gaudenz Steinlin <gaudenz@soziologie.ch> [2003-12-21 12:10]:
> > > After boot, eth0 and eth1 suddenly changed!  I told debian-installer to use
> > > eth1 (the 3Com) for DHCP, but after reboot the 3Com was suddenly eth0!
> > Do you have any clue why this happened? This sounds like nasty problem
> > with module loading order...
> 
> Ok, I did some more debugging and found why this happens.  discover
> recognizes the devices in the same order all the time.  However, while
> hw-detect honours that order, after boot /etc/init.d/discover sorts
> the modules in order to eliminate duplicates:
> 
>   MODULES=$(discover --module $ARGUMENTS | sort -u)
> 
> So while "discover --module all" reports:
> 
> via-rhine
> 3c59x
> 
> They are in fact loaded in reverse order after the sort.
I'm not sure what's the best way to solve this. I tend to think this is
really a kernel bug. The assignment of netdevices should not depend on
the order the modules are loaded. But this is probably not easy to
fix...

I think the easiest way to solve this is to not sort the modules in
/etc/init.d/discover. 

BTW as I'm also the new co-maintainer of discover this is not an attempt
to move the problem out of my way with cheap arguments :-)

Gaudenz