From cf45fbd1353d1cca5ada1e0413d9c487c0f65c95 Mon Sep 17 00:00:00 2001
From: Gerard Beekmans <gerard@linuxfromscratch.org>
Date: Sat, 2 Feb 2002 17:04:30 +0000
Subject: explained why we cp+rm during gzip install

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@1535 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
---
 chapter05/gzip-exp.xml | 16 ++++++++++++++++
 chapter05/gzip.xml     |  1 +
 2 files changed, 17 insertions(+)
 create mode 100644 chapter05/gzip-exp.xml

(limited to 'chapter05')

diff --git a/chapter05/gzip-exp.xml b/chapter05/gzip-exp.xml
new file mode 100644
index 000000000..ceabd4d47
--- /dev/null
+++ b/chapter05/gzip-exp.xml
@@ -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>
+
diff --git a/chapter05/gzip.xml b/chapter05/gzip.xml
index 9ae7efa96..0155e02e1 100644
--- a/chapter05/gzip.xml
+++ b/chapter05/gzip.xml
@@ -6,6 +6,7 @@
 Estimated required disk space:  &gzip-compsize-static;</screen>
 
 &c5-gzip-inst;
+&c5-gzip-exp;
 &aa-gzip-desc;
 &aa-gzip-dep;
 
-- 
cgit v1.2.3-54-g00ecf