1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
|
Features:
=========
* Protect index against OOM
* Implement actions in kmod tool like 'insert', 'remove', 'info', etc
* testsuite:
- when fake delete_module() succeeds, remove its entry from /sys/module
* Stop using system() inside the library and use fork + exec instead
* config: configs that do not need to be matched by fnmatch() could be using a
vector instead of a list. This way we could search in it by calling
bsearch().
* review API, maybe unify all of these getters:
- kmod_module_version_get_symbol()
- kmod_module_version_get_crc()
- kmod_module_symbol_get_symbol()
- kmod_module_symbol_get_crc()
- kmod_module_dependency_symbol_get_symbol()
- kmod_module_dependency_symbol_get_crc()
- kmod_module_versions_free_list()
- kmod_module_symbols_free_list()
- kmod_module_dependency_symbols_free_list()
* index: drop the "open(), seek(), read()" implementation and use another one
with mmap(). When lookup() is called and the file is not mmaped, mmap it.
* Finish removal of "rmmod -w" when it's gone from kernel.
* Deprecate not using KMOD_REMOVE_NOWAIT on libkmod.
Things to be added/removed in kernel (check what is really needed):
===================================================================
* list of currently loaded modules
- readdir() in /sys/modules: dir without a 'initstate' file means the
module is builtin.
* kill /proc/modules ?
- Unlikely, given other tools might depend on it
Things that are different from module-init-tools on purpose (!TODO)
===================================================================
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 modprobe so we
can remove modules depending on that one
* modprobe doesn't parse configuration files with names not ending in
'.alias' or '.conf'. modprobe used to warn about these files.
* modprobe doesn't parse 'config' and 'include' commands in configuration
files.
* 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
|
