We may actually provide an alternative implementation in kmod that works better than what module-init-tools provided, but no one had enough interest to implement it yet.
By the way, AFAIR this was usually used to check "where is the file for kernel module XYZ?" This can be better done by modinfo.
Posted Dec 17, 2012 9:46 UTC (Mon) by gfa (subscriber, #53331)
[Link]
i remember that feature being deprecated (but worked) on module-init-tools
can you tell me why it was deprecated? what was the issue with it? i only saw the deprecation notice, but never the rationale behind
thanks
The eudev project launches
Posted Dec 18, 2012 7:38 UTC (Tue) by jamesh (guest, #1159)
[Link]
You could read the man page, which states "This option is provided for backwards compatibility and may go away in future: see find(1) and basename(1) for a more flexible alternative".
So presumably they felt it was better to direct people to use standard shell tools.
modprobe -l replacement
Posted Dec 19, 2012 5:04 UTC (Wed) by pr1268 (subscriber, #24648)
[Link]
For those who need a non-deprecated version: the shell command
albeit in a different sort order (at least on my laptop). I'm unsure where basename(1) fits into all this.
The eudev project launches
Posted Dec 17, 2012 10:50 UTC (Mon) by zuki (subscriber, #41808)
[Link]
> By the way, AFAIR this was usually used to check "where is the file for
> kernel module XYZ?" This can be better done by modinfo.
I don't think so: most people (me included) use it to generate a list of modules or to remind oneself about the name of some module. Using 'find' is of course possible, but much less convenient.