|
@@ -1,4 +1,4 @@
|
|
|
-<?xml version="1.0" encoding="ISO-8859-1"?>
|
|
|
+<?xml version="1.0" encoding="UTF-8"?>
|
|
|
<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
|
|
|
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
|
|
|
<!ENTITY % general-entities SYSTEM "../general.ent">
|
|
@@ -8,9 +8,9 @@
|
|
|
<sect1 id="pre-architecture">
|
|
|
<?dbhtml filename="architecture.html"?>
|
|
|
|
|
|
- <title>LFS Target Architectures</title>
|
|
|
+ <title>LFS 的目标架构</title>
|
|
|
|
|
|
-<para>The primary target architectures of LFS are the AMD/Intel x86 (32-bit)
|
|
|
+<!--para>The primary target architectures of LFS are the AMD/Intel x86 (32-bit)
|
|
|
and x86_64 (64-bit) CPUs. On the other hand, the instructions in this book are
|
|
|
also known to work, with some modifications, with the Power PC and ARM CPUs. To
|
|
|
build a system that utilizes one of these CPUs, the main prerequisite, in
|
|
@@ -18,36 +18,61 @@ addition to those on the next few pages, is an existing Linux system such as an
|
|
|
earlier LFS installation, Ubuntu, Red Hat/Fedora, SuSE, or other distribution
|
|
|
that targets the architecture that you have. Also note that a 32-bit
|
|
|
distribution can be installed and used as a host system on a 64-bit AMD/Intel
|
|
|
-computer.</para>
|
|
|
+computer.</para-->
|
|
|
|
|
|
-<para>Some other facts about 64-bit systems need to be added here. When
|
|
|
+<para>LFS 的主要目标架构是 AMD/Intel 的 x86 (32 位) 和 x86_64 (64 位) CPU 。此外,
|
|
|
+ 如果对本书中的一些指令作适当的修改,它们也应该适用于 Power PC 和 ARM 架构的
|
|
|
+ CPU。为了在一块这样的 CPU 上成功构建 LFS 系统,您首先需要一个能够在 CPU 上
|
|
|
+ 正常运行的 Linux 系统。例如,一个已经构建好的 LFS 系统,或者 Ubuntu,
|
|
|
+ Red Hat/Fedora,SuSE 等支持您的硬件架构的发行版。另外,32 位发行版也能够在
|
|
|
+ 64 位的 AMD/Intel 计算机上正常运行,并作为 LFS 的构建环境。</para>
|
|
|
+
|
|
|
+<!--para>Some other facts about 64-bit systems need to be added here. When
|
|
|
compared to a 32-bit system, the sizes of executable programs are slightly
|
|
|
larger and the execution speeds of arbitrary programs are only slightly faster.
|
|
|
For example, in a test build of LFS-6.5 on a Core2Duo CPU based system, the
|
|
|
-following statistics were measured:</para>
|
|
|
+following statistics were measured:</para-->
|
|
|
+
|
|
|
+<para>关于 64 位系统,我们需要说明,与 32 位系统相比,64 位系统所需的空间稍大一些,
|
|
|
+ 对于大多数程序来说,运行速度也仅仅稍快一些,没有特别明显的优势。例如,在一块
|
|
|
+ Core2Duo CPU 上构建 LFS-6.5 版本时,我们得到的实验数据为:</para>
|
|
|
|
|
|
-<screen><computeroutput>Architecture Build Time Build Size
|
|
|
-32-bit 198.5 minutes 648 MB
|
|
|
-64-bit 190.6 minutes 709 MB</computeroutput></screen>
|
|
|
+<screen><computeroutput>架构 构建时间 系统大小
|
|
|
+32 位 198.5 minutes 648 MB
|
|
|
+64 位 190.6 minutes 709 MB</computeroutput></screen>
|
|
|
|
|
|
-<para>As you can see, the 64-bit build is only 4% faster and is 9% larger than
|
|
|
+<!--para>As you can see, the 64-bit build is only 4% faster and is 9% larger than
|
|
|
the 32-bit build. The gain from going to a 64-bit system is relatively
|
|
|
minimal. Of course, if you have more than 4GB of RAM or want to manipulate
|
|
|
-data that exceeds 4GB, the advantages of a 64-bit system are substantial.</para>
|
|
|
+data that exceeds 4GB, the advantages of a 64-bit system are substantial.</para-->
|
|
|
+
|
|
|
+<para>可以看出,64 位系统仅仅比 32 位系统快 4% ,体积则大了 9% 。因此,并不需要
|
|
|
+ 特意追求 64 位系统。然而如果您拥有超过 4GB 的内存,或需要操作大于 4GB 的数据,
|
|
|
+ 64 位系统的优势就相当关键了。 </para>
|
|
|
|
|
|
-<note><para>The above discussion is only appropriate when comparing
|
|
|
+<!--note><para>The above discussion is only appropriate when comparing
|
|
|
builds on the same hardware. Modern 64-bit systems are considerably
|
|
|
faster than older 64-bit systems and the LFS authors recommend building
|
|
|
-on a 64-bit system when given a choice.</para></note>
|
|
|
+on a 64-bit system when given a choice.</para></note-->
|
|
|
|
|
|
-<para>The default 64-bit build that results from LFS is considered a "pure"
|
|
|
+<note><para>以上讨论仅适用于当时的硬件。现代的 64 位系统比以前快得多,因此 LFS 作者
|
|
|
+ 推荐尽量使用 64 位系统构建 LFS。</para></note>
|
|
|
+
|
|
|
+<!--para>The default 64-bit build that results from LFS is considered a "pure"
|
|
|
64-bit system. That is, it supports 64-bit executables only. Building a
|
|
|
"multi-lib" system requires compiling many applications twice, once for a
|
|
|
32-bit system and once for a 64-bit system. This is not directly supported in
|
|
|
LFS because it would interfere with the educational objective of providing the
|
|
|
instructions needed for a straightforward base Linux system. You can refer to
|
|
|
the <ulink url="http://trac.clfs.org/">Cross Linux From Scratch</ulink>
|
|
|
-project for this advanced topic.</para>
|
|
|
+project for this advanced topic.</para-->
|
|
|
+
|
|
|
+<para>完全按照本书构建的 LFS 系统是一个<quote>纯粹的</quote>64 位系统。换句话说,
|
|
|
+ 它只能运行 64 位可执行程序。构建一个<quote>multi-lib</quote> 系统需要将许多程序
|
|
|
+ 编译两次,一次编译为 32 位,另一次编译为 64 位。本书不涉及这方面的内容,因为
|
|
|
+ 它与本书提供一个最基本的 Linux 系统的教育目标相冲突。您可以参考
|
|
|
+ <ulink url="http://trac.clfs.org/">Cross Linux From Scratch</ulink> 项目获得
|
|
|
+ 关于这个高级话题的更多信息。</para>
|
|
|
|
|
|
<!-- This does not appear to be valid for LFS/BLFS any more
|
|
|
<para>There is one last comment about 64-bit systems. There are some older
|