[networking-guide] master: Path to grub config file was incorrect (a27f666)

[stephenw at fedoraproject.org]

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

On branch  : master

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

commit a27f666b6ac910aba158228cdac1c9ea66ee01d5
Author: Stephen Wadeley <swadeley at redhat.com>
Date:   Wed Aug 20 23:02:00 2014 +0200

    Path to grub config file was incorrect


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

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

diff --git a/en-US/Consistent_Network_Device_Naming.xml b/en-US/Consistent_Network_Device_Naming.xml
index c509d62..4d046ee 100644
--- a/en-US/Consistent_Network_Device_Naming.xml
+++ b/en-US/Consistent_Network_Device_Naming.xml
@@ -259,7 +259,7 @@ The name of the parent interface plus the VLAN ID with out padding by means of a
   <section id="sec-Consistent_Network_Device_Naming_Using_biosdevname">
     <title>Consistent Network Device Naming Using biosdevname</title>
     <para>
-   This feature, implemented via the <application>biosdevname</application> <application>udev</application> helper utility, will change the name of all embedded network interfaces, PCI card network interfaces, and virtual function network interfaces from the existing <interfacename>eth[0123&#8230;]</interfacename> to the new naming convention as shown in <xref linkend="tabl-Consistent_Network_Device_Naming_biosdevname" />. Note that unless the system is a Dell system, or <application>biosdevname</application> explicitly enabled as described in <xref linkend="sec-Consistent_Network_Device_Naming-Enabling_and_Disabling" />, the <systemitem class="daemon">systemd</systemitem> naming scheme will take precedence.
+   This feature, implemented via the <application>biosdevname</application> <application>udev</application> helper utility, will change the name of all embedded network interfaces, PCI card network interfaces, and virtual function network interfaces from the existing <interfacename>eth[0123&#8230;]</interfacename> to the new naming convention as shown in <xref linkend="tabl-Consistent_Network_Device_Naming_biosdevname" />. Note that unless the system is a Dell system, or <application>biosdevname</application> is explicitly enabled as described in <xref linkend="sec-Consistent_Network_Device_Naming-Enabling_and_Disabling" />, the <systemitem class="daemon">systemd</systemitem> naming scheme will take precedence.
   </para>
   <table id="tabl-Consistent_Network_Device_Naming_biosdevname">
     <title>The biosdevname Naming Convention</title>
@@ -352,7 +352,7 @@ The name of the parent interface plus the VLAN ID with out padding by means of a
   <section id="sec-Consistent_Network_Device_Naming-Notes">
     <title>Notes for Administrators</title>
     <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.
+      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 <application>iptables</application> rules, scripts altering <systemitem class="daemon">irqbalance</systemitem>, and other similar configuration files. Also, enabling this change for installation will require modification to existing <application>kickstart</application> files that use device names via the <option>ksdevice</option> parameter; these <application>kickstart</application> files will need to be updated to use the network device's MAC address or the network device's new name.
     </para>
     <note>
     <para>
@@ -423,7 +423,7 @@ The name provided by <systemitem class="daemon">systemd-udev</systemitem> will b
     </listitem>
      <listitem>
       <para>
-        Add the following line to the <filename>/etc/grub.conf</filename> file:
+        Add the following line to the <filename>/etc/default/grub</filename> file:
         <synopsis>net.ifnames=0</synopsis>
         or pass it to the kernel at boot time using the GRUB2 command line interface. For more information about GRUB2 see <ulink url="https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/"><citetitle pubwork="book">&MAJOROSVER; System Administrator's Guide</citetitle></ulink>.</para>
     </listitem>