From 8f752242daade0f5a6ef94e7bcf7b7f082f2837e Mon Sep 17 00:00:00 2001 From: Alex Gronenwoud Date: Wed, 15 Oct 2003 22:39:23 +0000 Subject: Putting tarballs and patches in $LFS/sources. git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2988 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689 --- chapter04/chapter04.xml | 20 ++++++++++++-------- 1 file changed, 12 insertions(+), 8 deletions(-) (limited to 'chapter04/chapter04.xml') 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 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 $LFS/tools/sources/packages for the -tarballs, and $LFS/tools/sources as the working directory -and 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. +works well is to use $LFS/sources as the place to store +the tarballs and patches, and 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. -So you may want to execute the following command before starting -your download session: +So you may want to execute, as root, the following +command before starting your download session: -mkdir -p $LFS/tools/sources/packages +mkdir $LFS/sources + +And make this directory writable (and sticky) for your normal user -- as +you won't do the downloading as root, we guess: + +chmod a+wt $LFS/sources