On 10/1/09, Jon Masters <jcm@xxxxxxxxxxxxxx> wrote: > Traditionally, kernel modules lived only in /lib/modules/<kernelversion>. In > the past, we added support for prioritized "update" directories within this > hierarchy so that distributions and their users could insert updates to > existing drivers and have those take precendence. But there are times when > it is also necessary to search a completely different * > (and kernel specific) * > directory, perhaps on a different filesystem, for module updates. > This patch introduces a new depmod.conf configuration option called > "path", which can be used in combination with the existing "search" > option to specify which directories will be searched before building > the kernel specific modules.dep and modules.dep.bin files. Paths are > searched in the order given, with preference within the path determined > by the value of the "search" option, allowing flexible configurations. > > Signed-off-by: Jon Masters <jcm@xxxxxxxxxxxxxx> I can't see the "kernel specific" part here, outside of the default "current-version" path. I don't see how you specify a custom path which is dependent on the kernel version. Could you please demonstrate it with an example? Incentive: if you outline how this will be used, I could write a test case for it :-). Thanks Alan -- To unsubscribe from this list: send the line "unsubscribe linux-modules" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
