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
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/mips64el
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, we will assume that all the
|
|---|
| 5 | packages that were downloaded are placed somewhere in $LFS/usr/src.</para>
|
|---|
| 6 |
|
|---|
| 7 | <para>A convention you could use is having a $LFS/usr/src/sources directory.
|
|---|
| 8 | Under sources, you can create the directory 0-9 and the directories a
|
|---|
| 9 | through z. A package like sysvinit-&sysvinit-version;.tar.bz2 is stored under
|
|---|
| 10 | $LFS/usr/src/sources/s/. A package like bash-&bash-version;.tar.bz2 is stored
|
|---|
| 11 | under $LFS/usr/src/sources/b/, and so forth.</para>
|
|---|
| 12 |
|
|---|
| 13 | <para>The next chapter contains the list of all the packages that need to be
|
|---|
| 14 | downloaded, but the partition that is going to contain our LFS system isn't
|
|---|
| 15 | created yet. Therefore, you should store the files somewhere else and later
|
|---|
| 16 | moved to $LFS/usr/src/ when the chapter in which the new partition is
|
|---|
| 17 | prepared has been finished.</para>
|
|---|
| 18 |
|
|---|
| 19 | </sect1>
|
|---|
| 20 |
|
|---|
Note:
See
TracBrowser
for help on using the repository browser.
