Repository :
http://git.fedorahosted.org/cgit/docs/networking-guide.git
On branch : master
---------------------------------------------------------------
commit a2703d052f3469e3263e48434668381d1f474fdc
Author: Stephen Wadeley <swadeley(a)redhat.com>
Date: Mon Jul 28 23:07:37 2014 +0200
Improve "Naming Schemes Hierarchy"
---------------------------------------------------------------
en-US/Consistent_Network_Device_Naming.xml | 21 ++++++++++++---------
1 files changed, 12 insertions(+), 9 deletions(-)
diff --git a/en-US/Consistent_Network_Device_Naming.xml
b/en-US/Consistent_Network_Device_Naming.xml
index 4bba7cf..d6aea54 100644
--- a/en-US/Consistent_Network_Device_Naming.xml
+++ b/en-US/Consistent_Network_Device_Naming.xml
@@ -44,37 +44,40 @@
</para>
</listitem>
</orderedlist>
-By default, <systemitem class="daemon">systemd</systemitem> will
name interfaces using the following policy to apply the schemes listed above:
-<orderedlist>
+</para>
+<bridgehead id="bh-Naming_Schemes_Hierarchy">Naming Schemes
Hierarchy</bridgehead>
+<para>
+By default, <systemitem class="daemon">systemd</systemitem> will
name interfaces using the following policy to apply the naming schemes listed above :
+<itemizedlist>
<listitem>
<para>
- Use scheme 1 if that information from the firmware is applicable and available,
falling back to scheme 2;
+ <emphasis role="bold">Scheme 1:</emphasis> Names incorporating
Firmware or BIOS provided index numbers for on-board devices (example:
<literal>eno1</literal>), are applied if that information from the firmware or
BIOS is applicable and available, else falling back to scheme 2;
</para>
</listitem>
<listitem>
<para>
- Use scheme 2 if that information from the firmware is applicable and available,
falling back to scheme 3;
+ <emphasis role="bold">Scheme 2:</emphasis> Names incorporating
Firmware or BIOS provided PCI Express hotplug slot index numbers (example:
<literal>ens1</literal>) are applied if that information from the firmware or
BIOS is applicable and available, else falling back to scheme 3;
</para>
</listitem>
<listitem>
<para>
- Use scheme 3 if applicable, falling back to scheme 5 in all other cases;
+ <emphasis role="bold">Scheme 3:</emphasis> Names
incorporating physical location of the connector of the hardware (example:
<literal>enp2s0</literal>), are applied if applicable, else falling directly
back to scheme 5 in all other cases;
</para>
</listitem>
<listitem>
<para>
- Scheme 4 is not used by default, but is available if the user chooses;
+ <emphasis role="bold">Scheme 4:</emphasis> Names
incorporating interface's MAC address, is not used by default, but is available if the
user chooses;
</para>
</listitem>
<listitem>
<para>
- Scheme 5 is used if all other methods fail.
+ <emphasis role="bold">Scheme 5:</emphasis> The traditional
unpredictable kernel naming scheme, is used if all other methods fail.
</para>
</listitem>
-</orderedlist>
+</itemizedlist>
- </para>
+</para>
<para>
This policy, the procedure outlined above, is the default. If the system has
<application>BIOSDEVNAME</application> enabled, it will take precedence. If
the user has added <systemitem class="daemon">udevd</systemitem>
rules which change the name of the kernel devices, those rules will take precedence too.