1 |
On Tue, Aug 16, 2016, at 18:20 CDT, William Hubbs <williamh@g.o> wrote: |
2 |
|
3 |
> All, |
4 |
> |
5 |
> I have received a request to implement a feature in OpenRC to allow |
6 |
> multiple software packages to drop files in a directory, /etc/modules.d |
7 |
> for example, which would define modules the /etc/init.d/modules script |
8 |
> would load. |
9 |
|
10 |
What about /etc/modules-load.d containing various files that list one |
11 |
module to load per line? With this, OpenRC's behavior would be |
12 |
compatible with systemd-modules-load [1]. |
13 |
|
14 |
Best, |
15 |
Matthias |
16 |
|
17 |
|
18 |
|
19 |
[1] To quote systemd's manpage: |
20 |
|
21 |
NAME |
22 |
modules-load.d - Configure kernel modules to load at boot |
23 |
|
24 |
SYNOPSIS |
25 |
/etc/modules-load.d/*.conf |
26 |
|
27 |
/run/modules-load.d/*.conf |
28 |
|
29 |
/usr/lib/modules-load.d/*.conf |
30 |
|
31 |
DESCRIPTION |
32 |
systemd-modules-load.service(8) reads files from the above |
33 |
directories which contain kernel modules to load during boot in a |
34 |
static list. Each configuration file is named in the style of |
35 |
/etc/modules-load.d/program.conf. Note that it is usually a |
36 |
better idea to rely on the automatic module loading by PCI IDs, |
37 |
USB IDs, DMI IDs or similar triggers encoded in the kernel |
38 |
modules themselves instead of static configuration like this. In |
39 |
fact, most modern kernel modules are prepared for automatic |
40 |
loading already. |
41 |
|
42 |
CONFIGURATION FORMAT |
43 |
The configuration files should simply contain a list of kernel |
44 |
module names to load, separated by newlines. Empty lines and |
45 |
lines whose first non-whitespace character is # or ; are |
46 |
ignored. |