* Update udev's explanatory text now that /etc/udev/permissions.d is no longer used

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

chapter07/udev.xml

@@ -94,19 +94,15 @@ 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
-permissions of each and every device that <command>udevstart</command>
-creates are set using files from the <filename
-class="directory">/etc/udev.d/permissions.d/</filename> directory.
-These are numbered in a similar fashion to the LFS bootscripts.  If
-<command>udev</command> cannot find a permissions file for the device
-it is creating, it will default permissions to
-<emphasis>600</emphasis> and ownership to
-<emphasis>root:root</emphasis>.  The names 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.</para>
+<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>Once the above stage is complete, all devices that were already
 present and have compiled-in drivers will be available for use. What