Changeset a0d96d25

Timestamp:

04/13/2006 08:17:52 PM (17 years ago)

Author:

Archaic <archaic@…>

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, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, 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/parallelism, xry111/pip3, xry111/rust-wip-20221008

Children:

470b5d4

Parents:

d2c332bc

Message:

Tweaked some of the educational text regarding udev.

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

Files:

• chapter06/kernfs.xml (modified) (1 diff)
• chapter07/udev.xml (modified) (5 diffs)

chapter06/kernfs.xml

@@ -32 +32 @@
     class="devicefile">console</filename> and <filename
     class="devicefile">null</filename> devices. The device nodes will be created
-    on the hard disk so that they are available before <command>udev</command>
-    has been started, and additionally when Linux is started in single user mode
-    (hence the restrictive permissions on <filename
-    class="devicefile">console</filename>). Create the devices by running the
+    on the hard disk so that they are available before <command>udevd</command>
+    has been started, and additionally when Linux is started with
+    <parameter>init=/bin/bash</parameter>. Create the devices by running the
     following commands:</para>
 

chapter07/udev.xml

@@ -96 +96 @@
 
       <para>The <command>S10udev</command> initscript takes care of creating
-      device nodes when Linux is booted. The script starts by unsetting the
-      hotplug event handler from the default of <command>/sbin/hotplug</command>
-      This is done because, instead of the kernel calling out to an external
-      binary, <command>udevd</command> will listen on a netlink socket for
-      hotplug events that the kernel raises. The bootscript copies any static
+      device nodes when Linux is booted. The script unsets the uevent handler
+      from the default of <command>/sbin/hotplug</command>.  This is done
+      because the kernel no longer needs to call out to an external binary.
+      Instead <command>udevd</command> will listen on a netlink socket for
+      uevents that the kernel raises. Next, the bootscript copies any static
       device nodes that exist in <filename
       class="directory">/lib/udev/devices</filename> to <filename
       class="directory">/dev</filename>. This is necessary because some devices,
-      directories and symlinks are needed before the dynamic device handling
+      directories, and symlinks are needed before the dynamic device handling
       processes are available during the early stages of booting a system.
-      Creating static device nodes in
-      <filename class="directory">/lib/udev/devices</filename> also provides
-      an easy workaround for devices that are not supported by the dynamic
-      device handling infrastructure.  The bootscript then starts the Udev
-      daemon, <command>udevd</command>, which will act on any hotplug events it
-      receives. Finally, the bootscript &quot;coldplugs&quot; any devices that
-      have already been registered with the kernel by forcing them to raise
-      hotplug events which <command>udevd</command> will then handle.</para>
+      Creating static device nodes in <filename
+      class="directory">/lib/udev/devices</filename> also provides an easy
+      workaround for devices that are not supported by the dynamic device
+      handling infrastructure. The bootscript then starts the Udev daemon,
+      <command>udevd</command>, which will act on any uevents it receives.
+      Finally, the bootscript forces the kernel to replay uevents for any
+      devices that have already been registered and then waits for
+      <command>udevd</command> to handle them.</para>
 
     </sect3>
@@ -178 +178 @@
       <para>When you plug in a device, such as a Universal Serial Bus (USB) MP3
       player, the kernel recognizes that the device is now connected and
-      generates a hotplug event. This hotplug event is then handled by
+      generates a uevent. This uevent is then handled by
       <command>udevd</command> as described above.</para>
 
@@ -198 +198 @@
       class="filesystem">sysfs</systemitem>. In other cases, one should
       arrange module loading by other means. With Linux-&linux-version;, Udev is
-      known to load properly-written drivers for PCI, USB, SCSI, SERIO and
-      FireWire devices.</para>
-
-      <!-- After linux-2.6.16, add INPUT and IDE to the list above -->
+      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
@@ -218 +216 @@
       directory under <filename class="directory">/sys/bus</filename>, this
       means that the kernel developers have not yet added modalias support to
-      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 -->
+      this bus type. With Linux-&linux-version;, this is the case with ISA
+      busses. Expect this issue to be fixed in later kernel versions.</para>
 
       <para>Udev is not intended to load <quote>wrapper</quote> drivers such as
@@ -270 +266 @@
 
       <para>This usually happens if a rule unexpectedly matches a device. For
-      example, a poorly-writen rule can match by both a SCSI disk (as desired)
+      example, a poorly-writen rule can match both a SCSI disk (as desired)
       and the corresponding SCSI generic device (incorrectly) by vendor.
       Increase the logging verbosity of Udev, find the offending rule by