Changeset c6b5ddb for chapter01/how.xml

Timestamp:

03/07/2004 12:09:31 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:

5b7293a

Parents:

4f4b4e84

Message:

Shifting chapter contents, and moving preparational sections of chapter 5 to a separate chapter.

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

File:

• chapter01/how.xml (modified) (1 diff)

chapter01/how.xml

@@ -10 +10 @@
 as one of the options when you installed your distribution.</para>
 
-<para>In <xref linkend="chapter-making-space"/> you will first create a new Linux native
+<para>In <xref linkend="chapter-making-space"/> you will first create a new
 partition and file system, the place where your new LFS system will be compiled
-and installed. Then in <xref linkend="chapter-getting-materials"/> you download all the
-packages and patches required to build an LFS system, and store them on the new
-file system.</para>
+and installed. Then in <xref linkend="chapter-getting-materials"/> you download
+all the packages and patches needed to build an LFS system, and store them on
+the new file system. In <xref linkend="chapter-preparation"/> you set up a good
+environment to work in.</para>
 
-<para><xref linkend="chapter-temporary-tools"/> then discusses the installation of a number
-of packages that will form the basic development suite (or toolchain) which is
-used to build the actual system in <xref linkend="chapter-building-system"/>. Some of these
-packages are needed to resolve circular dependencies -- for example, to compile
-a compiler you need a compiler.</para>
+<para><xref linkend="chapter-temporary-tools"/> then discusses the installation
+of a number of packages that form the basic development suite used to build the
+actual system in <xref linkend="chapter-building-system"/>.</para>
 
-<para>The first thing to be done in <xref linkend="chapter-temporary-tools"/> is build a
-first pass of the toolchain, made up of Binutils and GCC. The programs from
-these packages will be linked statically in order for them to be usable
-independently of the host system. The second thing to do is build Glibc, the
-C library. Glibc will be compiled by the toolchain programs we just built in
-the first pass. The third thing to do is build a second pass of the toolchain.
-This time the toolchain will be dynamically linked against the newly built
-Glibc. The remaining <xref linkend="chapter-temporary-tools"/> packages are all built using
-this second pass toolchain and dynamically linked against the new
-host-independent Glibc. When this is done, the LFS installation process will no
-longer depend on the host distribution, with the exception of the running
-kernel.</para>
+<para>The first thing to be done in <xref linkend="chapter-temporary-tools"/>
+is build a first pass of the <emphasis>toolchain</emphasis>, consisting of
+Binutils and GCC. The programs from these packages will be linked statically in
+order for them to be usable independently of the host system (thus making it
+in theory possible to skip the second passes). The second thing to do is build
+Glibc, the C library. Glibc will be compiled by the just-built toolchain
+programs. The third thing to do is build a second pass of the toolchain, this
+time linking it dynamically against the newly built Glibc. The remaining <xref
+linkend="chapter-temporary-tools"/> packages are all built using this second
+pass toolchain and are dynamically linked against the new host-independent
+Glibc. When this is done, the LFS installation process will no longer depend on
+the host distribution, with the exception of the running kernel.</para>
 
 <para>You may be thinking that <quote>this seems like a lot of work, just to
 get away from my host distribution</quote>. Well, a full technical explanation
-is provided at the start of <xref linkend="chapter-temporary-tools"/>, including some notes
-on the differences between statically and dynamically linked programs.</para>
+is provided at the start of <xref linkend="chapter-temporary-tools"/>,
+including some notes on the differences between statically and dynamically
+linked programs.</para>
 
-<para>In <xref linkend="chapter-building-system"/> your real LFS system will be built. The
-chroot (change root) program is used to enter a virtual environment and start
-a new shell whose root directory will be set to the LFS partition. This is very
-similar to rebooting and instructing the kernel to mount the LFS partition as
-the root partition. The reason that you don't actually reboot, but instead
-chroot, is that creating a bootable system requires additional work which isn't
-necessary just yet. But the major advantage is that chrooting allows you to
-continue using the host while LFS is being built. While waiting for package
-compilation to complete, you can simply switch to a different VC (Virtual
-Console) or X desktop and continue using the computer as you normally
-would.</para>
+<para>In <xref linkend="chapter-building-system"/> your real LFS system will be
+built. The <command>chroot</command> (change root) program is used to enter a
+virtual environment and start a new shell whose root directory will be set to
+the LFS partition. This is very similar to rebooting and instructing the kernel
+to mount the LFS partition as the root partition. The reason that you don't
+actually reboot, but instead chroot, is that creating a bootable system
+requires additional work which isn't necessary just yet. But the major
+advantage is that chrooting allows you to continue using the host while LFS is
+being built. While waiting for package compilation to complete, you can simply
+switch to a different VC (Virtual Console) or X desktop and continue using the
+computer as you normally would.</para>
 
 <para>To finish the installation, the bootscripts are set up in
 <xref linkend="chapter-bootscripts"/>, the kernel and bootloader are set up in
-<xref linkend="chapter-mixture"/>, and <xref linkend="chapter-finalizing"/> contains some
-pointers to help you after you finish the book. Then, finally, you're ready to
-reboot your computer into your new LFS system.</para>
+<xref linkend="chapter-mixture"/>, and <xref linkend="chapter-finalizing"/>
+contains some pointers to help you after you finish the book. Then, finally,
+you're ready to reboot your computer into your new LFS system.</para>
 
-<para>This is the process in a nutshell. Detailed information on the steps you 
-will take are discussed in the chapters and package descriptions as you 
-progress through them. If something isn't completely clear now, don't worry, 
-everything will fall into place soon.</para>
-
-<para>Please read <xref linkend="chapter-preparation"/> carefully as it explains a few
-important things you should be aware of before you begin to work through
-<xref linkend="chapter-temporary-tools"/> and beyond.</para>
+<para>This is the process in a nutshell. Detailed information on all the steps
+taken is given in the chapters and sections as you progress through them. If
+something isn't completely clear now, don't worry, everything will fall into
+place soon.</para>
 
 </sect1>
-