aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorSimon Perreault <nomis80@videotron.ca>2001-05-13 22:07:24 +0000
committerSimon Perreault <nomis80@videotron.ca>2001-05-13 22:07:24 +0000
commit9e4e34c05027fbcda217a3744ebe91a541ee093a (patch)
tree46ce76510c2bbf0aeb47d99fbb84e5a647f1ed3e
parent0c4eb2c99a6005a262108a18fc460161c6d22783 (diff)
he -> you
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@635 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
-rw-r--r--chapter06/lilo-inst.xml4
-rw-r--r--chapter06/m4-inst.xml8
-rw-r--r--chapter06/tar-inst.xml2
-rw-r--r--chapter06/vim-inst.xml4
4 files changed, 9 insertions, 9 deletions
diff --git a/chapter06/lilo-inst.xml b/chapter06/lilo-inst.xml
index 63f9744c5..26a4be20b 100644
--- a/chapter06/lilo-inst.xml
+++ b/chapter06/lilo-inst.xml
@@ -19,8 +19,8 @@ Install Lilo by running the following commands:
<para>
It appears that compilation of this package fails on certain machines
-when the -g compiler flag is being used. If a user can't compile Lilo at
-all, he should try to remove the -g value from the CFLAGS variable in the
+when the -g compiler flag is being used. If you can't compile Lilo at
+all, you should try to remove the -g value from the CFLAGS variable in the
<filename>Makefile</filename> file.
</para>
diff --git a/chapter06/m4-inst.xml b/chapter06/m4-inst.xml
index 6985745fe..e43aeece3 100644
--- a/chapter06/m4-inst.xml
+++ b/chapter06/m4-inst.xml
@@ -13,11 +13,11 @@ Install M4 by running the following commands:
<para>
If the base system is running a 2.0 kernel and the Glibc version is
-2.1 then a user will most likely get problems executing M4 in the
+2.1 then you will most likely get problems executing M4 in the
chroot'ed environment due to incompatibilities between the M4 program,
-Glibc-2.1 and the running 2.0 kernel. If he has problems executing the
-m4 program in the chroot'ed environment (for example when he installs
-the autoconf and automake packages) he'll have to exit the chroot'ed
+Glibc-2.1 and the running 2.0 kernel. If you have problems executing the
+m4 program in the chroot'ed environment (for example when you install
+the autoconf and automake packages) you'll have to exit the chroot'ed
environment and compile M4 statically. This way the binary is linked
against Glibc 2.0 (if he runs kernel 2.0, Glibc version is 2.0 as
well on a decent system. Kernel 2.0 and Glibc-2.1 don't mix very well)
diff --git a/chapter06/tar-inst.xml b/chapter06/tar-inst.xml
index 6d8e084a0..6c779cdb4 100644
--- a/chapter06/tar-inst.xml
+++ b/chapter06/tar-inst.xml
@@ -2,7 +2,7 @@
<title>Installation of Tar</title>
<para>
-If a user wants to be able to directly use bzip2 files with tar, he can
+If you want to be able to directly use bzip2 files with tar, you can
use the tar
patch available from the LFS FTP site. This patch will add the -y option
to tar which works the same as the -z option to tar (which can be used
diff --git a/chapter06/vim-inst.xml b/chapter06/vim-inst.xml
index e010b8c9b..81366f63a 100644
--- a/chapter06/vim-inst.xml
+++ b/chapter06/vim-inst.xml
@@ -25,8 +25,8 @@ in which order it is done. Install Vim by running the following commands:
</literallayout></blockquote>
<para>
-If you plan on installing the X Window system on his LFS
-system, you might want to re-compile Vim after he has installed X. Vim
+If you plan on installing the X Window system on your LFS
+system, you might want to re-compile Vim after you have installed X. Vim
comes with a nice GUI version of the editor which requires X and a few
other libraries to be installed. For more information read the Vim
documentation.