aboutsummaryrefslogtreecommitdiffstats
path: root/chapter04/chapter04.xml
diff options
context:
space:
mode:
Diffstat (limited to 'chapter04/chapter04.xml')
-rw-r--r--chapter04/chapter04.xml20
1 files changed, 12 insertions, 8 deletions
diff --git a/chapter04/chapter04.xml b/chapter04/chapter04.xml
index 86ce11068..36a04ae34 100644
--- a/chapter04/chapter04.xml
+++ b/chapter04/chapter04.xml
@@ -32,16 +32,20 @@ of the alternative means of downloading listed on
<para>You'll need to store all the downloaded packages and patches somewhere
that is conveniently available throughout the entire build. You'll also need a
working directory in which to unpack the sources and build them. A scheme that
-works well is to use <filename>$LFS/tools/sources/packages</filename> for the
-tarballs, and <filename>$LFS/tools/sources</filename> as the working directory
-<emphasis>and</emphasis> as the place to store the patches. In this way,
-everything will be on the LFS partition and available during all stages of the
-building process.</para>
+works well is to use <filename>$LFS/sources</filename> as the place to store
+the tarballs and patches, <emphasis>and</emphasis> as a working directory.
+This way everything you need will be located on the LFS partition and available
+during all stages of the building process.</para>
-<para>So you may want to execute the following command before starting
-your download session:</para>
+<para>So you may want to execute, as <emphasis>root</emphasis>, the following
+command before starting your download session:</para>
-<screen><userinput>mkdir -p $LFS/tools/sources/packages</userinput></screen>
+<screen><userinput>mkdir $LFS/sources</userinput></screen>
+
+<para>And make this directory writable (and sticky) for your normal user -- as
+you won't do the downloading as <emphasis>root</emphasis>, we guess:</para>
+
+<screen><userinput>chmod a+wt $LFS/sources</userinput></screen>
<!--
<para>For your convenience the top of the list contains a link to a file