Differences between current version and previous revision of ModuleInitTools.
Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 9 | Last edited on Saturday, May 27, 2006 10:36:07 pm | by AristotlePagaltzis | |
| Older page: | version 8 | Last edited on Saturday, May 27, 2006 10:35:28 pm | by AristotlePagaltzis | Revert |
@@ -5,8 +5,8 @@
You might have ModuleInitTools already installed without knowing it. The ModuleInitTools can coexist with modutils on the same machine. The old modutils binaries will have <tt>.old</tt> (or <tt>.modutils</tt> for DebianLinux users) appended to their names, and will be called by the ModuleInitTools equivalents if a 2.4 series [Kernel] is detected. Most modern distributions are already set up this way. If this is the case then the <tt>make moveold</tt> target of the ModuleInitTools MakeFile will __destroy your setup!__ The <tt>make install</tt> target is harmless, you can use it to upgrade your ModuleInitTools without affecting the old modutils.
!! Indications that ModuleInitTools are already installed
-* There is a <tt>modprobe.old<tt> or <tt>modprobe.modutils</tt> binary in your path.
+* There is a <tt>modprobe.old</
tt> or <tt>modprobe.modutils</tt> binary in your path.
* There is a <tt>man modprobe.old</tt> (or <tt>modprobe.modutils</tt>) page.
* <tt>depmod --version</tt> displays "<tt>module-init-tools ...</tt>"
* <tt>depmod --help</tt> displays two sets of usage messages. (One for ModuleInitTools and one for modutils.)
