mirror of
https://git.linuxfromscratch.org/lfs.git
synced 2025-06-18 19:29:21 +01:00
Grammar fixes.
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@327 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
parent
01c82183ad
commit
a8e58c7e81
@ -3,7 +3,7 @@
|
||||
|
||||
<para>
|
||||
Typing out all the bootscripts in chapters 7 and 9 can be a long tedious
|
||||
process, not to mention very error prone.
|
||||
process, not to mention very error-prone.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
@ -12,7 +12,7 @@ from <ulink
|
||||
url="http://download.linuxfromscratch.org/bootscripts/">
|
||||
http://download.linuxfromscratch.org/bootscripts/</ulink> or <ulink
|
||||
url="ftp://download.linuxfromscratch.org/bootscripts/">
|
||||
ftp://download.linuxfromscratch.org/bootscripts/</ulink>
|
||||
ftp://download.linuxfromscratch.org/bootscripts/</ulink>.
|
||||
</para>
|
||||
|
||||
</sect1>
|
||||
|
@ -4,10 +4,10 @@
|
||||
<para>
|
||||
Before you can actually start doing something with a package, you need
|
||||
to unpack it first. Often you will find the package files being tar'ed and
|
||||
gzip'ed (you can determind this 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 you how to do that once, in this paragraph.
|
||||
gzip'ed. (You can determine this 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 you how to do that once, in this section.
|
||||
There is also the possibility that you have the ability of downloading
|
||||
a .tar.bz2 file. Such a file is tar'ed and compressed with the bzip2 program.
|
||||
Bzip2 achieves a better compression than the commonly used gzip does. In
|
||||
@ -91,8 +91,8 @@ When you have a file that is gzip'ed, you unpack it by running:
|
||||
<para>
|
||||
After you have installed a package you can do two things with it. You can
|
||||
either delete the directory that contains the sources or you can keep it.
|
||||
If you decide to keep it, that's fine by me. But if you need the same package
|
||||
again in a later chapter you need to delete the directory first before using
|
||||
If you decide to keep it, that's fine with me. But, if you need the same package
|
||||
again in a later chapter, you need to delete the directory first before using
|
||||
it again. If you don't do this, you might end up in trouble because old
|
||||
settings will be used (settings that apply to your normal Linux system but
|
||||
which don't always apply to your LFS system). Doing a simple make clean
|
||||
|
Loading…
Reference in New Issue
Block a user