Changeset 487d471b

Timestamp:

07/31/2006 12:13:57 AM (18 years ago)

Author:

Bruce Dubbs <bdubbs@…>

Children:

4a316ba, 501f9cf8, d93bc961

Parents:

3a234c0a

Message:

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

Files:

• chapter01/changelog.xml (modified) (1 diff)
• chapter07/network.xml (modified) (1 diff)
• chapter07/symlinks.xml (modified) (1 diff)

chapter01/changelog.xml

@@ -40 +40 @@
       <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

chapter07/network.xml

@@ -58 +58 @@
 <!-- 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

chapter07/symlinks.xml

@@ -42 +42 @@
 </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