|
@@ -25,12 +25,13 @@ we call dynamically linked, as the library is loaded and unloaded dynamically,
|
|
|
as the program needs it.</para>
|
|
|
|
|
|
<para>So now we have a 1 KB file and a 2.5 MB file, but we still haven't saved any
|
|
|
-space (except maybe RAM until the library is needed). The REAL advantage to
|
|
|
+space (except maybe RAM until the library is needed). The
|
|
|
+<emphasis>real</emphasis> advantage of
|
|
|
dynamically linked libraries is that we only need one copy of the library.
|
|
|
If <filename>ls</filename> and <filename>rm</filename> both use the same
|
|
|
library, then we don't need two copies of the
|
|
|
library, as they can both get the code from the same file.
|
|
|
-Even when in memory, both programs share the same code, rather than loading
|
|
|
+Even when in memory, the two programs share the same code, rather than loading
|
|
|
duplicates into memory. So not only are we saving hard disk space, but also
|
|
|
precious RAM.</para>
|
|
|
|
|
@@ -46,9 +47,9 @@ need to make sure that the libraries are statically linked when you build
|
|
|
them, hence the <userinput>--enable-static-link</userinput>,
|
|
|
<userinput>--disable-shared</userinput>, and
|
|
|
<userinput>-static</userinput> flags used
|
|
|
-through Chapter 5. Once in Chapter 6, the first thing we do is build the
|
|
|
+through chapter 5. Once in chapter 6, the first thing we do is build the
|
|
|
main set of system libraries, glibc. Once this is made we start rebuilding
|
|
|
-all the programs we just did in Chapter 5, but this time dynamically linked,
|
|
|
+all the programs we just did in chapter 5, but this time dynamically linked,
|
|
|
so that we can take advantage of the space saving opportunities.</para>
|
|
|
|
|
|
<para>And there you have it, that's why you need to use those weird
|