[673b0d8] | 1 | <?xml version="1.0" encoding="ISO-8859-1"?>
|
---|
[1770019] | 2 | <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
|
---|
[673b0d8] | 3 | <!ENTITY % general-entities SYSTEM "../general.ent">
|
---|
| 4 | %general-entities;
|
---|
| 5 | ]>
|
---|
| 6 | <sect1 id="ch-system-introduction">
|
---|
| 7 | <title>Introduction</title>
|
---|
| 8 | <?dbhtml filename="introduction.html"?>
|
---|
| 9 |
|
---|
[81fd230] | 10 | <para>In this chapter, we enter the building site and start
|
---|
| 11 | constructing the LFS system in earnest. That is, we chroot into the
|
---|
| 12 | temporary mini Linux system, make a few final preparations, and then
|
---|
| 13 | begin installing the packages.</para>
|
---|
| 14 |
|
---|
| 15 | <para>The installation of this software is straightforward. Although
|
---|
| 16 | in many cases the installation instructions could be made shorter and
|
---|
| 17 | more generic, we have opted to provide the full instructions for every
|
---|
| 18 | package to minimize the possibilities for mistakes. The key to
|
---|
| 19 | learning what makes a Linux system work is to know what each package
|
---|
| 20 | is used for and why the user (or the system) needs it. For every
|
---|
| 21 | installed package, a summary of its contents is given, followed by
|
---|
| 22 | concise descriptions of each program and library the package
|
---|
| 23 | installed.</para>
|
---|
| 24 |
|
---|
| 25 | <para>If using the compiler optimizations provided in this chapter,
|
---|
| 26 | please review the optimization hint at <ulink
|
---|
| 27 | url="&hints-root;optimization.txt"/>. Compiler optimizations can make
|
---|
| 28 | a program run slightly faster, but they may also cause compilation
|
---|
| 29 | difficulties and problems when running the program. If a package
|
---|
| 30 | refuses to compile when using optimization, try to compile it without
|
---|
| 31 | optimization and see if that fixes the problem. Even if the package
|
---|
| 32 | does compile when using optimization, there is the risk it may have
|
---|
| 33 | been compiled incorrectly because of the complex interactions between
|
---|
| 34 | the code and build tools. The small potential gains achieved in using
|
---|
| 35 | compiler optimizations are often outweighed by the risks. First-time
|
---|
| 36 | builders of LFS are encouraged to build without custom optimizations.
|
---|
| 37 | The subsequent system will still run very fast and be stable at the
|
---|
| 38 | same time.</para>
|
---|
| 39 |
|
---|
| 40 | <para>The order that packages are installed in this chapter needs to
|
---|
| 41 | be strictly followed to ensure that no program accidentally acquires a
|
---|
| 42 | path referring to <filename class="directory">/tools</filename>
|
---|
| 43 | hard-wired into it. For the same reason, do not compile packages in
|
---|
| 44 | parallel. Compiling in parallel may save time (especially on dual-CPU
|
---|
| 45 | machines), but it could result in a program containing a hard-wired
|
---|
| 46 | path to <filename class="directory">/tools</filename>, which will
|
---|
| 47 | cause the program to stop working when that directory is
|
---|
| 48 | removed.</para>
|
---|
| 49 |
|
---|
| 50 | <para>Before the installation instructions, each installation page
|
---|
| 51 | provides information about the package, including a concise
|
---|
| 52 | description of what it contains, approximately how long it will take
|
---|
| 53 | to build, how much disk space is required during this building
|
---|
| 54 | process, and any other packages needed to successfully build the
|
---|
| 55 | package. Following the installation instructions, there is a list of
|
---|
| 56 | programs and libraries (along with brief descriptions of these) that
|
---|
| 57 | the package installs.</para>
|
---|
| 58 |
|
---|
| 59 | <para>To keep track of which package installs particular files, a package
|
---|
| 60 | manager can be used. For a general overview of different styles of package
|
---|
| 61 | managers, please refer to <ulink
|
---|
[f3a70cd] | 62 | url="&blfs-root;view/svn/introduction/important.html"><phrase
|
---|
| 63 | condition="pdf">&blfs-root;view/svn/ introduction/important.html</phrase></ulink>.
|
---|
[81fd230] | 64 | For a package management method specifically geared towards LFS, we recommend <ulink
|
---|
| 65 | url="&hints-root;more_control_and_pkg_man.txt"/>.</para>
|
---|
| 66 |
|
---|
[5707154] | 67 | <note><para>The remainder of this book is to be performed while logged in as
|
---|
| 68 | user <emphasis>root</emphasis> and no longer as user <emphasis>lfs</emphasis>.
|
---|
| 69 | Also, double check that <envar>$LFS</envar> is set.</para></note>
|
---|
[673b0d8] | 70 |
|
---|
| 71 | </sect1>
|
---|
[81fd230] | 72 |
|
---|