Changeset efcb393 for chapter01/how.xml


Ignore:
Timestamp:
05/03/2020 09:02:51 PM (4 years ago)
Author:
Pierre Labastie <pieere@…>
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, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, 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:
a715dec
Parents:
9d719e2
Message:

Make the new book

git-svn-id: http://svn.linuxfromscratch.org/LFS/branches/cross-chap5@11831 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

File:
1 edited

Legend:

Unmodified
Added
Removed
  • chapter01/how.xml

    r9d719e2 refcb393  
    4747  work your way through <xref linkend="chapter-temporary-tools"/> and beyond.</para>
    4848
    49   <para><xref linkend="chapter-temporary-tools"/> explains the
    50   installation of a number of packages that will form the basic
    51   development suite (or toolchain) which is used to build the actual
    52   system in <xref linkend="chapter-building-system"/>. Some of these
    53   packages are needed to resolve circular dependencies&mdash;for example,
    54   to compile a compiler, you need a compiler.</para>
     49  <para><xref linkend="chapter-temporary-tools"/> explains the installation of
     50  a number of packages that are needed to resolve circular
     51  dependencies&mdash;for example, to compile a compiler, you need a compiler.
     52  or to unpack the tar package, you need tar.</para>
    5553
    5654  <para><xref linkend="chapter-temporary-tools"/> also shows you how to
     
    6765
    6866  <para>This effort to isolate the new system from the host distribution may
    69   seem excessive. A full technical explanation as to why this is done is provided in
    70   <xref linkend="ch-tools-toolchaintechnotes"/>.</para>
     67  seem excessive. A full technical explanation as to why this is done is
     68  provided in <xref linkend="ch-tools-toolchaintechnotes"/>.</para>
    7169
    72   <para>In <xref linkend="chapter-building-system"/>, the full LFS system is
    73   built. The <command>chroot</command> (change root) program is used to enter
    74   a virtual environment and start a new shell whose root directory will be
    75   set to the LFS partition. This is very similar to rebooting and instructing
    76   the kernel to mount the LFS partition as the root partition. The system
    77   does not actually reboot, but instead uses <command>chroot</command> because
    78   creating a bootable system requires additional work which is not necessary
    79   just yet. The major advantage is that <quote>chrooting</quote> allows you
    80   to continue using the host system while LFS is being built. While waiting
    81   for package compilations to complete, you can continue using your computer as
    82   normal.</para>
     70  <para><xref linkend="chapter-building-system"/> begins with installing the
     71  remaining packages needed to build and test the final toolchain. Then, the
     72  full LFS system is built. But first, the <command>chroot</command> (change
     73  root) program is used to enter a virtual environment and start a new shell
     74  whose root directory will be set to the LFS partition. This is very similar
     75  to rebooting and instructing the kernel to mount the LFS partition as the
     76  root partition. The system does not actually reboot, but instead uses
     77  <command>chroot</command> because creating a bootable system requires
     78  additional work which is not necessary just yet. The major advantage is
     79  that <quote>chrooting</quote> allows you to continue using the host system
     80  while LFS is being built. While waiting for package compilations to
     81  complete, you can continue using your computer as normal.</para>
    8382
    8483  <para>To finish the installation, the basic system configuration is set up in
Note: See TracChangeset for help on using the changeset viewer.