Ignore:
File:
1 edited

Legend:

Unmodified
Added
Removed
  • chapter09/network.xml

    r1966b8d rc5c1e86  
    1818    <title>Creating Network Interface Configuration Files</title>
    1919
    20     <para>Which interfaces are brought up and down by the network script
    21     usually depends on the files in <filename
    22     class="directory">/etc/sysconfig/</filename>.  This directory should
     20    <para>The files in <filename class="directory">/etc/sysconfig/</filename>
     21    usually determine which interfaces are brought up and down by the network
     22    script.  This directory should
    2323    contain a file for each interface to be configured, such as
    24     <filename>ifconfig.xyz</filename>, where <quote>xyz</quote> should describe
     24    <filename>ifconfig.xyz</filename>, where <quote>xyz</quote> describes
    2525    the network card.  The interface name (e.g. eth0) is usually appropriate.
    26     Inside this file are attributes to this interface, such as its IP
    27     address(es), subnet masks, and so forth.  It is necessary that the stem of
    28     the filename be <emphasis>ifconfig</emphasis>.</para>
     26    Each file contains the attributes of one interface, such as its IP
     27    address(es), subnet masks, and so forth.  The stem of
     28    the filename must be <emphasis>ifconfig</emphasis>.</para>
    2929
    3030    <note>
     
    3939      configuration of the udev daemon running on the system.  The udev
    4040      daemon for LFS (installed in <xref linkend="ch-system-eudev"/>) will
    41       not run until the LFS system is booted.  So it's unreliable to
    42       determine the interface names being used in LFS system by running
     41      not run until the LFS system is booted.  So the interface names
     42      in the LFS system cannot always be determined by running
    4343      those commands on the host distro,
    44       <emphasis>even though in the chroot environment</emphasis>.</para>
     44      <emphasis>even in the chroot environment</emphasis>.</para>
    4545    </note>
    4646
     
    6060EOF</userinput></screen>
    6161
    62     <para>The values in italics must be changed in every file to match
    63     the proper setup.</para>
     62    <para>The values in italics must be changed in each file, to set
     63    the interfaces up correctly.</para>
    6464
    6565    <para>If the <envar>ONBOOT</envar> variable is set to <quote>yes</quote> the
    6666    System V network script will bring up the Network Interface Card (NIC) during
    67     the system boot process. If set to anything but <quote>yes</quote> the NIC
    68     will be ignored by the network script and not be automatically brought up.
    69     The interface can be manually started or stopped with the
     67    the system boot process. If set to anything besides <quote>yes</quote>, the NIC
     68    will be ignored by the network script and will not be started automatically.
     69    Interfaces can be manually started or stopped with the
    7070    <command>ifup</command> and <command>ifdown</command> commands.</para>
    7171
     
    8585    variable entirely.</para>
    8686
    87     <para>The <envar>PREFIX</envar> variable contains the number of
    88     bits used in the subnet. Each octet in an IP address is 8 bits. If the
    89     subnet's netmask is 255.255.255.0, then it is using the first three octets
     87    <para>The <envar>PREFIX</envar> variable specifies the number of
     88    bits used in the subnet. Each segment of an IP address is 8 bits. If the
     89    subnet's netmask is 255.255.255.0, then it is using the first three segments
    9090    (24 bits) to specify the network number. If the netmask is 255.255.255.240,
    91     it would be using the first 28 bits.  Prefixes longer than 24 bits are
     91    the subnet is using the first 28 bits.  Prefixes longer than 24 bits are
    9292    commonly used by DSL and cable-based Internet Service Providers (ISPs).
    9393    In this example (PREFIX=24), the netmask is 255.255.255.0. Adjust the
     
    140140
    141141  <sect2 id="ch-config-hostname">
    142     <title>Configuring the system hostname</title>
     142    <title>Configuring the System Hostname</title>
    143143
    144144    <indexterm zone="ch-config-hostname">
     
    157157     <para><replaceable>&lt;lfs&gt;</replaceable> needs to be replaced with the
    158158     name given to the computer. Do not enter the Fully Qualified Domain Name
    159      (FQDN) here. That information is put in the
     159     (FQDN) here. That information goes in the
    160160     <filename>/etc/hosts</filename> file.</para>
    161161
Note: See TracChangeset for help on using the changeset viewer.