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. The aim is to be compatible with tools, configurations and
indexes from module-init-tools project.

Source Files (show merged sources derived from linked package)
Filename Size Changed Actions
0002-modprobe-Recognize-allow-unsupported-modules-on-comm.patch 0000001138 1.11 KB about 1 year
0003-libkmod-config-Recognize-allow_unsupported_modules-i.patch 0000000928 928 Bytes about 1 year
0009-libkmod-Implement-filtering-of-unsupported-modules-o.patch 0000003400 3.32 KB about 1 year
0010-modprobe-Implement-allow-unsupported-modules.patch 0000003261 3.18 KB about 1 month
0011-Do-not-filter-unsupported-modules-when-running-a-van.patch 0000001510 1.47 KB about 1 year
0012-modprobe-print-unsupported-status.patch 0000002423 2.37 KB about 1 year
kmod-27.tar.sign 0000000833 833 Bytes about 1 month
kmod-27.tar.xz 0000548924 536 KB about 1 month
kmod-testsuite.changes 0000005296 5.17 KB about 1 year
kmod-testsuite.spec 0000002992 2.92 KB about 1 month
kmod.changes 0000021134 20.6 KB about 1 month
kmod.spec 0000005556 5.43 KB about 1 month
Comments for kmod 2

Luciano Santos's avatar

luc14n0 wrote over 2 years ago

Why are we using /usr/include/kmod/? The standard location across the major distros is /usr/include/. Only openSUSE and NixOS (that I know so far) use a subdirectory under the include directory to place its header files. I just had to patch an app because of that, now I don't even know if a change upstream to maybe use a var to store the libkmod.h location will be accepted.

Jan Engelhardt's avatar

jengelh wrote over 2 years ago

To flag all apps that fail to use pkg-config to discover the paths.