r4133 - branches/testing/BOOK/chapter07

manuel at linuxfromscratch.org manuel at linuxfromscratch.org
Sun Sep 5 09:24:00 PDT 2004


Author: manuel
Date: 2004-09-05 10:23:58 -0600 (Sun, 05 Sep 2004)
New Revision: 4133

Modified:
   branches/testing/BOOK/chapter07/bootscripts.xml
   branches/testing/BOOK/chapter07/console.xml
   branches/testing/BOOK/chapter07/inputrc.xml
   branches/testing/BOOK/chapter07/network.xml
   branches/testing/BOOK/chapter07/profile.xml
   branches/testing/BOOK/chapter07/setclock.xml
   branches/testing/BOOK/chapter07/udev.xml
Log:
Tags corrections, Chapter 7.

Modified: branches/testing/BOOK/chapter07/bootscripts.xml
===================================================================
--- branches/testing/BOOK/chapter07/bootscripts.xml	2004-09-05 13:22:23 UTC (rev 4132)
+++ branches/testing/BOOK/chapter07/bootscripts.xml	2004-09-05 16:23:58 UTC (rev 4133)
@@ -3,7 +3,7 @@
   <!ENTITY % general-entities SYSTEM "../general.ent">
   %general-entities;
 ]>
-<sect1 id="ch-scripts-bootscripts" xreflabel="Bootscripts" role="wrap">
+<sect1 id="ch-scripts-bootscripts" role="wrap">
 <title>LFS-Bootscripts-&bootscripts-version;</title>
 <?dbhtml filename="bootscripts.html"?>
 

Modified: branches/testing/BOOK/chapter07/console.xml
===================================================================
--- branches/testing/BOOK/chapter07/console.xml	2004-09-05 13:22:23 UTC (rev 4132)
+++ branches/testing/BOOK/chapter07/console.xml	2004-09-05 16:23:58 UTC (rev 4133)
@@ -45,13 +45,13 @@
 FONT="lat9-16 -u iso01"</literal>
 EOF</userinput></screen>
 
-<note><para>The FONT line above is correct only for the ISO 8859-15
+<note><para>The <envar>FONT</envar> line above is correct only for the ISO 8859-15
 character set. If using ISO 8859-1 and, therefore, a pound sign
-instead of Euro, the correct FONT line is:</para>
+instead of Euro, the correct <envar>FONT</envar> line is:</para>
 
 <screen><userinput>FONT="lat1-16"</userinput></screen></note>
 
-<para>If the KEYMAP or FONT variable is not set, the
+<para>If the <envar>KEYMAP</envar> or <envar>FONT</envar> variable is not set, the
 <command>console</command> initscript will not run the corresponding
 program.</para>
 
@@ -87,7 +87,7 @@
 
 <para>To compile the keymap directly into the kernel instead of
 setting it every time from the <command>console</command> bootscript,
-follow the instructions given in <xref linkend="ch-bootable-kernel"/>.
+follow the instructions given in <xref linkend="ch-bootable-kernel" role="."/>
 Doing this ensures that the keyboard will always work as expected,
 even when booting into maintenance mode (by passing
 <parameter>init=/bin/sh</parameter> to the kernel), because the
@@ -98,7 +98,7 @@
 to rely on non-ASCII characters while in maintenance mode.</para>
 
 <para>Since the kernel will set up the keymap, it is possible to omit
-the KEYMAP variable from the
+the <envar>KEYMAP</envar> variable from the
 <filename>/etc/sysconfig/console</filename> configuration file. It can
 also be left in place, if desired, without consequence.  Keeping it
 could be beneficial if running several different kernels where it is

Modified: branches/testing/BOOK/chapter07/inputrc.xml
===================================================================
--- branches/testing/BOOK/chapter07/inputrc.xml	2004-09-05 13:22:23 UTC (rev 4132)
+++ branches/testing/BOOK/chapter07/inputrc.xml	2004-09-05 16:23:58 UTC (rev 4133)
@@ -11,7 +11,7 @@
 
 <para>The <filename>/etc/inputrc</filename> file deals with mapping
 the keyboard for specific situations. This file is the start-up file
-used by <application>readline</application>, the input-related
+used by <application>Readline</application>, the input-related
 library used by <application>Bash</application> and most other
 shells.</para>
 

Modified: branches/testing/BOOK/chapter07/network.xml
===================================================================
--- branches/testing/BOOK/chapter07/network.xml	2004-09-05 13:22:23 UTC (rev 4132)
+++ branches/testing/BOOK/chapter07/network.xml	2004-09-05 16:23:58 UTC (rev 4133)
@@ -53,24 +53,24 @@
 EOF</userinput></screen>
 
 <para>The values of these variables must be changed in every file to
-match the proper setup. If the <emphasis>ONBOOT</emphasis> variable is
+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 <emphasis>SERVICE</emphasis> variable defines the method of
+<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 <emphasis>GATEWAY</emphasis> variable should contain 
+<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 <emphasis>PREFIX</emphasis> variable needs to contain the
+<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

Modified: branches/testing/BOOK/chapter07/profile.xml
===================================================================
--- branches/testing/BOOK/chapter07/profile.xml	2004-09-05 13:22:23 UTC (rev 4132)
+++ branches/testing/BOOK/chapter07/profile.xml	2004-09-05 16:23:58 UTC (rev 4133)
@@ -52,7 +52,7 @@
 values</para></listitem>
 </itemizedlist>
 
-<para>This script also sets the <emphasis>INPUTRC</emphasis>
+<para>This script also sets the <envar>INPUTRC</envar>
 environment variable that makes <application>Bash</application> and
 <application>Readline</application> use the
 <filename>/etc/inputrc</filename> file created earlier.</para>

Modified: branches/testing/BOOK/chapter07/setclock.xml
===================================================================
--- branches/testing/BOOK/chapter07/setclock.xml	2004-09-05 13:22:23 UTC (rev 4132)
+++ branches/testing/BOOK/chapter07/setclock.xml	2004-09-05 16:23:58 UTC (rev 4133)
@@ -34,7 +34,7 @@
 substracting an hour (or only add six in the first place) during the summer
 months.</para>
 
-<para>Change the value of the <emphasis>UTC</emphasis> variable below
+<para>Change the value of the <envar>UTC</envar> variable below
 to a value of <parameter>0</parameter> (zero) if the hardware clock
 is <emphasis>not</emphasis> set to UTC time.</para>
 
@@ -51,7 +51,7 @@
 
 <para>A good hint explaining how to deal with time on LFS is available
 at <ulink url="&hints-root;time.txt"/>. It explains issues such as
-time zones, UTC, and the TZ environment variable.</para>
+time zones, UTC, and the <envar>TZ</envar> environment variable.</para>
 
 </sect1>
 

Modified: branches/testing/BOOK/chapter07/udev.xml
===================================================================
--- branches/testing/BOOK/chapter07/udev.xml	2004-09-05 13:22:23 UTC (rev 4132)
+++ branches/testing/BOOK/chapter07/udev.xml	2004-09-05 16:23:58 UTC (rev 4133)
@@ -11,7 +11,7 @@
 <primary sortas="a-Udev">Udev</primary>
 <secondary>usage</secondary></indexterm>
 
-<para>In <xref linkend="chapter-building-system"/>, we installed the udev
+<para>In <xref linkend="chapter-building-system"/>, we installed the Udev
 package.  Before we go into the details regarding how this works,
 a brief history of previous methods of handling devices is in
 order.</para>
@@ -22,7 +22,7 @@
 thousands of nodes), regardless of whether the corresponding hardware
 devices actually exist. This is typically done via a
 <command>MAKEDEV</command> script, which contains a number of
-calls to the 'mknod' program with the relevant major and minor device
+calls to the <command>mknod</command> program with the relevant major and minor device
 numbers for every possible device that might exist in the world. Using
 the udev method, only those devices which are detected by the kernel
 get device nodes created for them. Because these device nodes will be
@@ -181,7 +181,8 @@
 <para>There are a few known problems when it comes to automatically creating
 devices nodes:</para>
 
-<para>1) A kernel driver may not export its data to sysfs</para>
+<para>1) A kernel driver may not export its data to <systemitem
+class="filesystem">sysfs</systemitem>.</para>
    
 <para>This is most common with third party drivers from outside the
 kernel tree.  These drivers will not end up having their device nodes
@@ -204,8 +205,8 @@
 <listitem><para>Using an
 <quote>install</quote> line in
 <filename>/etc/modprobe.conf</filename>. This tells the
-modprobe command <quote>when loading this module, also load this other
-module, at the same time.</quote>  For example:</para>
+<command>modprobe</command> command <quote>when loading this module, 
+also load this other module, at the same time.</quote>  For example:</para>
 
 <screen><userinput>install snd-pcm modprobe -i snd-pcm ; modprobe \
     snd-pcm-oss ; true</userinput></screen>




More information about the lfs-book mailing list