Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 582830 - sys-apps/openrc: procfs init script produces error message if modprobe is not installed
Summary: sys-apps/openrc: procfs init script produces error message if modprobe is not...
Status: RESOLVED DUPLICATE of bug 342313
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All Linux
: Normal normal
Assignee: OpenRC Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-12 13:23 UTC by hal
Modified: 2016-05-13 17:22 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description hal 2016-05-12 13:23:52 UTC
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?
Comment 1 Mike Gilbert gentoo-dev 2016-05-12 15:15:45 UTC
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.
Comment 2 hal 2016-05-12 20:39:50 UTC
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
```
Comment 3 Mike Gilbert gentoo-dev 2016-05-12 22:57:12 UTC
Adjusting summary and assigning to OpenRC team.
Comment 4 William Hubbs gentoo-dev 2016-05-13 17:22:13 UTC

*** This bug has been marked as a duplicate of bug 342313 ***