commit 31b0ca5ccfae3fa0f0b032d3055be3ec09c233f6 Author: Stephen Wadeley <swadeley(a)redhat.com&gt; Date: Thu Dec 13 11:12:09 2012 +0100 Appendix A: Consistent Network Device Naming | Removing parts which no longer apply. based on e-mail from Kay Sievers "..udev will no longer try to rename network devices by default <snip> biosdevname should be used by default." Date: Tue, 11 Sep 2012 11:25:59 -0400 (EDT) From: Kay Sievers To: Stephen Wadeley Cc: Harald Hoyer en-US/Consistent_Network_Device_Naming.xml | 6 +++++- 1 files changed, 5 insertions(+), 1 deletions(-) --- diff --git a/en-US/Consistent_Network_Device_Naming.xml b/en-US/Consistent_Network_Device_Naming.xml index 4ccd7d3..e9de1cf 100644 --- a/en-US/Consistent_Network_Device_Naming.xml +++ b/en-US/Consistent_Network_Device_Naming.xml @@ -71,10 +71,11 @@ </tbody> </tgroup> </table> + <!-- No longer applies in Fedora 17 <para> System administrators may continue to write rules in <filename>/etc/udev/rules.d/70-persistent-net.rules</filename> to change the device names to anything desired; those will take precedence over this physical location naming convention. </para> - <section id="sect-Consistent_Network_Device_Naming-Affected_Systems"> + <section id="sect-Consistent_Network_Device_Naming-Affected_Systems"> <title>Affected Systems</title> <para> Consistent network device naming is enabled by default for all systems that meet the requirements in <xref linkend="sect-Consistent_Network_Device_Naming-System_Requirements" />. @@ -83,6 +84,7 @@ Regardless of the type of system, Fedora guests will not have devices renamed unless the virtual machine BIOS provides the SMBIOS information outlined in <xref linkend="sect-Consistent_Network_Device_Naming-System_Requirements" />. Also, upgrades from prior releases that did not use this naming convention (that is, Fedora 14 and older) are unaffected, and the old naming convention will continue to be used. </para> </section> + --> <section id="sect-Consistent_Network_Device_Naming-System_Requirements"> <title>System Requirements</title> <para> @@ -114,8 +116,10 @@ <para> Many system customization files can include network interface names, and thus will require updates if moving a system from the old convention to the new convention. If you use the new naming convention, you will also need to update network interface names in areas such as custom iptables rules, scripts altering irqbalance, and other similar configuration files. Also, enabling this change for installation will require modification to existing kickstart files that use device names via the <option>ksdevice</option> parameter; these kickstart files will need to be updated to use the network device's MAC address or the network device's new name. </para> + <!-- No longer applies in Fedora 17 <para> &OSORG; strongly recommends that you consider this feature to be an install-time choice; enabling or disabling the feature post-install, while technically possible, can be complicated and is not recommended. For those system administrators who wish to do so, on a system that meets the minimum requirements, remove the <filename>/etc/udev/rules.d/70-persistent-net.rules</filename> file and the <option>HWADDR</option> lines from all <filename>/etc/sysconfig/network-scripts/ifcfg-*</filename> files. In addition, rename those <filename>ifcfg-*</filename> files to use this new naming convention. The new names will be in effect after reboot. Remember to update any custom scripts, iptables rules, and service configuration files that might include network interface names. </para> + --> </section> </appendix>