| 1 |
On 08/16/2016 07:20 PM, William Hubbs wrote: |
| 2 |
> All, |
| 3 |
> |
| 4 |
> I have received a request to implement a feature in OpenRC to allow |
| 5 |
> multiple software packages to drop files in a directory, /etc/modules.d |
| 6 |
> for example, which would define modules the /etc/init.d/modules script |
| 7 |
> would load. |
| 8 |
> |
| 9 |
> The design I'm thinking of would not change the use of |
| 10 |
> /etc/conf.d/modules, but the entries from the files would be added to |
| 11 |
> the appropriate module lists after the ones listed there. |
| 12 |
> |
| 13 |
> I'll write more about the design as I get closer to formulating the |
| 14 |
> details, but at this point I just want to know what others thinkabout |
| 15 |
> this feature. |
| 16 |
> |
| 17 |
> Thanks, |
| 18 |
> |
| 19 |
> William |
| 20 |
> |
| 21 |
|
| 22 |
Just a side note on how I currently take advantage of the modules |
| 23 |
initscript: |
| 24 |
|
| 25 |
I have several symlinks, one for each set of modules that I want to |
| 26 |
control. Then I create a corresponding conf.d based off of the modules |
| 27 |
conf.d. So, for example, /etc/init.d/vbox-modules->/etc/init.d/modules |
| 28 |
just controls the vbox modules. This gives me fine control over module |
| 29 |
sets without having to worry about all of them at once. I can have |
| 30 |
certain sets of modules start in different runlevels, and I can |
| 31 |
independently load and unload sets of modules when necessary. |
| 32 |
|
| 33 |
If you do end up switching to some system that reads a directory, I'd |
| 34 |
like to see something that if the name of the initscript isn't modules, |
| 35 |
it sources just the corresponding file, rather than the whole dir. |
| 36 |
|
| 37 |
-- |
| 38 |
NP-Hardass |
Archives