Adding note on why MAKEDEV must remain in /dev.

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

chapter06/glibc.xml

@@ -51,8 +51,8 @@ cd ../glibc-build</userinput></screen>
 location of the <filename>pt_chown</filename> program from its default of 
 <filename class="directory">/usr/libexec</filename> to
 <filename class="directory">/usr/lib</filename>. The use of
-<emphasis>libexec</emphasis> is considered not FHS compliant because the FHS
-doesn't even mention it.</para></listitem>
+<emphasis>libexec</emphasis> is considered not to be FHS-compliant because the
+FHS doesn't even mention it.</para></listitem>
 
 <listitem><para><userinput>--with-headers=/usr/include</userinput>: This
 ensures that the kernel headers in <filename>/usr/include</filename> are used

chapter06/makedev.xml

@@ -48,6 +48,11 @@ Alternatively, you may create devices via the <userinput>mknod</userinput>
 program. Please refer to its man and info pages if you need more
 information.</para>
 
+<para>If you wish your system to be FHS-compliant, then the
+<filename>MAKEDEV</filename> script has to remain present in the
+<filename class="directory">/dev</filename> directory. This way it is always
+available for making extra device nodes.</para>
+
 <para>Additionally, if you were unable to mount the devpts filesystem earlier
 in <xref linkend="ch06-proc"/>, now is the time to try the alternatives. If
 your kernel supports the devfs file system, run the following command to mount