On Monday 28 January 2008 14:20:10 Jon Masters wrote: > 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. Please bear in mind that modules.alias is a (cimpletely undocumented) internal module utilities detail: in theory modprobe is reading all the aliases out of modules themselves (that's too slow, since nowdays probe-by-alias is the common case). So since this is a temporary hack anyway, I think backwards is fine. Cheers, Rusty. - 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
