1 |
On Wed, Aug 17, 2016 at 11:23:13PM -0700, Daniel Campbell wrote: |
2 |
> Is there a reliable way to test for kernel functionality _before_ |
3 |
> calling modprobe? I think if a service needs certain kernel |
4 |
> functionality then it should complain -- loudly, if needed -- so the |
5 |
> admin knows what to do, be it building the feature into the kernel or |
6 |
> facilitating a module. But I don't think modules should be required. I |
7 |
> generally don't enable things with M unless some technical situation |
8 |
> requires it. The only real module I have is the nvidia-drivers module |
9 |
> which takes care of itself. Everything else is built into my kernels. |
10 |
|
11 |
Yes, and we do that testing. What we do right now is, if that testing |
12 |
fails, we run modprobe to attempt to load the modules. That causes |
13 |
"modprobe: command not found" errors for systems that do not have kmod |
14 |
installed. |
15 |
|
16 |
I want to change what happens if the testing fails so that it loads the |
17 |
module, then complains to the admin letting them know that the module |
18 |
needs to be built in or loaded in /etc/conf.d/modules. |
19 |
|
20 |
In a future release, I will remove the module loading assuming that you |
21 |
have everything built in, configured in /etc/conf.d/modules, or your |
22 |
device manager is taking care of loading the modules. |
23 |
|
24 |
> lsmod and modprobe can handle modules -- what can be used to target |
25 |
> kernels that have functionality built-in? Not every system will have |
26 |
> /proc/config.gz support (though honestly I don't know why you wouldn't |
27 |
> want that). |
28 |
> |
29 |
> Hiding error or warning messages seems irresponsible to me and could |
30 |
> lead to confusion. So I guess I'm in favor overall, but don't want to |
31 |
> see lightweight installs lose anything or become forced to install |
32 |
> things as modules, as it complicates the kernel configuring process |
33 |
> needlessly. |
34 |
|
35 |
There's nothing to do if the kernel has the functionality built in, I |
36 |
just want to deprecate the behind-the-scenesloading of modules you don't |
37 |
know we are loading. |
38 |
|
39 |
William |