gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-01-19 13:37:39 +00:00
Code Issues Packages Projects Releases Wiki Activity

explained why we cp+rm during gzip install

Browse Source 
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@1535 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Gerard Beekmans 2002-02-02 17:04:30 +00:00
parent 8e498d1c22
commit cf45fbd135
3 changed files with 18 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
chapter05/gzip-exp.xml Normal file
View File

@ -0,0 +1,16 @@
<sect2>
<title>Command explanations</title>
<para><userinput>cp $LFS/usr/bin/gunzip $LFS/usr/bin/gzip $LFS/bin &&
rm $LFS/usr/bin/gunzip $LFS/usr/bin/gzip:</userinput> The reason we don't
simply use <quote>mv</quote> to move the files to the new location is
because gunzip is a hardlink to gzip. On older distributions you can't
move a hardlink to another partition (and it's very possible that $LFS and
$LFS/usr are seperate partitions). With more recent distributions this
isn't a problem. If you run mv to move hardlinks across partitions it'll
just do a regular <quote>cp</quote> and discard the hardlink. But, we
can't assume that every host distribution has a new enough kernel and
fileutils that works this way.</para>
</sect2>

1
chapter05/gzip.xml
View File

@ -6,6 +6,7 @@
Estimated required disk space: &gzip-compsize-static;</screen>
&c5-gzip-inst;
&c5-gzip-exp;
&aa-gzip-desc;
&aa-gzip-dep;

1
index.xml
View File

@ -166,6 +166,7 @@
<!ENTITY c5-grep-inst SYSTEM "chapter5/grep-inst.xml">
<!ENTITY c5-gzip SYSTEM "chapter5/gzip.xml">
<!ENTITY c5-gzip-inst SYSTEM "chapter5/gzip-inst.xml">
<!ENTITY c5-gzip-exp SYSTEM "chapter5/gzip-exp.xml">
<!ENTITY c5-kernel SYSTEM "chapter5/kernel.xml">
<!ENTITY c5-kernel-inst SYSTEM "chapter5/kernel-inst.xml">
<!ENTITY c5-kernel-exp SYSTEM "chapter5/kernel-exp.xml">