[deployment-guide/comm-rel: 312/727] Moved the Persistent Module Loading section.

[Jaromir Hradilek]

commit 636feb1ee1fe5b5cf6787deafee162f015b389f3
Author: Jaromir Hradilek <jhradile at redhat.com>
Date:   Tue Aug 10 14:55:57 2010 +0200

    Moved the Persistent Module Loading section.

 en-US/Working_with_Kernel_Modules.xml |   60 ++++++++++++++++----------------
 1 files changed, 30 insertions(+), 30 deletions(-)
---
diff --git a/en-US/Working_with_Kernel_Modules.xml b/en-US/Working_with_Kernel_Modules.xml
index cdd1404..0a0790f 100644
--- a/en-US/Working_with_Kernel_Modules.xml
+++ b/en-US/Working_with_Kernel_Modules.xml
@@ -250,45 +250,45 @@ debug:Debug level (0=none,...,16=all)</screen>
       <screen>~]#&#160;<command>/sbin/modinfo -n e100</command>
 /lib/modules/2.6.32-54.el6.i686/kernel/drivers/net/e100.ko</screen>
     </section>
-  </section>
-  <section
-    id="s1-kernel-modules-persistent">
-    <title>Persistent Module Loading</title>
-    <indexterm>
-      <primary>kernel module</primary>
-      <secondary>persistent loading</secondary>
-    </indexterm>
-    <indexterm>
-      <primary>kernel module</primary>
-      <secondary>/etc/sysconfig/modules/</secondary>
-    </indexterm>
-    <para>As shown in the example in <xref linkend="s2-kernel-module-utils-lsmod" />, many kernel modules are loaded automatically at boot time. To specify additional modules to be loaded, you can create a <filename><replaceable>&lt;filename&gt;</replaceable>.modules</filename> file in the <filename class="directory">/etc/sysconfig/modules/</filename> directory. Note that as a shell script, it has to contain the interpreter directive such as <literal>#!/bin/sh</literal> on the first line, and it has to be executable.</para>
-    <note>
-      <title>Note</title>
-      <para>To make the script executable, type the following at a shell prompt:</para>
-      <screen>~]#&#160;<command>chmod 755 <replaceable>&lt;filename&gt;</replaceable>.modules</command></screen>
-    </note>
-    <para>For example, the following script loads the <systemitem class="resource">uinput</systemitem> module:</para>
-    <example
-      id="ex-bluez-uinput.modules">
-      <title>/etc/sysconfig/modules/bluez-uinput.modules</title>
+    <section
+      id="s2-kernel-modules-persistent">
+      <title>Persistent Module Loading</title>
+      <indexterm>
+        <primary>kernel module</primary>
+        <secondary>persistent loading</secondary>
+      </indexterm>
+      <indexterm>
+        <primary>kernel module</primary>
+        <secondary>/etc/sysconfig/modules/</secondary>
+      </indexterm>
+      <para>As shown in the example in <xref linkend="s2-kernel-module-utils-lsmod" />, many kernel modules are loaded automatically at boot time. To specify additional modules to be loaded, you can create a <filename><replaceable>&lt;filename&gt;</replaceable>.modules</filename> file in the <filename class="directory">/etc/sysconfig/modules/</filename> directory. Note that as a shell script, it has to contain the interpreter directive such as <literal>#!/bin/sh</literal> on the first line, and it has to be executable.</para>
+      <note>
+        <title>Note</title>
+        <para>To make the script executable, type the following at a shell prompt:</para>
+        <screen>~]#&#160;<command>chmod 755 <replaceable>&lt;filename&gt;</replaceable>.modules</command></screen>
+      </note>
+      <para>For example, the following script loads the <systemitem class="resource">uinput</systemitem> module:</para>
+      <example
+        id="ex-bluez-uinput.modules">
+        <title>/etc/sysconfig/modules/bluez-uinput.modules</title>
       <programlisting>#!/bin/sh
 
 if [ ! -c /dev/input/uinput ] ; then
         exec /sbin/modprobe uinput &gt;/dev/null 2&gt;&amp;1
 fi</programlisting>
-    </example>
-    <para>The <literal>if</literal> conditional statement on the third line ensures that the <filename>/dev/input/uinput</filename> file does <emphasis>not</emphasis> exist (the <literal>!</literal> symbol negates the condition), and, if that is the case, then executes <command>/sbin/modprobe</command> with the name of the kernel module to load—<systemitem class="resource">uinput</systemitem> in this example. The remainder of the line redirects any output to <filename>/dev/null</filename> so that the <command>modprobe</command> command remains quiet.</para>
-    <note
-      id="note-No_Need_to_Load_Network_and_SCSI_Modules">
-      <title>Note: Do Not Load Network and SCSI Modules</title>
-      <para>Networking and SCSI modules do not generally need to be manually loaded as they have their own particular loading mechanisms.</para>
-    </note>
+      </example>
+      <para>The <literal>if</literal> conditional statement on the third line ensures that the <filename>/dev/input/uinput</filename> file does <emphasis>not</emphasis> exist (the <literal>!</literal> symbol negates the condition), and, if that is the case, then executes <command>/sbin/modprobe</command> with the name of the kernel module to load—<systemitem class="resource">uinput</systemitem> in this example. The remainder of the line redirects any output to <filename>/dev/null</filename> so that the <command>modprobe</command> command remains quiet.</para>
+      <note
+        id="note-No_Need_to_Load_Network_and_SCSI_Modules">
+        <title>Note: Do Not Load Network and SCSI Modules</title>
+        <para>Networking and SCSI modules do not generally need to be manually loaded as they have their own particular loading mechanisms.</para>
+      </note>
+    </section>
   </section>
   <section
     id="s1-modules-parameters">
     <title>Kernel Module Parameters</title>
-    <para>This section lists modules used for a common hardware, and their respective parameters. Refer to <xref linkend="s2-kernel-module-utils-modprobe" /> for information on how to load them to the running kernel, and <xref linkend="s1-kernel-modules-persistent" /> for instructions on how to load them automatically at boot time. Note that to view parameters for a certain module, you can use the <command>modinfo</command> command as described in <xref linkend="s2-kernel-module-utils-modinfo" />.</para>
+    <para>This section lists modules used for a common hardware, and their respective parameters. Refer to <xref linkend="s2-kernel-module-utils-modprobe" /> for information on how to load them to the running kernel, and <xref linkend="s2-kernel-modules-persistent" /> for instructions on how to load them automatically at boot time. Note that to view parameters for a certain module, you can use the <command>modinfo</command> command as described in <xref linkend="s2-kernel-module-utils-modinfo" />.</para>
     <section
       id="s2-modules-scsi">
       <title>Storage Parameters</title>