Commit 83bf06e8 authored by Rusty Russell's avatar Rusty Russell Committed by Linus Torvalds

[PATCH] Remove modules.txt

Thanks to Stephen Hemminger for pointing out how obsolete modules.txt is.

modules.txt contains mainly ancient information which is replicated
in the kconfig help message, README, makefile.txt or the modprobe manual
page.  The only part which is not covered elsewhere is the "building
external modules" which is still being debated (and belongs under the
kbuild docs).  kmod.txt reference removed from index, too.
parent a04e856a
...@@ -116,8 +116,6 @@ kernel-docs.txt ...@@ -116,8 +116,6 @@ kernel-docs.txt
- listing of various WWW + books that document kernel internals. - listing of various WWW + books that document kernel internals.
kernel-parameters.txt kernel-parameters.txt
- summary listing of command line / boot prompt args for the kernel. - summary listing of command line / boot prompt args for the kernel.
kmod.txt
- info on the kernel module loader/unloader (kerneld replacement).
ldm.txt ldm.txt
- a brief description of LDM (Windows Dynamic Disks). - a brief description of LDM (Windows Dynamic Disks).
locks.txt locks.txt
...@@ -144,8 +142,6 @@ mkdev.cciss ...@@ -144,8 +142,6 @@ mkdev.cciss
- script to make /dev entries for SMART controllers (see cciss.txt) - script to make /dev entries for SMART controllers (see cciss.txt)
mkdev.ida mkdev.ida
- script to make /dev entries for Intelligent Disk Array Controllers. - script to make /dev entries for Intelligent Disk Array Controllers.
modules.txt
- short guide on how to make kernel parts into loadable modules
moxa-smartio moxa-smartio
- info on installing/using Moxa multiport serial driver. - info on installing/using Moxa multiport serial driver.
mtrr.txt mtrr.txt
......
This diff is collapsed.
...@@ -204,15 +204,22 @@ menu "Loadable module support" ...@@ -204,15 +204,22 @@ menu "Loadable module support"
config MODULES config MODULES
bool "Enable loadable module support" bool "Enable loadable module support"
help help
Kernel modules are small pieces of compiled code which can be Kernel modules are small pieces of compiled code which can
inserted in or removed from the running kernel, using the programs be inserted in the running kernel, rather than being
insmod and rmmod. This is described in the file permanently built into the kernel. You use the "modprobe"
<file:Documentation/modules.txt>, including the fact that you have tool to add (and sometimes remove) them. If you say Y here,
to say "make modules" in order to compile the modules that you chose many parts of the kernel can be built as modules (by
during kernel configuration. Modules can be device drivers, file answering M instead of Y where indicated): this is most
systems, binary executable formats, and so on. If you think that you useful for infrequently used options which are not required
may want to make use of modules with this kernel in the future, then for booting. For more information, see the man pages for
say Y here. If unsure, say Y. modprobe, lsmod, modinfo, insmod and rmmod.
If you say Y here, you will need to run "make
modules_install" to put the modules under /lib/modules/
where modprobe can find them (you may need to be root to do
this).
If unsure, say Y.
config MODULE_UNLOAD config MODULE_UNLOAD
bool "Module unloading" bool "Module unloading"
...@@ -251,21 +258,18 @@ config MODVERSIONS ...@@ -251,21 +258,18 @@ config MODVERSIONS
compiled for different kernels, by adding enough information compiled for different kernels, by adding enough information
to the modules to (hopefully) spot any changes which would to the modules to (hopefully) spot any changes which would
make them incompatible with the kernel you are running. If make them incompatible with the kernel you are running. If
you say Y here, you will need a copy of genksyms. If
unsure, say N. unsure, say N.
config KMOD config KMOD
bool "Kernel module loader" bool "Automatic kernel module loading"
depends on MODULES depends on MODULES
help help
Normally when you have selected some drivers and/or file systems to Normally when you have selected some parts of the kernel to
be created as loadable modules, you also have the responsibility to be created as kernel modules, you must load them (using the
load the corresponding modules (using the programs insmod or "modprobe" command) before you can use them. If you say Y
modprobe) before you can use them. If you say Y here however, the here, some parts of the kernel will be able to load modules
kernel will be able to load modules for itself: when a part of the automatically: when a part of the kernel needs a module, it
kernel needs a module, it runs modprobe with the appropriate runs modprobe with the appropriate arguments, thereby
arguments, thereby loading the module if it is available. (This is a loading the module if it is available. If unsure, say Y.
replacement for kerneld.) Say Y here and read about configuring it
in <file:Documentation/kmod.txt>.
endmenu endmenu
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment