Changeset dc37bc5

Timestamp:

09/02/2003 09:59:26 PM (21 years ago)

Author:

Alex Gronenwoud <alex@…>

Branches:

10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.0, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, v5_0, v5_1, v5_1_1, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc

Children:

38cd1e0

Parents:

7fcbee1

Message:

Rewording the SBUs section.

git-svn-id: ​http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2719 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

File:

• chapter02/aboutsbus.xml (modified) (1 diff)

chapter02/aboutsbus.xml

@@ -3 +3 @@
 <?dbhtml filename="aboutsbus.html" dir="chapter02"?>
 
-<para>SBUs are <emphasis>Static Bash Units</emphasis> and they are our way
-of identifying how long a package takes to compile. Why don't we use normal
-times like anybody else?</para>
+<para>Most people would like to know beforehand how long it approximately
+takes to compile and install each package. But "Linux from Scratch" is built
+on so many different systems, it is not possible to give actual times that are
+anywhere near accurate: the biggest package (Glibc) won't take more than
+twenty minutes on the fastest systems, but will take something like three days
+on the slowest -- no kidding. So instead of giving actual times, we've come up
+with the idea of using the <emphasis>Static Binutils Unit</emphasis>
+(abbreviated to <emphasis>SBU</emphasis>).</para>
 
-<para>The biggest problem is that times cannot be accurate, not even a
-little bit. So many people install LFS on so many different systems, the
-times it takes to compile something varies too much. One package may take
-20 minutes on one system, but that same package may take 3 days on another
-(this is not an exaggeration). So instead we've come up with a
-<emphasis>Static Bash Unit</emphasis> or <emphasis>SBU</emphasis>.</para>
+<para>It works like this: the first package you compile in this book is the
+statically linked Binutils in Chapter 5, and the time it takes to compile this
+package is what we call the "Static Binutils Unit" or "SBU". All other compile
+times will be expressed relative to this time.</para>
 
-<para>It works like this: the very first package you compile in this book
-is Bash in Chapter 5 and it'll be statically linked. The time it takes to
-compile this package will be the basis and called the SBU. All other
-compile times are relative to the time it takes to install Bash. For
-example, GCC-3.2 takes about 9.5 SBUs and it's proven that this number is
-fairly consistent among a lot of different systems. So multiply 9.5 by the
-number of seconds it takes for Bash to install (the SBU value) and you get
-a close approximation of how long GCC will take on your system.</para>
+<para>For example, the time it takes to build the static version of GCC is 3.9
+SBU. This means that if on your system it took 10 minutes to compile and
+install the static Binutils, then you know it will take nearly 40 minutes to
+build the static GCC. Fortunately, most build times are much shorter than the
+one of Binutils.</para>
 
-<para>Note: We've seen that SBUs don't work well on SMP based machines. So
-all bets are off if you're lucky enough to have an SMP setup.</para>
+<para>Note that SBUs don't work well for SMP-based machines. But if you're so
+lucky as to have multiple processors, chances are that your system is so fast
+that you don't mind.</para>
 
 </sect1>