Changeset 81fd230 for chapter06/introduction.xml

Timestamp:

02/19/2005 10:16:42 PM (19 years ago)

Author:

Gerard Beekmans <gerard@…>

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.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, 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:

3d31fc4

Parents:

2f9131f

Message:

Trunk is now identical to Testing

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

File:

• chapter06/introduction.xml (modified) (1 diff)

chapter06/introduction.xml

@@ -8 +8 @@
 <?dbhtml filename="introduction.html"?>
 
-<para>See testing</para>
+<para>In this chapter, we enter the building site and start
+constructing the LFS system in earnest. That is, we chroot into the
+temporary mini Linux system, make a few final preparations, and then
+begin installing the packages.</para>
+
+<para>The installation of this software is straightforward. Although
+in many cases the installation instructions could be made shorter and
+more generic, we have opted to provide the full instructions for every
+package to minimize the possibilities for mistakes.  The key to
+learning what makes a Linux system work is to know what each package
+is used for and why the user (or the system) needs it.  For every
+installed package, a summary of its contents is given, followed by
+concise descriptions of each program and library the package
+installed.</para>
+
+<para>If using the compiler optimizations provided in this chapter,
+please review the optimization hint at <ulink
+url="&hints-root;optimization.txt"/>.  Compiler optimizations can make
+a program run slightly faster, but they may also cause compilation
+difficulties and problems when running the program. If a package
+refuses to compile when using optimization, try to compile it without
+optimization and see if that fixes the problem. Even if the package
+does compile when using optimization, there is the risk it may have
+been compiled incorrectly because of the complex interactions between
+the code and build tools.  The small potential gains achieved in using
+compiler optimizations are often outweighed by the risks. First-time
+builders of LFS are encouraged to build without custom optimizations.
+The subsequent system will still run very fast and be stable at the
+same time.</para>
+
+<para>The order that packages are installed in this chapter needs to
+be strictly followed to ensure that no program accidentally acquires a
+path referring to <filename class="directory">/tools</filename>
+hard-wired into it. For the same reason, do not compile packages in
+parallel. Compiling in parallel may save time (especially on dual-CPU
+machines), but it could result in a program containing a hard-wired
+path to <filename class="directory">/tools</filename>, which will
+cause the program to stop working when that directory is
+removed.</para>
+
+<para>Before the installation instructions, each installation page
+provides information about the package, including a concise
+description of what it contains, approximately how long it will take
+to build, how much disk space is required during this building
+process, and any other packages needed to successfully build the
+package. Following the installation instructions, there is a list of
+programs and libraries (along with brief descriptions of these) that
+the package installs.</para>
+
+<para>To keep track of which package installs particular files, a package
+manager can be used. For a general overview of different styles of package
+managers, please refer to <ulink
+url="&blfs-root;view/svn/introduction/important.html"/>.
+For a package management method specifically geared towards LFS, we recommend <ulink
+url="&hints-root;more_control_and_pkg_man.txt"/>.</para>
+
+<note><para>The remainder of this book is to be performed while logged
+in as user <emphasis>root</emphasis> and no longer as user
+<emphasis>lfs</emphasis>.</para></note>
 
 </sect1>
+