From 1e6acd6f703fb691ec8d54672f8058ebc9fadad5 Mon Sep 17 00:00:00 2001 From: Timothy Bauscher Date: Sun, 22 Sep 2002 03:01:40 +0000 Subject: Applied Bill Maltby's grammatic-fixes patch. git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2124 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689 --- chapter02/download.xml | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) (limited to 'chapter02/download.xml') diff --git a/chapter02/download.xml b/chapter02/download.xml index d8ff18345..a3e1d990a 100644 --- a/chapter02/download.xml +++ b/chapter02/download.xml @@ -6,13 +6,14 @@ packages that were downloaded are placed somewhere in $LFS/usr/src. While it doesn't matter at all where you save the downloaded -packages, we recommend storing it at least on the LFS partition. This just -makes sense because you would still have access to those files when you boot -into the LFS system. $LFS/usr/src is just a logical place to store source -code, but by no means a requirement. You may even want to create a -subdirectory under $LFS/usr/src for tarball storage. That way you can -separate tarballs from temporary build directories, but again that's up -to you. +packages, we recommend storing it at least on the LFS partition. This +just makes sense because you need to have access to those those files +when you chroot to $LFS and when you boot into the LFS system, although +access when booted to $LFS could be handled other ways. $LFS/usr/src is +just a logical place to store source code, but by no means a requirement. +You may even want to create a subdirectory under $LFS/usr/src for tarball +storage. That way you can separate tarballs from temporary build +directories, but again that's up to you. The next chapter contains a list of all the packages that need to be downloaded. The LFS partition isn't created yet, so you can't store it -- cgit v1.2.3-54-g00ecf