On Mon, 2009-11-09 at 10:21 +0000, Alan Jenkins wrote: > 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? The initial reason for this is for split module trees as used e.g. by an installer - so you might need to provide (kernel specific) drivers that aren't in the usual location, but instead in a tmpfs after the installer read them in from individual driver disks. This is the case for Fedora and RHEL, and probably other distributions. > Incentive: if you outline how this will be used, I could write a test > case for it :-). I will send an example. Also, I'm really glad to see your work on symbol sorting going in upstream. Thanks for your hard work! Jon. -- 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
