Changeset c0d9af5

Timestamp:

03/25/2006 12:56:15 PM (18 years ago)

Author:

Manuel Canales Esparcia <manuel@…>

Children:

11d4252

Parents:

6d8d38c

Message:

Indentation and tagging fixes.

git-svn-id: ​http://svn.linuxfromscratch.org/LFS/branches/udev_update/BOOK@7456 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

File:

• chapter07/udev.xml (modified) (16 diffs)

chapter07/udev.xml

@@ -89 +89 @@
       available to userspace processes and to <command>udevd</command> for device
       node creation.</para>
+
     </sect3>
 
@@ -113 +114 @@
       have already been registered with the kernel by forcing them to raise
       hotplug events which <command>udevd</command> will then handle.</para>
+
     </sect3>
 
@@ -135 +137 @@
       rules configuration files are available in
       <filename>/usr/share/doc/udev-&udev-version;/index.html</filename></para>
+
     </sect3>
 
@@ -167 +170 @@
       <para>The kernel itself is also able to load modules for network
       protocols, filesystems and NLS support on demand.</para>
+
     </sect3>
 
@@ -176 +180 @@
       generates a hotplug event. This hotplug event is then handled by
       <command>udevd</command> as described above.</para>
+
     </sect3>
 
@@ -188 +193 @@
     <sect3>
       <title>A kernel module is not loaded automatically</title>
+
       <para>Udev will only load a module if it has a bus-specific alias and the
       bus driver properly exports the necessary aliases to <systemitem
@@ -202 +208 @@
       <filename class="directory">/sys/bus</filename> and check whether there is
       a <filename>modalias</filename> file there.</para>
-      
+
       <para>If the <filename>modalias</filename> file exists in <systemitem
       class="filesystem">sysfs</systemitem>, the driver supports the device and
@@ -214 +220 @@
       this bus type. With Linux-&linux-version;, this is the case with ISA and
       IDE busses. Expect this issue to be fixed in later kernel versions.</para>
-      
+
       <!-- Remove IDE from the list above after Linux-2.6.16 -->
 
@@ -220 +226 @@
       <emphasis>snd-pcm-oss</emphasis> and non-hardware drivers such as
       <emphasis>loop</emphasis> at all.</para>
+
     </sect3>
 
@@ -233 +240 @@
       wrapped module. To do this, add an <quote>install</quote> line in
       <filename>/etc/modprobe.conf</filename>. For example:</para>
-<screen role="nodump">install snd-pcm modprobe -i snd-pcm ; modprobe \
-    snd-pcm-oss ; true</screen>
-    
+
+<screen role="nodump"><literal>install snd-pcm modprobe -i snd-pcm ; modprobe \
+    snd-pcm-oss ; true</literal></screen>
+
       <para>If the module in question is not a wrapper and is useful by itself,
       configure the <command>S05modules</command> bootscript to load this
@@ -241 +249 @@
       <filename>/etc/sysconfig/modules</filename> file on a separate line.
       This works for wrapper modules too, but is suboptimal in that case.</para>
+
     </sect3>
 
@@ -249 +258 @@
       <filename>/etc/modprobe.conf</filename> file as done with the
       <emphasis>forte</emphasis> module in the example below:</para>
-<screen role="nodump">blacklist forte</screen>
+
+<screen role="nodump"><literal>blacklist forte</literal></screen>
 
       <para>Blacklisted modules can still be loaded manually with the
       explicit <command>modprobe</command> command.</para>
+
     </sect3>
 
@@ -263 +274 @@
       Increase the logging verbosity of Udev, find the offending rule by
       examining the logs and make it more specific.</para>
+
     </sect3>
 
     <sect3>
       <title>Udev rule works unreliably</title>
+
       <para>This may be another manifestation of the previous problem. If not,
       and your rule uses <systemitem class="filesystem">sysfs</systemitem>
@@ -273 +286 @@
       <systemitem class="filesystem">sysfs</systemitem> attribute and appending
       it to the <filename>/etc/udev/rules.d/10-wait_for_sysfs.rules</filename>
-      file. Please notify the LFS Development list if you do so and it helps.
-      </para>
-    </sect3>
-    
+      file. Please notify the LFS Development list if you do so and it
+      helps.</para>
+
+    </sect3>
+
     <sect3>
       <title>Udev does not create a device</title>
+
       <para>Further text assumes that the driver is built statically into the
       kernel or already loaded as a module, and that you have already checked
       that Udev doesn't create a misnamed device.</para>
-      
+
       <para>Udev has no information needed to create a device node if a kernel
       driver does not export its data to <systemitem
@@ -294 +309 @@
       <filename class="directory">/dev</filename> by the
       <command>S10udev</command> bootscript.</para>
-    </sect3>
-    
+
+    </sect3>
+
     <sect3>
       <title>Device naming order changes randomly after rebooting</title>
+
       <para>This is due to the fact that Udev, by design, handles uevents and
       loads modules in parallel, and thus in an unpredictable order. This will
@@ -306 +323 @@
       See also the network interface renaming example in
       <xref linkend="ch-scripts-network"/>.</para>
-    </sect3>
-    
+
+    </sect3>
+
   </sect2>