[deployment-guide/comm-rel: 293/727] Updated the Loading a Module section.

[Jaromir Hradilek]

commit b7cb5254b6c75fadd45da2664357ebb9be2c68bb
Author: Jaromir Hradilek <jhradile at redhat.com>
Date:   Mon Aug 9 17:10:45 2010 +0200

    Updated the Loading a Module section.

 en-US/Working_with_Kernel_Modules.xml |   33 +++++++++++++++------------------
 1 files changed, 15 insertions(+), 18 deletions(-)
---
diff --git a/en-US/Working_with_Kernel_Modules.xml b/en-US/Working_with_Kernel_Modules.xml
index f0635b6..ecb798b 100644
--- a/en-US/Working_with_Kernel_Modules.xml
+++ b/en-US/Working_with_Kernel_Modules.xml
@@ -128,31 +128,28 @@ dm_mod                 73839  8 dm_mirror,dm_log</screen>
         <primary>kernel module</primary>
         <secondary>loading</secondary>
       </indexterm>
-      <para>To load a kernel module, use the <command>/sbin/modprobe</command> command followed by the kernel module name. By default, <command>modprobe</command> attempts to load the module from the <filename>/lib/modules/<replaceable>&lt;kernel-version&gt;</replaceable>/kernel/drivers/</filename> subdirectories. There is a subdirectory for each type of module, such as the <filename>net/</filename> subdirectory for network interface drivers. Some kernel modules have module dependencies, meaning that other modules must be loaded first for it to load. The <command>/sbin/modprobe</command> command checks for these dependencies and loads the module dependencies before loading the specified module.</para>
-      <para>For example, the command:</para>
-      <screen>~]#&#160;<command>/sbin/modprobe e100</command>
-      </screen>
-      <para>…first loads all module dependencies of the <systemitem
-          class="resource">e100</systemitem>
-   module before loading the <systemitem
-          class="resource">e100</systemitem>
-   module itself.</para>
-      <para>To print to the screen all commands as <command>/sbin/modprobe</command> executes them, use the <option>-v</option> option. For example:</para>
+      <para>To load a kernel module, use the <command>modprobe</command> command in the following form:</para>
+      <screen><command>/sbin/modprobe <replaceable>&lt;module&gt;</replaceable></command></screen>
+      <para>For example, to load the <systemitem class="resource">wacom</systemitem> module, type:</para>
+      <screen>~]#&#160;<command>modprobe wacom</command></screen>
+      <para>By default, <command>modprobe</command> attempts to load the module from <filename class="directory">/lib/modules/<replaceable>&lt;kernel-version&gt;</replaceable>/kernel/drivers/</filename>. In this directory, each type of module has its own subdirectory, such as <filename class="directory">net/</filename> for network interface drivers.</para>
+      <para>Some kernel modules have module dependencies, which means that other modules must be loaded first for them to load successfully. The <command>modprobe</command> command checks for these dependencies, and loads the required modules automatically so that you do not have to resolve the dependencies manually. This way, typing the <command>/sbin/modprobe e100</command> command first loads all dependencies of <systemitem class="resource">e100</systemitem>, and then the module itself.</para>
+      <para>To display all commands as <command>modprobe</command> executes them, use the <option>-v</option> option. For example:</para>
       <screen>~]#&#160;<command>/sbin/modprobe -v e100</command>
-      </screen>
-      <para>Output similar to the following is displayed:</para>
-      <screen>
-/sbin/insmod /lib/modules/2.6.33-5.EL/kernel/drivers/net/e100.ko
-Using /lib/modules/2.6.33-5.EL/kernel/drivers/net/e100.ko
-Symbol version prefix 'smp_'
-      </screen>
+insmod /lib/modules/2.6.32-54.el6.i686/kernel/drivers/net/mii.ko
+insmod /lib/modules/2.6.32-54.el6.i686/kernel/drivers/net/e100.ko</screen>
       <indexterm
         significance="normal">
         <primary>
           <command>insmod</command>
         </primary>
       </indexterm>
-      <para>The <command>/sbin/insmod</command> command can also be used to load kernel modules; however, it does not resolve dependencies. You should thus always use <command>/sbin/modprobe</command> instead of the <command>insmod</command> command to load kernel modules.</para>
+      <important>
+        <title>Important: Do Not Use <command>insmod</command> Directly</title>
+        <para>
+          Although the <command>/sbin/insmod</command> command can also be used to load kernel modules, it does not resolve dependencies. Because of this, you should always use <command>modprobe</command> instead.
+        </para>
+      </important>
     </section>
     <section
       id="s2-kernel-module-utils-rmmod">