diff options
| -rw-r--r-- | chapter09/network.xml | 42 |
1 files changed, 21 insertions, 21 deletions
diff --git a/chapter09/network.xml b/chapter09/network.xml index 5ea7e3add..e2d0a5edf 100644 --- a/chapter09/network.xml +++ b/chapter09/network.xml @@ -17,15 +17,15 @@ <sect2> <title>Creating Network Interface Configuration Files</title> - <para>Which interfaces are brought up and down by the network script - usually depends on the files in <filename - class="directory">/etc/sysconfig/</filename>. This directory should + <para>The files in <filename class="directory">/etc/sysconfig/</filename> + usually determine which interfaces are brought up and down by the network + script. This directory should contain a file for each interface to be configured, such as - <filename>ifconfig.xyz</filename>, where <quote>xyz</quote> should describe + <filename>ifconfig.xyz</filename>, where <quote>xyz</quote> describes the network card. The interface name (e.g. eth0) is usually appropriate. - Inside this file are attributes to this interface, such as its IP - address(es), subnet masks, and so forth. It is necessary that the stem of - the filename be <emphasis>ifconfig</emphasis>.</para> + Each file contains the attributes of one interface, such as its IP + address(es), subnet masks, and so forth. The stem of + the filename must be <emphasis>ifconfig</emphasis>.</para> <note> <para>If the procedure in the previous section was not used, udev @@ -38,10 +38,10 @@ <para>The interface names depend on the implementation and configuration of the udev daemon running on the system. The udev daemon for LFS (installed in <xref linkend="ch-system-eudev"/>) will - not run until the LFS system is booted. So it's unreliable to - determine the interface names being used in LFS system by running + not run until the LFS system is booted. So the interface names + in the LFS system cannot always be determined by running those commands on the host distro, - <emphasis>even though in the chroot environment</emphasis>.</para> + <emphasis>even in the chroot environment</emphasis>.</para> </note> <para>The following command creates a sample file for the @@ -59,14 +59,14 @@ PREFIX=<replaceable>24</replaceable> BROADCAST=<replaceable>192.168.1.255</replaceable></literal> EOF</userinput></screen> - <para>The values in italics must be changed in every file to match - the proper setup.</para> + <para>The values in italics must be changed in each file, to set + the interfaces up correctly.</para> <para>If the <envar>ONBOOT</envar> variable is set to <quote>yes</quote> the System V network script will bring up the Network Interface Card (NIC) during - the system boot process. If set to anything but <quote>yes</quote> the NIC - will be ignored by the network script and not be automatically brought up. - The interface can be manually started or stopped with the + the system boot process. If set to anything besides <quote>yes</quote>, the NIC + will be ignored by the network script and will not be started automatically. + Interfaces can be manually started or stopped with the <command>ifup</command> and <command>ifdown</command> commands.</para> <para>The <envar>IFACE</envar> variable defines the interface name, @@ -84,11 +84,11 @@ EOF</userinput></screen> gateway IP address, if one is present. If not, then comment out the variable entirely.</para> - <para>The <envar>PREFIX</envar> variable contains the number of - bits used in the subnet. Each octet in an IP address is 8 bits. If the - subnet's netmask is 255.255.255.0, then it is using the first three octets + <para>The <envar>PREFIX</envar> variable specifies the number of + bits used in the subnet. Each segment of an IP address is 8 bits. If the + subnet's netmask is 255.255.255.0, then it is using the first three segments (24 bits) to specify the network number. If the netmask is 255.255.255.240, - it would be using the first 28 bits. Prefixes longer than 24 bits are + the subnet is using the first 28 bits. Prefixes longer than 24 bits are commonly used by DSL and cable-based Internet Service Providers (ISPs). In this example (PREFIX=24), the netmask is 255.255.255.0. Adjust the <envar>PREFIX</envar> variable according to your specific subnet. @@ -139,7 +139,7 @@ EOF</userinput></screen> </sect2> <sect2 id="ch-config-hostname"> - <title>Configuring the system hostname</title> + <title>Configuring the System Hostname</title> <indexterm zone="ch-config-hostname"> <primary sortas="d-hostname">hostname</primary> @@ -156,7 +156,7 @@ EOF</userinput></screen> <para><replaceable><lfs></replaceable> needs to be replaced with the name given to the computer. Do not enter the Fully Qualified Domain Name - (FQDN) here. That information is put in the + (FQDN) here. That information goes in the <filename>/etc/hosts</filename> file.</para> </sect2> |