I setup `CONFIG_MODULES is not set` in order to disable support for module loading. As a consequence I unmerged `virtual/modutils` and `sys-apps/kmod` which results in complaints by various init scripts which can't find `/sbin/modprobe` anymore. Could we patch those scripts in order to validate if `modprobe` is available at all before calling it?
It seems like most init scripts check for special files in /dev, /sys, or /proc before calling modprobe. If you have the necessary stuff compiled into your kernel, modprobe should not get called at all. If you have examples where this is not the case, please provide them. You will probably need to file a separate bug for each package that installs them.
Ok, it makes sense to report an issue for each package individually. As an example - which hit me in that specific case - I'd like to name `/etc/init.d/procfs`: ``` procfs |/etc/init.d/procfs: line 18: modprobe: command not found ```
Adjusting summary and assigning to OpenRC team.
*** This bug has been marked as a duplicate of bug 342313 ***