[deployment-guide/comm-rel: 94/727] Updated the /etc/sysconfig/network section.
Jaromir Hradilek
jhradile at fedoraproject.org
Tue Oct 19 12:32:04 UTC 2010
commit b8e0fbe215579870705e4363f818151994de2e65
Author: Jaromir Hradilek <jhradile at redhat.com>
Date: Wed Jul 21 16:51:32 2010 +0200
Updated the /etc/sysconfig/network section.
en-US/The_sysconfig_Directory.xml | 80 ++++++++++++++----------------------
1 files changed, 31 insertions(+), 49 deletions(-)
---
diff --git a/en-US/The_sysconfig_Directory.xml b/en-US/The_sysconfig_Directory.xml
index 61c81a7..e8d37e2 100644
--- a/en-US/The_sysconfig_Directory.xml
+++ b/en-US/The_sysconfig_Directory.xml
@@ -648,57 +648,39 @@
<secondary><filename>/etc/sysconfig/network</filename></secondary>
</indexterm>
<para>
- The <filename>/etc/sysconfig/network</filename> file is used to specify information about the desired network configuration. The following values may be used:
+ The <filename>/etc/sysconfig/network</filename> file is used to specify information about the desired network configuration. By default, it contains the following options:
</para>
- <itemizedlist>
- <listitem>
- <para>
- <command>NETWORKING=<replaceable><value></replaceable></command>, where <command><replaceable><value></replaceable></command> is one of the following boolean values:
- </para>
- <itemizedlist>
- <listitem>
- <para>
- <command>yes</command> — Networking should be configured.
- </para>
- </listitem>
- <listitem>
- <para>
- <command>no</command> — Networking should not be configured.
- </para>
- </listitem>
- </itemizedlist>
- </listitem>
- <listitem>
- <para>
- <command>HOSTNAME=<replaceable><value></replaceable></command>, where <command><replaceable><value></replaceable></command> should be the <firstterm>Fully Qualified Domain Name</firstterm> (<firstterm>FQDN</firstterm>), such as <filename>hostname.expample.com</filename>, but can be whatever hostname is necessary.
- </para>
- </listitem>
- <listitem>
- <para>
- <command>GATEWAY=<replaceable><value></replaceable></command>, where <command><replaceable><value></replaceable></command> is the IP address of the network's gateway.
- </para>
- </listitem>
- <listitem>
- <para>
- <command>GATEWAYDEV=<replaceable><value></replaceable></command>, where <command><replaceable><value></replaceable></command> is the gateway device, such as <filename>eth0</filename>. Configure this option if you have multiple interfaces on the same subnet, and require one of those interfaces to be the preferred route to the default gateway.
- </para>
- </listitem>
- <listitem>
- <para>
- <command>NISDOMAIN=<replaceable><value></replaceable></command>, where <command><replaceable><value></replaceable></command> is the NIS domain name.
- </para>
- </listitem>
- <listitem>
- <para>
- <command>NOZEROCONF=<replaceable><value></replaceable></command>, where setting <command><replaceable><value></replaceable></command> to <command>true</command> disables the zeroconf route.
- </para>
- <para>
- By default, the zeroconf route (169.254.0.0) is enabled when the system boots. For more information about zeroconf, refer to <ulink url="http://www.zeroconf.org/" />.
- </para>
- </listitem>
- </itemizedlist>
+ <variablelist>
+ <varlistentry>
+ <term><option>NETWORKING=<replaceable>boolean</replaceable></option></term>
+ <listitem>
+ <para>
+ A boolean to enable (<option>yes</option>) or disable (<option>no</option>) the networking. For example:
+ </para>
+ <screen>NETWORKING=yes</screen>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>HOSTNAME=<replaceable>value</replaceable></option></term>
+ <listitem>
+ <para>
+ The hostname of the machine. For example:
+ </para>
+ <screen>HOSTNAME=penguin.example.com</screen>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><option>GATEWAY=<replaceable>value</replaceable></option></term>
+ <listitem>
+ <para>
+ The IP address of the network's gateway. For example:
+ </para>
+ <screen>GATEWAY=192.168.1.0</screen>
+ </listitem>
+ </varlistentry>
+ </variablelist>
<warning>
- <title>Warning</title>
+ <title>Warning: Avoid Using Custom Init Scripts</title>
<para>
Do not use custom initscripts to configure network settings. When performing a post-boot network service restart, custom initscripts configuring network settings that are run outside of the network init script lead to unpredictable results.
</para>
More information about the docs-commits
mailing list