Merge udev.xml and udevd.xml files.

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

1 files changed, 25 insertions, 4 deletions

diff --git a/chapter07/udev.xml b/chapter07/udev.xml
index f42260fb6..9a18bc7ef 100644
--- a/chapter07/udev.xml
+++ b/chapter07/udev.xml
@@ -5,7 +5,7 @@
   %general-entities;
 ]>
 
-<sect1 id="ch-scripts-udev" revision="sysv">
+<sect1 id="ch-scripts-udev">
   <?dbhtml filename="udev.html"?>
 
   <title>Overview of Device and Module Handling</title>
@@ -16,9 +16,10 @@
   </indexterm>
 
   <para>In <xref linkend="chapter-building-system"/>, we installed the Udev
-  package when eudev was built. Before we go into the details regarding how
-  this works, a brief history of previous methods of handling devices is in
-  order.</para>
+  package when <phrase revision="sysv">eudev</phrase>
+  <phrase revision="systemd">systemd</phrase> was built. Before we go into the
+  details regarding how this works, a brief history of previous methods of
+  handling devices is in order.</para>
 
   <para>Linux systems in general traditionally used a static device creation
   method, whereby a great many device nodes were created under <filename
@@ -273,6 +274,26 @@
     </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 class="filesystem">sysfs</systemitem>. This is most common
+      with third party drivers from outside the kernel tree. Create a static
+      device node in <filename>/lib/udev/devices</filename> with the
+      appropriate major/minor numbers (see the file
+      <filename>devices.txt</filename> inside the kernel documentation or the
+      documentation provided by the third party driver vendor). The static
+      device node will be copied to <filename class="directory">/dev</filename>
+      by <command>udev</command>.</para>
+
+    </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