aboutsummaryrefslogtreecommitdiffstats
path: root/chapter07/network.xml
diff options
context:
space:
mode:
authorManuel Canales Esparcia <manuel@linuxfromscratch.org>2004-06-19 16:54:58 +0000
committerManuel Canales Esparcia <manuel@linuxfromscratch.org>2004-06-19 16:54:58 +0000
commitf67f5cfed55cb2ac26f29d16ad1f099461e7cf98 (patch)
treecdb61a57a3414232a71d7bdc81779c9fd0364604 /chapter07/network.xml
parent8ad79807a3c97e18a90319c9b91018b0be2bbb3c (diff)
Tags corrections
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3813 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'chapter07/network.xml')
-rw-r--r--chapter07/network.xml35
1 files changed, 18 insertions, 17 deletions
diff --git a/chapter07/network.xml b/chapter07/network.xml
index 0082c47d9..19109c01e 100644
--- a/chapter07/network.xml
+++ b/chapter07/network.xml
@@ -16,7 +16,7 @@ card.</para>
<para>If you don't have any network cards, you are most likely not going to
create any configuration files relating to network cards. If that is the
-case, you must remove the <filename>network</filename> symlinks from all the
+case, you must remove the <filename class="symlink">network</filename> symlinks from all the
run-level directories
(<filename class="directory">/etc/rc.d/rc*.d</filename>)</para>
@@ -24,36 +24,36 @@ run-level directories
<title>Creating network interface configuration files</title>
<para>Which interfaces are brought up and down by the network script depends on
-the files in the /etc/sysconfig/network-devices directory. This
-directory should contain files in the form of ifconfig.xyz, where xyz is a
+the files in the <filename class="directory">/etc/sysconfig/network-devices</filename> directory. This
+directory should contain files in the form of <filename>ifconfig.xyz</filename>, where <quote>xyz</quote> is a
network interface name (such as eth0 or eth0:1)</para>
-<para>If you decide to rename or move this /etc/sysconfig/network-devices
-directory, make sure you update the /etc/sysconfig/rc file as well and
-update the network_devices by providing it with the new path.</para>
+<para>If you decide to rename or move this <filename class="directory">/etc/sysconfig/network-devices</filename>
+directory, make sure you update the <filename>/etc/sysconfig/rc</filename> file as well and
+update the <quote>network_devices</quote> by providing it with the new path.</para>
<para>Now, new files are created in that directory.
-The following command creates a sample ifconfig.eth0 file:</para>
+The following command creates a sample <filename>ifconfig.eth0</filename> file:</para>
-<screen><userinput>cat &gt; /etc/sysconfig/network-devices/ifconfig.eth0 &lt;&lt; "EOF"</userinput>
+<screen><userinput>cat &gt; /etc/sysconfig/network-devices/ifconfig.eth0 &lt;&lt; "EOF"
ONBOOT=yes
SERVICE=static
IP=192.168.1.1
GATEWAY=192.168.1.2
NETMASK=255.255.255.0
BROADCAST=192.168.1.255
-<userinput>EOF</userinput></screen>
+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 yes, the network script will bring up the equivalent NIC (Network Interface Card)
+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 yes, the equivalent NIC will be ignored by the network script
+If set to anything but <quote>yes</quote>, the equivalent NIC 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 /etc/sysconfig/network-devices/services, you can allow
+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>
@@ -62,8 +62,9 @@ have one. If not, then comment out the variable entirely.</para>
</sect2>
-<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>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
@@ -71,15 +72,15 @@ addresses. This is best achieved by placing the IP address of your DNS, availabl
into <filename>/etc/resolv.conf</filename>. Create the file by running the
following:</para>
-<screen><userinput>cat &gt; /etc/resolv.conf &lt;&lt; "EOF"</userinput>
+<screen><userinput>cat &gt; /etc/resolv.conf &lt;&lt; "EOF"
# Begin /etc/resolv.conf
-nameserver &lt;IP address of your nameserver&gt;
+nameserver <replaceable>[IP address of your nameserver]</replaceable>
# End /etc/resolv.conf
-<userinput>EOF</userinput></screen>
+EOF</userinput></screen>
-<para>Of course, replace &lt;IP address of your nameserver&gt; with the IP
+<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>