diff --git a/chapter01/changelog.xml b/chapter01/changelog.xml
index 6936ca0ef..090031ade 100644
--- a/chapter01/changelog.xml
+++ b/chapter01/changelog.xml
@@ -36,13 +36,26 @@
     </listitem>
 -->
 
+    <listitem>
+      <para>2007-02-18</para>
+      <itemizedlist>
+        <listitem>
+          <para>[bryan] - Fix obsolete syntax used in the example Udev rules
+          in section 7.12.2. Fixes the easy part of
+          <ulink url="&lfs-ticket-root;1963">#1963</ulink>. Also re-add the
+          note about the backslash at the end of the udev rule lines.</para>
+        </listitem>
+      </itemizedlist>
+    </listitem>
+
     <listitem>
       <para>2007-02-17</para>
       <itemizedlist>
         <listitem>
           <para>[bryan] - Use upstream's rule_generator rules exclusively for
           NIC naming, and generate the rules before configuring the network
-          script, so the user knows what NIC names to use.</para>
+          script, so the user knows what NIC names to use. Fixes the rest of
+          <ulink url="&lfs-ticket-root;1912">#1912</ulink>.</para>
         </listitem>
         <listitem>
           <para>[bryan] - Change from writing CD symlink rules files directly
diff --git a/chapter07/symlinks.xml b/chapter07/symlinks.xml
index 1407d553f..5846a46e0 100644
--- a/chapter07/symlinks.xml
+++ b/chapter07/symlinks.xml
@@ -122,13 +122,25 @@
 <screen role="nodump"><userinput>cat &gt; /etc/udev/rules.d/83-duplicate_devs.rules &lt;&lt; EOF
 <literal>
 # Persistent symlinks for webcam and tuner
-KERNEL=="video*", SYSFS{idProduct}=="1910", SYSFS{idVendor}=="0d81", \
+KERNEL=="video*", ATTRS{idProduct}=="1910", ATTRS{idVendor}=="0d81", \
     SYMLINK+="webcam"
-KERNEL=="video*", SYSFS{device}=="0x036f", SYSFS{vendor}=="0x109e", \
+KERNEL=="video*", ATTRS{device}=="0x036f", ATTRS{vendor}=="0x109e", \
     SYMLINK+="tvtuner"
 </literal>
 EOF</userinput></screen>
 
+    <note>
+      <para>Be aware that Udev does not recognize the backslash for line
+      continuation.  This example works properly because both the backslash
+      and newline are ignored by the shell.  This makes the shell send each
+      rule to cat on only one line.  (The shell ignores this sequence because
+      the EOF string used in the here-document redirection is not enclosed in
+      either double or single quotes.  For more details, see the bash(1)
+      manpage, and search it for "Here Documents".)</para> 
+      <para>If modifying Udev rules with an editor, be sure to leave each
+      rule on one physical line.</para>
+    </note>
+
     <para>The result is that <filename>/dev/video0</filename> and
     <filename>/dev/video1</filename> devices still refer randomly to the tuner
     and the web camera (and thus should never be used directly), but there are