gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-03-06 06:14:47 +00:00
Code Issues Packages Projects Releases Wiki Activity

Updated the changelog.

Browse Source 
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2041 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Timothy Bauscher 2002-07-29 19:09:14 +00:00
parent 9be68e94b2
commit 415157ef41
2 changed files with 26 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
chapter01/changelog.xml
View File

@ -13,7 +13,7 @@
<listitem><para>binutils-2.12.1</para></listitem>
<listitem><para>bison-1.35</para></listitem>
<listitem><para>diffutils-2.8.1</para></listitem>
<listitem><para>file-3.38</para></listitem>
<listitem><para>file-3.39</para></listitem>
<listitem><para>gawk-3.1.1</para></listitem>
<listitem><para>gcc-3.1</para></listitem>
<listitem><para>gettext-0.11.2</para></listitem>
@ -23,7 +23,7 @@
<listitem><para>ncurses-5.2-2.patch</para></listitem>
<listitem><para>psmisc-21</para></listitem>
<listitem><para>texinfo-4.2</para></listitem>
<listitem><para>util-linux-2.11r</para></listitem>
<listitem><para>util-linux-2.11t</para></listitem>
</itemizedlist>
</para></listitem>
@ -46,6 +46,16 @@
</itemizedlist>
</para></listitem>
<listitem><para>July 29th, 2002 [timothy]: Removed Reiserfsprogs.
Updated to util-linux-2.11t and file-3.39. Chapter 04 &amp; 05 - Creating a
new partition, Introduction, Why static: grammatic changes. Diffutils,
Fileutils, Grep, Texinfo: set LDFLAGS=-static before configure instead
of as an argument to make. GCC: appended HAVE_GAS_HIDDEN to auto-host.h.
Chapter 06 - Glibc: added --disable-profile flag. Chapter 08 - Linux:
added information about modules and kernel documentaiton. Chapter 09 -
Rebooting the system: added a command to remove the static
directory.</para></listitem>
<listitem><para>July 8th, 2002 [timothy]: Chapter 09 - Rebooting the
system: Pointed to BLFS as the next step.</para></listitem>

29
chapter05/whystatic.xml
View File

@ -19,18 +19,17 @@ has.</para>
can often be around 2.5 MB), so you may not want a separate copy of each
library attached to the program. Just imagine if you had a simple command
like ls with an extra 2.5 MB attached to it! Instead of making the library
an actual part of the program, or statically linked, the library is stored as a
separate file, which is loaded only when the program needs it. This is what
we call dynamically linked, as the library is loaded and unloaded dynamically,
as the program needs it.</para>
an actual part of the program, or statically linked, the library is stored
as a separate file, which is loaded only when the program needs it. This
is what 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
<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.
<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
<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, 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>
@ -42,8 +41,8 @@ available because they are somewhere else in your old directory tree
(<filename>/usr/lib</filename> for example) which won't be accessible
from within your LFS root (<filename>$LFS</filename>).</para>
<para>So in order for your new programs to run inside the chroot environment you
need to make sure that the libraries are statically linked when you build
<para>So in order for your new programs to run inside the chroot environment
you 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
@ -57,7 +56,7 @@ so that we can take advantage of the space saving opportunities.</para>
without them, you'll see very quickly what
happens when you chroot into your newly crippled LFS system.</para>
<para>If you want to know more about Dynamically Linked Libraries, consult a
book or website on programming, especially a Linux-related site.</para>
<para>If you want to know more about Dynamically Linked Libraries, consult
a book or website on programming, especially a Linux-related site.</para>
</sect1>