1 | <?xml version="1.0" encoding="ISO-8859-1"?>
|
---|
2 | <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
|
---|
3 | "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
|
---|
4 | <!ENTITY % general-entities SYSTEM "../../general.ent">
|
---|
5 | %general-entities;
|
---|
6 | ]>
|
---|
7 |
|
---|
8 | <sect1 id="conventions">
|
---|
9 | <?dbhtml filename="conventions.html"?>
|
---|
10 |
|
---|
11 | <sect1info>
|
---|
12 | <othername>$LastChangedBy$</othername>
|
---|
13 | <date>$Date$</date>
|
---|
14 | </sect1info>
|
---|
15 |
|
---|
16 | <title>Conventions Used in this Book</title>
|
---|
17 |
|
---|
18 | <sect2>
|
---|
19 | <title>Typographical Conventions</title>
|
---|
20 | <para>To make things easy to follow, there are a number of conventions used
|
---|
21 | throughout the book. Following are some examples:</para>
|
---|
22 |
|
---|
23 | <screen><userinput>./configure --prefix=/usr</userinput></screen>
|
---|
24 |
|
---|
25 | <blockquote>
|
---|
26 | <para>This form of text is designed to be typed exactly as seen unless
|
---|
27 | otherwise noted in the surrounding text. It is also used to identify
|
---|
28 | references to specific commands.</para>
|
---|
29 | </blockquote>
|
---|
30 |
|
---|
31 | <screen><computeroutput>install-info: unknown option
|
---|
32 | `--dir-file=/mnt/lfs/usr/info/dir'</computeroutput></screen>
|
---|
33 |
|
---|
34 | <blockquote>
|
---|
35 | <para>This form of text (fixed width text) is showing screen
|
---|
36 | output, probably a result from issuing a command. It is also used to
|
---|
37 | show filenames such as <filename>/boot/grub/grub.conf</filename></para>
|
---|
38 | </blockquote>
|
---|
39 |
|
---|
40 | <para><emphasis>Emphasis</emphasis></para>
|
---|
41 |
|
---|
42 | <blockquote>
|
---|
43 | <para>This form of text is used for several purposes in the
|
---|
44 | book but mainly to emphasize important points or to give examples as to
|
---|
45 | what to type.</para>
|
---|
46 | </blockquote>
|
---|
47 |
|
---|
48 | <para><ulink url="http://www.&lfs-domainname;/"/></para>
|
---|
49 |
|
---|
50 | <blockquote>
|
---|
51 | <para>This form of text is used for hypertext links external to
|
---|
52 | the book such as HowTos, download locations, websites, etc.</para>
|
---|
53 | </blockquote>
|
---|
54 |
|
---|
55 | <para><xref linkend="seamonkey"/></para>
|
---|
56 |
|
---|
57 | <blockquote>
|
---|
58 | <para>This form of text is used for links internal to
|
---|
59 | the book such as another section describing a different package.</para>
|
---|
60 | </blockquote>
|
---|
61 |
|
---|
62 | <screen><userinput>cat > $LFS/etc/group << "EOF"
|
---|
63 | <literal>root:x:0:
|
---|
64 | bin:x:1:
|
---|
65 | ......</literal>
|
---|
66 | EOF</userinput></screen>
|
---|
67 |
|
---|
68 | <blockquote>
|
---|
69 | <para>This type of section is used mainly when creating configuration
|
---|
70 | files. The first command (in bold) tells the system to create
|
---|
71 | the file <filename>$LFS/etc/group</filename> from whatever is typed on the
|
---|
72 | following lines until the sequence EOF is encountered.
|
---|
73 | Therefore, this whole section is generally typed as seen.</para>
|
---|
74 | </blockquote>
|
---|
75 |
|
---|
76 | <para><replaceable><REPLACED TEXT></replaceable></para>
|
---|
77 |
|
---|
78 | <blockquote>
|
---|
79 | <para>This form of text is used to encapsulate text that should be
|
---|
80 | modified and is not to be typed as seen, or copy and pasted. Note that
|
---|
81 | the square brackets are not part of the text, but should be substituted
|
---|
82 | for as well.</para>
|
---|
83 | </blockquote>
|
---|
84 |
|
---|
85 | <para><systemitem class='username'>root</systemitem></para>
|
---|
86 |
|
---|
87 | <blockquote>
|
---|
88 | <para>This form of text is used to show a specific system user or group
|
---|
89 | reference in the instructions.</para>
|
---|
90 | </blockquote>
|
---|
91 |
|
---|
92 | </sect2>
|
---|
93 |
|
---|
94 | <sect2>
|
---|
95 | <title>Conventions Used for Package Dependencies</title>
|
---|
96 |
|
---|
97 | <para>When packages are created, the authors depend on prior work. In
|
---|
98 | order to build a package in BLFS, these dependencies must be built prior to
|
---|
99 | the desired package. For each package, any prerequsite packages are listed
|
---|
100 | in one or more separate sections: Required, Recommended, and Optional.</para>
|
---|
101 |
|
---|
102 | <bridgehead renderas="sect3">Required Dependencies</bridgehead>
|
---|
103 |
|
---|
104 | <para>These dependencies are the minimum prerequsite packages required to
|
---|
105 | build the package. Omitted from the list are packages in LFS and required
|
---|
106 | dependencies of other required packages.</para>
|
---|
107 |
|
---|
108 | <bridgehead renderas="sect3">Recommended Dependencies</bridgehead>
|
---|
109 |
|
---|
110 | <para>These dependencies are those that the BLFS editors have determined
|
---|
111 | are important to give the package reasonable capabilities. Package
|
---|
112 | installation instructions assume thay are installed. If a recommended
|
---|
113 | package is not desired, the instructions may need to be modified to
|
---|
114 | accommodate the missing package.</para>
|
---|
115 |
|
---|
116 | <bridgehead renderas="sect3">Optional Dependencies</bridgehead>
|
---|
117 |
|
---|
118 | <para>These dependencies are those that the package may use. Integration
|
---|
119 | of optional dependencies may be automatic by the package or may need
|
---|
120 | additional instructions not presented by BLFS. Optional packages may be
|
---|
121 | listed without corresponding BLFS instructions. In this case it is up to
|
---|
122 | the user to determine appropriate installation instructions. </para>
|
---|
123 |
|
---|
124 | </sect2>
|
---|
125 |
|
---|
126 | <sect2>
|
---|
127 | <title>SBU values in BLFS</title>
|
---|
128 |
|
---|
129 | <para>As in LFS, each package in BLFS has a build time listed in Standard
|
---|
130 | Build Units (SBUs). These times are relative to the time it took to build
|
---|
131 | binutils in LFS and are intended to provide some insight into how long it
|
---|
132 | will take to build a package. Most times listed are for a single processor
|
---|
133 | or core to build the package. In some cases, large, long running builds
|
---|
134 | tested on multi-core systems have SBU times listed with comments such
|
---|
135 | as '(parallelism=4)'. These values indicate testing was done using
|
---|
136 | multiple cores. Note that while this speeds up the build on systems with
|
---|
137 | the appropriate hardware, the speedup is not linear and to some extent
|
---|
138 | depends on the individual package and specific hardware used. </para>
|
---|
139 |
|
---|
140 | <para>Some packages do not support parallel builds and using -j1 for the
|
---|
141 | make command is required. Packages that are known to have such limits are
|
---|
142 | marked as such in the text.</para>
|
---|
143 |
|
---|
144 | </sect2>
|
---|
145 |
|
---|
146 | </sect1>
|
---|