10.0
10.0-rc1
10.1
10.1-rc1
11.0
11.0-rc1
11.0-rc2
11.0-rc3
11.1
11.1-rc1
11.2
11.2-rc1
11.3
11.3-rc1
12.0
12.0-rc1
12.1
12.1-rc1
12.2
12.2-rc1
6.0
6.1
6.1.1
6.3
6.4
6.5
6.6
6.7
6.8
7.0
7.1
7.2
7.3
7.4
7.5
7.5-systemd
7.6
7.6-systemd
7.7
7.7-systemd
7.8
7.8-systemd
7.9
7.9-systemd
8.0
8.1
8.2
8.3
8.4
9.0
9.1
arm
bdubbs/gcc13
ml-11.0
multilib
renodr/libudev-from-systemd
s6-init
trunk
v3_0
v3_1
v3_2
v3_3
v4_0
v4_1
v5_0
v5_1
v5_1_1
xry111/arm64
xry111/arm64-12.0
xry111/clfs-ng
xry111/lfs-next
xry111/loongarch
xry111/loongarch-12.0
xry111/loongarch-12.1
xry111/loongarch-12.2
xry111/mips64el
xry111/multilib
xry111/pip3
xry111/rust-wip-20221008
xry111/update-glibc
Line | |
---|
1 | <sect1 id="ch02-download">
|
---|
2 | <title>How to download the software</title>
|
---|
3 |
|
---|
4 | <para>Throughout this document, I will assume that all the
|
---|
5 | packages that were downloaded are placed somewhere in $LFS/usr/src.</para>
|
---|
6 |
|
---|
7 | <para>I use the convention of having a $LFS/usr/src/sources directory.
|
---|
8 | Under sources, I have the directory 0-9 and the directories a
|
---|
9 | through z. A package like sysvinit-2.78.tar.gz is stored under
|
---|
10 | $LFS/usr/src/sources/s/. A package like bash-2.04.tar.gz is stored under
|
---|
11 | $LFS/usr/src/sources/b/, and so forth. This convention does not have to be
|
---|
12 | followed, of course; I was just giving an example. It's better to keep
|
---|
13 | the packages out of $LFS/usr/src and move them to a subdirectory, so
|
---|
14 | we'll have a clean $LFS/usr/src directory in which we will unpack the
|
---|
15 | packages and work with them.</para>
|
---|
16 |
|
---|
17 | <para>The next chapter contains the list of all the packages that need to be
|
---|
18 | downloaded,
|
---|
19 | but the partition that is going to contain our LFS system isn't created yet.
|
---|
20 | Therefore, the files are temporarily stored somewhere else (it's up to
|
---|
21 | you to decide where this 'else' is) and later moved to $LFS/usr/src/ when
|
---|
22 | the chapter in which the new partition is prepared has been finished.</para>
|
---|
23 |
|
---|
24 | </sect1>
|
---|
25 |
|
---|
Note:
See
TracBrowser
for help on using the repository browser.