Changeset c0155c7

Timestamp:

07/15/2004 07:33:53 PM (20 years ago)

Author:

Matthew Burgess <matthew@…>

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:

715f65f

Parents:

a088964

Message:

• Fixed various networking inaccuracies

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

Files:

• chapter01/changelog.xml (modified) (1 diff)
• chapter06/iproute2.xml (modified) (5 diffs)
• chapter07/network.xml (modified) (4 diffs)
• general.ent (modified) (1 diff)

chapter01/changelog.xml

@@ -80 +80 @@
 </listitem>
 
+<listitem><para>July 15, 2004 [matt]: Fixed various networking inaccuracies
+(Kevin P. Fleming)</para></listitem>
+
 <listitem><para>July 14, 2004 [matt]: Upgraded to lfs-bootscripts-2.2.0.</para>
 </listitem>

chapter06/iproute2.xml

@@ -8 +8 @@
 <?dbhtml filename="iproute2.html"?>
   <indexterm zone="ch-system-iproute2">
-    <primary sortas="a-IProute2">IProute2</primary>
+    <primary sortas="a-iproute2">iproute2</primary>
   </indexterm>
   <sect2 role="package">
     <title/>
-    <para>The IPRoute2 package contains programs for basic networking.</para>
+    <para>The iproute2 package contains programs for basic and advanced
+          IPV4-based networking.
+    </para>
     <segmentedlist>
       <segtitle>&buildtime;</segtitle>
@@ -22 +24 @@
     </segmentedlist>
     <segmentedlist>
-      <segtitle>IPRoute2 installation depends on</segtitle>
+      <segtitle>iproute2 installation depends on</segtitle>
       <seglistitem>
         <seg>sed, GCC, Glibc, Make, Linux-Headers</seg>
@@ -29 +31 @@
   </sect2>
   <sect2 role="installation">
-    <title>Installation of IProute2</title>
-    <para>The <command>arp</command> binary included in this package is
-          dependent on Berkeley-DB.  As <command>arp</command> is not a very
+    <title>Installation of iproute2</title>
+    <para>The <command>arpd</command> binary included in this package is
+          dependent on Berkeley DB.  As <command>arpd</command> is not a very
           common requirement on a base Linux system we remove the dependency on
-          Berkeley-DB by applying the patch using the command below.  If you
-          need the <command>arp</command> binary, then instructions for
-          compiling Berkeley-DB can be found in the <ulink
+          Berkeley DB by applying the patch using the command below.  If you
+          need the <command>arpd</command> binary, then instructions for
+          compiling Berkeley DB can be found in the <ulink
           url="http://www.linuxfromscratch.org/blfs/view/cvs/content/databases.html#db">BLFS book</ulink>.
     </para>
@@ -41 +43 @@
     <screen><userinput>patch -Np1 -i ../iproute2-&iproute2-version;-remove_db-1.patch</userinput></screen>
 
-    <para>Prepare IProute2 for compilation:</para>
+    <para>Prepare iproute2 for compilation:</para>
     <screen> <userinput>./configure </userinput></screen>
 
@@ -54 +56 @@
 
   <sect2 id="contents-iproute2" role="content">
-    <title>Contents of IPRoute2</title>
+    <title>Contents of iproute2</title>
     <segmentedlist>
       <segtitle>Installed programs</segtitle>

chapter07/network.xml

@@ -28 +28 @@
 directory should contain subdirectories in the form of
 <filename>ifconfig.xyz</filename>, where <quote>xyz</quote> is a network
-interface name (such as eth0 or eth0:1)</para>
+interface name (such as eth0)</para>
 
 <para>If you decide to rename or move this
@@ -46 +46 @@
 IP=192.168.1.1
 GATEWAY=192.168.1.2
-NETMASK=24
+PREFIX=24
 BROADCAST=192.168.1.255
 EOF</userinput></screen>
 
-<para>Of course, the values of those variables have to be changed 
-in every file to match the proper setup. If the ONBOOT variable is set
-to <quote>yes</quote>, the network script will bring up the equivalent NIC (Network Interface Card)
- during the booting of the system.
-If set to anything but <quote>yes</quote>, the equivalent NIC will be ignored by the network script
-and not brought up.</para>
+<para>Of course, the values of those variables have to be changed in every file
+to match the proper setup. If the ONBOOT variable is set to <quote>yes</quote>,
+the network script will bring up the equivalent interface during the booting of
+the system.  If set to anything but <quote>yes</quote>, the equivalent interface
+will be ignored by the network script and not brought up.</para>
 
-<para>The SERVICE entry defines the method of obtaining the IP address.
-The LFS bootscripts have a modular IP assignment format, and by creating
-additional files in <filename class="directory">/etc/sysconfig/network-devices/services</filename>, you can allow
-other IP assignment methods.  This would commonly be used if you need DHCP,
-which is addressed in the BLFS book.</para>
+<para>The SERVICE entry defines the method of obtaining the IP address.  The LFS
+bootscripts have a modular IP assignment format, and by creating additional
+files in
+<filename class="directory">/etc/sysconfig/network-devices/services</filename>,
+you can allow other IP assignment methods.  This would commonly be used if you
+need DHCP, which is addressed in the BLFS book.</para>
 
 <para>Of course, GATEWAY should contain the IP of your default gateway, if you
-have one. If not, then comment out the variable entirely.</para>
+have one. If not, then don't include the GATEWAY line in the configuration
+file.</para>
 
 </sect2>
@@ -74 +75 @@
 <para>If you're going to be connected to the Internet then most likely you'll
 need some means of DNS name resolution to resolve Internet domain names to IP
-addresses. This is best achieved by placing the IP address of your DNS, available from your ISP (Internet Service Provider) or network administrator,
-into <filename>/etc/resolv.conf</filename>. Create the file by running the
-following:</para>
+addresses. This is best achieved by placing the IP address of your assigned DNS
+resolver, available from your ISP (Internet Service Provider) 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"
@@ -87 +89 @@
 EOF</userinput></screen>
 
-<para>Of course, replace <replaceable>[IP address of your nameserver]</replaceable> with the IP
-address of the DNS most appropriate for your setup. There will often be
-more than one entry (requirements demand secondary servers for fallback capability). The IP address may even be a router on your local network.</para>
+<para>Of course, replace
+<replaceable>[IP address of your nameserver]</replaceable> with the IP address
+of the DNS resolver assigned for your use. There will often be more than one
+entry (requirements demand secondary servers for fallback capability). The IP
+address may even be a router on your local network.</para>
 
 </sect2>

general.ent

@@ -1 +1 @@
 <?xml version="1.0" encoding="ISO-8859-1"?>
-<!ENTITY version "SVN-20040714">
-<!ENTITY releasedate "July 14, 2004">
+<!ENTITY version "SVN-20040715">
+<!ENTITY releasedate "July 15, 2004">
 <!ENTITY milestone "6.0">