Changing chapter IDs in anticipation.

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3221 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

4 files changed, 7 insertions, 7 deletions

diff --git a/chapter02/aboutlfs.xml b/chapter02/aboutlfs.xml
index ff1ecf0e0..7aac118ba 100644
--- a/chapter02/aboutlfs.xml
+++ b/chapter02/aboutlfs.xml
@@ -6,7 +6,7 @@
 variable LFS will be used frequently. $LFS must at all times be replaced with
 the directory where the partition that contains the LFS system is mounted. How
 to create and where to mount the partition will be explained in full detail in
-<xref linkend="chapter03"/>. For the moment let's assume that the LFS partition
+<xref linkend="chapter-making-space"/>. For the moment let's assume that the LFS partition
 is mounted on <filename>/mnt/lfs</filename>.</para>
 
 <para>When you are told to run a command like
diff --git a/chapter02/aboutsbus.xml b/chapter02/aboutsbus.xml
index d1a7485e5..cf2685e70 100644
--- a/chapter02/aboutsbus.xml
+++ b/chapter02/aboutsbus.xml
@@ -12,7 +12,7 @@ with the idea of using the <emphasis>Static Binutils Unit</emphasis>
 (abbreviated to <emphasis>SBU</emphasis>).</para>
 
 <para>It works like this: the first package you compile in this book is the
-statically linked Binutils in <xref linkend="chapter05"/>, and the time it
+statically linked Binutils in <xref linkend="chapter-temporary-tools"/>, and the time it
 takes to compile this package is what we call the "Static Binutils Unit" or
 "SBU". All other compile times will be expressed relative to this time.</para>
 
diff --git a/chapter02/abouttestsuites.xml b/chapter02/abouttestsuites.xml
index 258f35352..e580a9a79 100644
--- a/chapter02/abouttestsuites.xml
+++ b/chapter02/abouttestsuites.xml
@@ -16,12 +16,12 @@ properly functioning system. But be warned, the test suites for GCC and Glibc
 can take a very long time to complete, especially on slower hardware.</para>
 
 <para>Experience has shown us that there is little to be gained from running
-the test suites in <xref linkend="chapter05"/>. There can be no escaping the
+the test suites in <xref linkend="chapter-temporary-tools"/>. There can be no escaping the
 fact that the host system always exerts influence on the tests in that chapter,
 often causing weird and inexplicable failures. Not only that, the tools built
-in <xref linkend="chapter05"/> are temporary and eventually discarded. For the
+in <xref linkend="chapter-temporary-tools"/> are temporary and eventually discarded. For the
 average reader of this book we recommend <emphasis>not</emphasis> to run the
-test suites in <xref linkend="chapter05"/>. The instructions for running those
+test suites in <xref linkend="chapter-temporary-tools"/>. The instructions for running those
 test suites are still provided for the benefit of testers and developers, but
 they are strictly optional for everyone else.</para>
 
@@ -35,7 +35,7 @@ is running out of pseudo terminals (PTYs for short). The symptom is an
 unusually high number of failing tests. This can happen for a number of
 reasons. Most likely is that the host system doesn't have the
 <emphasis>devpts</emphasis> file system set up correctly. We'll discuss this in
-more detail later on in <xref linkend="chapter05"/>.</para></note>
+more detail later on in <xref linkend="chapter-temporary-tools"/>.</para></note>
 
 </sect1>
 
diff --git a/chapter02/chapter02.xml b/chapter02/chapter02.xml
index 3265cac98..9d6956300 100644
--- a/chapter02/chapter02.xml
+++ b/chapter02/chapter02.xml
@@ -1,4 +1,4 @@
-<chapter id="chapter02" xreflabel="Chapter 2">
+<chapter id="chapter-preparation" xreflabel="Chapter 2">
 <title>Important information</title>
 <?dbhtml filename="chapter02.html" dir="chapter02"?>