bardo wrote: > What I mean is that I find nonsense (semantically speaking) having to > write "!module module".
Ya, looks silly and might be confusing, but if you know how it works, it makes sense. > It'd be nice to have hwdetect loading the > modules in the order it finds them. Frankly, I always thought it was > acting this way, and I relied on this wrong assumption. The point is that hwdetect isn't responsible for loading modules any more. It seems that it was a temporary solution until udev had its own coldplugging capabilities (hwdetect is still used in mkinitrd script). Udev is much faster in loading the modules than hwdetect, because it loads modules in parallel. This way you can never predict which device registers with the kernel first and thus becomes "eth0". This is why I like the possibility of giving your network interfaces persistant names, because then it does not matter at all in which order something is loaded, everything _always_ stays consistent (even if you remove your first network card, the second will have the same name). Maybe we should add a prototype custom rule file to udev which includes typical rules and some explanations, so customization is easier for the "non-udev guru". _______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
