On Mon, 2008-01-28 at 10:45 +0900, Tejun Heo wrote: > Yeah, the alias file can be generated in reverse but I think it's better > to do things straight. It may cause some surprises (after upgrading > modprobe, the other driver is being loaded!) but IMHO we'll be better > off with forward-ordered aliases in the long run. After all, module > loading order was undefined anyway. I actually agree, in that the first entry is probably what people expect to get loaded, and that works well with things like Modules.order. I guess I'll just throw that together, since this wasn't defined anyway, and perhaps add a config option so you can reverse order if you want. Really we should all fix this through rebinding of loaded drivers. We're beyond the days of one driver per device, into the realm of SATA chipsets that also do "legacy", and much more funky stuff. A few of us are already looking at dynamic driver updates for "Enterprise" distros, and we have debated the rebinding issue. David Z. and I discussed using a GUI tool like the hal device manager to facilitate udev rule writing. It'll probably all happen at some point, hopefully before OLs :) Jon. - To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
