Small text rearrangement in Chapter 1 - how.xml.

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2857 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Greg Schafer 2003-09-21 08:03:23 +00:00
parent 39dbad2e34
commit 638a39cb6a

View File

@ -41,8 +41,8 @@ of Chapter 5.</para>
<para>You may be asking yourself <quote>that seems like a lot of work, just to
get away from my host distribution</quote>. Let us take a few minutes to
discuss this question. The work involved in building the packages in Chapter 5
is to ensure that as little information from your host makes it into your
brand new LFS system. When you build the first two packages in Chapter 5,
is to ensure that as little information as possible from your host makes it into
your brand new LFS system. When you build the first two packages in Chapter 5,
Binutils and GCC, they will be compiled statically. This means that the
version of the C library on your host distribution will be embedded inside all
the binary programs you just compiled. This has the potential to cause
@ -61,11 +61,11 @@ 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. As well,
chrooting allows you to continue using the host while LFS is being built.
While software is being installed you can simply switch to a different VC
(Virtual Console) or X desktop and continue using the computer as you normally
would.</para>
a bootable system requires additional work which isn't necessary just yet.
Another 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>When all the software from Chapter 6 is installed, the temporary tools
built in Chapter 5 will be removed. Chapters 7, 8 and 9 will finalize the