Added notes that udev does not recognize a backslash for line continuation.

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

chapter01/changelog.xml

@@ -39,6 +39,10 @@
     <listitem>
       <para>July 30, 2006</para>
       <itemizedlist>
+        <listitem>
+          <para>[bdubbs] - Added notes that udev does not recognize
+          a backslash for line continuation.</para>
+        </listitem>
         <listitem>
           <para>[bdubbs] - Expanded the note in vim to better explain
           spell files.</para>

chapter07/network.xml

@@ -58,6 +58,13 @@ EOF</userinput></screen>
 <!-- Yes, I know that VLANs are beyond BLFS. This is not the reason to get them
      incorrect by default when every distro does this right. -->
 
+    <note>
+      <para>Although the examples in this book work properly, be aware that
+      <application>udev</application> does not recognize the backslash for line
+      continuation.  If modifying <application>udev</application> rules with an
+      editor, be sure to leave each rule on one physical line.</para>
+    </note>
+
     <para>If you are going to use the bus position as a key, create
     Udev rules similar to the following:</para>
 

chapter07/symlinks.xml

@@ -42,6 +42,13 @@ SUBSYSTEM=="block", ENV{ID_MODEL}=="PHILIPS_CDD5301", \
 </literal>
 EOF</userinput></screen>
 
+    <note>
+      <para>Although the examples in this book work properly, be aware that
+      <application>udev</application> does not recognize the backslash for line
+      continuation.  If modifying <application>udev</application> rules with an
+      editor, be sure to leave each rule on one physical line.</para>
+    </note>
+
     <para>This way, the symlinks will stay correct even if you move the drives
     to different positions on the IDE bus, but the
     <filename>/dev/cdrom</filename> symlink won't be created if you replace