[networking-guide] master: Consistent Network Device Naming (a90280d)

[stephenw at fedoraproject.org]

Repository : http://git.fedorahosted.org/cgit/docs/networking-guide.git

On branch  : master

>---------------------------------------------------------------

commit a90280d5f9318dc76bb96f90246123399b80db7e
Author: Stephen Wadeley <swadeley at redhat.com>
Date:   Wed Sep 3 22:27:49 2014 +0200

    Consistent Network Device Naming
    
    improvements after review by msekleta and lnykryn


>---------------------------------------------------------------

 en-US/Consistent_Network_Device_Naming.xml |    9 ++++++---
 1 files changed, 6 insertions(+), 3 deletions(-)

diff --git a/en-US/Consistent_Network_Device_Naming.xml b/en-US/Consistent_Network_Device_Naming.xml
index 4d046ee..6cf8b9f 100644
--- a/en-US/Consistent_Network_Device_Naming.xml
+++ b/en-US/Consistent_Network_Device_Naming.xml
@@ -52,7 +52,7 @@
 
 
    <para>
-     This policy, the procedure outlined above, is the default. If the system has <application>biosdevname</application> enabled, it will take precedence. Note that enabling <application>biosdevname</application> requires passing <command>biosdevname=1</command> as a command line parameter except in the case of a Dell system, where <application>biosdevname</application> will be used by default as long as it is installed. If the user has added <application>udev</application> rules which change the name of the kernel devices, those rules will take precedence too.
+     This policy, the procedure outlined above, is the default. If the system has <application>biosdevname</application> enabled, it will be used. Note that enabling <application>biosdevname</application> requires passing <command>biosdevname=1</command> as a command line parameter except in the case of a Dell system, where <application>biosdevname</application> will be used by default as long as it is installed. If the user has added <application>udev</application> rules which change the name of the kernel devices, those rules will take precedence.
    </para>
 
    </section>
@@ -75,15 +75,18 @@
   </step>
   <step>
     <para>
-        A rule in <filename>/lib/udev/rules.d/75-net-description.rules</filename> instructs <application>udev</application> to fill in ID_NET_NAME_ONBOARD, ID_NET_NAME_SLOT, ID_NET_NAME_PATH, ID_NET_NAME_MAC by examining the network interface device. Note, that some variables can be empty.
+        A rule in <filename>/lib/udev/rules.d/75-net-description.rules</filename> instructs <application>udev</application> to fill in the internal <application>udev</application> device property values ID_NET_NAME_ONBOARD, ID_NET_NAME_SLOT, ID_NET_NAME_PATH, ID_NET_NAME_MAC by examining the network interface device. Note, that some device properties might be undefined.
     </para>
   </step>
   <step>
     <para>
-      A rule in <filename>/usr/lib/udev/rules.d/80-net-name-slot.rules</filename> instructs <application>udev</application> to rename the interface, provided that it was not renamed in a previous step, and the kernel parameter <command>net.ifnames=0</command> was not given, according to the following priority: ID_NET_NAME_ONBOARD, ID_NET_NAME_SLOT, ID_NET_NAME_PATH. It falls through to the next in the list, if one is unset. If none of these are set, then the interface will not be renamed.
+      A rule in <filename>/usr/lib/udev/rules.d/80-net-name-slot.rules</filename> instructs <application>udev</application> to rename the interface, provided that it was not renamed in step 1 or 2, and the kernel parameter <command>net.ifnames=0</command> was not given, according to the following priority: ID_NET_NAME_ONBOARD, ID_NET_NAME_SLOT, ID_NET_NAME_PATH. It falls through to the next in the list, if one is unset. If none of these are set, then the interface will not be renamed.
       </para>
   </step>
 </procedure>
+   <para>
+     Steps 3 and 4 are implementing the naming schemes 1, 2, 3, and optionally 4, described in <xref linkend="sec-Naming_Schemes_Hierarchy" />. Step 2 is explained in more detail in <xref linkend="sec-Consistent_Network_Device_Naming_Using_biosdevname" />.
+   </para>
   </section>
 
    <section id="sec-Understanding_the_Predictable_Network_Interface_Device_Names">