aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorGreg Schafer <greg@linuxfromscratch.org>2004-01-16 12:45:51 +0000
committerGreg Schafer <greg@linuxfromscratch.org>2004-01-16 12:45:51 +0000
commitb05a83179d382145b6c1c8ae566870fac5ed84cb (patch)
tree9b2bc3ad4b212239237fc95ffc7260e7f0e313c3
parent31b2ae676d85a5b1efe3ef3105ef14f9ae6623af (diff)
Add small clarifications based on feedback from support list.
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3171 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
-rw-r--r--chapter05/chapter05.xml8
1 files changed, 6 insertions, 2 deletions
diff --git a/chapter05/chapter05.xml b/chapter05/chapter05.xml
index 6cc82baae..484a06d13 100644
--- a/chapter05/chapter05.xml
+++ b/chapter05/chapter05.xml
@@ -24,13 +24,17 @@ them to pollute the soon-to-be LFS system.</para>
<para>The build instructions assume that you are using the
<userinput>bash</userinput> shell. It is also expected that you have already
-unpacked the sources and performed a <userinput>cd</userinput> into the source
+unpacked a source package (while logged in as user <emphasis>lfs</emphasis> --
+explained shortly) and performed a <userinput>cd</userinput> into the source
directory of a package before issuing its build commands.</para>
<para>Several of the packages are patched before compilation, but only when
the patch is needed to circumvent a problem. Often the patch is needed in
both this and the next chapter, but sometimes in only one of them. Therefore,
-don't worry when instructions for a downloaded patch seem to be missing.</para>
+don't worry when instructions for a downloaded patch seem to be missing. When
+applying a patch you'll occasionally see a warning message about
+<emphasis>offset</emphasis> or <emphasis>fuzz</emphasis>. These warnings are
+nothing to worry about as the patch was still successfully applied.</para>
<para>During the installation of most packages you will
see all kinds of compiler warnings scroll by on your screen. These are