Ignore:
Timestamp:
12/20/2004 07:09:48 PM (19 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.1, 6.1.1, 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:
d16b694b
Parents:
e0a04e8
Message:

Removed text in chapter 07.

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

File:
1 edited

Legend:

Unmodified
Added
Removed

  • chapter07/network.xml

    re0a04e8 r1d317bb  
    1212<secondary>configuring</secondary></indexterm>
    1313
    14 <para>This section only applies if you're going to configure a network
    15 card.</para>
    16 
    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>
    22 
    2314<sect2>
    2415<title>Creating network interface configuration files</title>
    2516
    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>
    31 
    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>
    36 
    37 <para>Now, new files are created in that directory.  The following command
    38 creates a sample <filename>ipv4</filename> file for the
     17<para>The following command creates a sample <filename>ipv4</filename> file for the
    3918<filename>eth0</filename> device:</para>
    4019
    … …  
    5029EOF</userinput></screen>
    5130
    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>
    57 
    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>
    64 
    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>
    68 
    6931</sect2>
    7032
    … …  
    7335<indexterm zone="resolv.conf"><primary sortas="e-/etc/resolv.conf">/etc/resolv.conf</primary></indexterm>
    7436
    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>
     37<para>Create the file by running the following:</para>
    8138
    8239<screen><userinput>cat &gt; /etc/resolv.conf &lt;&lt; "EOF"
    … …  
    8946EOF</userinput></screen>
    9047
    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 
    9748</sect2>
    9849
Note: See TracChangeset for help on using the changeset viewer.