Changeset 15b6ed4 for chapter06


Ignore:
Timestamp:
01/21/2004 10:15:22 PM (20 years ago)
Author:
Alex Gronenwoud <alex@…>
Branches:
10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.0, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, v5_1, v5_1_1, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
Children:
5618bb7
Parents:
d12fdb1
Message:

Adding a few cross references.

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

Location:
chapter06
Files:
4 edited

Legend:

Unmodified
Added
Removed

  • chapter06/chapter06.xml

    rd12fdb1 r15b6ed4  
    274274use the group's name.</para>
    275275
    276 <para>Lastly, we re-login to the chroot environment.  User name and group name
    277 resolution will start working immediately after the
    278 <filename>/etc/passwd</filename> and <filename>/etc/group</filename> files are
    279 created, because we installed a full Glibc in Chapter 5.  This will get rid of
    280 the <quote>I have no name!</quote> prompt.</para>
     276<para>To get rid of the "I have no name!" prompt, we will start a new shell.
     277Since we installed a full Glibc in <xref linkend="chapter05"/>, and have just
     278created the <filename>/etc/passwd</filename> and
     279<filename>/etc/group</filename> files, user name and group name resolution
     280will now work.</para>
    281281
    282282<screen><userinput>exec /tools/bin/bash --login +h</userinput></screen>
    … …  
    330330
    331331<note><para>If you somehow missed the earlier warning to retain the Binutils
    332 source and build directories from the second pass in Chapter 5 or otherwise
    333 accidentally deleted them or just don't have access to them, don't worry, all is
    334 not lost. Just ignore the above command. The result will be that the next
    335 package, Binutils, will link against the Glibc libraries in
    336 <filename class="directory">/tools</filename> rather than
    337 <filename class="directory">/usr</filename>. This is not ideal, however, our
    338 testing has shown that the resulting Binutils program binaries should be
     332source and build directories from the second pass in
     333<xref linkend="chapter05"/>, or otherwise accidentally deleted them or just
     334don't have access to them, don't worry, all is not lost. Just ignore the above
     335command. The result will be that the next package, Binutils, will link against
     336the Glibc libraries in <filename class="directory">/tools</filename> rather
     337than <filename class="directory">/usr</filename>. This is not ideal, however,
     338our testing has shown that the resulting Binutils program binaries should be
    339339identical.</para></note>
    340340

  • chapter06/gcc.xml

    rd12fdb1 r15b6ed4  
    3838
    3939<note><para>Be careful <emphasis role="strong">not</emphasis> to apply the GCC
    40 Specs patch from Chapter 5 here.</para></note>
     40Specs patch from <xref linkend="chapter05"/> here.</para></note>
    4141
    4242<para>First apply the No-Fixincludes patch that we also used in the previous
    … …  
    9696<xref linkend="ch06-adjustingtoolchain"/> and repeat the check. If the results
    9797are wrong, then most likely you erroneously applied the GCC Specs patch from
    98 Chapter 5.</para></note>
     98<xref linkend="chapter05"/>.</para></note>
    9999
    100100</sect2>

  • chapter06/makedev.xml

    rd12fdb1 r15b6ed4  
    4949information.</para>
    5050
    51 <para>Additionally, if you were unable to mount the devpts filesystem earlier in
    52 the "Mounting the proc and devpts file systems" section, now is the time to
    53 try the alternatives. If your kernel supports the devfs file system, run the
    54 following command to mount devfs:</para>
     51<para>Additionally, if you were unable to mount the devpts filesystem earlier
     52in <xref linkend="ch06-proc"/>, now is the time to try the alternatives. If
     53your kernel supports the devfs file system, run the following command to mount
     54devfs:</para>
    5555
    5656<screen><userinput>mount -t devfs devfs /dev</userinput></screen>

  • chapter06/mountproc.xml

    rd12fdb1 r15b6ed4  
    4848<emphasis>devfs</emphasis> is listed there, then we'll be able to work around
    4949the problem by mounting the host's devfs file system on top of the new
    50 <filename>/dev</filename> structure which we'll create later on in the
    51 "Creating devices (Makedev)" section. If devfs was not listed, do not worry
     50<filename>/dev</filename> structure which we'll create later on in the section
     51on <xref linkend="ch06-MAKEDEV"/>. If devfs was not listed, do not worry
    5252because there is yet a third way to get PTYs working inside the chroot
    53 environment. We'll cover this shortly in the aforementioned Makedev
    54 section.</para>
     53environment. We'll cover this shortly in the aforementioned
     54<xref linkend="ch06-MAKEDEV"/> section.</para>
    5555
    5656<para>Remember, if for any reason you stop working on your LFS, and start again
Note: See TracChangeset for help on using the changeset viewer.