Changes in chapter09/udev.xml [360fdfca:b1774158]

File:

• chapter09/udev.xml (modified) (5 diffs)

chapter09/udev.xml

@@ -1 @@
-<?xml version="1.0" encoding="UTF-8"?>
+<?xml version="1.0" encoding="ISO-8859-1"?>
 <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
   "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
@@ -130 +130 @@
       supported by a module. For example, the <emphasis>snd-fm801</emphasis>
       driver supports PCI devices with vendor ID 0x1319 and device ID 0x0801,
-      and has an alias of <literal>pci:v00001319d00000801sv*sd*bc04sc01i*</literal>.
+      and has an alias of <quote>pci:v00001319d00000801sv*sd*bc04sc01i*</quote>.
       For most devices, the bus driver exports the alias of the driver that
       would handle the device via <systemitem
@@ -136 +136 @@
       <filename>/sys/bus/pci/devices/0000:00:0d.0/modalias</filename> file
       might contain the string
-      <literal>pci:v00001319d00000801sv00001319sd00001319bc04sc01i00</literal>.
+      <quote>pci:v00001319d00000801sv00001319sd00001319bc04sc01i00</quote>.
       The default rules provided with udev will cause <command>udevd</command>
       to call out to <command>/sbin/modprobe</command> with the contents of the
@@ -226 +226 @@
       <literal>pre:</literal> dependencies, or a mixture of both
       <literal>pre:</literal> and <literal>post:</literal> dependencies.  See
-      the <ulink role='man' url='&man;modprobe.d.5'>modprobe.d(5)</ulink>
-      manual page for more information on <quote>softdep</quote> syntax and
-      capabilities.</para>
+      the <filename>modprobe.d(5)</filename> manual page for more information
+      on <quote>softdep</quote> syntax and capabilities.</para>
 
       <para revision="sysv">If the module in question is not a wrapper and is
@@ -302 +301 @@
       <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
-      never be <quote>fixed.</quote> You should not rely upon the kernel device
+      never be <quote>fixed</quote>. You should not rely upon the kernel device
       names being stable. Instead, create your own rules that make symlinks with
       stable names based on some stable attributes of the device, such as a