gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-06-19 03:39:20 +01:00
Code Issues Packages Projects Releases Wiki Activity

Applied Bill Maltby's grammar patch. Changed $LFS to LFS where appropriate. Internal XML cleanup: removed double spacing where appropriate.

Browse Source 
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2138 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Timothy Bauscher 2002-09-28 21:08:29 +00:00
parent f5cc1c171b
commit 2c094d60db
75 changed files with 230 additions and 227 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
appendixa/autoconf-desc.xml
View File

@ -24,18 +24,18 @@ statements for configure to use.</para></sect4>
<sect4><title>autoreconf</title>
<para>If there are a lot of autoconf-generated configure scripts, the
autoreconf program can save some work. It runs autoconf (and
autoheader, where appropriate) repeatedly to remake the autoconf
autoreconf program can save some work. It runs autoconf and
autoheader (where appropriate) repeatedly to remake the autoconf
configure scripts and configuration header templates in the directory
tree rooted at the current directory.</para></sect4>
<sect4><title>autoscan</title>
<para>The autoscan program can help to create a configure.in file for
a software package. autoscan examines source files in the directory
tree rooted at a directory given as a command line argument, or the
current directory if none is given. It searches the source files for
common portability problems and creates a file configure.scan which
is a preliminary configure.in for that package.</para></sect4>
a software package. autoscan examines the source files in a directory
tree. If a directory is not specified on the command line, then the
current working directory is used. The source files are searched for
common portability problems and a configure.scan file is created to
serve as the preliminary configure.in for that package.</para></sect4>
<sect4><title>autoupdate</title>
<para>The autoupdate program updates a configure.in file that calls
@ -46,9 +46,9 @@ macro names.</para></sect4>
<para>ifnames can help when writing a configure.in for a software
package. It prints the identifiers that the package already uses in C
preprocessor conditionals. If a package has already been set up to
have some portability, this program can help to figure out what its
configure needs to check for. It may help fill in some gaps in a
configure.in generated by autoscan.</para></sect4>
have some portability, this program can help to determine what configure
needs to check. It may fill in some gaps in a configure.in file generated
by autoscan.</para></sect4>
</sect3>

8
appendixa/automake-desc.xml
View File

@ -14,13 +14,13 @@ mdate-sh, missing, mkinstalldirs, py-compile, ylwrap</para></sect3>
<sect4><title>aclocal, aclocal-1.6</title>
<para>automake includes a number of autoconf macros which can be used in
packages; some of them are actually required by automake in certain
situations. These macros must be defined in the aclocal.m4-file;
otherwise they will not be seen by autoconf.</para>
packages, some of which are needed by automake in certain
situations. These macros must be defined in the aclocal.m4-file
or they will not be seen by autoconf.</para>
<para>The aclocal program will automatically generate aclocal.m4 files
based on the contents of configure.in. This provides a convenient
way to get automake-provided macros, without having to search around.
way to get automake-provided macros without having to search around.
Also, the aclocal mechanism is extensible for use
by other packages.</para></sect4>

2
appendixa/bin86-desc.xml
View File

@ -18,7 +18,7 @@ into a C file prog.v to be included in or linked with programs like boot
block installers.</para></sect4>
<sect4><title>ld86</title>
<para>ld86 understands only the object files produced by the as86 assembler, it
<para>ld86 understands only the object files produced by the as86 assembler. It
can link them into either an impure or a
separate I&amp;D executable.</para></sect4>

2
appendixa/binutils-desc.xml
View File

@ -53,7 +53,7 @@ programmers who just want their program to compile and work.</para></sect4>
<sect4><title>ranlib</title>
<para>ranlib generates an index to the contents of an archive, and stores it in
the archive. The index lists each symbol defined by a member of an archive
the archive. The index lists each symbol defined by an archive member
that is a relocatable object file.</para></sect4>
<sect4><title>readelf</title>

2
appendixa/bison-desc.xml
View File

@ -39,7 +39,7 @@ to the compiler:</para>
multiplies 2 and 3. The result of that multiplication is remembered and
the next thing that the computer sees is the result of 2*3 and the
number 1 which are joined by the add symbol. Adding 1 to the previous
result makes 7. In calculating the most complex calculations can be
result makes 7. In calculating, the most complex calculations can be
broken down in this tree format and the computer just starts at the
bottom and works its way up to the top and comes with the correct
answer. Of course, bison isn't only used for calculators

10
appendixa/bzip2-desc.xml
View File

@ -26,9 +26,9 @@ bzip2 compressed files.</para></sect4>
<sect4><title>bzip2</title>
<para>bzip2 compresses files using the Burrows-Wheeler block sorting text
compression algorithm, and Huffman coding. Compression is generally
compression algorithm and Huffman coding. Compression is generally
considerably better than that achieved by more conventional LZ77/LZ78-based
compressors, and approaches the performance of the PPM family of statistical
compressors and approaches the performance of the PPM family of statistical
compressors.</para></sect4>
<sect4><title>bzip2recover</title>
@ -36,12 +36,12 @@ compressors.</para></sect4>
<sect4><title>bzless</title>
<para>bzless is a filter which allows examination of compressed
or plain text files one screenful at a time on a soft-copy
or plain text files, one screenful at a time on a soft-copy
terminal, like less.</para></sect4>
<sect4><title>bzmore</title>
<para>bzmore is a filter which allows examination of compressed
or plain text files one screenful at a time on a soft-copy
or plain text files, one screenful at a time on a soft-copy
terminal, like more.</para></sect4>
</sect3>
@ -52,7 +52,7 @@ libbz2.so.1.0.2) and libbz2.so.1.0.2</para>
<sect4><title>libbz2</title>
<para>libbz2 is the library for implementing lossless, block-sorting data
compression using the Burrows-Wheeler algorithm.</para></sect4>
compression, using the Burrows-Wheeler algorithm.</para></sect4>
</sect3>

22
appendixa/e2fsprogs-desc.xml
View File

@ -20,9 +20,9 @@ partition).</para></sect4>
system.</para></sect4>
<sect4><title>compile_et</title>
<para>compile_et is used to convert a table listing error-code names
and associated messages into a C source file suitable for use with the
com_err library.</para></sect4>
<para>compile_et is used to convert a table, listing error-code names
and associated messages, into a C source file that is suitable for use
with the com_err library.</para></sect4>
<sect4><title>debugfs</title>
<para>The debugfs program is a file system debugger. It can be used to examine
@ -33,8 +33,8 @@ and change the state of an ext2 file system.</para></sect4>
filesystem present on a specified device.</para></sect4>
<sect4><title>e2fsck and fsck.ext2</title>
<para>e2fsck is used to check and optionally repair Linux second
extended filesystems. fsck.ext2 does the same as e2fsck.</para></sect4>
<para>e2fsck and fsck.ext2 are used to check, and optionally repair, Linux
second extended filesystems.</para></sect4>
<sect4><title>e2image</title>
<para>e2image is used to save critical ext2 filesystem data to
@ -45,11 +45,11 @@ a file.</para></sect4>
filesystem located on the specified device.</para></sect4>
<sect4><title>fsck</title>
<para>fsck is used to check and optionally repair a Linux
file system.</para></sect4>
<para>fsck is used to check, and optionally repair, a Linux file
system.</para></sect4>
<sect4><title>fsck.ext3</title>
<para>fsck.ext3 is used to check and optionally repair a Linux ext3
<para>fsck.ext3 is used to check, and optionally repair, a Linux ext3
filesystems.</para></sect4>
<sect4><title>lsattr</title>
@ -58,7 +58,7 @@ file system.</para></sect4>
<sect4><title>mk_cmds</title>
<para>The mk_cmds utility takes a command table file as input and produces
a C source file as output which is intended to be used with the subsystem
a C source file as output, which is intended to be used with the subsystem
library, libss.</para></sect4>
<sect4><title>mke2fs and mkfs.ext2</title>
@ -84,8 +84,8 @@ filesystem.</para></sect4>
<sect4><title>uuidgen</title>
<para>The uuidgen program creates a new universally unique identifier (UUID)
using the libuuid library. The new UUID can reasonably be considered unique
among all UUIDs created on the local system, and among UUIDs created on other
systems in the past and in the future.</para></sect4>
among all UUIDs created, on the local system and on other
systems, in the past and in the future.</para></sect4>
</sect3>

2
appendixa/file-desc.xml
View File

@ -10,7 +10,7 @@
<sect4><title>file</title>
<para>file tests each specified file in an attempt to classify it. There are
three sets of tests, performed in this order: filesystem tests,
magic number tests, and language tests. The first test that succeeds
magic number tests and language tests. The first test that succeeds
causes the file type to be printed.</para></sect4>
</sect3>

14
appendixa/fileutils-desc.xml
View File

@ -15,7 +15,7 @@ which can be either a group name or a numeric group ID.</para></sect4>
<sect4><title>chmod</title>
<para>chmod changes the permissions of each given file according to mode, which
can be either a symbolic representation of changes to make, or an octal
can be either a symbolic representation of changes to make or an octal
number representing the bit pattern for the new permissions.</para></sect4>
<sect4><title>chown</title>
@ -38,10 +38,10 @@ available on all currently mounted filesystems is shown.</para></sect4>
<sect4><title>dir, ls and vdir</title>
<para>dir and vdir are versions of ls with different default output formats.
These programs list each given file or directory name. Directory contents
are sorted alphabetically. For ls, files are by default listed in columns,
sorted vertically, if the standard output is a terminal; otherwise they
are listed one per line. For dir, files are by default listed in columns,
sorted vertically. For vdir, files are by default listed in
are sorted alphabetically. For ls, files are, by default, listed in columns
sorted vertically if the standard output is a terminal; otherwise they
are listed one per line. For dir, files are, by default, listed in columns
sorted vertically. For vdir, files are, by default, listed in
long format.</para></sect4>
<sect4><title>dircolors</title>
@ -50,8 +50,8 @@ The LS_COLOR variable is use to change the default color scheme used by
ls and related utilities.</para></sect4>
<sect4><title>du</title>
<para>du displays the amount of disk space used by each argument and for each
subdirectory of directory arguments.</para></sect4>
<para>du displays the amount of disk space used by each file or directory
listed on the command-line and by each of their subdirectories.</para></sect4>
<sect4><title>install</title>
<para>install copies files and sets their permission modes and, if possible,

9
appendixa/flex-desc.xml
View File

@ -10,11 +10,10 @@
<sect4><title>flex</title>
<para>flex is a tool for generating programs which recognize
patterns in text. Pattern recognition is very useful in many applications.
A user sets up rules
what to look for and flex will make a program that looks for those
patterns. The reason people use flex is that it is much easier to set up
rules for what to look for than to write the actual program which finds
the text.</para></sect4>
A user sets up rules about what to look for and flex will make a program
that looks for those patterns. The reason people use flex is that it is
much easier to set up rules for what to look for than to write the actual
program which finds the text.</para></sect4>
<sect4><title>flex++</title>
<para>flex++ invokes a version of flex which is used exclusively for

8
appendixa/gettext-desc.xml
View File

@ -11,11 +11,11 @@ team-address, trigger, urlget, user-email and xgettext</para></sect3>
<sect3><title>Descriptions</title>
<sect4><title>config.charset</title>
<para>The config.charset script outputs a system dependent table of
<para>The config.charset script outputs a system-dependent table of
character encoding aliases.</para></sect4>
<sect4><title>config.rpath</title>
<para>The config.rpath script outputs a system dependent set of variables,
<para>The config.rpath script outputs a system-dependent set of variables,
describing how to set the run time search path of shared libraries in an
executable.</para></sect4>
@ -23,7 +23,7 @@ executable.</para></sect4>
<para>The gettext package is used for internationalization (also known as
i18n) and for localization (also known as l10n). Programs can be
compiled with Native Language Support (NLS) which enable them to output
messages in the users native language rather than in the default English
messages in the user's native language rather than in the default English
language.</para></sect4>
<sect4><title>gettextize</title>
@ -36,7 +36,7 @@ forms.</para></sect4>
<sect4><title>msgattrib</title>
<para>The msgattrib program filters the messages of a translation catalog
according to their attributes, and manipulates the attributes.</para></sect4>
according to their attributes and manipulates the attributes.</para></sect4>
<sect4><title>msgcat</title>
<para>The msgcat program finds messages which are common in several raw

2
appendixa/groff-desc.xml
View File

@ -76,7 +76,7 @@ standard output.</para></sect4>
is not a terminal), reads from the standard input a line containing a set
of keywords, searches the bibliographic databases in a specified file for
references containing those keywords, prints any references found on the
standard output, and repeats this process until the end of input.</para></sect4>
standard output and repeats this process until the end of input.</para></sect4>
<sect4><title>mmroff</title>
<para>mmroff is a simple preprocessor for groff.</para></sect4>

7
appendixa/gzip-desc.xml
View File

@ -23,9 +23,8 @@ performance).</para></sect4>
Lempel-Ziv coding (LZ77).</para></sect4>
<sect4><title>zcat</title>
<para>zcat uncompresses either a list of files on the command line or a
file being read from its standard input. Then, that uncompressed data is
written to standard output.</para></sect4>
<para>zcat uncompresses, and writes to standard output, either a list of files
on the command line or a file being read from standard input.</para></sect4>
<sect4><title>zcmp</title>
<para>zcmp invokes the cmp program on compressed files.</para></sect4>
@ -43,7 +42,7 @@ after a file transfer.</para></sect4>
<sect4><title>zmore</title>
<para>zmore is a filter which allows examination of compressed or plain text
files one screen at a time on a soft-copy terminal (similar to the
files, one screen at a time on a soft-copy terminal (similar to the
more program).</para></sect4>
<sect4><title>znew</title>

4
appendixa/kbd-desc.xml
View File

@ -68,7 +68,7 @@ table entries.</para></sect4>
<sect4><title>setleds</title>
<para>setleds sets the keyboard LEDs. Many people find it useful to have numlock
enabled by default, and it is by using this program that you can
enabled by default and, by using this program, you can
achieve this.</para></sect4>
<sect4><title>setlogcons</title>
@ -83,7 +83,7 @@ achieve this.</para></sect4>
<sect4><title>showfont</title>
<para>showfont displays data about a font. The information shown includes font
information, font properties, character metrics, and
information, font properties, character metrics and
character bitmaps.</para></sect4>
<sect4><title>showkey</title>

2
appendixa/less-desc.xml
View File

@ -9,7 +9,7 @@
<sect4><title>less</title>
<para>The less program is a file pager (or text viewer). It
displays the contents of a file with the ability to scroll. Less is an
displays the contents of a file and has the ability to scroll. Less is an
improvement on the common pager called <quote>more</quote>. Less has
the ability to scroll backwards through files as well and it doesn't need
to read the entire file when it starts, which makes it faster when reading

2
appendixa/libtool-desc.xml
View File

@ -24,7 +24,7 @@ package.</para></sect4>
<sect3><title>Descriptions</title>
<sect4><title>libltdl, libltdl.so.3, libltdl.so.3.1.0</title>
<para>A small library that aims at hiding from programmers
<para>A small library that aims at hiding, from programmers,
the various difficulties of dlopening libraries.</para></sect4>
</sect3>

2
appendixa/m4-desc.xml
View File

@ -8,7 +8,7 @@
<sect3><title>Descriptions</title>
<sect4><title>m4</title>
<para>m4 is a macro processor. It copies input to output expanding macros as it
<para>m4 is a macro processor. It copies input to output, expanding macros as it
goes. Macros are either built-in or user-defined and can take any number
of arguments. Besides just doing macro expansion, m4 has built-in functions
for including named files, running Unix commands, doing integer arithmetic,

11
appendixa/man-desc.xml
View File

@ -9,14 +9,14 @@ whatis</para></sect3>
<sect3><title>Descriptions</title>
<sect4><title>apropos</title>
<para>apropos searches a set of database files containing short descriptions
of system commands for keywords and displays the result on the standard
<para>apropos searches for keywords in a set of database files, containing
short descriptions of system commands, and displays the result on the standard
output.</para></sect4>
<sect4><title>makewhatis</title>
<para>makewhatis reads all the manual pages contained in given sections of
manpath or the pre-formatted pages contained in the given sections of
catpath. For each page, it writes a line in the whatis database; each
catpath. For each page, it writes a line in the whatis database. Each
line consists of the name of the page and a short description,
separated by a dash. The description is extracted using the content of
the NAME section of the manual page.</para></sect4>
@ -31,8 +31,9 @@ the NAME section of the manual page.</para></sect4>
<para>man2html converts a manual page into html.</para></sect4>
<sect4><title>whatis</title>
<para>whatis searches a set of database files containing short descriptions
of system commands for keywords and displays the result on the standard
<para>
whatis searches for keywords in a set of database files, containing short
descriptions of system commands, and displays the result on the standard
output. Only complete word matches are displayed.</para></sect4>
</sect3>

2
appendixa/nettools-desc.xml
View File

@ -36,7 +36,7 @@ addresses.</para></sect4>
<sect4><title>netstat</title>
<para>netstat is a multi-purpose tool used to print the network connections,
routing tables, interface statistics, masquerade connections, and multicast
routing tables, interface statistics, masquerade connections and multicast
memberships.</para></sect4>
<sect4><title>nisdomainname</title>

4
appendixa/perl-desc.xml
View File

@ -29,7 +29,7 @@ pod2usage, podchecker, podselect, pstruct, s2p and splain</para></sect3>
<sect4><title>perl, perl5.6.1</title>
<para>perl is the Practical Extraction and Report Language. It combines
some of the best features of C, sed, awk, and sh into one powerful
some of the best features of C, sed, awk and sh into one powerful
language.</para></sect4>
<sect4><title>perlbug</title>
@ -41,7 +41,7 @@ modules that come with it, and mail them.</para></sect4>
<sect4><title>perldoc</title>
<para>perldoc looks up a piece of documentation in .pod format that is
embedded in the perl installation tree or in a perl script, and displays it
embedded in the perl installation tree or in a perl script and displays it
via "pod2man | nroff -man | $PAGER".</para></sect4>
<sect4><title>pl2pm</title>

6
appendixa/shellutils-desc.xml
View File

@ -42,7 +42,7 @@ integer numbers.</para></sect4>
<para>false always exits with a status code indicating failure.</para></sect4>
<sect4><title>groups</title>
<para>groups prints the groups a user is in.</para></sect4>
<para>groups prints a user's group memberships.</para></sect4>
<sect4><title>hostid</title>
<para>hostid prints the numeric identifier (in hexadecimal) for the current
@ -60,7 +60,7 @@ user or a given user.</para></sect4>
<sect4><title>nohup</title>
<para>nohup runs a command immune to hangups, with output to a
non-tty.</para></sect4>
log file.</para></sect4>
<sect4><title>pathchk</title>
<para>pathchk checks whether file names are valid or portable.</para></sect4>
@ -73,7 +73,7 @@ a certain user.</para></sect4>
<para>printenv prints all or part of the environment.</para></sect4>
<sect4><title>printf</title>
<para>printf formats and prints data (the same as the printf C
<para>printf formats and prints data (the same as the C printf
function).</para></sect4>
<sect4><title>pwd</title>

6
appendixa/texinfo-desc.xml
View File

@ -11,7 +11,7 @@ texindex</para></sect3>
<sect4><title>info</title>
<para>The info program reads Info documents, usually contained in the
/usr/share/info directory. Info documents are like man(ual) pages, but
they tend to be more in depth than just explaining the options to a
they tend to go deeper than just explaining the options to a
program.</para></sect4>
<sect4><title>infokey</title>
@ -22,8 +22,8 @@ a binary format.</para></sect4>
<para>The install-info program updates the info entries. When the info
program is run, a list with available topics (ie: available info documents)
will be presented. The install-info program is used to maintain this list of
available topics. If info files are removed manually, it is also necessary
to delete the topic in the index file as well. This program is used for
available topics. If info files are removed manually, you must also delete
the topic in the index file. This program is used for
that. It also works the other way around when info documents are
added.</para></sect4>

4
appendixa/textutils-desc.xml
View File

@ -106,8 +106,8 @@ output.</para></sect4>
<para>uniq removes duplicate lines from a sorted file.</para></sect4>
<sect4><title>wc</title>
<para>wc prints line, word, and byte counts for each specified file, and a
total line if more than one file is specified.</para></sect4>
<para>wc prints line, word and byte counts for each specified file and a
total line, if more than one file is specified.</para></sect4>
</sect3>

4
chapter01/changelog.xml
View File

@ -59,6 +59,10 @@
</itemizedlist>
</para></listitem>
<listitem><para>September 28th, 2002 [timothy]: Applied Bill Maltby's
grammatic-fixes patch. Changed "$LFS" to "LFS" when speaking of the LFS
environment variable.</para></listitem>
<listitem><para>September 23rd, 2002 [timothy]: Applied Bill Maltby's
grammatic-related patches.</para></listitem>

8
chapter02/aboutlfs.xml
View File

@ -3,7 +3,7 @@
<?dbhtml filename="aboutlfs.html" dir="chapter02"?>
<para>Please read the following carefully: throughout this book
the variable $LFS will be used frequently. $LFS must at all times be
the variable LFS will be used frequently. $LFS must at all times be
replaced with the directory where the partition that contains the LFS system
is mounted. How to create and where to mount the partition will be
explained in full detail in Chapter 4. For example, let's assume that
@ -28,18 +28,18 @@ it literally. Your shell will replace $LFS with /mnt/lfs when it processes
the command line (meaning when you hit enter after having typed the
command).</para>
<para>If you plan to use $LFS, do not forget to set the $LFS variable at all
<para>If you plan to use $LFS, do not forget to set the LFS variable at all
times. If the variable is not set and is used in a command, $LFS will
be ignored and whatever is left will be executed. A command like
<userinput>echo "root:x:0:0:root:/root:/bin/bash" &gt;
$LFS/etc/passwd</userinput> without the $LFS variable set will
$LFS/etc/passwd</userinput> without the LFS variable set will
re-create your host system's /etc/passwd file. Simply put: it will
destroy your current password database file.</para>
<para>One way to make sure that $LFS is set at all times is adding it to
the /root/.bash_profile and /root/.bashrc files so that every time
you login as user root, or you <userinput>su</userinput> to user root,
the $LFS variable is set.</para>
the LFS variable is set.</para>
</sect1>

4
chapter03/mounting.xml
View File

@ -19,8 +19,8 @@ directory is chosen, just make sure you remember what you chose.</para>
<para>Replace <quote>xxx</quote> by the partition's designation (like hda11).</para>
<para>This directory (/mnt/lfs) is the $LFS variable you have read about
back in Chapter 2. If you were planning to make use of the $LFS environment
<para>This directory (/mnt/lfs) is the LFS variable you have read about
back in Chapter 2. If you were planning to make use of the LFS environment
variable, <userinput>export LFS=/mnt/lfs</userinput> has to be executed
now.</para>

4
chapter06/aboutdebug.xml
View File

@ -2,7 +2,7 @@
<title>About debugging symbols</title>
<?dbhtml filename="aboutdebug.html" dir="chapter06"?>
<para>Most programs and libraries are by default compiled with debugging
<para>Most programs and libraries are, by default, compiled with debugging
symbols included (with gcc option -g).</para>
<para>When debugging a program or library that was compiled with debugging
@ -43,7 +43,7 @@ Wildcards can be used to treat multiple files (use something like
<para>For your convenience, Chapter 9 includes one simple command to strip
all debugging symbols from all programs and libraries on your system.
Additional information on optimization you can find in the hint at
Additional information on optimization can be found in the hint at
<ulink url="&hints-root;optimization.txt"/>.</para>
</sect1>

2
chapter06/binutils-exp.xml
View File

@ -2,7 +2,7 @@
<title>Command explanations</title>
<para><userinput>tooldir=/usr:</userinput> Normally, the tooldir (the
directory where the executables from binutils end up in) is set to
directory where the executables from binutils end up) is set to
$(exec_prefix)/$(target_alias) which expands into, for example,
/usr/i686-pc-linux-gnu. Since we only build for our own system, we don't
need this target specific directory in /usr. That setup would be used

2
chapter06/bzip2-exp.xml
View File

@ -3,7 +3,7 @@
<para><userinput>make -f Makefile-libbz2_so:</userinput> This will cause bzip2
to be built using a different Makefile file, in this case the
Makefile-libbz2_so file which creates a dynamic libbz2.so library and
Makefile-libbz2_so file, which creates a dynamic libbz2.so library and
links the bzip2 utilities against it.</para>
</sect2>

2
chapter06/bzip2-inst.xml
View File

@ -16,7 +16,7 @@ mv /usr/bin/{bzip2recover,bzless,bzmore} /bin &amp;&amp;
ln -s bzip2 /bin/bunzip2 &amp;&amp;
ln -s bzip2 /bin/bzcat</userinput></screen></para>
<para>Although it's not strictly a part of a basic LFS system it's worth
<para>Although it's not strictly a part of a basic LFS system, it's worth
mentioning that a patch for Tar can be downloaded which enables the tar
program to compress and uncompress using bzip2/bunzip2 easily. With a
plain tar, you have to use constructions like

12
chapter06/chroot.xml
View File

@ -1,14 +1,14 @@
<sect1 id="ch06-chroot">
<title>Entering the chroot'ed environment</title>
<title>Entering the chroot environment</title>
<?dbhtml filename="chroot.html" dir="chapter06"?>
<para>It is time to enter the chroot'ed environment in order to begin installing
<para>It is time to enter the chroot environment in order to begin installing
the packages we need. Before you can chroot, however, you need to become
<emphasis>root</emphasis>, since only <emphasis>root</emphasis>
can execute the <userinput>chroot</userinput> command.</para>
<para>Become <emphasis>root</emphasis> and run the following command
to enter the chroot'ed environment:</para>
to enter the chroot environment:</para>
<para><screen><userinput>chroot $LFS /static/bin/env -i \
&nbsp;&nbsp;&nbsp;&nbsp;HOME=/root TERM=$TERM PS1='\u:\w\$ ' \
@ -17,20 +17,20 @@ to enter the chroot'ed environment:</para>
</para>
<para>The <userinput>-i</userinput> option given to the
<userinput>env</userinput> command will clear all variables of the chroot'ed
<userinput>env</userinput> command will clear all variables of the chroot
environment. After that, only the HOME, TERM, PS1 and PATH variables are
set again. The TERM=$TERM construct will set the TERM variable inside chroot
to the same value as outside chroot; this variable is needed for programs
like vim and less to operate properly. If you need other variables present,
such as CFLAGS or CXXFLAGS, this is a good place to set them again.</para>
<para>From this point on there's no need anymore to use the $LFS variable,
<para>From this point on there's no need anymore to use the LFS variable,
because everything you do will be restricted to the LFS file system -- since
what the shell thinks is <filename class="directory">/</filename> is actually
<filename class="directory">/mnt/lfs</filename>.</para>
<para>You have to make sure all the commands in the rest of this chapter and
in the following chapters are run from within the chroot'ed environment.
in the following chapters are run from within the chroot environment.
If you ever leave this environment for any reason (rebooting for example),
you must remember to again enter chroot and mount proc (discussed later)
before continuing with the installations.</para>

10
chapter06/creatingdirs.xml
View File

@ -2,7 +2,7 @@
<title>Creating directories</title>
<?dbhtml filename="creatingdirs.html" dir="chapter06"?>
<para>Let's now create some structure in our LFS file system, let's create
<para>Let's now create some structure in our LFS file system. Let's create
a directory tree. Issuing the following commands will create a more or less
standard tree:</para>
@ -22,7 +22,7 @@ mkdir /opt/{bin,doc,include,info} &amp;&amp;
mkdir -p /opt/{lib,man/man{1,2,3,4,5,6,7,8}} &amp;&amp;
ln -s ../var/tmp /usr</userinput></screen></para>
<para>Directories are by default created with permission mode 755, but this
<para>Directories are, by default, created with permission mode 755, but this
isn't desirable for all directories. We will make two changes: one to the home
directory of root, and another to the directories for temporary files.</para>
@ -31,11 +31,11 @@ chmod 1777 /tmp /var/tmp</userinput></screen></para>
<para>The first mode change ensures that not just everybody can enter the
<filename class="directory">/root</filename> directory -- the same
a normal user would do with his or her home directory.
as a normal user would do with his or her home directory.
The second mode change makes sure that any user can write to the
<filename class="directory">/tmp</filename> and
<filename class="directory">/var/tmp</filename> directories, but
cannot remove other users's files from them. The latter is prohibited
cannot remove other users' files from them. The latter is prohibited
by the so-called "sticky bit" -- the highest bit in the 1777 bit mask.</para>
<para>Now that the directories are created, move the source tarballs that
@ -53,7 +53,7 @@ tree this standard stipulates the existence of
<filename class="directory">/usr/share/games</filename>, but we don't
much like these for a base system. However, feel free to make your system
FHS-compliant. As to the structure of the
<filename class="directory">/usr/local/share</filename> subdirectory the FHS
<filename class="directory">/usr/local/share</filename> subdirectory, the FHS
isn't precise, so we created here the directories that we think are needed.</para>
</sect2>

4
chapter06/e2fsprogs-exp.xml
View File

@ -5,9 +5,9 @@
reason for supplying this option is because of the setup of the
e2fsprogs Makefile. Some programs are essential for system use when,
for example, /usr isn't mounted (like the e2fsck program). These
programs and libraries therefore belong in directories like /lib and
programs and libraries, therefore, belong in directories like /lib and
/sbin. If this option isn't passed to E2fsprogs's configure, it places
these programs in /usr which is not what we want.</para>
these programs in /usr, which is not what we want.</para>
<para><userinput>--enable-elf-shlibs:</userinput> This creates shared
libraries that some programs in this package can make use of.</para>

2
chapter06/glibc-exp.xml
View File

@ -30,7 +30,7 @@ of libraries with profiling information. This command may be omitted if
you plan to do profiling.</para>
<para><userinput>--enable-add-ons:</userinput> This enables the add-on that
we install with Glibc: linuxthreads</para>
we install with Glibc, linuxthreads</para>
<para><userinput>--libexecdir=/usr/bin:</userinput> This will cause the
pt_chown program to be installed in the /usr/bin directory.</para>

2
chapter06/glibc-inst.xml
View File

@ -49,7 +49,7 @@ to create it first.</para>
<para>The Linux Threads man pages are not going to be installed at this
point because it requires a working Perl installation. We'll install Perl
later on in this chapter so we'll come back to the Linux Threads man page
later on in this chapter, so we'll come back to the Linux Threads man page
installation after that.</para>
<para>During the configure stage you will see the following warning:</para>

2
chapter06/groff-exp.xml
View File

@ -2,7 +2,7 @@
<title>Command explanations</title>
<para><userinput>make PROCESSEDEXAMPLEFILES="":</userinput> Groff has a few
extra dependencies that we don't install with LFS. This option disable the
extra dependencies that we don't install with LFS. This option disables the
need for those tools.</para>
<para><userinput>ln -s ...</userinput>: These symlinks are needed for some

8
chapter06/kbd-exp.xml
View File

@ -3,11 +3,11 @@
<para><userinput>patch -Np1 -i ../kbd-&kbd-patch-version;.patch</userinput>:
This patch fixes two problems. The first one is the <userinput>loadkeys -d</userinput>
behaviour which is broken in current kbd versions. It is necessary to fix this,
behaviour, which is broken in current kbd versions. It is necessary to fix this,
because the boot scripts rely on a proper <userinput>loadkeys -d</userinput>.
The second part of the patch changes a Makefile so some utilities (setlogcons,
setvesablank and getunimap) that are not installed by default, are installed as
well.</para>
The second part of the patch changes a Makefile so some utilities that are
not installed by default (setlogcons, setvesablank and getunimap) are also
installed.</para>
</sect2>

2
chapter06/kernel-exp.xml
View File

@ -8,7 +8,7 @@ for that. At the end we remove it again.</para>
<para><userinput>make mrproper</userinput>: This ensures that the kernel
tree is absolutely clean. The kernel team recommends that this command be
issued prior to <emphasis>each</emphasis> kernel compilation, and that you
issued prior to <emphasis>each</emphasis> kernel compilation and that you
shouldn't rely on the source tree being clean after untarring.</para>
<para><userinput>make include/linux/version.h</userinput> and

2
chapter06/lilo-inst.xml
View File

@ -21,7 +21,7 @@ update. Don't do this, as it has no use: the /etc/lilo.conf isn't present
yet. We will complete the installation of lilo in Chapter 8.</para>
<para>The standard LILO prompt, or menu, may be replaced by the
LFS logo, or any logo you like. Martin Imobersteg has written a
LFS logo or any logo you like. Martin Imobersteg has written a
hint about this, which is located at
<ulink url="&hints-root;bootlogo.txt"/>.</para>

2
chapter06/makedev-exp.xml
View File

@ -6,7 +6,7 @@ bunch of devices. Normally, these are all the devices you will need. But it
is possible that some special devices needed for your hardware configuration
are missing. Create these with ./MAKEDEV -v &lt;device&gt;.
The <userinput>generic-nopty</userinput> option mostly creates the same
devices as <userinput>generic-nopty</userinput>, but skips those that aren't
devices as <userinput>generic</userinput>, but skips those that aren't
needed if you are using devpts.</para>
</sect2>

4
chapter06/makedev-inst.xml
View File

@ -1,8 +1,8 @@
<sect2>
<title>Creating devices</title>
<para>(Note that unpacking the MAKEDEV-&makedev-version;.bz2 file doesn't create
a directory for you to cd into, as the file only contains a script.)</para>
<para>Note that unpacking the MAKEDEV-&makedev-version;.bz2 file doesn't create
a directory for you to cd into, as the file only contains a script.</para>
<para>Prepare for the creation of the device files by running the
following commands:</para>

2
chapter06/man-inst.xml
View File

@ -17,7 +17,7 @@ edit the man.conf file and add the <userinput>-c</userinput> argument
to nroff.</para>
<para>You may want to take a look at the man hint
at <ulink url="&hints-root;man.txt"/> which deals with formatting
at <ulink url="&hints-root;man.txt"/>, which deals with formatting
and compression issues for man pages.</para>
</sect2>

4
chapter06/mountproc.xml
View File

@ -3,7 +3,7 @@
<?dbhtml filename="proc.html" dir="chapter06"?>
<para>In order for certain programs to function properly, the proc file
system must be available within the chroot'ed environment.
system must be available within the chroot environment.
As a file system can be mounted as many times and in as many places
as you like, it's not a problem that the proc file system is already
mounted on your host system -- especially so because proc is a
@ -21,7 +21,7 @@ command, such as these:</para>
<blockquote><screen>warning: can't open /etc/fstab: No such file or directory
not enough memory</screen></blockquote>
<para>Ignore these, they're just caused due to the fact that the system
<para>Ignore these, they're just due to the fact that the system
isn't installed completely yet and some files are missing. The mount itself
will be successful and that's all we care about at this point.</para>

2
chapter06/ncurses-exp.xml
View File

@ -9,7 +9,7 @@ constructions that are no longer valid in the new C++ standard.</para>
shared ncurses library files.</para>
<para><userinput>chmod 755 *.5.2:</userinput> Shared libraries should be
executable. Ncurses install routine doesn't set the permissions
executable. Ncurses's install routine doesn't set the permissions
properly so we do it manually instead.</para>
<para><userinput>ln -sf libncurses.a libcurses.a:</userinput> Some

2
chapter06/nettools-inst.xml
View File

@ -14,7 +14,7 @@ make update</userinput></screen></para>
<para>If you don't know what to answer to all the questions asked during
the <userinput>make</userinput> phase, then just accept the defaults, which
will be just in fine in the majority of the cases. What you are asked here
will be just fine in the majority of the cases. What you are asked here
are a bunch of questions relating to the kind of network protocols that you
have enabled in your kernel.</para>

2
chapter06/perl-inst.xml
View File

@ -8,7 +8,7 @@ make &amp;&amp;
make install</userinput></screen></para>
<para>If you want more control over the way perl sets itself up to be
build, you can run the interactive <userinput>Configure</userinput> script
built, you can run the interactive <userinput>Configure</userinput> script
and modify the way perl is built. If you think you can live with the
(sensible) defaults perl auto-detects, then just use the commands listed
above.</para>

4
chapter06/pwdgroup.xml
View File

@ -35,8 +35,8 @@ audio:x:11:
<para>The created groups aren't part of any standard -- they are the groups
that the MAKEDEV script in the next section uses.
Besides the group "root", the LSB recommends only a group "bin" with a GID
of 1 to be present. All other group names and GIDs can be chosen freely by
Besides the group "root", the LSB recommends only a group "bin", with a GID
of 1, be present. All other group names and GIDs can be chosen freely by
the user, as well-written packages don't depend on GID numbers but use the
group's name.</para>