source: BOOK/final-system/common/introduction.xml@ f6c354f

clfs-1.2 clfs-2.1 clfs-3.0.0-systemd clfs-3.0.0-sysvinit systemd sysvinit
Last change on this file since f6c354f was 3f8be484, checked in by Jim Gifford <clfs@…>, 19 years ago

r627@server (orig r625): jim | 2005-10-31 12:59:34 -0800
Import of Cross-LFS Book

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