kmod package moved modinfo binary from /sbin to /usr/bin, but the module-init-tools bash completion script has /sbin/modinfo hard-coded. Reproducible: Always Steps to Reproduce: 1. install kmod 2. eselect bashcomp enable --global module-init-tools 3. modprobe snd <TAB> Actual Results: bash: /sbin/modinfo: No such file or directory Expected Results: list of possible module parameters, for example, for snd module, "cards_limit debug major slots" why not trust $PATH?
The alsaconf script also references /sbin/modinfo directly. Therefore, it might be a good idea to set-up a symbolic link from /sbin/modinfo to /usr/bin/kmod instead of changing other references throughout other packages.
(In reply to Howard B. Golden from comment #1) > The alsaconf script also references /sbin/modinfo directly. Therefore, it > might be a good idea to set-up a symbolic link from /sbin/modinfo to > /usr/bin/kmod instead of changing other references throughout other packages. alsaconf is no longer installed (it's incompatible with sys-apps/kmod because depmod from kmod doesn't generate modules.pcimap or .usbmap files) and kmod installs to / and modinfo to both /bin and /sbin futhermore I don't see the mentioned hardcoding in bash-completion-2.1-r1, or sys-apps/kmod-14-r1 anymore I think it's safe to close this as FIXED now
