summaryrefslogtreecommitdiffstats
path: root/Documentation/debugging-modules.txt
diff options
context:
space:
mode:
authorStephen Kitt <steve@sk2.org>2020-02-18 13:59:17 +0100
committerJonathan Corbet <corbet@lwn.net>2020-02-19 11:34:13 +0100
commit0317c5371e6a9b71a2e25b47013dd5c62d55d1a6 (patch)
tree975c9cd4db8d95da0704be704ef74314ea3dbac9 /Documentation/debugging-modules.txt
parentdocs: pretty up sysctl/kernel.rst (diff)
downloadlinux-0317c5371e6a9b71a2e25b47013dd5c62d55d1a6.tar.xz
linux-0317c5371e6a9b71a2e25b47013dd5c62d55d1a6.zip
docs: merge debugging-modules.txt into sysctl/kernel.rst
This fits nicely in sysctl/kernel.rst, merge it (and rephrase it) instead of linking to it. Signed-off-by: Stephen Kitt <steve@sk2.org> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Diffstat (limited to 'Documentation/debugging-modules.txt')
-rw-r--r--Documentation/debugging-modules.txt22
1 files changed, 0 insertions, 22 deletions
diff --git a/Documentation/debugging-modules.txt b/Documentation/debugging-modules.txt
deleted file mode 100644
index 172ad4aec493..000000000000
--- a/Documentation/debugging-modules.txt
+++ /dev/null
@@ -1,22 +0,0 @@
-Debugging Modules after 2.6.3
------------------------------
-
-In almost all distributions, the kernel asks for modules which don't
-exist, such as "net-pf-10" or whatever. Changing "modprobe -q" to
-"succeed" in this case is hacky and breaks some setups, and also we
-want to know if it failed for the fallback code for old aliases in
-fs/char_dev.c, for example.
-
-In the past a debugging message which would fill people's logs was
-emitted. This debugging message has been removed. The correct way
-of debugging module problems is something like this:
-
-echo '#! /bin/sh' > /tmp/modprobe
-echo 'echo "$@" >> /tmp/modprobe.log' >> /tmp/modprobe
-echo 'exec /sbin/modprobe "$@"' >> /tmp/modprobe
-chmod a+x /tmp/modprobe
-echo /tmp/modprobe > /proc/sys/kernel/modprobe
-
-Note that the above applies only when the *kernel* is requesting
-that the module be loaded -- it won't have any effect if that module
-is being loaded explicitly using "modprobe" from userspace.