| 1 |
Am 27.01.2013 03:24, schrieb Canek Peláez Valdés: |
| 2 |
> On Sat, Jan 26, 2013 at 6:15 PM, Florian Philipp <lists@×××××××××××.net> wrote: |
| 3 |
>> Hi list! |
| 4 |
>> |
| 5 |
>> Quick question: If I deactivate the kmod use flag in udev and keep |
| 6 |
>> sys-apps/module-init-tools, does udev still load modules or is kmod a |
| 7 |
>> required flag for that? |
| 8 |
> |
| 9 |
> I'm not 100% sure, but I don't think so. The git repository has not a |
| 10 |
> single instance of the strings "modprobe" or "insmod", apparently the |
| 11 |
> only way to load modules in udev is to use kmod. I think the kmod |
| 12 |
> configure option (which is the one the USE flag activate/deactivate), |
| 13 |
> is for systems where all the modules are built-in, like embedded ones. |
| 14 |
> |
| 15 |
|
| 16 |
Okay. I thought I've heard about some dev patching udev to work with |
| 17 |
modprobe at one point. Could be mistaken or outdated, though. |
| 18 |
|
| 19 |
> Unless udev has no other means to load modules, I think disabling kmod |
| 20 |
> assumes then that all the modules are built-in. And if you use |
| 21 |
> modules, may I ask why you would prefer module-init-tools over kmod? |
| 22 |
> Specially when the later is a drop-in, better supported replacement? |
| 23 |
> |
| 24 |
|
| 25 |
Is it really a drop-in? I was under the impression that for example |
| 26 |
`modprobe -l` is not implemented (mentioned in a comment on the eudev |
| 27 |
fork on LWN). I guess that's outdated as well. |
| 28 |
|
| 29 |
Thanks, |
| 30 |
Florian Philipp |
Archives