Ignore:
Timestamp:
08/08/2004 02:11:27 AM (20 years ago)
Author:
Gerard Beekmans <gerard@…>
Branches:
6.0
Children:
1dc34de7
Parents:
ef13657
Message:

Completed global edits for upcoming 6.0 release

git-svn-id: ​http://svn.linuxfromscratch.org/LFS/branches/testing/BOOK@4001 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

File:
1 edited

Legend:

Unmodified
Added
Removed

  • chapter07/network.xml

    ref13657 r5ba3d1d  
    1212<secondary>configuring</secondary></indexterm>
    1313
    14 <para>This section only applies if you're going to configure a network
    15 card.</para>
     14<para>This section only applies if a network card is to be
     15configured.</para>
    1616
    17 <para>If you don't have any network cards, you are most likely not going to
    18 create any configuration files relating to network cards. If that is the
    19 case, you must remove the <filename class="symlink">network</filename> symlinks from all the
    20 run-level directories
    21 (<filename class="directory">/etc/rc.d/rc*.d</filename>)</para>
     17<para>If a network card will not be used, there is likely no need to
     18create any configuration files relating to network cards. If that is
     19the case, remove the <filename class="symlink">network</filename>
     20symlinks from all run-level directories (<filename
     21class="directory">/etc/rc.d/rc*.d</filename>).</para>
    2222
    2323<sect2>
    2424<title>Creating network interface configuration files</title>
    2525
    26 <para>Which interfaces are brought up and down by the network script depends on
    27 the files in the <filename class="directory">/etc/sysconfig/network-devices</filename> directory. This
    28 directory should contain subdirectories in the form of
    29 <filename>ifconfig.xyz</filename>, where <quote>xyz</quote> is a network
    30 interface name (such as eth0)</para>
     26<para>Which interfaces are brought up and down by the network script
     27depends on the files in the <filename
     28class="directory">/etc/sysconfig/network-devices</filename> directory.
     29This directory should contain files in the form of
     30<filename>ifconfig.xyz</filename>, where <quote>xyz</quote> is a
     31network interface name (such as eth0 or eth0:1)</para>
    3132
    32 <para>If you decide to rename or move this
    33 <filename class="directory">/etc/sysconfig/network-devices</filename> directory,
    34 make sure you update the <filename>/etc/sysconfig/rc</filename> file as well and
    35 update the <quote>network_devices</quote> by providing it with the new path.</para>
     33<para>If the <filename
     34class="directory">/etc/sysconfig/network-devices</filename> directory
     35is to be renamed or moved, make sure to edit the
     36<filename>/etc/sysconfig/rc</filename> file and update the
     37<quote>network_devices</quote> option by providing it with the new
     38path.</para>
    3639
    37 <para>Now, new files are created in that directory.  The following command
    38 creates a sample <filename>ipv4</filename> file for the
    39 <filename>eth0</filename> device:</para>
     40<para>Now, new files are created in those directory. The following
     41command creates a sample <filename>ipv4</filename> file for the
     42<emphasis>eth0</emphasis> device:</para>
    4043
    4144<screen><userinput>cd /etc/sysconfig/network-devices &amp;&amp;
    … …  
    5053EOF</userinput></screen>
    5154
    52 <para>Of course, the values of those variables have to be changed in every file
    53 to match the proper setup. If the ONBOOT variable is set to <quote>yes</quote>,
    54 the network script will bring up the equivalent interface during the booting of
    55 the system.  If set to anything but <quote>yes</quote>, the equivalent interface
    56 will be ignored by the network script and not brought up.</para>
     55<para>The values of those variables must be changed in every file to
     56match the proper setup. If the <emphasis>ONBOOT</emphasis> variable is
     57set to <quote>yes</quote>, the network script will bring up the
     58Network Interface Card (NIC) during the booting of the system. If set
     59to anything but <quote>yes</quote>, the NIC will be ignored by the
     60network script and not brought up.</para>
    5761
    58 <para>The SERVICE entry defines the method of obtaining the IP address.  The LFS
    59 bootscripts have a modular IP assignment format, and by creating additional
    60 files in
    61 <filename class="directory">/etc/sysconfig/network-devices/services</filename>,
    62 you can allow other IP assignment methods.  This would commonly be used if you
    63 need DHCP, which is addressed in the BLFS book.</para>
     62<para>The <emphasis>SERVICE</emphasis> variable defines the method of
     63obtaining the IP address. The LFS bootscripts have a modular IP
     64assignment format, and creating additional files in the <filename
     65class="directory">/etc/sysconfig/network-devices/services</filename>
     66directory allows other IP assignment methods. This is commonly used
     67for DHCP, which is addressed in the BLFS book.</para>
    6468
    65 <para>Of course, GATEWAY should contain the IP of your default gateway, if you
    66 have one. If not, then don't include the GATEWAY line in the configuration
    67 file.</para>
     69<para>The <emphasis>GATEWAY</emphasis> variable should contain the IP
     70the your default gateway, if one is present. If not, then comment out
     71the variable entirely.</para>
     72
     73<para>The <emphasis>PREFIX</emphasis> variable needs to contain the
     74number of bits used in the subnet. Each octet in an IP address is 8
     75bits. If the subnet's netmask is 255.255.255.0, then it is using the
     76first three octets (24 bits) to specify the network number. If the
     77netmask is 255.255.255.240 it would be using the first 28 bits.
     78Prefixes longer than 24 bits are commonly used by DSL- and cable-based
     79Internet Service Providers.  In this example (PREFIX=24) the netmask
     80is 255.255.255.0. Adjust according to your subnet.</para>
    6881
    6982</sect2>
    … …  
    7386<indexterm zone="resolv.conf"><primary sortas="e-/etc/resolv.conf">/etc/resolv.conf</primary></indexterm>
    7487
    75 <para>If you're going to be connected to the Internet then most likely you'll
    76 need some means of DNS name resolution to resolve Internet domain names to IP
    77 addresses. This is best achieved by placing the IP address of your assigned DNS
    78 resolver, available from your ISP (Internet Service Provider) or network
    79 administrator, into <filename>/etc/resolv.conf</filename>. Create the file by
    80 running the following:</para>
     88<para>If the system is going to be connected to the Internet, it will
     89need some means of DNS name resolution to resolve Internet domain
     90names to IP addresses, and vice versa. This is best achieved by
     91placing the IP address of the DNS server, available from the Internet
     92Service Provider (ISP) or network administrator, into
     93<filename>/etc/resolv.conf</filename>. Create the file by running the
     94following:</para>
    8195
    8296<screen><userinput>cat &gt; /etc/resolv.conf &lt;&lt; "EOF"
    … …  
    8498
    8599domain {<replaceable>[Your Domain Name]</replaceable>}
    86 nameserver <replaceable>[IP address of your nameserver]</replaceable>
     100nameserver <replaceable>[IP address of your primary nameserver]</replaceable>
     101nameserver <replaceable>[IP address of your secondary nameserver]</replaceable>
    87102
    88103# End /etc/resolv.conf
    89104EOF</userinput></screen>
    90105
    91 <para>Of course, replace
    92 <replaceable>[IP address of your nameserver]</replaceable> with the IP address
    93 of the DNS resolver assigned for your use. There will often be more than one
    94 entry (requirements demand secondary servers for fallback capability). The IP
    95 address may even be a router on your local network.</para>
    96 
     106<para>Replace <replaceable>[IP address of the
     107nameserver]</replaceable> with the IP address of the DNS most
     108appropriate for the setup. There will often be more than one entry
     109(requirements demand secondary servers for fallback capability). If
     110you only need or want one DNS server, simply remove the second
     111<emphasis>nameserver</emphasis> line from the file. The IP address may
     112also be a router on the local network.</para>
    97113</sect2>
    98114
    99115</sect1>
     116
Note: See TracChangeset for help on using the changeset viewer.