Changeset 7f1fcd8 for chapter01/how.xml


Ignore:
Timestamp:
10/24/2003 05:28:42 PM (21 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_0, 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:
323ef74
Parents:
494f01f
Message:

Adding several cross reference tags.

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

File:
1 edited

Legend:

Unmodified
Added
Removed

  • chapter01/how.xml

    r494f01f r7f1fcd8  
    1010as one of the options when you installed your distribution.</para>
    1111
    12 <para>In Chapter 3 you will first create a new Linux native partition and file
    13 system, the place where your new LFS system will be compiled and installed. Then
    14 in Chapter 4 you download all the packages and patches required to build an LFS
    15 system, and store them on the new file system.</para>
     12<para>In <xref linkend="chapter03"/> you will first create a new Linux native
     13partition and file system, the place where your new LFS system will be compiled
     14and installed. Then in <xref linkend="chapter04"/> you download all the
     15packages and patches required to build an LFS system, and store them on the new
     16file system.</para>
    1617
    17 <para>Chapter 5 will then discuss the installation of a number of packages that
    18 will form the basic development suite (or toolchain) which is used to build the
    19 actual system in Chapter 6. Some of these packages are needed to resolve
    20 circular dependencies. For example, to compile a compiler you need a
    21 compiler.</para>
     18<para><xref linkend="chapter05"/> then discusses the installation of a number
     19of packages that will form the basic development suite (or toolchain) which is
     20used to build the actual system in <xref linkend="chapter06"/>. Some of these
     21packages are needed to resolve circular dependencies -- for example, to compile
     22a compiler you need a compiler.</para>
    2223
    23 <para>The first thing to be done in Chapter 5 is build a first pass of the
    24 toolchain, which is made up of Binutils and GCC. The programs from these
    25 packages will be linked statically in order for them to be used independently
    26 of the host system. The second thing to do is build Glibc, the C library. Glibc
    27 will be compiled by the toolchain programs we just built in the first
    28 pass. The third thing to do is build a second pass of the toolchain. This time
    29 the toolchain will be dynamically linked against the newly built Glibc. The
    30 remaining Chapter 5 packages are all built using this second pass toolchain and
    31 dynamically linked against the new host-independent Glibc. When this is done,
    32 the LFS installation process will no longer depend on the host distribution,
    33 with the exception of the running kernel.</para>
     24<para>The first thing to be done in <xref linkend="chapter05"/> is build a
     25first pass of the toolchain, made up of Binutils and GCC. The programs from
     26these  packages will be linked statically in order for them to be usable
     27independently of the host system. The second thing to do is build Glibc, the
     28C library. Glibc will be compiled by the toolchain programs we just built in
     29the first pass. The third thing to do is build a second pass of the toolchain.
     30This time the toolchain will be dynamically linked against the newly built
     31Glibc. The remaining <xref linkend="chapter05"/> packages are all built using
     32this second pass toolchain and dynamically linked against the new
     33host-independent Glibc. When this is done, the LFS installation process will no
     34longer depend on the host distribution, with the exception of the running
     35kernel.</para>
    3436
    35 <para>You may be asking yourself <quote>that seems like a lot of work, just to
    36 get away from my host distribution?</quote>. A full technical and in-depth
    37 explanation is provided at the start of Chapter 5, including some notes on the
    38 differences between statically and dynamically linked programs.</para>
     37<para>You may be thinking that <quote>this seems like a lot of work, just to
     38get away from my host distribution</quote>. Well, a full technical explanation
     39is provided at the start of <xref linkend="chapter05"/>, including some notes
     40on the differences between statically and dynamically linked programs.</para>
    3941
    40 <para>In Chapter 6 your real LFS system will be built. The chroot (change root)
    41 program is used to enter a virtual environment and start a new shell whose root
    42 directory will be set to the LFS partition. This is very similar to rebooting
    43 and instructing the kernel to mount the LFS partition as the root partition.
    44 The reason that you don't actually reboot, but instead chroot, is that creating
    45 a bootable system requires additional work which isn't necessary just yet.
    46 Another advantage is that chrooting allows you to continue using the host while
    47 LFS is being built. While waiting for package compilation to complete, you can
    48 simply switch to a different VC (Virtual Console) or X desktop and continue
    49 using the computer as you normally would.</para>
     42<para>In <xref linkend="chapter06"/> your real LFS system will be built. The
     43chroot (change root)  program is used to enter a virtual environment and start
     44a new shell whose root directory will be set to the LFS partition. This is very
     45similar to rebooting and instructing the kernel to mount the LFS partition as
     46the root partition. The reason that you don't actually reboot, but instead
     47chroot, is that creating a bootable system requires additional work which isn't
     48necessary just yet. But the major advantage is that chrooting allows you to
     49continue using the host while LFS is being built. While waiting for package
     50compilation to complete, you can simply switch to a different VC (Virtual
     51Console) or X desktop and continue using the computer as you normally
     52would.</para>
    5053
    51 <para>When all the software from Chapter 6 is installed, the temporary tools
    52 built in Chapter 5 are removed. In Chapters 7, 8 and 9 the installation will
    53 then be finalized. The bootscripts are set up in Chapter 7, the kernel and
    54 bootloader are set up in Chapter 8, and Chapter 9 has some pointers to help
    55 you after you finish the book.  Then, finally, you're ready to reboot your
    56 computer into your new LFS system.</para>
     54<para>To finish the installation, the bootscripts are set up in
     55<xref linkend="chapter07"/>, the kernel and bootloader are set up in
     56<xref linkend="chapter08"/>, and <xref linkend="chapter09"/> contains some
     57pointers to help you after you finish the book.  Then, finally, you're ready to
     58reboot your computer into your new LFS system.</para>
    5759
    5860<para>This is the process in a nutshell. Detailed information on the steps you
    … …  
    6163everything will fall into place soon.</para>
    6264
    63 <para>Please read Chapter 2 carefully as it explains a few important things you
    64 should be aware of before you begin to work through Chapters 5 and
    65 beyond.</para>
     65<para>Please read <xref linkend="chapter02"/> carefully as it explains a few
     66important things you should be aware of before you begin to work through
     67<xref linkend="chapter05"/> and beyond.</para>
    6668
    6769</sect1>
Note: See TracChangeset for help on using the changeset viewer.