Ian Kent wrote: > > We probably have to accept that people doing insmod with a specific > path are going to have a problem and they shouldn't use that method > anyway. But, AFAICS using a MODULE_ALIAS() in the kernel module will > allow for the name change but doesn't seem to take account of the > directory name change. Is that correct? > I'm not sure what that's supposed to mean. Generally the directory a module appears in doesn't matter. > There are those that may have an alias in the module-init-tools > configuration as well. But we need get rid of that practice as well as, > for a long time now, the alias hasn't been needed. > > Anyone have any thoughts how we might better handle these difficulties? I suspect the MODULE_ALIAS should just do it. -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
