|
@@ -34,8 +34,8 @@ 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 位系统所需的空间稍大一些,
|
|
<para>关于 64 位系统,我们需要说明,与 32 位系统相比,64 位系统所需的空间稍大一些,
|
|
- 对于大多数程序来说,运行速度也仅仅稍快一些,没有特别明显的优势。例如,在一块
|
|
|
|
- Core2Duo CPU 上构建 LFS-6.5 版本时,我们得到的实验数据为:</para>
|
|
|
|
|
|
+ 对于大多数程序来说,运行速度也仅仅稍快一些,没有特别明显的优势。例如,
|
|
|
|
+ 在一块 Core2Duo CPU 上构建 LFS-6.5 版本时,我们得到的实验数据为:</para>
|
|
|
|
|
|
<screen><computeroutput>架构 构建时间 系统大小
|
|
<screen><computeroutput>架构 构建时间 系统大小
|
|
32 位 198.5 minutes 648 MB
|
|
32 位 198.5 minutes 648 MB
|
|
@@ -46,17 +46,17 @@ 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
|
|
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>
|
|
|
|
|
|
+<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
|
|
builds on the same hardware. Modern 64-bit systems are considerably
|
|
faster than older 64-bit systems and the LFS authors recommend building
|
|
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-->
|
|
|
|
|
|
-<note><para>以上讨论仅适用于当时的硬件。现代的 64 位系统比以前快得多,因此 LFS 作者
|
|
|
|
- 推荐尽量使用 64 位系统构建 LFS。</para></note>
|
|
|
|
|
|
+<note><para>以上讨论仅适用于当时的硬件。现代的 64 位系统比以前快得多,
|
|
|
|
+ 因此 LFS 作者推荐尽量使用 64 位系统构建 LFS。</para></note>
|
|
|
|
|
|
<!--para>The default 64-bit build that results from LFS is considered a "pure"
|
|
<!--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
|
|
64-bit system. That is, it supports 64-bit executables only. Building a
|
|
@@ -67,12 +67,14 @@ instructions needed for a straightforward base Linux system. You can refer to
|
|
the <ulink url="http://trac.clfs.org/">Cross Linux From Scratch</ulink>
|
|
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>
|
|
|
|
|
|
+<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
|
|
<!-- 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
|
|
<para>There is one last comment about 64-bit systems. There are some older
|