aboutsummaryrefslogtreecommitdiffstats
path: root/chapter02/commands.xml
diff options
context:
space:
mode:
authorThomas Balu Walter <tw@itreff.de>2001-03-16 18:06:46 +0000
committerThomas Balu Walter <tw@itreff.de>2001-03-16 18:06:46 +0000
commitaff91c471bc146b4ac83faec877ca0b4f71d2782 (patch)
tree67a8a1a07d58a2add5db5ba3a04da30e4fcb458a /chapter02/commands.xml
parent1b256332de6a7e02813bd137d50d15bf774e9eae (diff)
You-fix
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@330 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'chapter02/commands.xml')
-rw-r--r--chapter02/commands.xml16
1 files changed, 9 insertions, 7 deletions
diff --git a/chapter02/commands.xml b/chapter02/commands.xml
index 3c64b2f76..36449dce8 100644
--- a/chapter02/commands.xml
+++ b/chapter02/commands.xml
@@ -4,18 +4,20 @@
<para>
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 your shell and install the packages, though some files
-need to be modified (for example when you install the console-tools
-package you need to select your keyboard layout file which can't be guessed).
+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
+guessed).
</para>
<para>
These files can be used to quickly find out which commands have been
-changed between the different LFS versions as well. You can download the
+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 you can see which package have
-updated installation instructions so you can modify your own scripts, or
-reinstall a package if you deem necessary.
+and run 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
+reinstall a package if it seems necessary.
</para>
<para>