As per bug #401899, sys-kernel/dracut should use virtual/modutils instead of sys-apps/module-init-tools. Reproducible: Always
Are kmod tools fully compatible with module-init-tools?
(In reply to comment #1) > Are kmod tools fully compatible with module-init-tools? From http://git.profusion.mobi/cgit.cgi/kmod.git/tree/README: "kmod is a set of tools to handle common tasks with Linux kernel modules like insert, remove, list, check properties, resolve dependencies and aliases. These tools are designed on top of libkmod, a library that is shipped with kmod. See libkmod/README for more details on this library and how to use it. The aim is to be compatible with tools, configurations and indexes from module-init-tools project." In http://git.profusion.mobi/cgit.cgi/kmod.git/tree/TODO they specify some things where kmod differs from module-init-tools on purpose: modprobe -------- * 'modprobe -l' was marked as deprecated and does not exist anymore * 'modprobe -t' is gone, together with 'modprobe -l' * there's and additional '--remove-dependencies' flags to kmod-modprobe so we can remove modules depending on that one * kmod-modprobe doesn't parse configuration files whose name don't end on '.alias' or '.conf'. modprobe used to warn about these files. * kmod-modprobe doesn't parse 'config' and 'include' commands in configuration files. * we don't use <module-dir>/modules.builtin{,.bin} indexes. Instead we rely on module appearing on /sys/modules/* without a initstate file to determine if it is builtin. * modprobe from m-i-t does not honour softdeps for install commands. E.g.: config: install bli "echo bli" install bla "echo bla" softdep bla pre: bli With m-i-t, the output of 'modprobe --show-depends bla' will be: install "echo bla" While with kmod: install "echo bli" install "echo bla" * kmod doesn't dump the configuration as is in the config files. Instead it dumps the configuration as it was parsed. Therefore, comments and file names are not dumped, but on the good side we know what the exact configuration kmod is using. We did this because if we only want to know the entire content of configuration files, it's enough to use find(1) in modprobe.d directories depmod ------ * there's no 'depmod -m' option: legacy modules.*map files are gone lsmod ----- * information is parsed from /sys instead of /proc/modules
OK, thanks. Looks promising. I'll test dracut later if it can be used with kmod tools, to be sure.
I have changed this already, but have not yet test how dracut behaves with kmod tools. It shouldn't cause much harm, because module-init-tools is by default pulled by this virtual.
Works for me, although I compile all my modules in-kernel.
Dracut depends on module-init-tools or >kmod-5[tools] explicitly instead of virtual/modutils.
kmod-9999 resolved this bug for me, here was my little odysse of it: https://forums.gentoo.org/viewtopic-p-6970756.html Please consider to backport kmod-5 or better push upstream to do a new release of kmod-6
Canek, thanks for the report. Canek, Ulenrich - thanks for testing. Ulenrich, I'm not kmod maintainer, ask base-system herd, please. Although better would be have this in 6 release, because I guess RHEL is going to depend on 6 or later, too.