Adding a few cross references.

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

1 files changed, 12 insertions, 12 deletions

diff --git a/chapter06/chapter06.xml b/chapter06/chapter06.xml
index 26e33a9d3..2797dcffc 100644
--- a/chapter06/chapter06.xml
+++ b/chapter06/chapter06.xml
@@ -273,11 +273,11 @@ with a GID of 1, be present. All other group names and GIDs can be chosen
 freely by the user, as well-written packages don't depend on GID numbers but 
 use the group's name.</para>
 
-<para>Lastly, we re-login to the chroot environment.  User name and group name
-resolution will start working immediately after the 
-<filename>/etc/passwd</filename> and <filename>/etc/group</filename> files are 
-created, because we installed a full Glibc in Chapter 5.  This will get rid of 
-the <quote>I have no name!</quote> prompt.</para>
+<para>To get rid of the "I have no name!" prompt, we will start a new shell.
+Since we installed a full Glibc in <xref linkend="chapter05"/>, and have just
+created the <filename>/etc/passwd</filename> and
+<filename>/etc/group</filename> files, user name and group name resolution
+will now work.</para>
 
 <screen><userinput>exec /tools/bin/bash --login +h</userinput></screen>
 
@@ -329,13 +329,13 @@ adjusted linker by running the following from within the
 <screen><userinput>make -C ld INSTALL=/tools/bin/install install</userinput></screen>
 
 <note><para>If you somehow missed the earlier warning to retain the Binutils
-source and build directories from the second pass in Chapter 5 or otherwise
-accidentally deleted them or just don't have access to them, don't worry, all is
-not lost. Just ignore the above command. The result will be that the next
-package, Binutils, will link against the Glibc libraries in
-<filename class="directory">/tools</filename> rather than
-<filename class="directory">/usr</filename>. This is not ideal, however, our
-testing has shown that the resulting Binutils program binaries should be
+source and build directories from the second pass in
+<xref linkend="chapter05"/>, or otherwise accidentally deleted them or just
+don't have access to them, don't worry, all is not lost. Just ignore the above
+command. The result will be that the next package, Binutils, will link against
+the Glibc libraries in <filename class="directory">/tools</filename> rather
+than <filename class="directory">/usr</filename>. This is not ideal, however,
+our testing has shown that the resulting Binutils program binaries should be
 identical.</para></note>
 
 <para>From now on every compiled program will link <emphasis>only</emphasis>