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

Grammar fixes.

Browse Source 
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@347 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Simon Perreault 2001-03-22 03:27:52 +00:00
parent 9bfaaaef19
commit 87c057b51b
3 changed files with 21 additions and 21 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
chapter02/bootscripts.xml
View File

@ -2,7 +2,7 @@
<title>Download the bootscripts</title>
<para>
Typing out all the bootscripts in chapters 7 and 9 can be a long tedious
Typing out all the bootscripts in chapters 7 and 9 can be a long, tedious
process, not to mention very error-prone.
</para>

10
chapter02/commands.xml
View File

@ -5,8 +5,8 @@
LFS Commands is a tarball containing files which list the installation
commands for the packages installed in this book. These files can be
used to dump to a shell and install the packages, though some files
need to be modified (for example when the console-tools package is
installed it is needed to select the keyboard layout file which can't be
need to be modified (for example, when the console-tools package is
installed, it is needed to select the keyboard layout file, which can't be
guessed).
</para>
@ -14,9 +14,9 @@ guessed).
These files can be used to quickly find out which commands have been
changed between the different LFS versions as well. A user just downloads the
lfs-commands tarball for this book version and the previous book version
and run a diff on the files. That way it is possible to see which packages
and runs a diff on the files. That way it is possible to see which packages
have
updated installation instructions and he can modify his own scripts, or
updated installation instructions, and he can modify his own scripts or
reinstall a package if it seems necessary.
</para>
@ -25,7 +25,7 @@ The lfscommands can be downloaded from <ulink
url="http://download.linuxfromscratch.org/lfs-commands/">
http://download.linuxfromscratch.org/lfs-commands/</ulink> or <ulink
url="ftp://download.linuxfromscratch.org/lfs-commands/">
ftp://download.linuxfromscratch.org/lfs-commands/</ulink>
ftp://download.linuxfromscratch.org/lfs-commands/</ulink>.
</para>
</sect1>

30
chapter02/install.xml
View File

@ -4,16 +4,16 @@
<para>
Before a user can actually start doing something with a package, he needs
to unpack it first. Often the package files are tar'ed and
gzip'ed. (that can determined by looking at the extension of the file.
tar'ed and gzip'ed archives have a .tar.gz or .tgz extension, for
gzip'ed. (That can determined by looking at the extension of the file.
Tar'ed and gzip'ed archives have a .tar.gz or .tgz extension, for
example.) I'm not going to write down every time how to ungzip and how
to untar an archive. I will tell how to do that once, in this section.
There is also the possibility that a .tar.bz2 file can be downloaded.
Such a file is tar'ed and compressed with the bzip2 program.
There is also the possibility that a .tar.bz2 file could be downloaded.
Such a file would be tar'ed and compressed with the bzip2 program.
Bzip2 achieves a better compression than the commonly used gzip does. In
order to use bz2 archives the bzip2 program needs to be installed.
Most if not every distribution comes with this program so chances are
high it is already installed on the host-system. If not, it's installed using
order to use bz2 archives, the bzip2 program needs to be installed.
Most if not every distribution comes with this program, so chances are
high it is already installed on the host system. If not, it's installed using
the distribution's installation tool.
</para>
@ -55,7 +55,7 @@ running:
<para>
Some tar programs (most of them nowadays but not all of them) are
slightly modified to be able to use bzip2 files directly using either
the I or the y tar parameter which works the same as the z tar parameter
the I or the y tar parameter, which works the same as the z tar parameter
to handle gzip archives.
</para>
@ -70,16 +70,16 @@ If a file is just tar'ed, it is unpacked by running:
</literallayout></blockquote>
<para>
When the archive is unpacked a new directory will be created under the
When the archive is unpacked, a new directory will be created under the
current directory (and this document assumes that the archives are unpacked
under the $LFS/usr/src directory). A user has to enter that new directory
before continuing with the installation instructions. So every time the
before continuing with the installation instructions. So, every time the
book is going to install a program, it's up to the user to unpack the source
archive.
</para>
<para>
f a file is gzip'ed, it is unpacked by running:
If a file is gzip'ed, it is unpacked by running:
</para>
<blockquote><literallayout>
@ -89,10 +89,10 @@ f a file is gzip'ed, it is unpacked by running:
</literallayout></blockquote>
<para>
After a package is installed two things can be done with it.
Either the directory that contains the sources can be deleted
or it can be kept.
If it is kept, that's fine with me. But, if the same package is needed
After a package is installed, two things can be done with it:
either the directory that contains the sources can be deleted,
either it can be kept.
If it is kept, that's fine with me, but if the same package is needed
again in a later chapter, the directory needs to be deleted first before using
it again. If this is not done, it might end up in trouble because old
settings will be used (settings that apply to the normal Linux system but