Brought all occurences of LFS-Bootscripts into conformity.

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

1 files changed, 18 insertions, 21 deletions

diff --git a/chapter07/udev.xml b/chapter07/udev.xml
index 5cdd2d363..7b9be92ad 100644
--- a/chapter07/udev.xml
+++ b/chapter07/udev.xml
@@ -82,27 +82,24 @@ built-in drivers registered with <systemitem
 class="filesystem">sysfs</systemitem> are available to userspace
 processes and to <command>udev</command> for device node creation.</para>
 
-<para>The <command>S10udev</command> initscript takes care of creating
-these device nodes when Linux is booted. This script starts with
-registering <command>/sbin/udevsend</command> as a hotplug event handler.
-Hotplug events (discussed below) should not be generated during this
-stage, but <command>udev</command> is registered just in case they do
-occur.  The <command>udevstart</command> program then walks through
-the <systemitem class="filesystem">/sys</systemitem> filesystem and
-creates devices under <filename class="directory">/dev</filename> that
-match the descriptions.  For example,
-<filename>/sys/class/tty/vcs/dev</filename> contains the string
-<quote>7:0</quote> This string is used by <command>udevstart</command>
-to create <filename>/dev/vcs</filename> with major number
-<emphasis>7</emphasis> and minor <emphasis>0</emphasis>.  The names and
-permissions of the nodes created under the
-<filename class="directory">/dev</filename> directory are configured according
-to the rules specified in the files within the
-<filename class="directory">/etc/udev/rules.d/</filename> directory.  These are
-numbered in a similar fashion to the LFS bootscripts.  If
-<command>udev</command> can't find a rule for the device it is creating, it will
-default permissions to <emphasis>660</emphasis> and ownership to
-<emphasis>root:root</emphasis>.</para>
+<para>The <command>S10udev</command> initscript takes care of creating these
+device nodes when Linux is booted. This script starts with registering
+<command>/sbin/udevsend</command> as a hotplug event handler.  Hotplug events
+(discussed below) should not be generated during this stage, but
+<command>udev</command> is registered just in case they do occur.  The
+<command>udevstart</command> program then walks through the <systemitem
+class="filesystem">/sys</systemitem> filesystem and creates devices under
+<filename class="directory">/dev</filename> that match the descriptions.  For
+example, <filename>/sys/class/tty/vcs/dev</filename> contains the string
+<quote>7:0</quote> This string is used by <command>udevstart</command> to create
+<filename>/dev/vcs</filename> with major number <emphasis>7</emphasis> and minor
+<emphasis>0</emphasis>.  The names and permissions of the nodes created under
+the <filename class="directory">/dev</filename> directory are configured
+according to the rules specified in the files within the <filename
+class="directory">/etc/udev/rules.d/</filename> directory. These are numbered in
+a similar fashion to the LFS-Bootscripts package. If <command>udev</command>
+can't find a rule for the device it is creating, it will default permissions to
+<emphasis>660</emphasis> and ownership to <emphasis>root:root</emphasis>.</para>
 
 <para>Once the above stage is complete, all devices that were already
 present and have compiled-in drivers will be available for use. What