Differences between version 8 and previous revision of ModuleInitTools.
Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 8 | Last edited on Saturday, May 27, 2006 10:35:28 pm | by AristotlePagaltzis | Revert |
| Older page: | version 7 | Last edited on Saturday, May 27, 2006 10:34:11 pm | by AristotlePagaltzis | Revert |
@@ -1,5 +1,5 @@
-The [module-init-tools | ftp://ftp.kernel.org/pub/linux/kernel/people/rusty/modules/] are a set of programs for loading, inserting, and removing [Kernel] [Module]s for [Linux] (versions 2.5.48 and above). It serves the same function that the <tt>modutils</tt> package serves for [Linux] 2.4. They are necessary because starting with 2.5.51, modules are handled differently. Every symbol of a module has versioning information, so that the [Kernel] can read the module and what hooks it uses, compare it to an internal database of what's critical and what's not, and decide whether the module can be used, even if it wasn't compiled specifically for the current running [Kernel]. This adds a lot more flexibility for people forced to run BinaryDrivers
.
+The [module-init-tools | ftp://ftp.kernel.org/pub/linux/kernel/people/rusty/modules/] are a set of programs for loading, inserting, and removing [Kernel] [Module]s for [Linux] (versions 2.5.48 and above). It serves the same function that the <tt>modutils</tt> package serves for [Linux] 2.4. They are necessary because starting with 2.5.51, modules are handled differently. Every symbol of a module has versioning information, so that the [Kernel] can read the module and what hooks it uses, compare it to an internal database of what's critical and what's not, and decide whether the module can be used, even if it wasn't compiled specifically for the current running [Kernel]. This adds a lot more flexibility for people forced to run BinaryDriver~s
.
!!! Installing ModuleInitTools – a word of Warning
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.
