diff options
Diffstat (limited to 'chapter06')
| -rw-r--r-- | chapter06/chapter06.xml | 24 | ||||
| -rw-r--r-- | chapter06/gcc.xml | 4 | ||||
| -rw-r--r-- | chapter06/makedev.xml | 8 | ||||
| -rw-r--r-- | chapter06/mountproc.xml | 8 |
4 files changed, 22 insertions, 22 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> diff --git a/chapter06/gcc.xml b/chapter06/gcc.xml index db2d3ab1b..9609b8713 100644 --- a/chapter06/gcc.xml +++ b/chapter06/gcc.xml @@ -37,7 +37,7 @@ compilers. Instructions for building these can be found at <ulink url="&blfs-root;view/stable/general/gcc.html"/>.</para> <note><para>Be careful <emphasis role="strong">not</emphasis> to apply the GCC -Specs patch from Chapter 5 here.</para></note> +Specs patch from <xref linkend="chapter05"/> here.</para></note> <para>First apply the No-Fixincludes patch that we also used in the previous chapter:</para> @@ -95,7 +95,7 @@ compiler. To satisfy those packages, create a symlink:</para> we performed earlier in this chapter. Refer back to <xref linkend="ch06-adjustingtoolchain"/> and repeat the check. If the results are wrong, then most likely you erroneously applied the GCC Specs patch from -Chapter 5.</para></note> +<xref linkend="chapter05"/>.</para></note> </sect2> diff --git a/chapter06/makedev.xml b/chapter06/makedev.xml index d48d57cfd..4b273d54e 100644 --- a/chapter06/makedev.xml +++ b/chapter06/makedev.xml @@ -48,10 +48,10 @@ Alternatively, you may create devices via the <userinput>mknod</userinput> program. Please refer to its man and info pages if you need more information.</para> -<para>Additionally, if you were unable to mount the devpts filesystem earlier in -the "Mounting the proc and devpts file systems" section, now is the time to -try the alternatives. If your kernel supports the devfs file system, run the -following command to mount devfs:</para> +<para>Additionally, if you were unable to mount the devpts filesystem earlier +in <xref linkend="ch06-proc"/>, now is the time to try the alternatives. If +your kernel supports the devfs file system, run the following command to mount +devfs:</para> <screen><userinput>mount -t devfs devfs /dev</userinput></screen> diff --git a/chapter06/mountproc.xml b/chapter06/mountproc.xml index c9ce922ea..d9190e8ac 100644 --- a/chapter06/mountproc.xml +++ b/chapter06/mountproc.xml @@ -47,11 +47,11 @@ your kernel supports by peeking into its internals with a command such as <userinput>cat /proc/filesystems</userinput>. If a file system type named <emphasis>devfs</emphasis> is listed there, then we'll be able to work around the problem by mounting the host's devfs file system on top of the new -<filename>/dev</filename> structure which we'll create later on in the -"Creating devices (Makedev)" section. If devfs was not listed, do not worry +<filename>/dev</filename> structure which we'll create later on in the section +on <xref linkend="ch06-MAKEDEV"/>. If devfs was not listed, do not worry because there is yet a third way to get PTYs working inside the chroot -environment. We'll cover this shortly in the aforementioned Makedev -section.</para> +environment. We'll cover this shortly in the aforementioned +<xref linkend="ch06-MAKEDEV"/> section.</para> <para>Remember, if for any reason you stop working on your LFS, and start again later, it's important to check that these filesystems are still mounted inside |