Ignore:
Timestamp:
12/18/2005 06:31:04 PM (18 years ago)
Author:
Manuel Canales Esparcia <manuel@…>
Branches:
10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
Children:
faaf88e
Parents:
b78c747
Message:

Chapter07 indentation.

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

File:
1 edited

Legend:

Unmodified
Added
Removed

  • chapter07/network.xml

    rb78c747 rd781ffb  
    11<?xml version="1.0" encoding="ISO-8859-1"?>
    2 <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
     2<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
     3  "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
    34  <!ENTITY % general-entities SYSTEM "../general.ent">
    45  %general-entities;
    56]>
     7
    68<sect1 id="ch-scripts-network">
    7 <title>Configuring the network Script</title>
    8 <?dbhtml filename="network.html"?>
     9  <?dbhtml filename="network.html"?>
    910
    10 <indexterm zone="ch-scripts-network">
    11 <primary sortas="d-network">network</primary>
    12 <secondary>configuring</secondary></indexterm>
     11  <title>Configuring the network Script</title>
    1312
    14 <para>This section only applies if a network card is to be
    15 configured.</para>
     13  <indexterm zone="ch-scripts-network">
     14    <primary sortas="d-network">network</primary>
     15  <secondary>configuring</secondary></indexterm>
    1616
    17 <para>If a network card will not be used, there is likely no need to
    18 create any configuration files relating to network cards. If that is
    19 the case, remove the <filename class="symlink">network</filename>
    20 symlinks from all run-level directories (<filename
    21 class="directory">/etc/rc.d/rc*.d</filename>).</para>
     17  <para>This section only applies if a network card is to be
     18  configured.</para>
    2219
    23 <sect2>
    24 <title>Creating Network Interface Configuration Files</title>
     20  <para>If a network card will not be used, there is likely no need to
     21  create any configuration files relating to network cards. If that is
     22  the case, remove the <filename class="symlink">network</filename>
     23  symlinks from all run-level directories (<filename
     24  class="directory">/etc/rc.d/rc*.d</filename>).</para>
    2525
    26 <!-- Edit Me -->
    27 <para>Which interfaces are brought up and down by the network script
    28 depends on the files and directories in the <filename
    29 class="directory">/etc/sysconfig/network-devices</filename> hierarchy.
    30 This directory should contain a sub-directory for each interface to be configured,
    31 such as <filename>ifconfig.xyz</filename>, where <quote>xyz</quote> is a
    32 network interface name. Inside this directory would be files defining
    33 the attributes to this interface, such as its IP address(es), subnet
    34 masks, and so forth.</para>
     26  <sect2>
     27    <title>Creating Network Interface Configuration Files</title>
    3528
    36 <para>The following command creates a sample <filename>ipv4</filename> file for
    37 the <emphasis>eth0</emphasis> device:</para>
     29    <para>Which interfaces are brought up and down by the network script
     30    depends on the files and directories in the <filename
     31    class="directory">/etc/sysconfig/network-devices</filename> hierarchy.
     32    This directory should contain a sub-directory for each interface to be
     33    configured, such as <filename>ifconfig.xyz</filename>, where
     34    <quote>xyz</quote> is a network interface name. Inside this directory
     35    would be files defining the attributes to this interface, such as its IP
     36    address(es), subnet masks, and so forth.</para>
     37
     38    <para>The following command creates a sample <filename>ipv4</filename>
     39    file for the <emphasis>eth0</emphasis> device:</para>
    3840
    3941<screen><userinput>cd /etc/sysconfig/network-devices &amp;&amp;
    … …  
    4850EOF</userinput></screen>
    4951
    50 <para>The values of these variables must be changed in every file to match the
    51 proper setup. If the <envar>ONBOOT</envar> variable is set to <quote>yes</quote>
    52 the network script will bring up the Network Interface Card (NIC) during booting
    53 of the system. If set to anything but <quote>yes</quote> the NIC will be ignored
    54 by the network script and not be brought up.</para>
     52    <para>The values of these variables must be changed in every file to match
     53    the proper setup. If the <envar>ONBOOT</envar> variable is set to
     54    <quote>yes</quote> the network script will bring up the Network Interface
     55    Card (NIC) during booting of the system. If set to anything but
     56    <quote>yes</quote> the NIC will be ignored by the network script and not
     57    be brought up.</para>
    5558
    56 <para>The <envar>SERVICE</envar> variable defines the method used for obtaining
    57 the IP address. The LFS-Bootscripts package has a modular IP assignment format,
    58 and creating additional files in the <filename
    59 class="directory">/etc/sysconfig/network-devices/services</filename> directory
    60 allows other IP assignment methods. This is commonly used for Dynamic Host
    61 Configuration Protocol (DHCP), which is addressed in the BLFS book.</para>
     59    <para>The <envar>SERVICE</envar> variable defines the method used for
     60    obtaining the IP address. The LFS-Bootscripts package has a modular IP
     61    assignment format, and creating additional files in the <filename
     62    class="directory">/etc/sysconfig/network-devices/services</filename>
     63    directory allows other IP assignment methods. This is commonly used for
     64    Dynamic Host Configuration Protocol (DHCP), which is addressed in the
     65    BLFS book.</para>
    6266
    63 <para>The <envar>GATEWAY</envar> variable should contain
    64 the default gateway IP address, if one is present. If not, then comment out
    65 the variable entirely.</para>
     67    <para>The <envar>GATEWAY</envar> variable should contain the default
     68    gateway IP address, if one is present. If not, then comment out the
     69    variable entirely.</para>
    6670
    67 <para>The <envar>PREFIX</envar> variable needs to contain the number of bits
    68 used in the subnet. Each octet in an IP address is 8 bits. If the subnet's
    69 netmask is 255.255.255.0, then it is using the first three octets (24 bits) to
    70 specify the network number. If the netmask is 255.255.255.240, it would be using
    71 the first 28 bits.  Prefixes longer than 24 bits are commonly used by DSL and
    72 cable-based Internet Service Providers (ISPs). In this example (PREFIX=24), the
    73 netmask is 255.255.255.0. Adjust the <envar>PREFIX</envar> variable according to
    74 your specific subnet.</para>
     71    <para>The <envar>PREFIX</envar> variable needs to contain the number of
     72    bits used in the subnet. Each octet in an IP address is 8 bits. If the
     73    subnet's netmask is 255.255.255.0, then it is using the first three octets
     74    (24 bits) to specify the network number. If the netmask is 255.255.255.240,
     75    it would be using the first 28 bits.  Prefixes longer than 24 bits are
     76    commonly used by DSL and cable-based Internet Service Providers (ISPs).
     77    In this example (PREFIX=24), the netmask is 255.255.255.0. Adjust the
     78    <envar>PREFIX</envar> variable according to your specific subnet.</para>
    7579
    76 </sect2>
     80  </sect2>
    7781
    78 <sect2 id="resolv.conf">
    79 <title>Creating the /etc/resolv.conf File</title>
    80 <indexterm zone="resolv.conf"><primary sortas="e-/etc/resolv.conf">/etc/resolv.conf</primary></indexterm>
     82  <sect2 id="resolv.conf">
     83    <title>Creating the /etc/resolv.conf File</title>
    8184
    82 <para>If the system is going to be connected to the Internet, it will
    83 need some means of Domain Name Service (DNS) name resolution to
    84 resolve Internet domain names to IP addresses, and vice versa. This is
    85 best achieved by placing the IP address of the DNS server, available
    86 from the ISP or network administrator, into
    87 <filename>/etc/resolv.conf</filename>. Create the file by running the
    88 following:</para>
     85    <indexterm zone="resolv.conf">
     86      <primary sortas="e-/etc/resolv.conf">/etc/resolv.conf</primary>
     87    </indexterm>
     88
     89    <para>If the system is going to be connected to the Internet, it will
     90    need some means of Domain Name Service (DNS) name resolution to
     91    resolve Internet domain names to IP addresses, and vice versa. This is
     92    best achieved by placing the IP address of the DNS server, available
     93    from the ISP or network administrator, into
     94    <filename>/etc/resolv.conf</filename>. Create the file by running the
     95    following:</para>
    8996
    9097<screen><userinput>cat &gt; /etc/resolv.conf &lt;&lt; "EOF"
    … …  
    98105EOF</userinput></screen>
    99106
    100 <para>Replace <replaceable>[IP address of the
    101 nameserver]</replaceable> with the IP address of the DNS most
    102 appropriate for the setup. There will often be more than one entry
    103 (requirements demand secondary servers for fallback capability). If
    104 you only need or want one DNS server, remove the second
    105 <emphasis>nameserver</emphasis> line from the file. The IP address may
    106 also be a router on the local network.</para>
    107 </sect2>
     107    <para>Replace <replaceable>[IP address of the nameserver]</replaceable>
     108    with the IP address of the DNS most appropriate for the setup. There will
     109    often be more than one entry (requirements demand secondary servers for
     110    fallback capability). If you only need or want one DNS server, remove the
     111    second <emphasis>nameserver</emphasis> line from the file. The IP address
     112    may also be a router on the local network.</para>
     113
     114  </sect2>
    108115
    109116</sect1>
    110 
Note: See TracChangeset for help on using the changeset viewer.