gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-07-07 13:00:00 +01:00
Code Issues Packages Projects Releases Wiki Activity

Typos and wording improvements (Chris Staub, sash and Kim McCall)

Browse Source 
git-svn-id: http://svn.linuxfromscratch.org/LFS/branches/6.1/BOOK@6467 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Matthew Burgess 2005-07-09 17:22:42 +00:00
parent c8f694ba08
commit 2d655672fa
7 changed files with 16 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
chapter01/askforhelp.xml
View File

@ -58,7 +58,7 @@ need to ask for help.</para>
<para>Both the screen output and the contents of various files are <para>Both the screen output and the contents of various files are
useful in determining the cause of compilation problems. The screen output useful in determining the cause of compilation problems. The screen output
from the <command>./configure</command> script and the from the <command>configure</command> script and the
<command>make</command> run can be helpful. It <command>make</command> run can be helpful. It
is not necessary to include the entire output, but do include enough is not necessary to include the entire output, but do include enough
of the relevant information. Below is an example of the type of of the relevant information. Below is an example of the type of

4
chapter02/creatingfilesystem.xml
View File

@ -11,8 +11,8 @@
be created. The most widely-used system in the Linux world is the be created. The most widely-used system in the Linux world is the
second extended file system (ext2), but with newer high-capacity second extended file system (ext2), but with newer high-capacity
hard disks, journaling file systems are becoming increasingly hard disks, journaling file systems are becoming increasingly
popular. We will create an ext2 file system, however build popular. We will create an ext2 file system. Build instructions for other file
instructions for other file systems can be found at <ulink systems can be found at <ulink
url="&blfs-root;view/svn/postlfs/filesystems.html"><phrase url="&blfs-root;view/svn/postlfs/filesystems.html"><phrase
condition="pdf">&blfs-root;view/svn/ postlfs/filesystems.html</phrase></ulink>.</para> condition="pdf">&blfs-root;view/svn/ postlfs/filesystems.html</phrase></ulink>.</para>

6
chapter05/toolchaintechnotes.xml
View File

@ -69,7 +69,7 @@ linker will be used</para></listitem>
</itemizedlist> </itemizedlist>
<para>Binutils is installed first because the <para>Binutils is installed first because the
<command>./configure</command> runs of both GCC and Glibc perform <command>configure</command> runs of both GCC and Glibc perform
various feature tests on the assembler and linker to determine which various feature tests on the assembler and linker to determine which
software features to enable or disable. This is more important than software features to enable or disable. This is more important than
one might first realize. An incorrectly configured GCC or Glibc can one might first realize. An incorrectly configured GCC or Glibc can
@ -96,7 +96,7 @@ succeeded</userinput> will show all the files successfully opened
during the linking.</para> during the linking.</para>
<para>The next package installed is GCC. An example of what can be <para>The next package installed is GCC. An example of what can be
seen during its run of <command>./configure</command> is:</para> seen during its run of <command>configure</command> is:</para>
<screen><computeroutput>checking what assembler to use... <screen><computeroutput>checking what assembler to use...
/tools/i686-pc-linux-gnu/bin/as /tools/i686-pc-linux-gnu/bin/as
@ -125,7 +125,7 @@ will always use the <command>gcc</command> found in a
The binary tools and kernel headers can be a bit more complicated. The binary tools and kernel headers can be a bit more complicated.
Therefore, take no risks and use the available configure switches to Therefore, take no risks and use the available configure switches to
enforce the correct selections. After the run of enforce the correct selections. After the run of
<command>./configure</command>, check the contents of the <command>configure</command>, check the contents of the
<filename>config.make</filename> file in the <filename <filename>config.make</filename> file in the <filename
class="directory">glibc-build</filename> directory for all important class="directory">glibc-build</filename> directory for all important
details. Note the use of <parameter>CC="gcc -B/tools/bin/"</parameter> details. Note the use of <parameter>CC="gcc -B/tools/bin/"</parameter>

2
chapter07/profile.xml
View File

@ -83,7 +83,7 @@ will print:</para>
<screen>ISO-8859-1</screen> <screen>ISO-8859-1</screen>
<para>This results in in a final locale setting of <quote>en_GB.ISO-8859-1</quote>.</para> <para>This results in a final locale setting of <quote>en_GB.ISO-8859-1</quote>.</para>
<para>Once the proper locale settings have been determined, create the <para>Once the proper locale settings have been determined, create the
<filename>/etc/profile</filename> file:</para> <filename>/etc/profile</filename> file:</para>

2
prologue/errata.xml
View File

@ -8,7 +8,7 @@
<?dbhtml filename="errata.html"?> <?dbhtml filename="errata.html"?>
<para>The software used to create an LFS system is constantly being updated and <para>The software used to create an LFS system is constantly being updated and
enhanced. Security warnings, and bug fixes may become available after the LFS enhanced. Security warnings and bug fixes may become available after the LFS
book has been released. To check whether the package versions or instructions in book has been released. To check whether the package versions or instructions in
this release of LFS need any modifications to accomodate security this release of LFS need any modifications to accomodate security
vulnerabilities or other bug fixes, please visit <ulink url="&errata;"/> before vulnerabilities or other bug fixes, please visit <ulink url="&errata;"/> before

6
prologue/hostreqs.xml
View File

@ -10,7 +10,7 @@
<para>The host must be running at least a 2.6.2 kernel compiled with GCC-3.0 or <para>The host must be running at least a 2.6.2 kernel compiled with GCC-3.0 or
higher. There are two main reasons for this requirement. First, the Native POSIX higher. There are two main reasons for this requirement. First, the Native POSIX
Threading Library (NPTL) test suite will segfault if the host's kernel has not Threading Library (NPTL) test suite will segfault if the host's kernel has not
been compiled with GCC-3.0 or a later version. Secondly, the 2.6.2 or later been compiled with GCC-3.0 or a later version. Second, the 2.6.2 or later
version of the kernel is required for the use of Udev. Udev creates devices version of the kernel is required for the use of Udev. Udev creates devices
dynamically by reading from the <systemitem dynamically by reading from the <systemitem
class="filesystem">sysfs</systemitem> file system. However, support for this class="filesystem">sysfs</systemitem> file system. However, support for this
@ -35,8 +35,8 @@ package. If so, you may wish to install it. If your vendor doesn't offer a 2.6.2
(or later) kernel package, or you would prefer not to install it, then you can (or later) kernel package, or you would prefer not to install it, then you can
compile a 2.6 kernel yourself. Instructions for compiling the kernel and compile a 2.6 kernel yourself. Instructions for compiling the kernel and
configuring the boot loader (assuming the host uses GRUB) are located in <xref configuring the boot loader (assuming the host uses GRUB) are located in <xref
linkend="chapter-bootable"/>. This second option can also been seen as a gauge linkend="chapter-bootable"/>. This second option can also be seen as a gauge
of your current Linux skills. If this second requirement is too steep then the of your current Linux skills. If this second requirement is too steep, then the
LFS book will not likely be much use to you at this time.</para> LFS book will not likely be much use to you at this time.</para>
</sect1> </sect1>

10
prologue/typography.xml
View File

@ -28,13 +28,13 @@ to show filenames, such as
<para><emphasis>Emphasis</emphasis></para> <para><emphasis>Emphasis</emphasis></para>
<para>This form of text is used for several purposes in the book, <para>This form of text is used for several purposes in the book. Its main
mainly to emphasize important points or items.</para> purpose is to emphasize important points or items.</para>
<para><ulink url="&lfs-root;"/></para> <para><ulink url="&lfs-root;"/></para>
<para>This format is used for hyperlinks, both within the LFS <para>This format is used for hyperlinks both within the LFS
community and to external pages, including HOWTOs, download locations, community and to external pages. It includes HOWTOs, download locations,
and websites.</para> and websites.</para>
<screen><userinput>cat &gt; $LFS/etc/group &lt;&lt; "EOF" <screen><userinput>cat &gt; $LFS/etc/group &lt;&lt; "EOF"
@ -52,7 +52,7 @@ Therefore, this entire section is generally typed as seen.</para>
<para><replaceable>[REPLACED TEXT]</replaceable></para> <para><replaceable>[REPLACED TEXT]</replaceable></para>
<para>This format is used to encapsulate text that is not to be typed <para>This format is used to encapsulate text that is not to be typed
as seen<phrase condition="html"> or copy-and-pasted</phrase>.</para> as seen or copied-and-pasted.</para>
<para><filename>passwd(5)</filename></para> <para><filename>passwd(5)</filename></para>