|
|
@@ -5,17 +5,19 @@
|
|
|
<para>Throughout this document, we will assume that all the
|
|
|
packages that were downloaded are placed somewhere in $LFS/usr/src.</para>
|
|
|
|
|
|
-<para>A convention you could use is having a $LFS/usr/src/sources directory.
|
|
|
-Under sources, you can create the directory 0-9 and the directories a
|
|
|
-through z. A package like sysvinit-&sysvinit-version;.tar.bz2 is stored under
|
|
|
-$LFS/usr/src/sources/s/. A package like bash-&bash-version;.tar.bz2 is stored
|
|
|
-under $LFS/usr/src/sources/b/, and so forth.</para>
|
|
|
+<para>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
|
|
|
+seperate tarballs from temporary build directories, but again that's up
|
|
|
+to you.</para>
|
|
|
|
|
|
-<para>The next chapter contains the list of all the packages that need to be
|
|
|
-downloaded, but the partition that is going to contain our LFS system isn't
|
|
|
-created yet. Therefore, you should store the files somewhere else and later
|
|
|
-on move them to $LFS/usr/src/ when the chapter in which the new partition is
|
|
|
-prepared has been finished.</para>
|
|
|
+<para>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
|
|
|
+there yet. Just save it elsewhere for now, and when the LFS partition is
|
|
|
+created, move them over.</para>
|
|
|
|
|
|
</sect1>
|
|
|
|
Gerard Beekmans