Ignore:
Timestamp:
06/19/2004 04:54:58 PM (20 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.0, 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:
8250be1
Parents:
8ad7980
Message:

Tags corrections

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

File:
1 edited

Legend:

Unmodified
Added
Removed

  • chapter07/network.xml

    r8ad7980 rf67f5cf  
    1717<para>If you don't have any network cards, you are most likely not going to
    1818create any configuration files relating to network cards. If that is the
    19 case, you must remove the <filename>network</filename> symlinks from all the
     19case, you must remove the <filename class="symlink">network</filename> symlinks from all the
    2020run-level directories
    2121(<filename class="directory">/etc/rc.d/rc*.d</filename>)</para>
    … …  
    2525
    2626<para>Which interfaces are brought up and down by the network script depends on
    27 the files in the /etc/sysconfig/network-devices directory. This
    28 directory should contain files in the form of ifconfig.xyz, where xyz is a
     27the files in the <filename class="directory">/etc/sysconfig/network-devices</filename> directory. This
     28directory should contain files in the form of <filename>ifconfig.xyz</filename>, where <quote>xyz</quote> is a
    2929network interface name (such as eth0 or eth0:1)</para>
    3030
    31 <para>If you decide to rename or move this /etc/sysconfig/network-devices
    32 directory, make sure you update the /etc/sysconfig/rc file as well and
    33 update the network_devices by providing it with the new path.</para>
     31<para>If you decide to rename or move this <filename class="directory">/etc/sysconfig/network-devices</filename>
     32directory, make sure you update the <filename>/etc/sysconfig/rc</filename> file as well and
     33update the <quote>network_devices</quote> by providing it with the new path.</para>
    3434
    3535<para>Now, new files are created in that directory.
    36 The following command creates a sample ifconfig.eth0 file:</para>
     36The following command creates a sample <filename>ifconfig.eth0</filename> file:</para>
    3737
    38 <screen><userinput>cat &gt; /etc/sysconfig/network-devices/ifconfig.eth0 &lt;&lt; "EOF"</userinput>
     38<screen><userinput>cat &gt; /etc/sysconfig/network-devices/ifconfig.eth0 &lt;&lt; "EOF"
    3939ONBOOT=yes
    4040SERVICE=static
    … …  
    4343NETMASK=255.255.255.0
    4444BROADCAST=192.168.1.255
    45 <userinput>EOF</userinput></screen>
     45EOF</userinput></screen>
    4646
    4747<para>Of course, the values of those variables have to be changed
    4848in every file to match the proper setup. If the ONBOOT variable is set
    49 to yes, the network script will bring up the equivalent NIC (Network Interface Card)
     49to <quote>yes</quote>, the network script will bring up the equivalent NIC (Network Interface Card)
    5050 during the booting of the system.
    51 If set to anything but yes, the equivalent NIC will be ignored by the network script
     51If set to anything but <quote>yes</quote>, the equivalent NIC will be ignored by the network script
    5252and not brought up.</para>
    5353
    5454<para>The SERVICE entry defines the method of obtaining the IP address.
    5555The LFS bootscripts have a modular IP assignment format, and by creating
    56 additional files in /etc/sysconfig/network-devices/services, you can allow
     56additional files in <filename class="directory">/etc/sysconfig/network-devices/services</filename>, you can allow
    5757other IP assignment methods.  This would commonly be used if you need DHCP,
    5858which is addressed in the BLFS book.</para>
    … …  
    6363</sect2>
    6464
    65 <sect2>
     65<sect2 id="resolv.conf">
    6666<title>Creating the /etc/resolv.conf file</title>
     67<indexterm zone="resolv.conf"><primary sortas="e-/etc/resolv.conf">/etc/resolv.conf</primary></indexterm>
    6768
    6869<para>If you're going to be connected to the Internet then most likely you'll
    … …  
    7273following:</para>
    7374
    74 <screen><userinput>cat &gt; /etc/resolv.conf &lt;&lt; "EOF"</userinput>
     75<screen><userinput>cat &gt; /etc/resolv.conf &lt;&lt; "EOF"
    7576# Begin /etc/resolv.conf
    7677
    77 nameserver &lt;IP address of your nameserver&gt;
     78nameserver <replaceable>[IP address of your nameserver]</replaceable>
    7879
    7980# End /etc/resolv.conf
    80 <userinput>EOF</userinput></screen>
     81EOF</userinput></screen>
    8182
    82 <para>Of course, replace &lt;IP address of your nameserver&gt; with the IP
     83<para>Of course, replace <replaceable>[IP address of your nameserver]</replaceable> with the IP
    8384address of the DNS most appropriate for your setup. There will often be
    8485more than one entry (requirements demand secondary servers for fallback capability). The IP address may even be a router on your local network.</para>
Note: See TracChangeset for help on using the changeset viewer.