aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--chapter05/gzip-exp.xml16
-rw-r--r--chapter05/gzip.xml1
-rw-r--r--index.xml1
3 files changed, 18 insertions, 0 deletions
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;
diff --git a/index.xml b/index.xml
index 79a70a1a4..3f56a44d5 100644
--- a/index.xml
+++ b/index.xml
@@ -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">