[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.

1 files changed, 24 insertions, 20 deletions

diff --git a/init/Kconfig b/init/Kconfig
index 3831775f5a3a0f..205e0ccbde31bf 100644
--- a/init/Kconfig
+++ b/init/Kconfig
@@ -204,15 +204,22 @@ menu "Loadable module support"
 config MODULES
 	bool "Enable loadable module support"
 	help
-	  Kernel modules are small pieces of compiled code which can be
-	  inserted in or removed from the running kernel, using the programs
-	  insmod and rmmod. This is described in the file
-	  <file:Documentation/modules.txt>, including the fact that you have
-	  to say "make modules" in order to compile the modules that you chose
-	  during kernel configuration.  Modules can be device drivers, file
-	  systems, binary executable formats, and so on. If you think that you
-	  may want to make use of modules with this kernel in the future, then
-	  say Y here.  If unsure, say Y.
+	  Kernel modules are small pieces of compiled code which can
+	  be inserted in the running kernel, rather than being
+	  permanently built into the kernel.  You use the "modprobe"
+	  tool to add (and sometimes remove) them.  If you say Y here,
+	  many parts of the kernel can be built as modules (by
+	  answering M instead of Y where indicated): this is most
+	  useful for infrequently used options which are not required
+	  for booting.  For more information, see the man pages for
+	  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
 	bool "Module unloading"
@@ -251,21 +258,18 @@ config MODVERSIONS
 	  compiled for different kernels, by adding enough information
 	  to the modules to (hopefully) spot any changes which would
 	  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.
 
 config KMOD
-	bool "Kernel module loader"
+	bool "Automatic kernel module loading"
 	depends on MODULES
 	help
-	  Normally when you have selected some drivers and/or file systems to
-	  be created as loadable modules, you also have the responsibility to
-	  load the corresponding modules (using the programs insmod or
-	  modprobe) before you can use them. If you say Y here however, the
-	  kernel will be able to load modules for itself: when a part of the
-	  kernel needs a module, it runs modprobe with the appropriate
-	  arguments, thereby loading the module if it is available. (This is a
-	  replacement for kerneld.) Say Y here and read about configuring it
-	  in <file:Documentation/kmod.txt>.
+	  Normally when you have selected some parts of the kernel to
+	  be created as kernel modules, you must load them (using the
+	  "modprobe" command) before you can use them. If you say Y
+	  here, some parts of the kernel will be able to load modules
+	  automatically: when a part of the kernel needs a module, it
+	  runs modprobe with the appropriate arguments, thereby
+	  loading the module if it is available.  If unsure, say Y.
 
 endmenu