Changeset 81fd230 for chapter07/network.xml

Timestamp:

02/19/2005 10:16:42 PM (19 years ago)

Author:

Gerard Beekmans <gerard@…>

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:

3d31fc4

Parents:

2f9131f

Message:

Trunk is now identical to Testing

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

File:

• chapter07/network.xml (modified) (3 diffs)

chapter07/network.xml

@@ -8 +8 @@
 <?dbhtml filename="network.html"?>
 
+<indexterm zone="ch-scripts-network">
+<primary sortas="d-network">network</primary>
+<secondary>configuring</secondary></indexterm>
+
+<para>This section only applies if a network card is to be
+configured.</para>
+
+<para>If a network card will not be used, there is likely no need to
+create any configuration files relating to network cards. If that is
+the case, remove the <filename class="symlink">network</filename>
+symlinks from all run-level directories (<filename
+class="directory">/etc/rc.d/rc*.d</filename>).</para>
 
 <sect2>
 <title>Creating Network Interface Configuration Files</title>
 
-<para>The following command creates a sample <filename>ipv4</filename> file for the
-<filename>eth0</filename> device:</para>
+<!-- Edit Me -->
+<para>Which interfaces are brought up and down by the network script
+depends on the files and directories in the <filename
+class="directory">/etc/sysconfig/network-devices</filename> hierarchy.
+This directory should contain a directory for each interface to be configured,
+such as <filename>ifconfig.xyz</filename>, where <quote>xyz</quote> is a
+network interface name. Inside this directory would be files defining
+the attributes to this interface, such as its IP address(es), subnet
+masks, and so forth.</para>
+<!-- -->
+
+<para>If the <filename
+class="directory">/etc/sysconfig/network-devices</filename> directory
+is to be renamed or moved, make sure to edit the
+<filename>/etc/sysconfig/rc</filename> file and update the
+<quote>network_devices</quote> option by providing it with the new
+path.</para>
+
+<para>New files are created in this directory. The following
+command creates a sample <filename>ipv4</filename> file for the
+<emphasis>eth0</emphasis> device:</para>
 
 <screen><userinput>cd /etc/sysconfig/network-devices &amp;&amp;
@@ -26 +57 @@
 EOF</userinput></screen>
 
+<para>The values of these variables must be changed in every file to
+match the proper setup. If the <envar>ONBOOT</envar> variable is
+set to <quote>yes</quote> the network script will bring up the
+Network Interface Card (NIC) during booting of the system. If set
+to anything but <quote>yes</quote> the NIC will be ignored by the
+network script and not brought up.</para>
+
+<para>The <envar>SERVICE</envar> variable defines the method of
+obtaining the IP address. The LFS bootscripts have a modular IP
+assignment format, and creating additional files in the <filename
+class="directory">/etc/sysconfig/network-devices/services</filename>
+directory allows other IP assignment methods. This is commonly used
+for Dynamic Host Configuration Protocol (DHCP), which is addressed in the BLFS book.</para>
+
+<para>The <envar>GATEWAY</envar> variable should contain
+the default gateway IP address, if one is present. If not, then comment out
+the variable entirely.</para>
+
+<para>The <envar>PREFIX</envar> variable needs to contain the
+number of bits used in the subnet. Each octet in an IP address is 8
+bits. If the subnet's netmask is 255.255.255.0, then it is using the
+first three octets (24 bits) to specify the network number. If the
+netmask is 255.255.255.240, it would be using the first 28 bits.
+Prefixes longer than 24 bits are commonly used by DSL- and cable-based
+Internet Service Providers (ISPs).  In this example (PREFIX=24), the netmask
+is 255.255.255.0. Adjust according to the specific subnet.</para>
+
 </sect2>
 
 <sect2 id="resolv.conf">
 <title>Creating the /etc/resolv.conf File</title>
+<indexterm zone="resolv.conf"><primary sortas="e-/etc/resolv.conf">/etc/resolv.conf</primary></indexterm>
 
-<para>Create the file by running the following:</para>
+<para>If the system is going to be connected to the Internet, it will
+need some means of Domain Name Service (DNS) name resolution to
+resolve Internet domain names to IP addresses, and vice versa. This is
+best achieved by placing the IP address of the DNS server, available
+from the ISP or network administrator, into
+<filename>/etc/resolv.conf</filename>. Create the file by running the
+following:</para>
 
 <screen><userinput>cat &gt; /etc/resolv.conf &lt;&lt; "EOF"
@@ -43 +108 @@
 EOF</userinput></screen>
 
+<para>Replace <replaceable>[IP address of the
+nameserver]</replaceable> with the IP address of the DNS most
+appropriate for the setup. There will often be more than one entry
+(requirements demand secondary servers for fallback capability). If
+you only need or want one DNS server, remove the second
+<emphasis>nameserver</emphasis> line from the file. The IP address may
+also be a router on the local network.</para>
 </sect2>
 
 </sect1>
+