Changeset a3d0817 for chapter09/udev.xml

Timestamp:

06/12/2020 08:42:32 PM (4 years ago)

Author:

Bruce Dubbs <bdubbs@…>

Branches:

10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc

Children:

9e7475a

Parents:

96f04d7

Message:

Text updated for cross2 chapter 9

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

File:

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

chapter09/udev.xml

@@ -16 +16 @@
   </indexterm>
 
-  <para>In <xref linkend="chapter-building-system"/>, we installed the Udev
+  <para>In <xref linkend="chapter-building-system"/>, we installed the udev
   package when <phrase revision="sysv">eudev</phrase>
   <phrase revision="systemd">systemd</phrase> was built. Before we go into the
@@ -31 +31 @@
   the world.</para>
 
-  <para>Using the Udev method, only those devices which are detected by the
+  <para>Using the udev method, only those devices which are detected by the
   kernel get device nodes created for them. Because these device nodes will be
   created each time the system boots, they will be stored on a <systemitem
@@ -136 +136 @@
       might contain the string
       <quote>pci:v00001319d00000801sv00001319sd00001319bc04sc01i00</quote>.
-      The default rules provided with Udev will cause <command>udevd</command>
+      The default rules provided with udev will cause <command>udevd</command>
       to call out to <command>/sbin/modprobe</command> with the contents of the
       <envar>MODALIAS</envar> uevent environment variable (which should be the
@@ -150 +150 @@
 
       <para>The kernel itself is also able to load modules for network
-      protocols, filesystems and NLS support on demand.</para>
+      protocols, filesystems, and NLS support on demand.</para>
 
     </sect3>
@@ -178 +178 @@
       bus driver properly exports the necessary aliases to <systemitem
       class="filesystem">sysfs</systemitem>. In other cases, one should
-      arrange module loading by other means. With Linux-&linux-version;, Udev is
+      arrange module loading by other means. With Linux-&linux-version;, udev is
       known to load properly-written drivers for INPUT, IDE, PCI, USB, SCSI,
       SERIO, and FireWire devices.</para>
 
       <para>To determine if the device driver you require has the necessary
-      support for Udev, run <command>modinfo</command> with the module name as
+      support for udev, run <command>modinfo</command> with the module name as
       the argument.  Now try locating the device directory under
       <filename class="directory">/sys/bus</filename> and check whether there is
@@ -191 +191 @@
       class="filesystem">sysfs</systemitem>, the driver supports the device and
       can talk to it directly, but doesn't have the alias, it is a bug in the
-      driver. Load the driver without the help from Udev and expect the issue
+      driver. Load the driver without the help from udev and expect the issue
       to be fixed later.</para>
 
@@ -207 +207 @@
 
     <sect3>
-      <title>A kernel module is not loaded automatically, and Udev is not
+      <title>A kernel module is not loaded automatically, and udev is not
       intended to load it</title>
 
@@ -215 +215 @@
       <emphasis>snd-pcm</emphasis> by making the sound cards available to OSS
       applications), configure <command>modprobe</command> to load the wrapper
-      after Udev loads the wrapped module. To do this, add a
+      after udev loads the wrapped module. To do this, add a
       <quote>softdep</quote> line to the corresponding
       <filename>/etc/modprobe.d/<replaceable>&lt;filename&gt;</replaceable>.conf</filename>
@@ -280 +280 @@
       <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>
+      that udev doesn't create a misnamed device.</para>
 
       <para>Udev has no information needed to create a device node if a kernel
@@ -298 +298 @@
       <title>Device naming order changes randomly after rebooting</title>
 
-      <para>This is due to the fact that Udev, by design, handles uevents and
+      <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
       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
-      serial number or the output of various *_id utilities installed by Udev.
+      serial number or the output of various *_id utilities installed by udev.
       See <xref linkend="ch-config-symlinks"/> and
       <xref linkend="ch-config-network"/> for examples.</para>