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_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 | <sect2>
|
|---|
| 2 | <title>Command explanations</title>
|
|---|
| 3 |
|
|---|
| 4 | <para><userinput>cp $LFS/usr/bin/gunzip $LFS/usr/bin/gzip $LFS/bin
|
|---|
| 5 | && rm $LFS/usr/bin/gunzip $LFS/usr/bin/gzip:</userinput> The reason
|
|---|
| 6 | we don't simply use <quote>mv</quote> to move the files to the new location
|
|---|
| 7 | is because gunzip is a hardlink to gzip. On older distributions you can't
|
|---|
| 8 | move a hardlink to another partition (and it's very possible that $LFS and
|
|---|
| 9 | $LFS/usr are separate partitions). With more recent distributions this
|
|---|
| 10 | isn't a problem. If you run mv to move hardlinks across partitions it'll
|
|---|
| 11 | just do a regular <quote>cp</quote> and discard the hardlink. But, we
|
|---|
| 12 | can't assume that every host distribution has a new enough kernel and
|
|---|
| 13 | fileutils that works this way.</para>
|
|---|
| 14 |
|
|---|
| 15 | </sect2>
|
|---|
| 16 |
|
|---|
Note:
See
TracBrowser
for help on using the repository browser.
