Index: BOOK/bootscripts/common/network.xml
===================================================================
--- BOOK/bootscripts/common/network.xml	(revision 5fc4a87be267bb617d26b6c91198d23929f74d2f)
+++ BOOK/bootscripts/common/network.xml	(revision de17e850d23cf3abe0d17cf39baef89a17d7597c)
@@ -23,90 +23,4 @@
   symlinks from all run-level directories (<filename
   class="directory">/etc/rc.d/rc*.d</filename>).</para>
-
-  <sect2>
-    <title>Creating stable names for network interfaces</title>
-
-    <para>Instructions in this section are optional if you have only one
-    network card.</para>
-
-    <para>With Udev and modular network drivers, the network interface numbering
-    is not persistent across reboots by default, because the drivers are loaded
-    in parallel and, thus, in random order. For example, on a computer having
-    two network cards made by Intel and Realtek, the network card manufactured
-    by Intel may become <filename class="devicefile">eth0</filename> and the
-    Realtek card becomes  <filename class="devicefile">eth1</filename>. In some
-    cases, after a reboot the cards get renumbered the other way around. To
-    avoid this, create Udev rules that assign stable names to network cards
-    based on their MAC addresses or bus positions.</para>
-
-    <para>If you are going to use MAC addresses to identify your network
-    cards, find the addresses with the following command:</para>
-
-<screen role="nodump"><userinput>grep -H . /sys/class/net/*/address</userinput></screen>
-
-    <para>For each network card (but not for the loopback interface),
-    invent a descriptive name, such as <quote>realtek</quote>, and create
-    Udev rules similar to the following:</para>
-
-<screen role="nodump"><userinput>cat &gt; /etc/udev/rules.d/26-network.rules &lt;&lt; EOF
-<literal>ACTION=="add", SUBSYSTEM=="net", SYSFS{address}=="<replaceable>00:e0:4c:12:34:56</replaceable>", \
-    NAME="<replaceable>realtek</replaceable>"
-ACTION=="add", SUBSYSTEM=="net", SYSFS{address}=="<replaceable>00:a0:c9:78:9a:bc</replaceable>", \
-    NAME="<replaceable>intel</replaceable>"</literal>
-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 Udev does not recognize the backslash for line continuation.
-      If modifying Udev 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>
-
-<screen role="nodump"><userinput>cat &gt; /etc/udev/rules.d/26-network.rules &lt;&lt; EOF
-<literal>ACTION=="add", SUBSYSTEM=="net", BUS=="<replaceable>pci</replaceable>", ID=="<replaceable>0000:00:0c.0</replaceable>", \
-    NAME="<replaceable>realtek</replaceable>"
-ACTION=="add", SUBSYSTEM=="net", BUS=="<replaceable>pci</replaceable>", ID=="<replaceable>0000:00:0d.0</replaceable>", \
-    NAME="<replaceable>intel</replaceable>"</literal>
-EOF</userinput></screen>
-
-    <para>These rules will always rename the network cards to
-    <quote>realtek</quote> and <quote>intel</quote>, independently
-    of the original numbering provided by the kernel (i.e.: the original
-    <quote>eth0</quote> and <quote>eth1</quote> interfaces will no longer
-    exist, unless you put such <quote>descriptive</quote> names in the NAME
-    key). Use the descriptive names from the Udev rules instead
-    of <quote>eth0</quote> in the network interface configuration files
-    below.</para>
-
-    <para>Note that the rules above don't work for every setup. For example,
-    MAC-based rules break when bridges or VLANs are used, because bridges and
-    VLANs have the same MAC address as the network card. One wants to rename
-    only the network card interface, not the bridge or VLAN interface, but the
-    example rule matches both. If you use such virtual interfaces, you have two
-    potential solutions. One is to add the DRIVER=="?*" key after
-    SUBSYSTEM=="net" in MAC-based rules which will stop matching the virtual
-    interfaces.  This is known to fail with some older Ethernet cards because
-    they don't have the DRIVER variable in the uevent and thus the rule does
-    not match with such cards. Another solution is to switch to rules that use
-    the bus position as a key.</para>
-
-    <para>The second known non-working case is with wireless cards using the
-    MadWifi or HostAP drivers, because they create at least two interfaces with
-    the same MAC address and bus position. For example, the Madwifi driver
-    creates both an athX and a wifiX interface where X is a digit.  To
-    differentiate these interfaces, add an appropriate KERNEL parameter such as
-    KERNEL=="ath*" after SUBSYSTEM=="net".</para>
-
-    <para>There may be other cases where the rules above don't work. Currently,
-    bugs on this topic are still being reported to Linux distributions, and no
-    solution that covers every case is available.</para>
-
-  </sect2>
 
   <sect2>
Index: BOOK/introduction/common/changelog.xml
===================================================================
--- BOOK/introduction/common/changelog.xml	(revision 5fc4a87be267bb617d26b6c91198d23929f74d2f)
+++ BOOK/introduction/common/changelog.xml	(revision de17e850d23cf3abe0d17cf39baef89a17d7597c)
@@ -41,5 +41,8 @@
       <itemizedlist>
         <listitem>
-          <para>[jciccone] Updated to Linux 2.6.18.1 and Linux-Headers 2.6.18.1-10222006.</para>
+          <para>[jciccone] -  Removed out of place udev text in bootscripts Networking.</para>
+        </listitem>
+        <listitem>
+          <para>[jciccone] - Updated to Linux 2.6.18.1 and Linux-Headers 2.6.18.1-10222006.</para>
         </listitem>
         <listitem>
