1 |
On 08/17/2016 12:54 PM, William Hubbs wrote: |
2 |
> All, |
3 |
> |
4 |
> I'm starting this thread because of the bug I'm citing below [1]. |
5 |
> |
6 |
> The issue is that some systems do not use kernel modules, and do not |
7 |
> have kmod installed at all. Since we run modprobe unconditionally in a |
8 |
> few places in OpenRC, we always generate "modprobe: command not found" |
9 |
> errors on systems which are set up like this. |
10 |
> |
11 |
> If you read the bug, the proposed fixes have been a bit controversial in |
12 |
> the past. Since we have the "want" dependency now, I would like to |
13 |
> propose a different fix. |
14 |
> |
15 |
> 1. all of the current openrc services that use modprobe should have |
16 |
> "want modules" in their dependencies. |
17 |
> 2. After this is done, these services should still attempt to load the |
18 |
> modules if necessary, but they should complain to the user about it and |
19 |
> recommend either building these modules in or using /etc/conf.d/modules |
20 |
> to configure them so they are loaded by the modules service. |
21 |
> 3. Then, at some point in the future, OpenRC could remove the modprobe |
22 |
> commands. |
23 |
> |
24 |
> Thoughts? |
25 |
> |
26 |
> William |
27 |
> |
28 |
> [1] https://bugs.gentoo.org/show_bug.cgi?id=342313 |
29 |
> |
30 |
|
31 |
As a gentoo user, developing a gentoo framework for rapid and frequent |
32 |
(and yes unattended installs) on heterogeneous gentoo clusters, I think |
33 |
Comment 8 says it all, repeat here for convenience:: |
34 |
|
35 |
Comment 8 <partial> |
36 |
"There are people for which having module-init-tools is just a waste of |
37 |
space/time/build; we force it already enough with the profile, you don't |
38 |
want to test for it everywhere, you don't want to hide output, tell me |
39 |
what you want, so I can make it, but I don't want module-init-tools |
40 |
forced in on LXC/xen/monolithic installs." |
41 |
|
42 |
+1, |
43 |
|
44 |
I rarely use loadable kernel modules, for my cluster builds. In fact I |
45 |
migrating to a large variety of complete stage-4 images for gentoo |
46 |
clusters, that are very use specific, highly tuned and minimized, |
47 |
including openrc, the base profile and old codes necessary for the work |
48 |
at hand, for the target hardware node. |
49 |
|
50 |
|
51 |
hth, |
52 |
James |