[networking-guide] master: Improve: static vs dynamic (6aa0e56)

[stephenw at fedoraproject.org]

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

On branch  : master

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

commit 6aa0e563f05761aff20c354e57e598043ef45c2d
Author: Stephen Wadeley <swadeley at redhat.com>
Date:   Sun Sep 14 18:45:53 2014 +0200

    Improve: static vs dynamic


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

 en-US/Configure_Networking.xml |    5 ++++-
 1 files changed, 4 insertions(+), 1 deletions(-)

diff --git a/en-US/Configure_Networking.xml b/en-US/Configure_Networking.xml
index 33bda92..c5a0faa 100644
--- a/en-US/Configure_Networking.xml
+++ b/en-US/Configure_Networking.xml
@@ -20,6 +20,9 @@
     Use static <systemitem class="protocol">IP</systemitem> addressing on those servers and devices whose network availability you want to ensure when automatic assignment methods, such as <systemitem class="protocol">DHCP</systemitem>, fail. <systemitem class="protocol">DHCP</systemitem>, <systemitem class="protocol">DNS</systemitem>, and authentication servers are typical examples. Interfaces for out-of-band management devices are also worth configuring with static settings as these devices are supposed to work, as far as is possible, independently of other network infrastructure.</para>
     <para>For hosts which are not considered vital, but for which static <systemitem class="protocol">IP</systemitem> addressing is still considered desirable, use an automated provisioning method when possible. For example, <systemitem class="protocol">DHCP</systemitem> servers can be configured to provide the same <systemitem class="protocol">IP</systemitem> address to the same host every time. This method could be used for communal printers for example.
     </para>
+    <para>
+      All the configuration tools listed in <xref linkend="sec-Selecting_Network_Configuration_Methods" /> allow assigning static <systemitem class="protocol">IP</systemitem> addresses manually. The <application>nmcli</application> tool is also suitable for use with scripted assignment of network configuration.
+    </para>
 
 </section>
 <section id="sec-When_to_Use_Dynamic_Interface_Settings">
@@ -27,7 +30,7 @@
   <para>
   </para>
   <para>
-    Enable and use dynamic assignment of <systemitem class="protocol">IP</systemitem> addresses and other network information whenever there is no compelling reason not to. The time saved in planning and documenting manual settings can be better spent elsewhere. See <xref linkend="sec-dhcp-why" /> for more information on this subject.
+    Enable and use dynamic assignment of <systemitem class="protocol">IP</systemitem> addresses and other network information whenever there is no compelling reason not to. The time saved in planning and documenting manual settings can be better spent elsewhere. The <firstterm>dynamic host control protocol</firstterm> (<acronym>DHCP</acronym>) is a traditional method of dynamically assigning network configurations to hosts. See <xref linkend="sec-dhcp-why" /> for more information on this subject.
     </para>
     <para>
       Note that <application>NetworkManager</application> will start the <systemitem class="protocol">DHCP</systemitem> client, <application>dhclient</application>, automatically.