Subversion Repositories svn LFS-FR

Compare Revisions

Ignore whitespace Rev 4 → Rev 5

/tags/cvs/lfs/chapter01/subscribe.xml
0,0 → 1,28
<sect2>
<title>Comment s'abonner ?</title>
 
<para>Il est possible de s'abonner à chacune des listes de diffusion indiquées ci-dessus en envoyant
un email à <ulink url="mailto:listar@linuxfromscratch.org">listar@linuxfromscratch.org</ulink>
et en tapant <emphasis>subscribe nom-de-la-liste</emphasis> dans le champ Objet de
l'entête du message.</para>
 
<para>Il est possible de s'abonner à plusieurs listes à la fois
en un seul email. Ceci peut être fait en laissant le champ Objet vide et en
mettant toutes les commandes dans le corps de l'email. Cet email peut ressembler
à :</para>
 
<blockquote><literallayout>To: listar@linuxfromscratch.org
Subject:
 
subscribe lfs-dev
subscribe blfs-support
subscribe alfs-discuss</literallayout></blockquote>
 
<para>Après que l'email ait été envoyé, le programme Listar répondra avec un
email de demande de confirmation d'abonnement.
Après que cette confirmation ait été renvoyée, Listar
retournera un autre email avec un message indiquant l'abonnement de l'utilisateur
à la/les liste(s) ainsi qu'un message d'introduction pour chacune d'entre elles.</para>
 
</sect2>
 
/tags/cvs/lfs/chapter01/lfssupport.xml
0,0 → 1,10
<sect2>
<title>lfs-support</title>
 
<para>La liste de diffusion "lfs-support" apporte un support aux utilisateurs construisant
un système LFS jusqu'à la fin du livre principal. Les demandes d'aides pour
installer un programme au-delà de ce point doivent être adressées à la liste "blfs-support".
</para>
 
</sect2>
 
/tags/cvs/lfs/chapter01/lfsdev.xml
0,0 → 1,12
<sect2>
<title>lfs-dev</title>
 
<para>La liste de diffusion "lfs-dev" traitent uniquement des sujets à propos
du livre LFS. Si le livre laisse apparaître des problèmes, qu'un bogue ou deux doivent être
rapportés, ou que des suggestions quant à l'amélioration du livre
doivent être faites, cette liste de diffusion est la bonne.</para>
 
<para>Les demandes d'aides doivent être adressées à "lfs-support" ou à "blfs-support".</para>
 
</sect2>
 
/tags/cvs/lfs/chapter01/blfssupport.xml
0,0 → 1,9
<sect2>
<title>blfs-support</title>
 
<para>La liste de diffusion blfs-support gère les demandes de support pour tous logiciels
installés mais non compris dans LFS. Cette liste n'est pas disponible pour vous aider
uniquement sur les logiciels indiqués dans BLFS mais pour tous logiciels.</para>
 
</sect2>
 
/tags/cvs/lfs/chapter01/alfsdiscuss.xml
0,0 → 1,12
<sect2>
<title>alfs-discuss</title>
 
<para>La liste de diffusion alfs-discuss traite du développement de ALFS, qui
signifie 'Automated Linux From Scratch'. Le but de ce projet est de développer un
outil d'installation qui permettrait d'installer de façon automatique un système LFS.
Le principal objectif est d'accélérer la compilation en se dégageant de l'obligation
d'entrer manuellement les commandes de configuration, de compilation et d'installation
des packages.</para>
 
</sect2>
 
/tags/cvs/lfs/chapter01/unsubscribe.xml
0,0 → 1,27
<sect2>
<title>Comment se désabonner</title>
 
<para>Pour se désabonner d'une liste, envoyer un email à
<ulink url="mailto:listar@linuxfromscratch.org">listar@linuxfromscratch.org</ulink>
et taper <emphasis>unsubscribe
nom-de-la-liste</emphasis> dans le champ Objet de l'entête du message.</para>
 
<para>Il est possible de se désabonner de plusieurs listes à la fois
en un seul email. Ceci peut être fait en laissant le champ Objet vide et en
mettant toutes les commandes dans le corps de l'email. Cet email peut ressembler
à : </para>
 
<blockquote><literallayout>To: listar@linuxfromscratch.org
Subject:
 
unsubscribe lfs-dev
unsubscribe blfs-support
unsubscribe alfs-discuss</literallayout></blockquote>
 
<para>Après que l'email ait été envoyé, le programme Listar répondra avec un
email de demande de confirmation de désabonnement.
Après que cette confirmation ait été renvoyée, Listar
retournera un autre email avec un message indiquant le désabonnement de l'utilisateur de(s) liste(s).</para>
 
</sect2>
 
/tags/cvs/lfs/chapter01/mailarchive.xml
0,0 → 1,11
<sect2>
<title>Archives des listes de diffusion</title>
 
<para>Toutes ces listes de diffusion sont archivées et peuvent être consultées en ligne à l'adresse
<ulink url="http://archive.linuxfromscratch.org/mail-archives">http://archive.linuxfromscratch.org/mail-archives</ulink> ou téléchargées
depuis <ulink url="&http-root;/mail-archives">&http-root;/mail-archives</ulink>
ou
<ulink url="&ftp-root;/mail-archives">&ftp-root;/mail-archives</ulink>.</para>
 
</sect2>
 
/tags/cvs/lfs/chapter01/blfsdev.xml
0,0 → 1,13
<sect2>
<title>blfs-dev</title>
 
<para>La liste de diffusion blfs-dev s'occupe des problèmes liés au livre BLFS
(Beyond LFS, c'est-à-dire après LFS). Si des problèmes surviennent avec ce livre, que ce
soient des bugs ou suggestions pour améliorer ce livre, cette liste de diffusion est là
pour ça.</para>
 
<para>Toutes demandes d'aide concernant l'installation ou la configuration de programmes
non inclus dans LFS doivent être postées sur la liste de diffusion blfs-support.</para>
 
</sect2>
 
/tags/cvs/lfs/chapter01/acknowledgments.xml
0,0 → 1,104
<sect1 id="ch01-acknowledgments">
<title>Acknowledgments</title>
<?dbhtml filename="acknowledgements.html" dir="chapter01"?>
 
<para>We would like to thank the following people and organizations for their
contributions toward the Linux From Scratch project:</para>
 
<itemizedlist>
 
<listitem><para><ulink url="mailto:strider@linux.com">Mark Stone</ulink>
&lt;mstone@linux.com&gt; for donating the linuxfromscratch.org
server.</para></listitem>
<listitem><para><ulink url="http://www.valinux.com">VA Linux
Systems</ulink> for providing rackspace and bandwidth for the
linuxfromscratch.org server.</para></listitem>
 
<listitem><para><ulink url="mailto:markh@linuxfromscratch.org">Mark
Hymers</ulink> &lt;markh@linuxfromscratch.org&gt; for being more than a
great help in editing this book.</para></listitem>
 
<listitem><para><ulink url="mailto:marc_heerdink@softhome.net">Marc
Heerdink</ulink> &lt;marc_heerdink@softhome.net&gt; for also being a great
help in editing this book.</para></listitem>
 
<listitem><para><ulink url="http://www.dreamwvr.com/services">DREAMWVR.COM</ulink> for their ongoing sponsorship by donating various resources to the LFS and
related sub projects.</para></listitem>
 
<listitem><para><ulink url="mailto:highos@linuxfromscratch.org">Jesse
Tie-Ten-Quee</ulink> &lt;highos@linuxfromscratch.org&gt; for running the
www.ca.linuxfromscratch.org mirror.</para></listitem>
 
<listitem><para><ulink url="mailto:jan.niemann@tu.bs.de">Jan
Niemann</ulink> &lt;jan.niemann@tu.bs.de&gt; for running the
www.de.linuxfromscratch.org mirror.</para></listitem>
 
<listitem><para><ulink url="mailto:westermann@linux-provider.net">Torsten
Westermann</ulink> &lt;westermann@linux-provider.net&gt; for running the
lfs.linux-provider.net mirror.</para></listitem>
 
<listitem><para><ulink url="mailto:ian@ichilton.co.uk">Ian
Chilton</ulink> &lt;ian@ichilton.co.uk&gt; for running the
www.us.linuxfromscratch.org and www.linuxfromscratch.co.uk
mirrors.</para></listitem>
 
<listitem><para><ulink url="mailto:dag@stenstad.net">Dag
Stenstad</ulink> &lt;dag@stenstad.net&gt; for providing the
www.no.linuxfromscratch.org mirror, and
<ulink url="mailto:ian@ichilton.co.uk">Ian Chilton</ulink>
&lt;ian@ichilton.co.uk&gt; for running it.</para></listitem>
 
<listitem><para><ulink url="mailto:Antonin.Sprinzl@tuwien.ac.at">Antonin
Sprinzl</ulink> &lt;Antonin.Sprinzl@tuwien.ac.at&gt; for running the
www.at.linuxfromscratch.org mirror.</para></listitem>
 
<listitem><para><ulink url="mailto:jason@dstc.edu.au">Jason
Andrade</ulink> &lt;jason@dstc.edu.au&gt; for running the
www.au.linuxfromscratch.org mirror.</para></listitem>
 
<listitem><para><ulink url="mailto:ian@wpi.edu">Ian
Cooper</ulink> &lt;ian@wpi.edu&gt; for running the
www.us2.linuxfromscratch.org mirror.</para></listitem>
 
<listitem><para><ulink url="http://www.valinux.com">VA Linux
Systems</ulink> who,
on behalf of <ulink url="http://www.linux.com">Linux.com</ulink>, donated
a VA Linux 420 (former StartX SP2) workstation
towards this project.</para></listitem>
 
<listitem><para><ulink url="mailto:johan@linuxfromscratch.org">Johan
Lenglet</ulink> &lt;johan@linuxfromscratch.org&gt; for leading the French
LFS translation project.</para></listitem>
 
<listitem><para><ulink url="mailto:highos@linuxfromscratch.org">Jesse
Tie-Ten-Quee</ulink> &lt;highos@linuxfromscratch.org&gt; for donating a
Yamaha CDRW 8824E cd writer.</para></listitem>
 
<listitem><para><ulink url="http://www.oreilly.com">O'Reilly</ulink> for
donating books on SQL and PHP.</para></listitem>
 
<listitem><para>Robert Briggs for donating the linuxfromscratch.org and
linuxfromscratch.com domain names.</para></listitem>
 
<listitem><para><ulink url="mailto:bkenoah@oswd.org">Frank
Skettino</ulink> &lt;bkenoah@oswd.org&gt; at <ulink
url="http://www.oswd.org">OSWD</ulink> for coming up with the
initial design of the LFS website.</para></listitem>
 
<listitem><para><ulink url="mailto:garrett@linux.com">Garrett
LeSage</ulink> &lt;garrett@linux.com&gt; for creating the LFS
banner</para></listitem>
 
<listitem><para><ulink url="mailto:dean@vipersoft.co.uk">Dean
Benson</ulink> &lt;dean@vipersoft.co.uk&gt; for helping out financially
with setting up the LFS non-profit organization.</para></listitem>
 
<listitem><para>Countless other people on the various LFS mailinglists who are
making this book happen by giving their suggestions, testing the book
and submitting bug reports.</para></listitem>
 
</itemizedlist>
 
</sect1>
 
/tags/cvs/lfs/chapter01/changelog.xml
0,0 → 1,438
<sect1 id="ch01-changelog">
<title>Changelog</title>
<?dbhtml filename="changelog.html" dir="chapter01"?>
 
<para>&version; - &releasedate;</para>
 
<itemizedlist>
 
<listitem><para>February 17th, 2002 [gerard]: Chapter 05 - Sh-utils: Added
the command again that moves $LFS/usr/bin/chroot to
$LFS/usr/sbin</para></listitem>
 
<listitem><para>February 17th, 2002 [gerard] Updated dependencies for all
packages.</para></listitem>
 
<listitem><para>February 15th, 2002 [gerard] Chapter 01: Added a new mirror
to the list located in The Netherlands (www.nl and
ftp.nl).</para></listitem>
 
<listitem><para>February 11th, 2002 [markh] Chapter 05: Sh-utils:
Removed extra &amp;&amp; from end of install
instructions.</para></listitem>
 
<listitem><para>February 10th, 2002 [gerard]: Chapter 05 - Sh-utils:
Removed <emphasis>su</emphasis> from the <emphasis>mv</emphasis> command
as this isn't installed in chapter 5.</para></listitem>
 
</itemizedlist>
 
<para>3.2-RC1 - February 10th, 2002</para>
 
<itemizedlist>
 
<listitem><para>Updated to:
 
<itemizedlist>
<listitem><para>bison-1.31</para></listitem>
<listitem><para>file-3.37</para></listitem>
<listitem><para>glibc-2.2.5</para></listitem>
<listitem><para>kbd-1.06-2.patch</para></listitem>
<listitem><para>lfs-bootscripts-1.5</para></listitem>
<listitem><para>linux-2.4.17</para></listitem>
<listitem><para>man-pages-1.47</para></listitem>
<listitem><para>psmisc-20.2</para></listitem>
<listitem><para>sysvinit-2.84</para></listitem>
<listitem><para>util-linux-2.11n</para></listitem>
</itemizedlist>
 
</para></listitem></itemizedlist>
 
<itemizedlist>
 
<listitem><para>February 10th, 2002 [gerard]: Chapter 6: Added a sed
command to change gzexe's hardcoded /usr/bin/gzip path and change it to
/bin/gzip.</para></listitem>
 
<listitem><para>February 10th, 2002 [gerard]: Chapter 5 + 6: Moved
additional programs to the ($LFS)/bin directory that are used by the
bootscripts. No programs used by bootscripts (except daemons themselves)
should be in the /usr directory in case /usr isn't available until far
along in the boot process (when it's an NFS share for
example).</para></listitem>
 
<listitem><para>February 6th, 2002 [markh]: Appendix A - All
descriptions now synced and updated.</para></listitem>
 
<listitem><para>February 2nd, 2002 [gerard]: Chapter 6 - Changing owner:
Added <quote>cd /</quote> so the leading slash can be removed from all the
directories in the chown commands. It's more pleasant to type out this
way.</para></listitem>
 
<listitem><para>February 2nd, 2002 [gerard]: Updated to
lfs-bootscripts-1.5</para></listitem>
 
<listitem><para>February 2nd, 2002 [gerard]: Chapter 6 - Gzip: Removed the
compress symlink. Gzip can uncompress .Z files but it can't compress into
that format.</para></listitem>
 
<listitem><para>February 1st, 2002 [gerard]: Updated to
lfs-bootscripts-1.3</para></listitem>
 
<listitem><para>February 1st, 2002 [gerard]: Chapter 6 - Glibc: Instead of
sed'ing the <filename>config.make</filename> file, create the
<filename>glibc-build/configparms</filename> file containing
<quote>cross-compiling = no</quote>.</para></listitem>
 
<listitem><para>January 30th, 2002 [marcheerdink]: Chapters 5: Changed
the commands to copy the header files to support versions of cp older
than 4.1.</para></listitem>
 
<listitem><para>January 30th, 2002 [markh]: Chapters 5+6: Added
CPPFLAGS="$CPPFLAGS -D_GNU_SOURCE" to the configure command for patch.
This fixes compilation on PPC and m68k platforms and doesn't hurt on
x86.</para></listitem>
 
<listitem><para>January 30th, 2002 [gerard]: Chapter 5 - Mounting proc:
Rephrased the text a bit (it implied you can only mount the proc fs more
than once, which isn't true anymore these days).</para></listitem>
 
<listitem><para>January 30th, 2002 [markh]: Chapter 5: Enhanced the make
mrproper explanation.</para></listitem>
 
<listitem><para>January 30th, 2002 [marcheerdink]: Chapters 5+6: Removed
the --libexecdir flag from fileutils' configure options.</para></listitem>
 
<listitem><para>January 30th, 2002 [marcheerdink]: Chapters 6: Added a
symlink from vipw to vigr after installing shadow.</para></listitem>
 
<listitem><para>January 30th, 2002 [markh]: Chapters 5+6: Changed
binutils and e2fsprogs installation instructions to use separate
directories ala gcc and glibc.</para></listitem>
 
<listitem><para>January 30th, 2002 [gerard]: Chapter 6 - Bootscripts: Added
a chown root.root after the cp.</para></listitem>
 
<listitem><para>January 30th, 2002 [gerard]: Appendix A - Texinfo: the info
programs works on the /usr/share/info directory not
/usr/doc/info.</para></listitem>
 
<listitem><para>January 30th, 2002 [gerard]: Chapter 6 - Procps: Fixed typo
the path to the app-defaults directory (it's
/usr/X11R6/lib/X11/app-defaults and not
usr/X11R6/lib/app-defaults).</para></listitem>
 
<listitem><para>January 30th, 2002 [gerard]: Chapter 6 - Configure
software: Simplified the commands to create the utmp, btmp, lastlog and
wtmp files.</para></listitem>
 
<listitem><para>January 30th, 2002 [gerard]: Chapter1: Moved
Acknowledgements to be displayed as the first page in chapter
1.</para></listitem>
 
<listitem><para>January 30th, 2002 [gerard]: Chapter 1: Created a separate
page to list the HTTP and FTP mirrors.</para></listitem>
 
<listitem><para>January 30th, 2002 [gerard]: Chapter 4 - Creating
partition: increased the suggested partition size from 750 MB to 1
GB.</para></listitem>
 
<listitem><para>January 29th, 2002 [gerard]: Chapter 6 - Shadow: Combined
the <quote>mv libshadow.a /usr/lib</quote> and
<quote>mv libshadow.la /usr/lib</quote> commands into
<quote>mv libshadow.*a /usr/lib</quote></para></listitem>
 
<listitem><para>January 26th, 2002 [gerard]: Upgraded to
lfs-bootscripts-1.2</para></listitem>
 
<listitem><para>January 26th, 2002 [marcheerdink]: Chapter 6: Removed the
datadir option from bisons configure flags, because recent bisons use the
correct directory by default.</para></listitem>
 
<listitem><para>January 23rd, 2002 [markh]: Chapter 6: Added the section
Create /etc/mtab symlink.</para></listitem>
 
<listitem><para>January 23rd, 2002 [gerard]: Removed the file -C command
from the file installation. This package runs this command at the very end
of the installation so we don't need to do this anymore.</para></listitem>
 
<listitem><para>January 23rd, 2002 [marcheerdink]: Chapter 4+5+6: The static
environment is now built as an unprivileged user, removing the risk of
overwriting files of the host distribution.</para></listitem>
 
<listitem><para>January 22nd, 2002 [markh]: Back out linuxthreads
man-page installation instructions as they don't work (they need perl
which we don't have installed at that point).</para></listitem>
 
<listitem><para>January 21st, 2002 [markh]: Updated to glibc-2.2.5. At
the same time, fixed the glibc installation so that the linuxthreads man
pages are installed.</para></listitem>
 
<listitem><para>January 21st, 2002 [markh]: Updated to bison-1.31,
file-3.37, kernel-2.4.17, psmisc-20.2 and
sysvinit-2.84.</para></listitem>
 
<listitem><para>January 21st, 2002 [markh]: Updated to util-linux-2.11n
and removed ADD_RAW=yes as it's no longer needed.</para></listitem>
 
<listitem><para>January 21st, 2002 [markh]: Updated to man-pages-1.47
and removed the man-pages patch.</para></listitem>
 
<listitem><para>January 15th, 2002 [gerard]: Appendix A: Added bootscripts
files (dependencies, download location, descriptions)</para></listitem>
 
<listitem><para>January 15th, 2002 [gerard]: Chapter 6: Added bootscripts
installation.</para></listitem>
 
<listitem><para>January 15th, 2002 [gerard]: Chapter 7: Removed most of the
scripts, only left the part of a few where we setup up config files in
/etc/sysconfig.</para></listitem>
 
<listitem><para>January 15th, 2002 [gerard]: Chapter 6 - Configuring
Sysvinit: Changed the inittab contents to match the new
bootscripts.</para></listitem>
 
<listitem><para>January 15th, 2002 [marcheerdink]: Chapter 6 - file: changed
the installation instruction so the sed isn't necessary anymore.</para></listitem>
 
<listitem><para>January 14th, 2002 [marcheerdink]: Changed the kernel header
files installation in chapter 5 so it's a bit more portable.</para></listitem>
 
<listitem><para>January 6th, 2002 [gerard]: Reformatted the dependency
lists.</para></listitem>
 
<listitem><para>January 1st, 2002 [gerard]: Happy New Year
LFS!</para></listitem>
 
<listitem><para>January 1st, 2002 [markh]: First Changelog of New Year!
Update copyright notice to cover 2002 ;-) OK - I'm
sad...</para></listitem>
 
<listitem><para>December 16th, 2001 [gerard]: Chapter 6 - Ed: Reworded why
ed is optional to eliminate some confusion.</para></listitem>
 
<listitem><para>December 16th, 2001 [gerard]: Chapter 6 - Texinfo: Reworded
the TEXMF explanation to eliminate some confusion.</para></listitem>
 
<listitem><para>December 15th, 2001 [gerard]: Chapter 4: Replaced the "One
partition hint" reference with lfs_next_to_existing_systems.txt hint
reference.</para></listitem>
 
<listitem><para>December 15th, 2001 [markh]: Finish Appendix merge. All
of the old appendices A, B and D are now in one (large) Appendix
A.</para></listitem>
 
<listitem><para>December 14th, 2001 [markh]: Merged appendices A and
B.</para></listitem>
 
<listitem><para>December 13th, 2001 [markh]: Appendix B: Changed dbhtml
tag so that the flex page is now created as flex.html instead of
flex</para></listitem>
 
<listitem><para>December 13th, 2001 [markh]: Appendix D: Moved
metalab.unc.edu and ftp.ibiblio.org references to the proper URL
ibiblio.org.</para></listitem>
 
<listitem><para>December 12th, 2001 [marcheerdink]: Chapter 6: Moved
the kbd patch to the default installation instructions; upgraded to
kbd-1.06-2.patch to fix installation of some programs; added the
descriptions for these programs; removed the loadkeys -d warning that
was a leftover from the time where loadkeys -d wasn't fixed yet.</para></listitem>
 
<listitem><para>December 11th, 2001 [markh]: Chapter 6: Add the "why we
cd $LFS before chroot" explanation.</para></listitem>
 
<listitem><para>December 10th, 2001 [markh]: Chapter 6: Add kbd patch
for loadkeys -d behaviour (patch by Matthias Benkmann; originally posted
to the lfs-dev list).</para></listitem>
 
<listitem><para>December 10th, 2001 [markh]: Chapter 6: Re-create
symlinks in bash, fileutils and gcc instructions to make the Chapter 6
instructions independent of those in chapter 5.</para></listitem>
 
<listitem><para>December 10th, 2001 [marcheerdink]: Chapter 5+6: Cleaned
up the sed commands to use the backup file that was created earlier instead
of writing to an intermediate 'tmp~' file.</para></listitem>
 
<listitem><para>December 10th, 2001 [marcheerdink]: Chapter 5+6: 'make'
command for diffutils installation changed to 'make PR_PROGRAM=/usr/bin/pr.'
This bug was reported by Greg Schafer.</para></listitem>
 
<listitem><para>December 7th, 2001 [gerard]: Chapter 6: Change the
configure command from <emphasis>./Configure -Dprefix=/usr</emphasis> to
<emphasis>./configure.gnu --prefix=/usr</emphasis>. This is more consistent
with the installation instructions for the other packages, and the result
is identical to the old way.</para></listitem>
 
<listitem><para>December 3rd, 2001 [markh]: Chapter 2: Added the Which
Platform? section.</para></listitem>
 
</itemizedlist>
 
<para>3.1 - December 3rd, 2001</para>
 
<itemizedlist>
 
<listitem><para>Added:
 
<itemizedlist>
<listitem><para>reiserfsprogs-3.x.0j</para></listitem>
</itemizedlist>
 
</para></listitem>
 
<listitem><para>Updated to:
 
<itemizedlist>
<listitem><para>MAKEDEV-1.4</para></listitem>
<listitem><para>bash-2.05a</para></listitem>
<listitem><para>e2fsprogs-1.25</para></listitem>
<listitem><para>gettext-0.10.40</para></listitem>
<listitem><para>libtool-1.4.2</para></listitem>
<listitem><para>lilo-22.1</para></listitem>
<listitem><para>linux-2.4.16</para></listitem>
<listitem><para>man-1.5j</para></listitem>
<listitem><para>man-pages-1.43</para></listitem>
<listitem><para>modutils-2.4.12</para></listitem>
<listitem><para>sysvinit-2.83</para></listitem>
<listitem><para>util-linux-2.11m</para></listitem>
<listitem><para>vim-6.0</para></listitem>
</itemizedlist>
 
</para></listitem>
 
<listitem><para>November 30th, 2001 [markh]: Chapter 6: Updated to
man-1.5j. Removed the sed which we had to use with the old version as
the new one detects awk properly.</para></listitem>
 
<listitem><para>November 30th, 2001 [markh]: Chapter 5: Added static
library explanation originally posted on lfs-apps (when it still
existed) by Plasmatic.</para></listitem>
 
<listitem><para>November 26th, 2001 [markh]: Chapter 5+6: Updated to
kernel-2.4.16 and modutils-2.4.12.</para></listitem>
 
<listitem><para>November 26th, 2001 [markh]: Chapter 6: Added FHS
compliance notes to the findutils installation.</para></listitem>
 
<listitem><para>November 19th, 2001 [markh]: Chapter 5+6: Updated to
bash-2.05a, lilo-22.1, MAKEDEV-1.4, man-pages-1.43 and
util-linux-2.11m.</para></listitem>
 
<listitem><para>November 5th, 2001 [markh]: Chapter 6: Created new lex
script instead of link to flex following comment on lfs-dev. (This is
similar to what we do with bison and yacc).</para></listitem>
 
<listitem><para>October 27th, 2001 [markh]: General: Large XML Tidy-up.
Shouldn't affect the book text or layout. If it does, something has
gone wrong!</para></listitem>
 
<listitem><para>October 27th, 2001 [markh]: Chapter 6: Added
reiserfsprogs-3.x.0j and updated to lilo-22.0.2.</para></listitem>
 
<listitem><para>October 24th, 2001 [markh]: General: Fixed a bundle of
spelling errors which were reported.</para></listitem>
 
<listitem><para>October 12th, 2001 [markh]: Chapter 5 - Kernel: Added
explanation as to why we copy the kernel headers rather than symlink
them.</para></listitem>
 
<listitem><para>October 12th, 2001 [markh]: Appendix A - Gzip: Added
uncompress to the gunzip description as it was
missing.</para></listitem>
 
<listitem><para>October 12th, 2001 [markh]: Chapter 6 - Util-linux:
Removed the USRGAMES_DIR=/usr/bin entry as it's no longer needed with
util-linux-2.11l.</para></listitem>
 
<listitem><para>October 9th, 2001 [gerard]: Chapter 6 - Kbd: Removed the
--datadir option, kbd's default is set properly already.</para></listitem>
 
<listitem><para>October 7th, 2001 [gerard]: Chapter 6 - Shadow: Mentioned
the <ulink url="http://hints.linuxfromscratch.org/hints/shadowpasswd_plus.txt">http://hints.linuxfromscratch.org/hints/shadowpasswd_plus.txt</ulink>
lfs-hint</para></listitem>
 
<listitem><para>October 7th, 2001 [gerard]: Chapter 6 - Vim: Changed the
installation instructions to fix a bug in vim-6.0's
<filename>syntax/sh.vim</filename> file, and added the CPPFLAGS variable
to specify the global vimrc file as
<filename>/etc/vimrc</filename></para></listitem>
 
<listitem><para>October 7th, 2001 [gerard]: Chapter 6: Updated to
libtool-1.4.2, lilo-22.0, man-pages-1.40, modutils-2.4.10, sysvinit-2.83,
util-linux-2.11l and vim-6.0</para></listitem>
 
<listitem><para>October 2nd, 2001 [gerard]: Chapter 9 - The End: Added the
reference to the LFS Counter at
<ulink url="http://linuxfromscratch.org/cgi-bin/lfscounter.cgi">
http://linuxfromscratch.org/cgi-bin/lfscounter.cgi</ulink></para></listitem>
 
<listitem><para>September 26th, 2001 [gerard]: Chapter 1 - News server:
Added reference to the news server</para></listitem>
 
<listitem><para>September 26th, 2001 [markh]: Chapter 6 - E2fsprogs: Changed
--with-root-prefix=/ to --with-root-prefix="" in e2fsprogs install
instructions. The reason for the change is that a value of / will cause
symlinks and installation paths to use things like //lib instead of
just /lib. This isn't bad perse, it just doesn't look
nice.</para></listitem>
 
<listitem><para>September 26th, 2001 [markh]: Chapter 5+6: Updated to
e2fsprogs-1.25, gettext-0.10.40, linux-2.4.10, modutils-2.4.9 and
util-linux-2.11i.</para></listitem>
 
<listitem><para>September 22nd, 2001 [markh]: Appendix A: Re-ordered the
descriptions into alphabetical order.</para></listitem>
 
</itemizedlist>
 
<para>3.0 - September 21st, 2001</para>
 
<itemizedlist>
 
<listitem><para>Updated to:
 
<itemizedlist>
 
<listitem><para>e2fsprogs-1.24</para></listitem>
 
</itemizedlist>
 
</para></listitem>
 
<listitem><para>September 21st, 2001 [markh]: Chapter 1+7: Changed the
mailing list information to reflect the new ml
structure. The Ch7 change is that the rc and rcS scripts now ask people
to report problems to lfs-dev instead of lfs-discuss.</para></listitem>
 
<listitem><para>September 18th, 2001 [gerard]: Chapter 5+6 - GCC:
Added --enable-threads=posix to chapter 5, and changed --enable-threads to
--enable-threads=posix in chapter 6. Although the default is posix threads
when
not specified, it's clearer this way what's being
enabled.</para></listitem>
 
<listitem><para>September 17th, 2001 [gerard]: Chapter 6 - Psmisc:
Added notes how to deal with psmisc's pidof symlink (in case sysvinit
isn't installed) and man page. Also, added --exec-prefix=/ to psmisc's
configure script in order for the programs to be installed in /bin
rather than /usr/bin (bootscripts may use them, so they must be in
/bin).</para></listitem>
 
<listitem><para>September 16th, 2001 [markh]: Chapter 6 - Util-linux:
Added USRGAMES_DIR=/usr/bin to the make install routine so that
/usr/games isn't created for banner and it is installed in
/usr/bin.</para></listitem>
 
<listitem><para>September 14th, 2001 [markh]: Chapter 6 - E2fsprogs:
Updated to version 1.24.</para></listitem>
 
<listitem><para>September 11th, 2001 [gerard]: Chapter 6 - Man: Added
missing &amp;&amp; to 'done' and chmod the configure script to mode 755
instead of 700 (more of a default mode so people don't _have_ to be
running as the owner of that file).</para></listitem>
 
</itemizedlist>
 
</sect1>
 
/tags/cvs/lfs/chapter01/mirrors.xml
0,0 → 1,123
<sect1 id="ch01-mirrors" xreflabel="Chapter 1 - Mirror sites">
<title>Mirror sites</title>
<?dbhtml filename="mirrors.html" dir="chapter01"?>
 
<para>Below is a list of our current HTTP and FTP mirror sites as
of February 15th, 2002. This list might not be accurate anymore.
The latest info can be found on our website at
<ulink url="http://www.linuxfromscratch.org">http://www.linuxfromscratch.org</ulink>.</para>
 
<sect2>
<title>HTTP Mirrors</title>
 
<sect3>
<title>North America</title>
 
<itemizedlist>
 
<listitem><para>Fremont, California, USA [100 Mbit] - <ulink
url="http://www.linuxfromscratch.org/lfs/intro.shtml">http://www.linuxfromscratch.org/lfs/intro.shtml</ulink></para></listitem>
 
<listitem><para>Columbus, Ohio, United States [1 Mbit] - <ulink
url="http://www.us.linuxfromscratch.org/lfs/intro.shtml">http://www.us.linuxfromscratch.org/lfs/intro.shtml</ulink></para></listitem>
 
</itemizedlist>
 
</sect3>
 
<sect3>
<title>Europe</title>
 
<itemizedlist>
 
<listitem><para>Mainz, Germany [100 Mbit] - <ulink
url="http://lfs.linux-provider.net/lfs/intro.shtml">http://lfs.linux-provider.net/lfs/intro.shtml</ulink></para></listitem>
 
<listitem><para>Vienna Univ. of Technology, Austria [16 Mbit] - <ulink
url="http://www.at.linuxfromscratch.org/lfs/intro.shtml">http://www.at.linuxfromscratch.org/lfs/intro.shtml</ulink></para></listitem>
 
<listitem><para>Oslo, Norway [100 Mbit] - <ulink
url="http://www.no.linuxfromscratch.org/lfs/intro.shtml">http://www.no.linuxfromscratch.org/lfs/intro.shtml</ulink></para></listitem>
 
<listitem><para>Teeside, United Kingdom [256 Kbit] - <ulink
url="http://www.linuxfromscratch.co.uk/lfs/intro.shtml">http://www.linuxfromscratch.co.uk/lfs/intro.shtml</ulink></para></listitem>
 
<listitem><para>Amsterdam, The Netherlands [100 Mbit] - <ulink
url="http://www.nl.linuxfromscratch.org/lfs/intro.shtml">http://www.nl.linuxfromscratch.org/lfs/intro.shtml</ulink></para></listitem>
 
</itemizedlist>
 
</sect3>
 
<sect3>
<title>Australia</title>
 
<itemizedlist>
 
<listitem><para>Brisbane, Australia [155 Mbit] - <ulink
url="http://www.au.linuxfromscratch.org/lfs/intro.shtml">http://www.au.linuxfromscratch.org/lfs/intro.shtml</ulink></para></listitem>
 
</itemizedlist>
 
</sect3>
 
</sect2>
 
<sect2>
<title>FTP Mirrors</title>
 
<sect3>
<title>North America</title>
 
<itemizedlist>
 
<listitem><para>Fremont, California, USA [FTP] [100 Mbit] - <ulink
url="&ftp-root;">&ftp-root;</ulink></para></listitem>
 
<listitem><para>Fremont, California, USA [HTTP] [100 Mbit] - <ulink
url="&http-root">&http-root;</ulink></para></listitem>
 
</itemizedlist>
 
</sect3>
 
<sect3>
<title>Europe</title>
 
<itemizedlist>
 
<listitem><para>Vienna Univ. of Tech., Austria [FTP] [16 Mbit] - <ulink
url="ftp://ftp.at.linuxfromscratch.org/pub/lfs">ftp://ftp.at.linuxfromscratch.org/pub/lfs</ulink></para></listitem>
 
<listitem><para>Vienna Univ. of Tech., Austria [HTTP] [16 Mbit] - <ulink
url="http://ftp.at.linuxfromscratch.org/pub/lfs">http://ftp.at.linuxfromscratch.org/pub/lfs</ulink></para></listitem>
 
<listitem><para>Oslo, Norway [FTP] [100 Mbit] - <ulink
url="ftp://ftp.no.linuxfromscratch.org/mirrors/lfs/">ftp://ftp.no.linuxfromscratch.org/mirrors/lfs/</ulink></para></listitem>
 
<listitem><para>Univ. of Twente, The Netherlands [HTTP] [100 Mbit] - <ulink
url="http://ftp.nl.linuxfromscratch.org/linux/lfs">http://ftp.nl.linuxfromscratch.org/linux/lfs</ulink></para></listitem>
 
<listitem><para>Univ. of Twente, The Netherlands [FTP] [100 Mbit] - <ulink
url="ftp://ftp.nl.linuxfromscratch.org/pub/linux/lfs">ftp:/ftp.nl.linuxfromscratch.org/pub/linux/lfs</ulink></para></listitem>
 
</itemizedlist>
 
</sect3>
 
<sect3>
<title>Australia</title>
 
<itemizedlist>
 
<listitem><para>Brisbane, Australia [FTP] [155 Mbit] - <ulink
url="ftp://ftp.planetmirror.com/pub/lfs/">ftp://ftp.planetmirror.com/pub/lfs/</ulink></para></listitem>
 
</itemizedlist>
 
</sect3>
 
</sect2>
 
</sect1>
 
/tags/cvs/lfs/chapter01/how.xml
0,0 → 1,43
<sect1 id="ch01-how">
<title>Comment les choses se dérouleront-elles</title>
<?dbhtml filename="how.html" dir="chapter01"?>
 
<para>Nous allons construire le système LFS en utilisant une distribution Linux déjà installée,
telle que Debian, SuSe, Slackware, Mandrake, RedHat, etc. Nul besoin de disquette de démarrage.
Nous utiliserons un système Linux existant comme base (puisque nous aurons besoin d'un compilateur,
d'un éditeur de liens, d'un éditeur de texte et d'autres outils). </para>
 
<para>Après avoir téléchargé les packages nécessaires à la constitution d'un système LFS,
vous devrez créer une nouvelle partition native Linux, sur laquelle sera installé le
système LFS. </para>
 
<para>L'étape suivante, abordée dans le Chapitre 5, est l'installation d'un nombre de packages
liés statiquement et installés sur la partition LFS. Ces packages forment une suite de
développement de base utilisée pour installer le système réel et sont aussi nécessaires pour
résoudre des dépendances circulaires. Les examples de dépendances circulaires sont:
vous avez besoin d'un compilateur pour installer un compilateur, vous avez
besoin d'un shell pour installer un shell. Et ainsi de suite.</para>
 
<para>Le Chapitre 6 permet l'installation du système de base en question. Nous utiliserons le programme
chroot pour commencer un nouveau shell, dont le répertoire root sera situé dans la partition LFS.
En un sens, cela équivaut à redémarrer et avoir le noyau monté sur la partition LFS de la même
manière qu'une partition root. Pourquoi nous ne redémarrons pas et, à la place, nous utilisons
le programme chroot ? Parce qu'ainsi, vous conservez la possibilité d'utiliser votre système hôte.
Tandis que le logiciel est en cours d'installation, vous pouvez passer sur une autre CV (Console Virtuelle)
ou bureau X et continuer d'utiliser votre ordinateur.</para>
 
<para>Lorsque le logiciel sera entièrement installé, on passera à la configuration des scripts de
démarrage dans le Chapitre 7. Le chapitre 8 configurera le chargeur Linux et dans le chapitre 9,
vous trouverez des astuces que vous pourrez mettre en oeuvre après avoir fini le livre.
Enfin vous pourrez redémarrer la machine sur votre nouveau systeme LFS, et commencer
à vraiment l'utiliser.</para>
 
<para>En résumé, telle est la démarche à suivre. Des informations détaillées sur les
différentes étapes sont fournies tout au long des chapitres au fur et à mesure de votre
progression. Si tout n'est pas encore clair, ne vous inquiétez pas. Cela ne saurait tarder. </para>
 
<para>Veuillez lire le Chapitre 2 avec attention car il explique un certain nombre de points
importants qu'il vous faut connaître avant d'en arriver au Chapitre 5 et au-delà. </para>
 
</sect1>
 
/tags/cvs/lfs/chapter01/lfsbook.xml
0,0 → 1,12
/tags/cvs/lfs/chapter01/maillists.xml
0,0 → 1,51
<sect1 id="ch01-maillists" xreflabel="Chapter 1 - Mailing lists and archives">
<title>Listes de diffusion et archives</title>
<?dbhtml filename="maillists.html" dir="chapter01"?>
 
<para>Le serveur linuxfromscratch.org accueille les listes de diffusion publics
suivantes:</para>
 
<itemizedlist>
 
<listitem><para>lfs-support</para></listitem>
 
<listitem><para>lfs-dev</para></listitem>
 
<listitem><para>lfs-announce</para></listitem>
 
<listitem><para>lfs-security</para></listitem>
 
<listitem><para>lfs-book</para></listitem>
 
<listitem><para>alfs-discuss</para></listitem>
 
<listitem><para>blfs-dev</para></listitem>
 
<listitem><para>blfs-book</para></listitem>
 
<listitem><para>blfs-support</para></listitem>
 
</itemizedlist>
 
&c1-ma-lfssupport;
&c1-ma-lfsdev;
&c1-ma-lfsannounce;
&c1-ma-lfssecurity;
&c1-ma-lfsbook;
 
&c1-ma-alfsdiscuss;
 
&c1-ma-blfsdev;
&c1-ma-blfsbook;
&c1-ma-blfssupport;
 
&c1-ma-mailarchive;
 
&c1-ma-howtopost;
 
&c1-ma-subscribe;
&c1-ma-unsubscribe;
&c1-ma-othermodes;
 
</sect1>
 
/tags/cvs/lfs/chapter01/blfsbook.xml
0,0 → 1,11
<sect2>
<title>blfs-book</title>
 
<para>La liste de diffusion blfs-book est utilisé par les éditeurs du livre BLFS
pour coordonner la maintenance du livre BLFS, par exemple pour des problèmes en relation
avec XML.
Les discussions sur ce qui doit être ajouté ou supprimé doivent avoir lieu sur blfs-dev.
</para>
 
</sect2>
 
/tags/cvs/lfs/chapter01/newsserver.xml
0,0 → 1,13
<sect1 id="ch01-newsserver">
<title>Serveur News</title>
<?dbhtml filename="newsserver.html" dir="chapter01"?>
 
<para>Toutes les listes de diffusion hébergées par linuxfromscratch.org sont aussi
accessibles via le serveur NNTP. Tous les messages postés à la liste de diffusion
sont copiés vers le newsgroup correspondant et vice versa.</para>
 
<para>Le serveur news peut être accédé par
<emphasis>news.linuxfromscratch.org</emphasis></para>
 
</sect1>
 
/tags/cvs/lfs/chapter01/conventions.xml
0,0 → 1,50
<sect1 id="ch01-conventions">
<title>Conventions utilisées dans ce livre</title>
<?dbhtml filename="conventions.html" dir="chapter01"?>
 
<para>Pour rendre les choses faciles à comprendre, il y a un certain nombre de conventions qui sont
utilisées tout au long du livre. Voici quelques exemples:</para>
 
<para><userinput>./configure --prefix=/usr</userinput></para>
 
<blockquote><para>Cette façon de présenter montre les textes qui doivent être tapés exactement
comme ils sont écrit sauf si le texte autour dit le contraire. Cela est aussi utilisé
dans les explications pour mettre en évidence les commandes auxquelles on fait référence.
</para></blockquote>
 
<para><filename>install-info: unknown option
`--dir-file=/mnt/lfs/usr/info/dir'</filename></para>
 
<blockquote><para>Cette façon de présenter (texte de largeur fixe) montre les textes
qui apparaissent à l'écran, très souvent comme résultat à la fin d'une commande. C'est aussi
utilisé pour faire ressortir les noms de fichiers comme <filename>/etc/lilo.conf</filename>
</para></blockquote>
 
<para><emphasis>Emphasis</emphasis></para>
 
<blockquote><para>Cette façon de présenter est utilisée dans ce livre pour différentes
choses mais principalement pour attirer l'attention sur des points importants ou pour
donner des exemples sur ce qu'il faut taper.</para></blockquote>
 
<para><ulink url="http://www.linuxfromscratch.org/">http://www.linuxfromscratch.org/</ulink></para>
 
<blockquote><para>Cette façon de présenter est utilisée pour les liens hypertextes
internes à ce livre mais aussi externes comme les HOWTOs, les sites de téléchargement,
les sites web, etc.</para></blockquote>
 
<para><screen><userinput>cat &gt; $LFS/etc/group &lt;&lt; "EOF"</userinput>
root:x:0:
bin:x:1:
......
<userinput>EOF</userinput>
</screen>
</para>
 
<blockquote><para>Cette façon de présenter est utilisée principalement lorsqu'il y a création
de fichiers de configuration. La première commande (en gras) demande au systeme
de créer le fichier $LFS/etc/group à partir de tout ce qui peut être
tapé dans les lignes qui suivent jusqu'à que la séquence EOF soit rencontrée. Par conséquent,
l'ensemble de cette partie est généralement tapé comme elle est présentée.</para></blockquote>
 
</sect1>
 
/tags/cvs/lfs/chapter01/howtopost.xml
0,0 → 1,17
<sect2>
<title>How to post to a list</title>
 
<para>You do not need to be subscribed to a mailing list in order to post to it.
However, if you post to a list you're not subscribed to, make sure you
mention this in your email so the list members can put you in the CC:
header of an email in order for you receive the replies.</para>
 
<para>The post address for a list is in the format of
<emphasis>listname@linuxfromscratch.org</emphasis> where
<emphasis>listname</emphasis> can be one of the lists in the Available lists
section above. Examples of post addresses are
<emphasis>lfs-dev@linuxfromscratch.org, lfs-support@linuxfromscratch.org and
blfs-support@linuxfromscratch.org</emphasis>.</para>
 
</sect2>
 
/tags/cvs/lfs/chapter01/contactinfo.xml
0,0 → 1,28
/tags/cvs/lfs/chapter01/chapter1.xml
0,0 → 1,15
<chapter id="chapter01">
<title>Introduction</title>
<?dbhtml filename="chapter01.html" dir="chapter01"?>
 
&c1-acknowledgments;
&c1-how;
&c1-conventions;
&c1-version;
&c1-mirrors;
&c1-changelog;
&c1-maillists;
&c1-newsserver;
&c1-contactinfo;
 
</chapter>
/tags/cvs/lfs/chapter01/versions.xml
0,0 → 1,11
+</sect1>
\ No newline at end of file
/tags/cvs/lfs/chapter01/othermodes.xml
0,0 → 1,55
<sect2>
<title>Autres modes de listes</title>
 
<para>Les modes pouvant être activés par l'utilisateur requiert l'envoi d'un email à
<ulink url="mailto:listar@linuxfromscratch.org">listar@linuxfromscratch.org</ulink>.
Les modes en eux-même sont activés en tapant les commandes appropriées dans le champ Objet du message.</para>
 
<para>Comme les noms l'indiquent, le <emphasis>Set command</emphasis> indique quoi
écrire pour activer un mode. La commande <emphasis>Unset command</emphasis> indique quoi
écrire pour désactiver un mode.</para>
 
<para>Le mot "nom-de-la-liste" dans l'exemple de champ Objet doit être remplacé avec
le nom de la liste pour laquelle le mode doit être activé. Si plus d'un mode est à
activer (pour une unique liste ou un ensemble d'entre elles)
en un email, ceci peut être réalisé en laissant
le champ Objet vide et en tapant les commandes dans le corps de l'email.</para>
 
</sect2>
 
<sect2>
<title>Résumé</title>
 
<literallayout>
Commande d'activation: <emphasis>set nom-de-la-liste digest</emphasis>
Commande de désactivation: <emphasis>unset nom-de-la-liste digest</emphasis>
</literallayout>
 
<para>Le mode "Digest" peut être appliqué à toutes les listes pour lesquelles
l'utilisateur s'est abonné. Le mode Digest vous empêche
de recevoir les messages à chaque fois qu'ils sont postés
sur la liste et vous fait envoyer un unique email par jour contenant
tous les messages postés sur la liste durant cette journée.</para>
 
<para>Le second mode Digest est appellé "Digest2". Si l'utilisateur active ce mode,
il recevra ce mail quotidien ainsi que chacun des emails dès qu'ils sont postés.
Pour activer ce mode, remplacez <emphasis>digest</emphasis> par
<emphasis>digest2</emphasis> dans la commande.</para>
 
</sect2>
 
<sect2>
<title>En vacances</title>
 
<literallayout>
Commande d'activation: <emphasis>set nom-de-la-liste vacation</emphasis>
Commande de désactivation: <emphasis>unset nom-de-la-liste vacation</emphasis>
</literallayout>
 
<para>Lorsqu'un utilisateur est en déplacement pour un temps et qu'il ne souhaite plus recevoir
d'email sans toutefois être désabonné de la liste, il peut
basculer vers le mode "vacation". Ceci a le même effet que de désabonner
sans avoir à le faire ainsi qu'à devoir se réabonner de nouveau par la suite.</para>
 
</sect2>
 
/tags/cvs/lfs/chapter01/lfsannounce.xml
0,0 → 1,12
<sect2>
<title>lfs-announce</title>
 
<para>la liste lfs-announce est une liste restreinte. Vous pouvez y souscrire, mais
vous ne pouvez pas y poster de messages. Cette liste sert à annoncer les nouvelles
versions stables. la liste lfs-dev quand à elle, annonce aussi les nouvelles versions
du développement. Il n'est pas utile pour un utilisateur de s'inscrire à la liste
lfs-announce si il est déjà inscrit à lfs-dev car tout ce qui est posté sur la première
l'est aussi sur la seconde.</para>
 
</sect2>
 
/tags/cvs/lfs/chapter01/lfssecurity.xml
0,0 → 1,9
<sect2>
<title>lfs-security</title>
 
<para>La liste de diffusion "lfs-security" traite des sujets touchant à la sécurité.
Les questionnements ou les problèmes de sécurité avec un package utilisé par LFS
doivent être adressés à cette liste.</para>
 
</sect2>
 
/tags/cvs/lfs/chapter02/commands.xml
0,0 → 1,38
<sect1 id="ch02-commands">
<title>Télécharger les commandes LFS</title>
<?dbhtml filename="commands.html" dir="chapter02"?>
 
<para>Les commandes LFS sont fournis sous la forme d'une archive tar qui
contient les fichiers donnant la liste des commandes d'installation pour
les package proposés dans ce livre.</para>
 
<para>Ces fichiers peuvent être utilisés pour trouver rapidement quelles
commandes ont changés entre les différentes versions de la LFS. Téléchargez
l'archive lfs-commands accompagnant cette version du livre et celle de la
version précédente, et lancez l'utilitaire diff sur les fichiers. Cela permet de mettre
en évidence pour quels packages les instructions d'installation ont été modifiés, de tel
façon que tout script que vous pourriez avoir puisse être modifié ou que vous puissez
réinstaller n'importe quel package si nécessaire.</para>
 
<para>Une des conséquences est que ces fichiers peuvent être utilisés à
partir d'un shell pour installer un package, bien que quelques fichiers
puissent nécéssiter des modifications (là où certains paramètres ne peuvent
pas être devinés, puisque dépendant des préférences de l'utilisateur ou
de la configuration matérielle). Gardez toujours à l'esprit que ces scripts n'ont pas
été vérifiés à la perfection. Il peut subsister quelques bugs dans les fichiers (car ils
sont créés manuellement pour le moment), donc prenez la peine de les vérifier vous-même
et ne croyez pas aveuglement.</para>
 
<para>Si vous décidez d'utiliser la commande pour installer automatiquement
un package et que cela ne fonctionne pas, commencez par lire les instructions
dans le livre avant de demander de l'aide sur la liste de discution.</para>
 
<para>Les commandes LFS peuvent être obtenues à partir de <ulink
url="&http-root;/lfs-commands/">&http-root;/lfs-commands/</ulink>
ou de <ulink
url="&ftp-root;/lfs-commands/">&ftp-root;/lfs-commands/</ulink>
.</para>
 
</sect1>
 
 
/tags/cvs/lfs/chapter02/platform.xml
0,0 → 1,16
<sect1 id="ch02-platform" xreflabel="Chapter 2 - Platform">
<title>Which Platform?</title>
<?dbhtml filename="platform.html" dir="chapter02"?>
 
<para>LFS intends to be as far as possible platform independent. Having
said that, the main LFS development work occurs on the x86 platform. We
attempt to include information where possible on differences for other
platforms such as PPC. If you come across a problem compiling which is
not related to the x86 platform, still feel free to ask for help on the
mailing lists. Even better, if you come up with a solution to a
particular problem related to one of the other platforms, please let us
know at the lfs-dev mailing list. We will then (subject to confirming
it works) include that in the book.</para>
 
</sect1>
 
/tags/cvs/lfs/chapter02/install.xml
0,0 → 1,84
<sect1 id="ch02-install" xreflabel="Chapter 2 - How to install the software">
<title>Comment installer les logiciels</title>
<?dbhtml filename="install.html" dir="chapter02"?>
 
<para>Avant que vous ne commenciez à utiliser le livre LFS, nous aimerions vous
faire remarquer que toutes les commandes employées supposent que vous utilisiez
le shell bash. Si cela n'est pas le cas, les commandes peuvent fonctionner mais
nous ne pouvons le garantir. Si vous voulez vous simplifier la vie, utilisez
bash.</para>
 
<para>Avant de pouvoir faire quelque chose d'un package, vous devrez d'abord le
déballer. Souvent, les packages sont des archives tar qui ont été compressés
avec gzip ou bzip2. Nous n'expliquerons pas à chaque fois comment déballer une
archive. Nous allons vous l'expliquer une bonne fois pour toutes dans cette
section.</para>
 
<para>Pour commencer, placez vous dans le répertoire $LFS/usr/src en lançant:</para>
 
<para><screen><userinput>cd $LFS/usr/src</userinput></screen></para>
 
<para>Si une archive est au format tar et gzip, elle est déballée grâce à
l'une de ces deux commandes, suivant le nom du fichier :</para>
 
<para><screen><userinput>tar xvzf filename.tar.gz</userinput>
<userinput>tar xvzf filename.tgz</userinput></screen></para>
 
 
<para>Si une archive est au format tar et bzip2, elle est déballée par la
commande :</para>
 
<para><screen><userinput>bzcat filename.tar.bz2 | tar xv</userinput></screen></para>
 
<para>Quelques versions de tar (la plupart de nos jours, mais pas encore toutes)
ont été modifiées pour utiliser directement bzip2 grâce à l'option I, y ou j, qui
fonctionne de manière identique à l'option z pour la gestion des archives
compressées avec gzip. La commande ci-dessus fonctionne quel que soit la manière
dont votre système a été modifié pour gérer le bzip2 dans la commande tar.</para>
 
<para>Si une archive est simplement en tar, elle est déballée par la commande :</para>
 
<para><screen><userinput>tar xvf filename.tar</userinput></screen></para>
 
<para>Quand une archive est déballée, un nouveau répertoire est créé dans le
répertoire courant (et ce livre suppose que les archives sont déballées dans
le répertoire $LFS/usr/src). Placez vous dans ce nouveau répertoire pour la
suite de la procédure d'installation. A chaque fois que ce livre vous
expliquera l'installation d'un package, ce sera à vous de déballer l'archive
des sources et de vous placer dans le répertoire créé.</para>
 
<para>De temps en temps, il vous faudra travailler avec de simple fichiers tels
que des fichiers de patch. Ces fichiers vous seront généralement fournis
compressés avec gzip ou bzip2. Avant de pouvoir les utiliser, il faudra les
décompresser.</para>
 
<para>Si un fichier a été compressé avec gzip, il sera décompressé par :</para>
 
<para><screen><userinput>gunzip filename.gz</userinput></screen></para>
 
<para>Si un fichier a été compressé avec bzip2, il sera décompressé par :</para>
 
<para><screen><userinput>bunzip2 filename.bz2</userinput></screen></para>
 
<para>Après l'installation d'un package, deux choix s'offrent à vous : soit
effacer le répertoire contenant les sources, soit le garder. Nous vous
recommendons vivement de le supprimer. Si vous ne le faites pas et essayez
de ré-utiliser les sources plus tard (par exemple, dans le chapitre 6,
ré-utiliser les sources compilés lors du chapitre 5), il est possible que cela
ne fonctionne pas de la manière attendue. En effet, les sources utilisés au
chapitre 5 auront des paramètres de configuration propres à la distribution
hôte que vous avez utilisé, qui ne sont pas toujours applicables au système
LFS après être rentré dans l'environnement chroot. Même l'utilisation de la
commande <emphasis>make clean</emphasis> ne garantie pas toujours le nettoyage
complet des sources.</para>
 
<para>Pensez donc à vous éviter nombre d'ennuis, et supprimez simplement le
répertoire contenant les sources après installation.</para>
 
<para>Il est cependant un cas d'exception à cette règle, c'est celui des
sources du noyau. Gardez le dans un coin, car vous en aurez besoin plus tard
pour compiler un noyau. Aucun package n'utilise les sources du noyau, donc
celles-ci ne seront pas un obstacle.</para>
 
</sect1>
 
/tags/cvs/lfs/chapter02/download.xml
0,0 → 1,22
<sect1 id="ch02-download">
<title>Comment télécharger les logiciels</title>
<?dbhtml filename="download.html" dir="chapter02"?>
 
<para>Tout au long de ce document, nous supposerons que vous avez placé les
packages dans le répertoire $LFS/usr/src.</para>
 
<para>Vous pourriez par exemple choisir comme convention d'avoir un répertoire
$LFS/usr/src/sources, dans lequel vous pourriez créer des répertoires 0-9 et
a à z. Un package tel que sysvinit-&sysvinit-version;.tar.bz2 serait alors placé
dans $LFS/usr/src/sources/s/. Le package bash-&bash-version;.tar.bz2 serait
quant à lui dans $LFS/usr/src/sources/b/, et ainsi de suite.</para>
 
<para>
Le chapitre suivant contient la liste de tous les packages que vous devez
télécharger, mais la partition devant héberger votre système LFS n'a pas
encore été créée. Les fichiers seront donc stockés temporairement ailleurs,
libre à vous de décider où, et ce ne sera qu'à la fin du chapitre décrivant
la préparation de cette partition que vous les déplacerez dans le répertoire
$LFS/usr/src/.</para>
 
</sect1>
/tags/cvs/lfs/chapter02/chapter2.xml
0,0 → 1,12
<chapter id="chapter02">
<title>Informations importantes</title>
<?dbhtml filename="chapter02.html" dir="chapter02"?>
 
&c2-aboutlfs;
&c2-download;
&c2-install;
&c2-platform;
&c2-askforhelp;
&c2-commands;
 
</chapter>
/tags/cvs/lfs/chapter02/askforhelp.xml
0,0 → 1,84
<sect1 id="ch02-askforhelp">
<title>Comment demander de l'aide</title>
<?dbhtml filename="askforhelp.html" dir="chapter02"?>
 
<para>Si vous rencontrez des problèmes en utilisant ce livre, vous vous rendrez
compte que les personnes sur IRC et sur les listes de discussion seront prêt à
vous aider. Vous trouverez la liste des listes de discussion
dans <xref linkend="ch01-maillists"/>. Pour nous permettre de vous aider, vous
devrez cependant vous assurer d'avoir le plus possible d'informations sur le
problème, afin de pouvoir diagnostiquer le problème et lui apporter une solution.
Cette partie du livre va vous indiquer le type d'informations utiles.</para>
 
<sect2>
<title>Information de base</title>
<para>Tout d'abord, nous aurons besoin d'une explication rapide du problème.
Les choses essentielles à inclure sont :</para>
 
<itemizedlist>
<listitem><para>la version du livre que vous utilisez, c'est-à-dire &version;</para></listitem>
<listitem><para>avec quel package ou section vous aves un problème</para></listitem>
<listitem><para>quel est le message d'erreur exact, ou quel symptôme, que vous recevez</para></listitem>
<listitem><para>si vous vous êtes éloigné du livre ou non.</para></listitem>
</itemizedlist>
 
<para>Notez que dire que vous vous êtes éloigné du livre ne signifie pas
que nous ne vous aiderons pas, car après tout la LFS est justement un
ensemble de choix. Cela nous aidera simplement à voir les autres causes
possibles à votre problème.</para>
 
</sect2>
 
<sect2>
<title>Problèmes de configuration</title>
 
<para>Quand quelque chose se passe mal pendant l'étape où le script
configure est lancé, regardez dans les dernières lignes du fichier
<filename>config.log</filename>. Il contient les erreurs possibles
qui ont été rencontrées pendant la phase de configuration, et qui
ne sont pas toujours affichées à l'écran. Incluez les lignes appropriées
si vous décidez de demander de l'aide.</para>
 
</sect2>
 
<sect2>
<title>Problèmes de compilation</title>
 
<para>Pour nous aider à trouver la cause du problème, à la fois les
textes affichés à l'écran et le contenu de plusieurs fichiers sont
utiles. Les informations affichées par à la fois le script ./configure
et la commande make peuvent être utiles. N'incluez pas aveuglément
l'ensemble, mais d'un autre côté n'en donnez pas trop peu. A titre
d'exemple, voici l'affichage d'une commande make :</para>
 
<para><screen>gcc -DALIASPATH=\"/mnt/lfs/usr/share/locale:.\"
-DLOCALEDIR=\"/mnt/lfs/usr/share/locale\" -DLIBDIR=\"/mnt/lfs/usr/lib\"
-DINCLUDEDIR=\"/mnt/lfs/usr/include\" -DHAVE_CONFIG_H -I. -I.
-g -O2 -c getopt1.c
gcc -g -O2 -static -o make ar.o arscan.o commands.o dir.o expand.o file.o
function.o getopt.o implicit.o job.o main.o misc.o read.o remake.o rule.o
signame.o variable.o vpath.o default.o remote-stub.o version.o opt1.o
-lutil job.o: In function `load_too_high':
/lfs/tmp/make-3.79.1/job.c:1565: undefined reference to `getloadavg'
collect2: ld returned 1 exit status
make[2]: *** [make] Error 1
make[2]: Leaving directory `/lfs/tmp/make-3.79.1'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/lfs/tmp/make-3.79.1'
make: *** [all-recursive-am] Error 2</screen></para>
 
<para>Dans ce genre de cas, nombreuses sont les personnes qui ne
fournissent que la section du bas contenant le texte
<screen>make [2]: *** [make] Error 1</screen> jusqu'en bas.
Cela n'est pas suffisant pour émettre un diagnostique sur le
problème, car cela nous signale que <emphasis>quelque chose</emphasis>
s'est mal passé, mais pas <emphasis>ce qui</emphasis> s'est mal passé.
La section complète, comme fournie ci-dessus, constitue ce qui doit
être inclus pour nous être utile, car il inclut la commande qui a été
exécutée avec son message d'erreur.</para>
 
</sect2>
 
</sect1>
 
/tags/cvs/lfs/chapter02/aboutlfs.xml
0,0 → 1,46
<sect1 id="ch02-aboutlfs">
<title>A propos de $LFS</title>
<?dbhtml filename="aboutlfs.html" dir="chapter02"?>
 
<para>S'il vous plait, lisez ce paragraphe attentivement : tout au long de ce livre,
la variable $LFS sera utilisée fréquemment. Vous devrez la remplacer partout
où vous la trouverez par le répertoire dans lequel vous avez monté la partition qui
contient votre système LFS. La méthode pour créer et l'endroit où monter cette partition
seront expliqués en détail au chapitre 4. A titre d'exemple, supposons que la partition LFS soit montée dans le
répertoire /mnt/lfs.</para>
 
<para>Quand il est demandé de lancer une commande telle que
<userinput>./configure --prefix=$LFS</userinput>, il vous faut en pratique
exécuter <userinput>./configure --prefix=/mnt/lfs</userinput></para>
 
<para>Il est très important que cela soit fait quel que soit l'endroit où vous
le lisez, que ce soit pour une commande à donner à un shell ou dans un
fichier édité ou créé.</para>
 
<para>Une solution possible est de définir la variable d'environnement LFS.
De cette façon, $LFS peut être tapé directement au lieu de le remplacer par /mnt/lfs.
Cela peut être accomplit en exécutant la commande
<userinput>export LFS=/mnt/lfs</userinput>.</para>
 
<para>A partir de ce moment, lorsqu'il vous sera demandé d'entrer une
commande telle que <userinput>./configure --prefix=$LFS</userinput> vous
pourrez la taper littéralement. Votre shell fera le remplacement de
$LFS par /mnt/lfs lors de l'analyse de la ligne de commande (c'est-à-dire après
avoir appuyé sur la touche Entrée).</para>
 
<para>Si vous décidez d'utiliser cette méthode pour $LFS, n'oubliez pas de
définir cette variable à chaque fois. Si la variable n'a pas été définie mais
qu'elle est utilisée dans une commande, $LFS sera remplacée par rien, et la
commande résultante sera tout de même exécutée. Une commande telle que
<userinput>echo "root:x:0:0:root:/root:/bin/bash" &gt;
$LFS/etc/passwd</userinput> avec la variable non définie va effacer et
re-créer le fichier /etc/passwd de votre système courant. En clair : vous
aurez perdu la base des utilisateurs sur votre machine !</para>
 
<para>Une bonne méthode pour s'assurer que la variable $LFS est définie à
chaque fois consiste à la définir dans le fichier /root/.bash_profile et
le fichier /root/.bashrc afin qu'à chacune de vos connections (ou sessions par 'su') vers
le compte root, la variable $LFS soit définie.</para>
 
</sect1>
 
/tags/cvs/lfs/chapter03/reiserfs.xml
0,0 → 1,4
Reiserfsprogs (&reiserfs-version;) - &reiserfs-size;:
<ulink url="&ftp;/reiserfsprogs-&reiserfs-version;.tar.bz2">&ftp;/reiserfsprogs-&reiserfs-version;.tar.bz2</ulink>
<ulink url="&http;/reiserfsprogs-&reiserfs-version;.tar.bz2">&http;/reiserfsprogs-&reiserfs-version;.tar.bz2</ulink>
 
/tags/cvs/lfs/chapter03/gettext.xml
0,0 → 1,4
Gettext (&gettext-version;) - &gettext-size;:
<ulink url="&ftp;/gettext-&gettext-version;.tar.bz2">&ftp;/gettext-&gettext-version;.tar.bz2</ulink>
<ulink url="&http;/gettext-&gettext-version;.tar.bz2">&http;/gettext-&gettext-version;.tar.bz2</ulink>
 
/tags/cvs/lfs/chapter03/shellutils-patch.xml
0,0 → 1,4
Patch de Sh-utils (&sh-utils-version;) - &sh-utils-patch-size;:
<ulink url="&ftp;/sh-utils-&sh-utils-version;.patch.bz2">&ftp;/sh-utils-&sh-utils-version;.patch.bz2</ulink>
<ulink url="&http;/sh-utils-&sh-utils-version;.patch.bz2">&http;/sh-utils-&sh-utils-version;.patch.bz2</ulink>
 
/tags/cvs/lfs/chapter03/diffutils.xml
0,0 → 1,4
Diff Utils (&diffutils-version;) - &diffutils-size;:
<ulink url="&ftp;/diffutils-&diffutils-version;.tar.bz2">&ftp;/diffutils-&diffutils-version;.tar.bz2</ulink>
<ulink url="&http;/diffutils-&diffutils-version;.tar.bz2">&http;/diffutils-&diffutils-version;.tar.bz2</ulink>
 
/tags/cvs/lfs/chapter03/gcc-patch.xml
0,0 → 1,4
Patch de GCC (&gcc-patch-version;) - &gcc-patch-size;:
<ulink url="&ftp;/gcc-&gcc-patch-version;.patch.bz2">&ftp;/gcc-&gcc-patch-version;.patch.bz2</ulink>
<ulink url="&http;/gcc-&gcc-patch-version;.patch.bz2">&http;/gcc-&gcc-patch-version;.patch.bz2</ulink>
 
/tags/cvs/lfs/chapter03/netkitbase.xml
0,0 → 1,4
Netkit-base (&netkit-base-version;) - &netkit-base-size;:
<ulink url="&ftp;/netkit-base-&netkit-base-version;.tar.bz2">&ftp;/netkit-base-&netkit-base-version;.tar.bz2</ulink>
<ulink url="&http;/netkit-base-&netkit-base-version;.tar.bz2">&http;/netkit-base-&netkit-base-version;.tar.bz2</ulink>
 
/tags/cvs/lfs/chapter03/toplevel.xml
0,0 → 1,6
Explorer avec FTP:
<ulink url="&ftp-root;/">&ftp-root;/</ulink>
 
Explorer avec HTTP:
<ulink url="&http-root;/">&http-root;/</ulink>
 
/tags/cvs/lfs/chapter03/utillinux.xml
0,0 → 1,4
Util Linux (&util-linux-version;) - &util-linux-size;:
<ulink url="&ftp;/util-linux-&util-linux-version;.tar.bz2">&ftp;/util-linux-&util-linux-version;.tar.bz2</ulink>
<ulink url="&http;/util-linux-&util-linux-version;.tar.bz2">&http;/util-linux-&util-linux-version;.tar.bz2</ulink>
 
/tags/cvs/lfs/chapter03/mawk.xml
0,0 → 1,4
Mawk (&mawk-version;) - &mawk-size;:
<ulink url="&ftp;/mawk&mawk-version;.tar.bz2">&ftp;/mawk&mawk-version;.tar.bz2</ulink>
<ulink url="&http;/mawk&mawk-version;.tar.bz2">&http;/mawk&mawk-version;.tar.bz2</ulink>
 
/tags/cvs/lfs/chapter03/kbd.xml
0,0 → 1,4
Kbd (&kbd-version;) - &kbd-size;:
<ulink url="&ftp;/kbd-&kbd-version;.tar.bz2">&ftp;/kbd-&kbd-version;.tar.bz2</ulink>
<ulink url="&http;/kbd-&kbd-version;.tar.bz2">&http;/kbd-&kbd-version;.tar.bz2</ulink>
 
/tags/cvs/lfs/chapter03/perl.xml
0,0 → 1,4
Perl (&perl-version;) - &perl-size;:
<ulink url="&ftp;/perl-&perl-version;.tar.bz2">&ftp;/perl-&perl-version;.tar.bz2</ulink>
<ulink url="&http;/perl-&perl-version;.tar.bz2">&http;/perl-&perl-version;.tar.bz2</ulink>
 
/tags/cvs/lfs/chapter03/libtool.xml
0,0 → 1,4
Libtool (&libtool-version;) - &libtool-size;:
<ulink url="&ftp;/libtool-&libtool-version;.tar.bz2">&ftp;/libtool-&libtool-version;.tar.bz2</ulink>
<ulink url="&http;/libtool-&libtool-version;.tar.bz2">&http;/libtool-&libtool-version;.tar.bz2</ulink>
 
/tags/cvs/lfs/chapter03/makedev.xml
0,0 → 1,4
MAKEDEV (&makedev-version;) - &makedev-size;:
<ulink url="&ftp;/MAKEDEV-&makedev-version;.bz2">&ftp;/MAKEDEV-&makedev-version;.bz2</ulink>
<ulink url="&http;/MAKEDEV-&makedev-version;.bz2">&http;/MAKEDEV-&makedev-version;.bz2</ulink>
 
/tags/cvs/lfs/chapter03/texinfo.xml
0,0 → 1,4
Texinfo (&texinfo-version;) - &texinfo-size;:
<ulink url="&ftp;/texinfo-&texinfo-version;.tar.bz2">&ftp;/texinfo-&texinfo-version;.tar.bz2</ulink>
<ulink url="&http;/texinfo-&texinfo-version;.tar.bz2">&http;/texinfo-&texinfo-version;.tar.bz2</ulink>
 
/tags/cvs/lfs/chapter03/kernel.xml
0,0 → 1,4
Noyau Linux (&kernel-version;) - &kernel-size;:
<ulink url="&ftp;/linux-&kernel-version;.tar.bz2">&ftp;/linux-&kernel-version;.tar.bz2</ulink>
<ulink url="&http;/linux-&kernel-version;.tar.bz2">&http;/linux-&kernel-version;.tar.bz2</ulink>
 
/tags/cvs/lfs/chapter03/m4.xml
0,0 → 1,4
M4 (&m4-version;) - &m4-size;:
<ulink url="&ftp;/m4-&m4-version;.tar.bz2">&ftp;/m4-&m4-version;.tar.bz2</ulink>
<ulink url="&http;/m4-&m4-version;.tar.bz2">&http;/m4-&m4-version;.tar.bz2</ulink>
 
/tags/cvs/lfs/chapter03/tar-patch.xml
0,0 → 1,4
Patch de Tar (&tar-version;) - &tar-patch-size;:
<ulink url="&ftp;/tar-1.13.patch.bz2">&ftp;/tar-1.13.patch.bz2</ulink>
<ulink url="&http;/tar-1.13.patch.bz2">&http;/tar-1.13.patch.bz2</ulink>
 
/tags/cvs/lfs/chapter03/sysvinit.xml
0,0 → 1,4
Sysvinit (&sysvinit-version;) - &sysvinit-size;:
<ulink url="&ftp;/sysvinit-&sysvinit-version;.tar.bz2">&ftp;/sysvinit-&sysvinit-version;.tar.bz2</ulink>
<ulink url="&http;/sysvinit-&sysvinit-version;.tar.bz2">&http;/sysvinit-&sysvinit-version;.tar.bz2</ulink>
 
/tags/cvs/lfs/chapter03/shellutils.xml
0,0 → 1,4
Sh-utils (&sh-utils-version;) - &sh-utils-size;:
<ulink url="&ftp;/sh-utils-&sh-utils-version;.tar.bz2">&ftp;/sh-utils-&sh-utils-version;.tar.bz2</ulink>
<ulink url="&http;/sh-utils-&sh-utils-version;.tar.bz2">&http;/sh-utils-&sh-utils-version;.tar.bz2</ulink>
 
/tags/cvs/lfs/chapter03/gcc.xml
0,0 → 1,4
GCC (&gcc-version;) - &gcc-size;:
<ulink url="&ftp;/gcc-&gcc-version;.tar.bz2">&ftp;/gcc-&gcc-version;.tar.bz2</ulink>
<ulink url="&http;/gcc-&gcc-version;.tar.bz2">&http;/gcc-&gcc-version;.tar.bz2</ulink>
 
/tags/cvs/lfs/chapter03/sysklogd.xml
0,0 → 1,4
Sysklogd (&sysklogd-version;) - &sysklogd-size;:
<ulink url="&ftp;/sysklogd-&sysklogd-version;.tar.bz2">&ftp;/sysklogd-&sysklogd-version;.tar.bz2</ulink>
<ulink url="&http;/sysklogd-&sysklogd-version;.tar.bz2">&http;/sysklogd-&sysklogd-version;.tar.bz2</ulink>
 
/tags/cvs/lfs/chapter03/patch.xml
0,0 → 1,4
Patch (&patch-version;) - &patch-size;:
<ulink url="&ftp;/patch-&patch-version;.tar.bz2">&ftp;/patch-&patch-version;.tar.bz2</ulink>
<ulink url="&http;/patch-&patch-version;.tar.bz2">&http;/patch-&patch-version;.tar.bz2</ulink>
 
/tags/cvs/lfs/chapter03/modutils.xml
0,0 → 1,4
Modutils (&modutils-version;) - &modutils-size;:
<ulink url="&ftp;/modutils-&modutils-version;.tar.bz2">&ftp;/modutils-&modutils-version;.tar.bz2</ulink>
<ulink url="&http;/modutils-&modutils-version;.tar.bz2">&http;/modutils-&modutils-version;.tar.bz2</ulink>
 
/tags/cvs/lfs/chapter03/groff.xml
0,0 → 1,4
Groff (&groff-version;) - &groff-size;:
<ulink url="&ftp;/groff-&groff-version;.tar.bz2">&ftp;/groff-&groff-version;.tar.bz2</ulink>
<ulink url="&http;/groff-&groff-version;.tar.bz2">&http;/groff-&groff-version;.tar.bz2</ulink>
 
/tags/cvs/lfs/chapter03/less.xml
0,0 → 1,4
Less (&less-version;) - &less-size;:
<ulink url="&ftp;/less-&less-version;.tar.bz2">&ftp;/less-&less-version;.tar.bz2</ulink>
<ulink url="&http;/less-&less-version;.tar.bz2">&http;/less-&less-version;.tar.bz2</ulink>
 
/tags/cvs/lfs/chapter03/nettools.xml
0,0 → 1,4
Net-tools (&net-tools-version;) - &net-tools-size;:
<ulink url="&ftp;/net-tools-&net-tools-version;.tar.bz2">&ftp;/net-tools-&net-tools-version;.tar.bz2</ulink>
<ulink url="&http;/net-tools-&net-tools-version;.tar.bz2">&http;/net-tools-&net-tools-version;.tar.bz2</ulink>
 
/tags/cvs/lfs/chapter03/chapter3.xml
0,0 → 1,9
<chapter id="chapter03">
<title>Packages qui doivent être téléchargés</title>
<?dbhtml filename="chapter03.html" dir="chapter03"?>
 
&c3-introduction;
&c3-packages;
 
</chapter>
 
/tags/cvs/lfs/chapter03/procinfo.xml
0,0 → 1,4
Procinfo (&procinfo-version;) - &procinfo-size;:
<ulink url="&ftp;/procinfo-&procinfo-version;.tar.bz2">&ftp;/procinfo-&procinfo-version;.tar.bz2</ulink>
<ulink url="&http;/procinfo-&procinfo-version;.tar.bz2">&http;/procinfo-&procinfo-version;.tar.bz2</ulink>
 
/tags/cvs/lfs/chapter03/introduction.xml
0,0 → 1,36
<sect1 id="ch03-introduction">
<title>Introduction</title>
<?dbhtml filename="introduction.html" dir="chapter03"?>
 
<para>
Ci-dessous, se trouve une liste de tous les paquetages à télécharger pour construire le système
de base. Les numéros de version affichés correspondent à des versions de logiciel qui
fonctionnent, et qui sont la base du livre. Si vous rencontrez des problèmes que vous
ne pouvez résoudre vous-même, veuillez télécharger dans ce cas la version indiquée
par le livre (au cas où vous auriez téléchargé une version plus récente).
</para>
 
<para>
Toutes les URLs ci-dessous appartiennent au serveur ftp.linuxfromscratch.org. Nous
avons quelques miroirs FTP disponibles, à partir desquels vous pouvez aussi télécharger les fichiers.
Les adresses des sites miroirs peuvent être trouvé sur <xref linkend="ch01-version"/>.
</para>
 
<para>
Nous avons fourni une liste des sites officiels de téléchargement des packages
dans <xref linkend="appendixa"/>. L'archive LFS FTP ne contient que les versions des
paquetages recommandées par ce livre. Vous avez toujours la possibilite de consulter
les sites officiels dans l'Annexe A afin de vérifier s'il existe une nouvelle version.
Pour ceux qui téléchargeront une version plus récente, nous apprécierions énormement
de savoir si vous êtes parvenus ou non à installer cette version, grâce aux instructions
de ce livre.
</para>
 
<para>
Prenez note que tous les fichiers téléchargés de l'archive LFS FTP sont
compressés avec bzip2 au lieu de gzip. Si vous ne savez pas comment
utiliser les fichiers bz2, veuillez vous reporter à <xref linkend="ch02-install"/>.
</para>
 
</sect1>
 
/tags/cvs/lfs/chapter03/tar.xml
0,0 → 1,4
Tar (&tar-version;) - &tar-size;:
<ulink url="&ftp;/tar-&tar-version;.tar.bz2">&ftp;/tar-&tar-version;.tar.bz2</ulink>
<ulink url="&http;/tar-&tar-version;.tar.bz2">&http;/tar-&tar-version;.tar.bz2</ulink>
 
/tags/cvs/lfs/chapter03/bzip2.xml
0,0 → 1,4
Bzip2 (&bzip2-version;) - &bzip2-size;:
<ulink url="&ftp;/bzip2-&bzip2-version;.tar.bz2">&ftp;/bzip2-&bzip2-version;.tar.bz2</ulink>
<ulink url="&http;/bzip2-&bzip2-version;.tar.bz2">&http;/bzip2-&bzip2-version;.tar.bz2</ulink>
 
/tags/cvs/lfs/chapter03/ed.xml
0,0 → 1,4
Ed (&ed-version;) - &ed-size;:
<ulink url="&ftp;/ed-&ed-version;.tar.bz2">&ftp;/ed-&ed-version;.tar.bz2</ulink>
<ulink url="&http;/ed-&ed-version;.tar.bz2">&http;/ed-&ed-version;.tar.bz2</ulink>
 
/tags/cvs/lfs/chapter03/binutils.xml
0,0 → 1,4
Binutils (&binutils-version;) - &binutils-size;:
<ulink url="&ftp;/binutils-&binutils-version;.tar.bz2">&ftp;/binutils-&binutils-version;.tar.bz2</ulink>
<ulink url="&http;/binutils-&binutils-version;.tar.bz2">&http;/binutils-&binutils-version;.tar.bz2</ulink>
 
/tags/cvs/lfs/chapter03/manpages.xml
0,0 → 1,4
Man-pages (&man-pages-version;) - &man-pages-size;:
<ulink url="&ftp;/man-pages-&man-pages-version;.tar.bz2">&ftp;/man-pages-&man-pages-version;.tar.bz2</ulink>
<ulink url="&http;/man-pages-&man-pages-version;.tar.bz2">&http;/man-pages-&man-pages-version;.tar.bz2</ulink>
 
/tags/cvs/lfs/chapter03/vim.xml
0,0 → 1,4
Vim (&vim-version;) - &vim-size;:
<ulink url="&ftp;/vim-&vim-version;.tar.bz2">&ftp;/vim-&vim-version;.tar.bz2</ulink>
<ulink url="&http;/vim-&vim-version;.tar.bz2">&http;/vim-&vim-version;.tar.bz2</ulink>
 
/tags/cvs/lfs/chapter03/grep.xml
0,0 → 1,4
Grep (&grep-version;) - &grep-size;:
<ulink url="&ftp;/grep-&grep-version;.tar.bz2">&ftp;/grep-&grep-version;.tar.bz2</ulink>
<ulink url="&http;/grep-&grep-version;.tar.bz2">&http;/grep-&grep-version;.tar.bz2</ulink>
 
/tags/cvs/lfs/chapter03/lilo.xml
0,0 → 1,4
Lilo (&lilo-version;) - &lilo-size;:
<ulink url="&ftp;/lilo-&lilo-version;.tar.bz2">&ftp;/lilo-&lilo-version;.tar.bz2</ulink>
<ulink url="&http;/lilo-&lilo-version;.tar.bz2">&http;/lilo-&lilo-version;.tar.bz2</ulink>
 
/tags/cvs/lfs/chapter03/findutils.xml
0,0 → 1,4
Find Utils (&findutils-version;) - &findutils-size;:
<ulink url="&ftp;/findutils-&findutils-version;.tar.bz2">&ftp;/findutils-&findutils-version;.tar.bz2</ulink>
<ulink url="&http;/findutils-&findutils-version;.tar.bz2">&http;/findutils-&findutils-version;.tar.bz2</ulink>
 
/tags/cvs/lfs/chapter03/procps.xml
0,0 → 1,4
Procps (&procps-version;) - &procps-size;:
<ulink url="&ftp;/procps-&procps-version;.tar.bz2">&ftp;/procps-&procps-version;.tar.bz2</ulink>
<ulink url="&http;/procps-&procps-version;.tar.bz2">&http;/procps-&procps-version;.tar.bz2</ulink>
 
/tags/cvs/lfs/chapter03/automake.xml
0,0 → 1,4
Automake (&automake-version;) - &automake-size;:
<ulink url="&ftp;/automake-&automake-version;.tar.bz2">&ftp;/automake-&automake-version;.tar.bz2</ulink>
<ulink url="&http;/automake-&automake-version;.tar.bz2">&http;/automake-&automake-version;.tar.bz2</ulink>
 
/tags/cvs/lfs/chapter03/all.xml
0,0 → 1,11
Vous pouvez soit télécharger une archive tar qui contient tous les packages
utilisés pour compiler un système LFS:
 
 
Tous les packages LFS - &all-size-kb;:
<ulink url="&ftp;/lfs-packages-&all-version;.tar">&ftp;/lfs-packages-&all-version;.tar</ulink>
<ulink url="&http;/lfs-packages-&all-version;.tar">&http;/lfs-packages-&all-version;.tar</ulink>
 
 
Soit télécharger individuellement les packages suivants:
 
/tags/cvs/lfs/chapter03/gzip.xml
0,0 → 1,4
Gzip (&gzip-version;) - &gzip-size;:
<ulink url="&ftp;/gzip-&gzip-version;.tar.bz2">&ftp;/gzip-&gzip-version;.tar.bz2</ulink>
<ulink url="&http;/gzip-&gzip-version;.tar.bz2">&http;/gzip-&gzip-version;.tar.bz2</ulink>
 
/tags/cvs/lfs/chapter03/bash.xml
0,0 → 1,4
Bash (&bash-version;) - &bash-size;:
<ulink url="&ftp;/bash-&bash-version;.tar.bz2">&ftp;/bash-&bash-version;.tar.bz2</ulink>
<ulink url="&http;/bash-&bash-version;.tar.bz2">&http;/bash-&bash-version;.tar.bz2</ulink>
 
/tags/cvs/lfs/chapter03/glibc.xml
0,0 → 1,4
Glibc (&glibc-version;) - &glibc-size;:
<ulink url="&ftp;/glibc-&glibc-version;.tar.bz2">&ftp;/glibc-&glibc-version;.tar.bz2</ulink>
<ulink url="&http;/glibc-&glibc-version;.tar.bz2">&http;/glibc-&glibc-version;.tar.bz2</ulink>
 
/tags/cvs/lfs/chapter03/ncurses.xml
0,0 → 1,4
Ncurses (&ncurses-version;) - &ncurses-size;:
<ulink url="&ftp;/ncurses-&ncurses-version;.tar.bz2">&ftp;/ncurses-&ncurses-version;.tar.bz2</ulink>
<ulink url="&http;/ncurses-&ncurses-version;.tar.bz2">&http;/ncurses-&ncurses-version;.tar.bz2</ulink>
 
/tags/cvs/lfs/chapter03/bin86.xml
0,0 → 1,4
Bin86 (&bin86-version;) - &bin86-size;:
<ulink url="&ftp;/bin86-&bin86-version;.tar.bz2">&ftp;/bin86-&bin86-version;.tar.bz2</ulink>
<ulink url="&http;/bin86-&bin86-version;.tar.bz2">&http;/bin86-&bin86-version;.tar.bz2</ulink>
 
/tags/cvs/lfs/chapter03/kbd-patch.xml
0,0 → 1,4
Kbd Patch (&kbd-patch-version;) - &kbd-patch-size;:
<ulink url="&ftp;/kbd-&kbd-patch-version;.patch.bz2">&ftp;/kbd-&kbd-patch-version;.patch.bz2</ulink>
<ulink url="&http;/kbd-&kbd-patch-version;.patch.bz2">&http;/kbd-&kbd-patch-version;.patch.bz2</ulink>
 
/tags/cvs/lfs/chapter03/psmisc.xml
0,0 → 1,4
Psmisc (&psmisc-version;) - &psmisc-size;:
<ulink url="&ftp;/psmisc-&psmisc-version;.tar.bz2">&ftp;/psmisc-&psmisc-version;.tar.bz2</ulink>
<ulink url="&http;/psmisc-&psmisc-version;.tar.bz2">&http;/psmisc-&psmisc-version;.tar.bz2</ulink>
 
/tags/cvs/lfs/chapter03/findutils-patch.xml
0,0 → 1,4
Patch de Find Utils (&findutils-version;) - &findutils-patch-size;:
<ulink url="&ftp;/findutils-&findutils-version;.patch.bz2">&ftp;/findutils-&findutils-version;.patch.bz2</ulink>
<ulink url="&http;/findutils-&findutils-version;.patch.bz2">&http;/findutils-&findutils-version;.patch.bz2</ulink>
 
/tags/cvs/lfs/chapter03/flex.xml
0,0 → 1,4
Flex (&flex-version;) - &flex-size;:
<ulink url="&ftp;/flex-&flex-version;.tar.bz2">&ftp;/flex-&flex-version;.tar.bz2</ulink>
<ulink url="&http;/flex-&flex-version;.tar.bz2">&http;/flex-&flex-version;.tar.bz2</ulink>
 
/tags/cvs/lfs/chapter03/fileutils.xml
0,0 → 1,4
File Utils (&fileutils-version;) - &fileutils-size;:
<ulink url="&ftp;/fileutils-&fileutils-version;.tar.bz2">&ftp;/fileutils-&fileutils-version;.tar.bz2</ulink>
<ulink url="&http;/fileutils-&fileutils-version;.tar.bz2">&http;/fileutils-&fileutils-version;.tar.bz2</ulink>
 
/tags/cvs/lfs/chapter03/shadowpwd.xml
0,0 → 1,4
Kit Shadow Password (&shadow-version;) - &shadow-size;:
<ulink url="&ftp;/shadow-&shadow-version;.tar.bz2">&ftp;/shadow-&shadow-version;.tar.bz2</ulink>
<ulink url="&http;/shadow-&shadow-version;.tar.bz2">&http;/shadow-&shadow-version;.tar.bz2</ulink>
 
/tags/cvs/lfs/chapter03/textutils.xml
0,0 → 1,4
Text Utils (&textutils-version;) - &textutils-size;:
<ulink url="&ftp;/textutils-&textutils-version;.tar.bz2">&ftp;/textutils-&textutils-version;.tar.bz2</ulink>
<ulink url="&http;/textutils-&textutils-version;.tar.bz2">&http;/textutils-&textutils-version;.tar.bz2</ulink>
 
/tags/cvs/lfs/chapter03/gzip-patch.xml
0,0 → 1,4
Patch de Gzip (&gzip-version;) - &gzip-patch-size;:
<ulink url="&ftp;/gzip-&gzip-version;.patch.bz2">&ftp;/gzip-&gzip-version;.patch.bz2</ulink>
<ulink url="&http;/gzip-&gzip-version;.patch.bz2">&http;/gzip-&gzip-version;.patch.bz2</ulink>
 
/tags/cvs/lfs/chapter03/glibc-threads.xml
0,0 → 1,4
Glibc-linuxthreads (&glibc-version;) - &glibc-threads-size;:
<ulink url="&ftp;/glibc-linuxthreads-&glibc-version;.tar.bz2">&ftp;/glibc-linuxthreads-&glibc-version;.tar.bz2</ulink>
<ulink url="&http;/glibc-linuxthreads-&glibc-version;.tar.bz2">&http;/glibc-linuxthreads-&glibc-version;.tar.bz2</ulink>
 
/tags/cvs/lfs/chapter03/bison.xml
0,0 → 1,4
Bison (&bison-version;) - &bison-size;:
<ulink url="&ftp;/bison-&bison-version;.tar.bz2">&ftp;/bison-&bison-version;.tar.bz2</ulink>
<ulink url="&http;/bison-&bison-version;.tar.bz2">&http;/bison-&bison-version;.tar.bz2</ulink>
 
/tags/cvs/lfs/chapter03/e2fsprogs.xml
0,0 → 1,4
E2fsprogs (&e2fsprogs-version;) - &e2fsprogs-size;:
<ulink url="&ftp;/e2fsprogs-&e2fsprogs-version;.tar.bz2">&ftp;/e2fsprogs-&e2fsprogs-version;.tar.bz2</ulink>
<ulink url="&http;/e2fsprogs-&e2fsprogs-version;.tar.bz2">&http;/e2fsprogs-&e2fsprogs-version;.tar.bz2</ulink>
 
/tags/cvs/lfs/chapter03/bootscripts.xml
0,0 → 1,4
LFS-Bootscripts (&bootscripts-version;) - &bootscripts-size;:
<ulink url="&ftp;/lfs-bootscripts-&bootscripts-version;.tar.bz2">&ftp;/lfs-bootscripts-&bootscripts-version;.tar.bz2</ulink>
<ulink url="&http;/lfs-bootscripts-&bootscripts-version;.tar.bz2">&http;/lfs-bootscripts-&bootscripts-version;.tar.bz2</ulink>
 
/tags/cvs/lfs/chapter03/man.xml
0,0 → 1,4
Man (&man-version;) - &man-size;:
<ulink url="&ftp;/man-&man-version;.tar.bz2">&ftp;/man-&man-version;.tar.bz2</ulink>
<ulink url="&http;/man-&man-version;.tar.bz2">&http;/man-&man-version;.tar.bz2</ulink>
 
/tags/cvs/lfs/chapter03/sed.xml
0,0 → 1,4
Sed (&sed-version;) - &sed-size;:
<ulink url="&ftp;/sed-&sed-version;.tar.bz2">&ftp;/sed-&sed-version;.tar.bz2</ulink>
<ulink url="&http;/sed-&sed-version;.tar.bz2">&http;/sed-&sed-version;.tar.bz2</ulink>
 
/tags/cvs/lfs/chapter03/make.xml
0,0 → 1,4
Make (&make-version;) - &make-size;:
<ulink url="&ftp;/make-&make-version;.tar.bz2">&ftp;/make-&make-version;.tar.bz2</ulink>
<ulink url="&http;/make-&make-version;.tar.bz2">&http;/make-&make-version;.tar.bz2</ulink>
 
/tags/cvs/lfs/chapter03/autoconf.xml
0,0 → 1,4
Autoconf (&autoconf-version;) - &autoconf-size;:
<ulink url="&ftp;/autoconf-&autoconf-version;.tar.bz2">&ftp;/autoconf-&autoconf-version;.tar.bz2</ulink>
<ulink url="&http;/autoconf-&autoconf-version;.tar.bz2">&http;/autoconf-&autoconf-version;.tar.bz2</ulink>
 
/tags/cvs/lfs/chapter03/packages.xml
0,0 → 1,72
<sect1 id="ch03-packages">
<title>Packages qui doivent être téléchargés</title>
<?dbhtml filename="packages.html" dir="chapter03"?>
 
<literallayout>
&c3-toplevel;
&c3-all;
&c3-bash;
&c3-binutils;
&c3-bzip2;
&c3-diffutils;
&c3-fileutils;
&c3-gcc;
&c3-gcc-patch;
&c3-kernel;
&c3-grep;
&c3-gzip;
&c3-gzip-patch;
&c3-make;
&c3-sed;
&c3-shellutils;
&c3-shellutils-patch;
&c3-tar;
&c3-tar-patch;
&c3-textutils;
&c3-mawk;
&c3-texinfo;
&c3-patch;
&c3-makedev;
&c3-glibc;
&c3-glibc-threads;
&c3-manpages;
&c3-ed;
&c3-findutils;
&c3-findutils-patch;
&c3-ncurses;
&c3-vim;
&c3-bison;
&c3-less;
&c3-groff;
&c3-man;
&c3-perl;
&c3-m4;
&c3-autoconf;
&c3-automake;
&c3-flex;
&c3-file;
&c3-libtool;
&c3-bin86;
&c3-gettext;
&c3-kbd;
&c3-kbd-patch;
&c3-e2fsprogs;
&c3-lilo;
&c3-modutils;
&c3-procinfo;
&c3-procps;
&c3-psmisc;
&c3-reiserfs;
&c3-shadowpwd;
&c3-sysklogd;
&c3-sysvinit;
&c3-utillinux;
&c3-netkitbase;
&c3-nettools;
&c3-bootscripts;
 
Taille totale de tous les packages: &all-size-kb; (&all-size-mb;)
</literallayout>
 
</sect1>
 
/tags/cvs/lfs/chapter03/file.xml
0,0 → 1,5
File (&file-version;) - &file-size;:
<ulink url="&ftp;/file-&file-version;.tar.bz2">&ftp;/file-&file-version;.tar.bz2</ulink>
<ulink url="&http;/file-&file-version;.tar.bz2">&http;/file-&file-version;.tar.bz2</ulink>
 
 
/tags/cvs/lfs/book/part1.xml
0,0 → 1,9
<part id="part1">
<title>Première Partie - Introduction</title>
 
&chapter01;
&chapter02;
 
</part>
 
 
/tags/cvs/lfs/book/part2.xml
0,0 → 1,12
<part id="part2">
<title>Deuxième partie - Installation du système LFS</title>
 
&chapter03;
&chapter04;
&chapter05;
&chapter06;
&chapter07;
&chapter08;
&chapter09;
 
</part>
/tags/cvs/lfs/book/part3.xml
0,0 → 1,8
<part id="part3">
<title>Troisième Partie - Annexes</title>
 
&appendixa;
&appendixb;
 
</part>
 
/tags/cvs/lfs/book/book.xml
0,0 → 1,7
&bookinfo;
&dedication;
&preface;
 
&part1;
&part2;
&part3;
/tags/cvs/lfs/chapter04/mounting.xml
0,0 → 1,33
<sect1 id="ch04-mounting">
<title>Montage d'une nouvelle partition</title>
<?dbhtml filename="mounting.html" dir="chapter04"?>
 
<para>
Maintenant que le système de fichiers a été créé, il est prêt à être utilisé.
Tout ce que nous avons à faire pour accéder à la partition (c'est-à-dire pour
pouvoir y lire ou écrire des données), c'est de la monter.
Si vous l'avez monté sous /mnt/lfs, vous pouvez accéder à cette partition en allant au
répertoire /mnt/lfs. Nous considérerons dans ce livre que vous l'avez montée dans
/mnt/lfs. Peu importe le répertoire que vous choisirez, du moment que vous vous en
rappelez.
</para>
 
<para>
Créez le répertoire /mnt/lfs en exécutant :
</para>
 
<para><screen><userinput>mkdir -p /mnt/lfs</userinput></screen></para>
 
<para>Maintenant, montez la partition LFS en exécutant :</para>
 
<para><screen><userinput>mount /dev/xxx /mnt/lfs</userinput></screen></para>
 
<para>Remplacez <quote>xxx</quote> par l'identificateur de votre partition (tel que hda11).</para>
 
<para>
Ce répertoire (/mnt/lfs) est la variable $LFS dont nous avons déjà parlé précédemment.
Désormais si vous voulez utiliser la variable d'environnement $LFS, il vous faudra
exécuter <userinput>export LFS=/mnt/lfs</userinput> maintenant.
</para>
 
</sect1>
/tags/cvs/lfs/chapter04/introduction.xml
0,0 → 1,13
<sect1 id="ch04-introduction">
<title>Introduction</title>
<?dbhtml filename="introduction.html" dir="chapter04"?>
 
<para>
Dans ce chapitre, nous allons préparer la partition qui accueillera le système
LFS. On créera tout d'abord cette partition, puis un système de
fichiers et enfin la structure des répertoires. Après cela,
nous pourrons passer au chapitre suivant et entamer réellement le processus de construction.
</para>
 
</sect1>
 
/tags/cvs/lfs/chapter04/creatingpart.xml
0,0 → 1,44
/tags/cvs/lfs/chapter04/creatingfs.xml
0,0 → 1,20
<sect1 id="ch04-creatingfs">
<title>Création d'un système de fichiers sur la nouvelle partition</title>
<?dbhtml filename="creatingfs.html" dir="chapter04"?>
 
<para>Une fois la partition créée, nous devons créer le nouveau système de fichiers sur
cette partition. Le système de fichiers standard utilisé actuellement est le système
de fichiers ext2, mais les système de fichiers journalisés deviennent aussi de plus
en plus populaires. C'est, bien sûr, à vous de décider quel système de fichiers
vous voulez créer, mais comme nous devons travailler avec un d'entre eux,
nous considèrons que vous avez choisi le système de fichier ext2.</para>
 
<para>Pour créer un système de fichiers ext2, utilisez la commande mke2fs. La partition LFS
est la seule option nécessaire à la commande et le système de fichiers est créé.</para>
 
<para><screen><userinput>mke2fs /dev/xxx</userinput></screen></para>
 
<para>Remplacer "xxx" par le nom de la partition (telle que hda11).</para>
 
</sect1>
 
/tags/cvs/lfs/chapter04/chapter4.xml
0,0 → 1,10
<chapter id="chapter04">
<title>Préparation d'une nouvelle partition</title>
<?dbhtml filename="chapter04.html" dir="chapter04"?>
 
&c4-introduction;
&c4-creatingpart;
&c4-creatingfs;
&c4-mounting;
 
</chapter>
/tags/cvs/lfs/chapter05/introduction.xml
0,0 → 1,57
<sect1 id="ch05-introduction">
<title>Introduction</title>
<?dbhtml filename="introduction.html" dir="chapter05"?>
 
<para>
Dans les chapitres suivants, nous allons installer tous les logiciels qui
font partie d'un système Linux de base. Après en avoir terminé avec ce
chapitre et le suivant, vous aurez un système Linux pleinement fonctionnel.
Les chapitres restants traitent de la création des scripts de démarrage,
de la manière de rendre le système LFS amorçable, et de la mise en place
du réseau de base.
</para>
 
<para>
Les logiciels dans ce chapitre seront liés statiquement et seront réinstallés au
chapitre suivant avec une édition de liens dynamiques. Nous commencons par une
version statique parce qu'il est possible que notre système Linux normal et notre
système LFS n'utilisent pas la même version de bibliothèque C. Si les programmes de
la première partie étaient liés à une version ancienne de la bibliothèque C,
ces programmes pourraient ne pas bien fonctionner dans le système LFS. Une autre
raison est de résoudre les dépendances circulaires. Un exemple d'une telle
dépendance est que vous avez besoin d'un compilateur pour installer un compilateur,
et que vous allez avoir besoin d'un shell pour installer un shell et le compilateur.
</para>
 
<para>
La clef pour apprendre ce qui fait fonctionner Linux est de savoir
exactement quelle est l'utilité de chaque package et en quoi un
utilisateur ou le système en a besoin. Les descriptions du contenu
des packages sont fournies après la sous-section Installation de
chaque package, et aussi dans l'annexe A.
</para>
 
<para>
Pendant l'installation de certains packages, vous verrez très
probablement des messages d'alerte du compilateur défilant sur
votre écran. Ceci est normal et peut être ignoré sans danger. Il s'agit
seulement de messages d'avertissement (principalement au sujet d'utilisation
incorrecte, mais pas illégale, de la syntaxe de C ou de C++. C'est simplement
que, souvent, les standards du langage C ont changé, et les packages
utilisent encore le vieux standard, ce qui n'est pas un problème).
</para>
 
<para>
Avant de commencer, assurez-vous que vous avez positionné correctement
la variable LFS, si vous avez décidé de l'utiliser. Exécutez ce qui suit:
</para>
 
<para><screen><userinput>echo $LFS</userinput></screen></para>
 
<para>
Vérifiez que la sortie contient le bon répertoire vers le point de montage
de la partition LFS (/mnt/lfs par exemple).
</para>
 
</sect1>
 
/tags/cvs/lfs/chapter05/kernel-exp-headers.xml
0,0 → 1,35
<sect2>
<title>Why we copy the kernel headers and don't symlink them</title>
 
<para>In the past, it was common practice for people to symlink the
/usr/include/linux and asm directories to /usr/src/linux/include/linux
and asm respectively. This is a <emphasis>bad</emphasis> idea as
this extract from a post by Linus Torvalds to the Linux Kernel
Mailing List points out:</para>
 
<screen>I would suggest that people who compile new kernels should:
 
- not have a single symbolic link in sight (except the one that the
kernel build itself sets up, namely the "linux/include/asm" symlink
that is only used for the internal kernel compile itself)
 
And yes, this is what I do. My /usr/src/linux still has the old 2.2.13
header files, even though I haven't run a 2.2.13 kernel in a _loong_
time. But those headers were what glibc was compiled against, so those
headers are what matches the library object files.
 
And this is actually what has been the suggested environment for at
least the last five years. I don't know why the symlink business keeps
on living on, like a bad zombie. Pretty much every distribution still
has that broken symlink, and people still remember that the linux
sources should go into "/usr/src/linux" even though that hasn't been
true in a _loong_ time.</screen>
 
<para>The relevant part here is where he states that the headers should
be the ones which <emphasis>glibc was compiled against</emphasis>. These are
the headers which should remain accessible and so by copying them, we ensure
that we follow these guidelines. Also note that as long as you don't have
those symlinks, it is perfectly fine to have the kernel sources
in <filename>/usr/src/linux</filename>.</para>
 
</sect2>
/tags/cvs/lfs/chapter05/gzip-inst.xml
0,0 → 1,24
<sect2>
<title>Installation de Gzip</title>
 
<para>Avant que Gzip soit installé, le patch doit être appliqué. Ce patch est
nécessaire pour éviter un conflit de noms de variables avec les systèmes Glibc-2.0
lors de la compilation et de l'édition de liens statiques, seulement
si votre système de base tourne avec Glibc-2.0. Toutefois, il est préférable
d'utiliser ce patch même si vous utilisez une version différente de Glibc. Si vous
n'êtes pas sûr, appliquez le patch.</para>
 
<para>Appliquer le patch en lançant la commande suivante:</para>
 
<para><screen><userinput>patch -Np1 -i ../gzip-&gzip-version;.patch</userinput></screen></para>
 
<para>Installer Gzip en lançant les commandes suivantes:</para>
 
<para><screen><userinput>./configure --prefix=$LFS/usr &amp;&amp;
make LDFLAGS=-static &amp;&amp;
make install &amp;&amp;
cp $LFS/usr/bin/gunzip $LFS/usr/bin/gzip $LFS/bin &amp;&amp;
rm $LFS/usr/bin/gunzip $LFS/usr/bin/gzip</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter05/bzip2.xml
0,0 → 1,14
<sect1 id="ch05-bzip2">
<title>Installing Bzip2-&bzip2-version;</title>
<?dbhtml filename="bzip2.html" dir="chapter05"?>
 
<screen>Estimated build time: &bzip2-time-static;
Estimated required disk space: &bzip2-compsize-static;</screen>
 
&c5-bzip2-inst;
&c5-bzip2-exp;
&aa-bzip2-desc;
&aa-bzip2-dep;
 
</sect1>
 
/tags/cvs/lfs/chapter05/gcc-exp.xml
0,0 → 1,36
<sect2>
<title>Explication des commandes</title>
 
<para><userinput>patch -Np1 -i ../gcc-&gcc-patch-version;.patch:</userinput>
Ce nouveau patch traite la gestion incorrecte des symboles faibles, la
sur-optimisation des appels vers ces symboles, un problème sur atexit et le
symbole __dso_handle requis pour la fonction propre de atexit.</para>
 
<para><userinput>make BOOT_LDFLAGS=-static:</userinput>
Ceci est l'équivalent de LDFLAGS=-static que nous utilisons avec d'autres packages
pour les compiler statiquement.</para>
 
<para><userinput>--prefix=/usr:</userinput> Ce n'est PAS une erreur de frappe. GCC
garde en dur certains chemins lors de la compilation et nous devons donc donner /usr
lors du ./configure. Nous donnons le vrai préfixe du chemin d'installation plus tard
lors de la commande make install.</para>
 
<para><userinput>--enable-languages=c,c++:</userinput> Ceci ne crée
que les compilateurs C et C++, et pas les autres compilateurs disponibles,
parce qu'ils sont en moyenne très peu utilisés. Si certains de
ces autres compilateurs sont nécessaires, le paramètre --enable-languages
peut être omis.</para>
 
<para><userinput>--enable-threads=posix:</userinput> Ceci permet la gestion des
exceptions C++ pour le code multithread.</para>
 
<para><userinput>ln -sf ../usr/bin/cpp:</userinput> Ceci crée le lien symbolique
$LFS/lib/cpp. Certains packages essaient explicitement de trouver cpp
dans /lib.</para>
 
<para><userinput>ln -sf ../bin/cpp:</userinput> Ceci crée le lien symbolique
$LFS/usr/lib/cpp, parce qu'il y a des packages qui s'attendent à ce que cpp soit
dans /usr/lib.</para>
 
</sect2>
 
/tags/cvs/lfs/chapter05/tar.xml
0,0 → 1,13
<sect1 id="ch05-tar">
<title>Installing Tar-&tar-version;</title>
<?dbhtml filename="tar.html" dir="chapter05"?>
 
<screen>Estimated build time: &tar-time-static;
Estimated required disk space: &tar-compsize-static;</screen>
 
&c5-tar-inst;
&aa-tar-desc;
&aa-tar-dep;
 
</sect1>
 
/tags/cvs/lfs/chapter05/bash-inst.xml
0,0 → 1,56
<sect2>
<title>Installation of Bash</title>
 
<para>Before you attempt to install Bash, you have to check to make sure
your distribution has the <filename>/usr/lib/libcurses.a</filename> and
<filename>/usr/lib/libncurses.a</filename> files. If your host
distribution is an LFS system, all files will be present if you followed
the instructions of the book version you read exactly.</para>
 
<para>If both of the files are missing, you have to install the ncurses
development package. This package is often called something like
<emphasis>ncurses-dev</emphasis>. If this package is already installed,
or you just installed it, check for the two files again. Often the
<filename>libcurses.a</filename> file is (still) missing. If so, then
create <filename>libcurses.a</filename> as a symlink by running the
following commands as user root:</para>
 
<para><screen><userinput>cd /usr/lib &amp;&amp;
ln -s libncurses.a libcurses.a</userinput></screen></para>
 
<para>Now we can continue. Install Bash by running the following
commands:</para>
 
<para><screen><userinput>./configure --enable-static-link --prefix=$LFS/usr \
&nbsp;&nbsp;&nbsp;--bindir=$LFS/bin --with-curses &amp;&amp;
make &amp;&amp;
make install &amp;&amp;
cd $LFS/bin &amp;&amp;
ln -sf bash sh</userinput></screen></para>
 
<para>If the make install phase ends with something along the lines of</para>
 
<blockquote><screen>install-info: unknown option `--dir-file=/mnt/lfs/usr/info/dir'
usage: install-info [--version] [--help] [--debug] [--maxwidth=nnn]
[--section regexp title] [--infodir=xxx] [--align=nnn]
[--calign=nnn] [--quiet] [--menuentry=xxx]
[--info-dir=xxx]
[--keep-old] [--description=xxx] [--test]
[--remove] [--] filename
make[1]: *** [install] Error 1
make[1]: Leaving directory `/mnt/lfs/usr/src/bash-&bash-version;/doc'
make: [install] Error 2 (ignored)</screen></blockquote>
 
<para>then that means that you are probably using Debian, and that you have an
old version of the texinfo package. This error is not severe by any means: the
info pages will be installed when we recompile bash dynamically in
chapter 6, so you can ignore it.</para>
 
<para>When we tested it with the latest Debian version, the last two
commands were executed because the install process didn't return with a
value larger than 0. But you would do good to check if you have the
<filename class="symlink">$LFS/bin/sh</filename> symlink on your LFS
partition. If not, run the last two commands manually now.</para>
 
</sect2>
 
/tags/cvs/lfs/chapter05/installasuser.xml
0,0 → 1,54
<sect1 id="ch05-installasuser">
<title>Install all software as an unprivileged user</title>
<?dbhtml filename="installasuser.html" dir="chapter05"?>
 
<para>When you are logged in as root during chapter 5, it is possible
that some files of your host system will be overwritten by the ones
you'll build in chapter 5. There can be all kinds of reasons for this
to happen, for example because the $LFS environment variable is not
set. Overwriting some files from your host system will most likely
cause all kinds of problems, so it's a good idea to be logged in as
an unprivileged user during chapter 5. To make sure the environment
is as clean as possible, we'll create a new user "lfs" that can be
used while building the static installation. Issuing the following
commands as root will create a new user "lfs":</para>
 
<para><screen><userinput>useradd -s /bin/bash -m lfs &amp;&amp;
passwd lfs</userinput></screen></para>
 
<para>Now it's time to change the permissions on your LFS partitions
so user "lfs" will have write access to it. Run the following command
as root to change the ownership of the LFS partition to user "lfs":</para>
 
<para><screen><userinput>chown -R lfs $LFS</userinput></screen></para>
 
<para>Now you can login as user "lfs". You can do this two ways: either
the normal way through the console or the display manager, or with
<userinput>su - lfs</userinput>. When you're working as user "lfs", type
the following commands to setup a good environment to work in:</para>
 
<para><screen><userinput>cat > ~/.bash_profile << "EOF"
umask 022
 
LFS=/mnt/lfs
LC_ALL=POSIX
export LFS LC_ALL
EOF
source ~/.bash_profile</userinput></screen></para>
 
<para>This profile makes sure the umask is set to 022 so newly created
files and directories will have the correct permission. It is advisable
to keep this setting throughout your LFS installation. Also, the $LFS
and $LC_ALL environment variables are set. $LFS has been explained in
previous chapters already. $LC_ALL is a variable that is used for
internationalization.</para>
 
<para>When your host distribution uses a glibc version older than 2.2.4,
having $LC_ALL set to something else than "C" or "POSIX" while working
through chapter 5 may cause trouble when you exit the chroot environment
of chapter 6 and try to return to it. By setting this to "POSIX" ("C"
is an alias for "POSIX") we ensure that everything will work as expected
in the chroot environment.</para>
 
</sect1>
 
/tags/cvs/lfs/chapter05/patch-exp.xml
0,0 → 1,11
<sect2>
<title>Command explanations</title>
 
<para><userinput>CPPFLAGS=-D_GNU_SOURCE: </userinput>
Adding <userinput>-D_GNU_SOURCE</userinput> to CPPFLAGS command before
we configure patch fixes installation of the package on PPC and m68k
platforms (that we know of). It also doesn't hurt compilation on other
platforms (such as x86) so we do it by default.</para>
 
</sect2>
 
/tags/cvs/lfs/chapter05/diffutils.xml
0,0 → 1,14
<sect1 id="ch05-diffutils">
<title>Installing Diffutils-&diffutils-version;</title>
<?dbhtml filename="diffutils.html" dir="chapter05"?>
 
<screen>Estimated build time: &diffutils-time-static;
Estimated required disk space: &diffutils-compsize-static;</screen>
 
&c5-diffutils-inst;
&c5-diffutils-exp;
&aa-diffutils-desc;
&aa-diffutils-dep;
 
</sect1>
 
/tags/cvs/lfs/chapter05/binutils.xml
0,0 → 1,14
<sect1 id="ch05-binutils">
<title>Installing Binutils-&binutils-version;</title>
<?dbhtml filename="binutils.html" dir="chapter05"?>
 
<screen>Estimated build time: &binutils-time-static;
Estimated required disk space: &binutils-compsize-static;</screen>
 
&c5-binutils-inst;
&c5-binutils-exp;
&aa-binutils-desc;
&aa-binutils-dep;
 
</sect1>
 
/tags/cvs/lfs/chapter05/fileutils-exp.xml
0,0 → 1,18
<sect2>
<title>Command explanations</title>
 
<para><userinput>cp lib/Makefile.in lib/Makefile.in.backup :</userinput> We
run this command in order to keep a backup of the file we are about to
change.</para>
 
<para><userinput>cp lib/Makefile.in lib/Makefile.in.backup &amp;&amp;
sed -e 's/\(.*\)\(fopen-safer\.c \)\\/\1\2atexit.c \\/' \
&nbsp;&nbsp;&nbsp;-e 's/\(.*\)\(idcache\$U\.\$.*\)\\/\1\2atexit$U.$(OBJEXT) \\/' \
&nbsp;&nbsp;&nbsp;lib/Makefile.in.backup &gt; lib/Makefile.in:</userinput>
This is used to fix a problem with building fileutils statically on glibc 2.2.3
systems. If this isn't done, then there is the possibility of all of the
fileutils programs causing segmentation faults once chroot is entered
in chapter 6.</para>
 
</sect2>
 
/tags/cvs/lfs/chapter05/grep.xml
0,0 → 1,13
<sect1 id="ch05-grep">
<title>Installing Grep-&grep-version;</title>
<?dbhtml filename="grep.html" dir="chapter05"?>
 
<screen>Estimated build time: &grep-time-static;
Estimated required disk space: &grep-compsize-static;</screen>
 
&c5-grep-inst;
&aa-grep-desc;
&aa-grep-dep;
 
</sect1>
 
/tags/cvs/lfs/chapter05/mawk.xml
0,0 → 1,14
<sect1 id="ch05-mawk">
<title>Installing Mawk-&mawk-version;</title>
<?dbhtml filename="mawk.html" dir="chapter05"?>
 
<screen>Estimated build time: &mawk-time-static;
Estimated required disk space: &mawk-compsize-static;</screen>
 
&c5-mawk-inst;
&c5-mawk-exp;
&aa-mawk-desc;
&aa-mawk-dep;
 
</sect1>
 
/tags/cvs/lfs/chapter05/bzip2-inst.xml
0,0 → 1,20
<sect2>
<title>Installation de Bzip2</title>
 
<para>Installez Bzip2 en exécutant les commandes suivantes :</para>
 
<para><screen><userinput>make CC="gcc -static" &amp;&amp;
make PREFIX=$LFS/usr install &amp;&amp;
cd $LFS/usr/bin &amp;&amp;
mv bzcat bunzip2 bzip2 bzip2recover $LFS/bin</userinput></screen></para>
 
<para>Bien qu'il ne fasse pas partie du système de base LFS, il est utile de mentionner
que le patch de compression/décompression utilisant les programmes bzip2/bunzip2 est
disponible au téléchargement. Sans ajout de ce patch, vous devrez utiliser des commandes
comme bzcat file.tar.bz|tar xv ou tar --use-compress-prog=bunzip2 -xvf file.tar.bz2 pour
utiliser bzip2/bunzip2 avec tar. Ce patch apporte l'option -j pour décompresser une
archive bzip2 avec la commande tar xvfj file.tar.bz2. Appliquer ce patch sera décrit
plus tard quand le package tar sera installé.</para>
 
</sect2>
 
/tags/cvs/lfs/chapter05/tar-inst.xml
0,0 → 1,21
<sect2>
<title>Installation de Tar</title>
 
<para>Pour pouvoir utiliser directement les fichiers bzip2 avec tar, utiliser le
patch tar disponible depuis le site FTP LFS. Ce patch ajoutera l'option -j à tar,
option qui fonctionne de manière identique à l'option -z de tar (qui permet d'utiliser
directement les fichiers gzip).</para>
 
<para>Installer le patch en lançant la commande suivante:</para>
 
<para><screen><userinput>patch -Np1 -i ../tar-1.13.patch</userinput></screen></para>
 
<para>Installer Tar en lançant les commandes suivantes:</para>
 
<para><screen><userinput>./configure --prefix=$LFS/usr --disable-nls \
&nbsp;&nbsp;&nbsp;--libexecdir=$LFS/usr/bin --bindir=$LFS/bin &amp;&amp;
make LDFLAGS=-static &amp;&amp;
make install</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter05/gzip.xml
0,0 → 1,14
<sect1 id="ch05-gzip">
<title>Installing Gzip-&gzip-version;</title>
<?dbhtml filename="gzip.html" dir="chapter05"?>
 
<screen>Estimated build time: &gzip-time-static;
Estimated required disk space: &gzip-compsize-static;</screen>
 
&c5-gzip-inst;
&c5-gzip-exp;
&aa-gzip-desc;
&aa-gzip-dep;
 
</sect1>
 
/tags/cvs/lfs/chapter05/patch-inst.xml
0,0 → 1,13
<sect2>
<title>Installation of Patch</title>
 
<para>Install Patch by running the following commands:</para>
 
<para><screen><userinput>export CPPFLAGS=-D_GNU_SOURCE &amp;&amp;
./configure --prefix=$LFS/usr &amp;&amp;
unset CPPFLAGS &amp;&amp;
make LDFLAGS=-static &amp;&amp;
make install</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter05/texinfo.xml
0,0 → 1,13
<sect1 id="ch05-texinfo">
<title>Installing Texinfo-&texinfo-version;</title>
<?dbhtml filename="texinfo.html" dir="chapter05"?>
 
<screen>Estimated build time: &texinfo-time-static;
Estimated required disk space: &texinfo-compsize-static;</screen>
 
&c5-texinfo-inst;
&aa-texinfo-desc;
&aa-texinfo-dep;
 
</sect1>
 
/tags/cvs/lfs/chapter05/bash.xml
0,0 → 1,14
<sect1 id="ch05-bash">
<title>Installing Bash-&bash-version;</title>
<?dbhtml filename="bash.html" dir="chapter05"?>
 
<screen>Estimated build time: &bash-time-static;
Estimated required disk space: &bash-compsize-static;</screen>
 
&c5-bash-inst;
&c5-bash-exp;
&aa-bash-desc;
&aa-bash-dep;
 
</sect1>
 
/tags/cvs/lfs/chapter05/creatingdirs.xml
0,0 → 1,66
<sect1 id="ch05-creatingdirs">
<title>Creating directories</title>
<?dbhtml filename="creatingdirs.html" dir="chapter05"?>
 
<para>Let's now create the directory tree on the LFS partition based on
the FHS standard, which can be found at
<ulink url="http://www.pathname.com/fhs/">http://www.pathname.com/fhs/</ulink>.
Issuing the following commands will create a default directory layout:</para>
<para><screen><userinput>cd $LFS &amp;&amp;
mkdir -p bin boot dev/pts etc/opt home lib mnt proc root sbin tmp var opt &amp;&amp;
for dirname in $LFS/usr $LFS/usr/local
<literal>&nbsp;&nbsp;&nbsp;do</literal>
&nbsp;&nbsp;&nbsp;mkdir $dirname
&nbsp;&nbsp;&nbsp;cd $dirname
&nbsp;&nbsp;&nbsp;mkdir bin etc include lib sbin share src var
&nbsp;&nbsp;&nbsp;ln -s share/man
&nbsp;&nbsp;&nbsp;ln -s share/doc
&nbsp;&nbsp;&nbsp;ln -s share/info
&nbsp;&nbsp;&nbsp;cd $dirname/share
&nbsp;&nbsp;&nbsp;mkdir dict doc info locale man nls misc terminfo zoneinfo
&nbsp;&nbsp;&nbsp;cd $dirname/share/man
&nbsp;&nbsp;&nbsp;mkdir man{1,2,3,4,5,6,7,8}
done &amp;&amp;
cd $LFS/var &amp;&amp;
mkdir -p lock log mail run spool tmp opt cache lib/misc local &amp;&amp;
cd $LFS/opt &amp;&amp;
mkdir bin doc include info lib man &amp;&amp;
cd $LFS/usr &amp;&amp;
ln -s ../var/tmp</userinput></screen></para>
 
<para>Normally, directories are created with permission mode 755, which isn't
desired for all directories. The first change is a mode 0750 for the
$LFS/root directory. This is to make sure that not just everybody can
enter the /root directory (the same a user would do with /home/username
directories). The second change is a mode 1777 for the tmp
directories. This way, any user can write data to the /tmp or /var/tmp
directory but cannot remove another user's files (the latter is caused
by the so-called "sticky bit" - bit 1 of the 1777 bit mask).</para>
 
<para><screen><userinput>cd $LFS &amp;&amp;
chmod 0750 root &amp;&amp;
chmod 1777 tmp var/tmp</userinput></screen></para>
 
<para>Now that the directories are created, copy the source files that were
downloaded in chapter 3 to some subdirectory under $LFS/usr/src (you
will need to create the desired directory yourself).</para>
 
<sect2>
<title>FHS compliance notes</title>
 
<para>The FHS stipulates that the /usr/local directory should contain the
bin, games, include, lib, man, sbin, and share subdirectories. You can
alter your /usr/local directory yourself if you want your system to be
FHS-compliant.</para>
 
<para>Also, the standard says that there should exist a /usr/share/games
directory, which we don't much like for a base system. But feel free to
make your system FHS-compliant if you wish. The FHS isn't precise as
to the structure of the /usr/local/share subdirectories, so we took the
liberty of creating the directories that we felt needed.</para>
 
</sect2>
 
</sect1>
 
/tags/cvs/lfs/chapter05/whystatic.xml
0,0 → 1,62
<sect1 id="ch05-whystatic">
<title>Why do we use static linking?</title>
<?dbhtml filename="whystatic.html" dir="chapter05"?>
 
<para>Thanks to Plasmatic for posting the text on which this is mainly
based to one of the LFS mailing lists.</para>
 
<para>When making (compiling) a program, rather than having to rewrite all the
functions for dealing with the kernel, hardware, files, etc. every time you
write a new program, all these basic functions are instead kept in libraries.
glibc, which you install later, is one of these major libraries, which
contains code for all the basic functions programs use, like opening files,
printing information on the screen, and getting feedback from the user. When
the program is compiled, these libraries of code are linked together with the
new program, so that it can use any of the functions that the library
has.</para>
 
<para>However, these libraries can be very large (for example, libc.a from
can often be around 2.5MB), 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.5MB attached to it! Instead of making the library
an actual part of the program, or statically linked, the library is kept 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 1kb file and a 2.5MB file, but we still haven't saved any
space (except maybe RAM until the library is needed). The REAL advantage to
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
duplicates into memory. So not only are we saving hard disk space, but also
precious RAM.</para>
 
<para>If dynamic linking saves so much room, then why are we making everything
statically linked? Well, that's because when you chroot into your brand new
(but very incomplete) LFS environment, these dynamic libraries won't be
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
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
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,
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
<userinput>-static</userinput> flags. If you try building everything
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>
 
</sect1>
/tags/cvs/lfs/chapter05/textutils-inst.xml
0,0 → 1,12
<sect2>
<title>Installation of Textutils</title>
 
<para>Install Textutils by running the following commands:</para>
 
<para><screen><userinput>./configure --prefix=$LFS/usr --disable-nls &amp;&amp;
make LDFLAGS=-static &amp;&amp;
make install &amp;&amp;
mv $LFS/usr/bin/cat $LFS/usr/bin/head $LFS/bin</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter05/kernel.xml
0,0 → 1,15
<sect1 id="ch05-kernel">
<title>Installing Linux Kernel-&kernel-version;</title>
<?dbhtml filename="kernel.html" dir="chapter05"?>
 
<screen>Estimated build time: &kernel-time-static;
Estimated required disk space: &kernel-compsize-static;</screen>
 
&c5-kernel-inst;
&c5-kernel-exp;
&c5-kernel-exp-headers;
&aa-kernel-desc;
&aa-kernel-dep;
 
</sect1>
 
/tags/cvs/lfs/chapter05/bzip2-exp.xml
0,0 → 1,8
<sect2>
<title>Explication des commandes</title>
 
<para><userinput>make CC="gcc -static": </userinput>Cette méthode nous permet de dire
à gcc que nous voulons lier bzip2 statiquement.</para>
 
</sect2>
 
/tags/cvs/lfs/chapter05/binutils-exp.xml
0,0 → 1,22
<sect2>
<title>Détails de la commande</title>
 
<para><userinput>--disable-nls:</userinput> Cette option invalide
l'internationalisation (aussi connue comme i18n). Nous n'avons pas besoin de
cela pour nos programmes statiques et NLS cause souvent quelques problèmes lors
de l'édition de liens statiques.</para>
 
<para><userinput>LDFLAGS=-all-static:</userinput> Mettre la variable LDFLAGS
à la valeur -all-static permet à Binutils d'être lié statiquement.</para>
 
<para><userinput>tooldir=$LFS/usr:</userinput> Normalement, tooldir (le
répertoire où les exécutables de binutils vont se situer) est
$(exec_prefix)/$(target_alias) ce qui donne, par exemple,
/usr/i686-pc-linux-gnu. Depuis que nous avons construit notre propre système,
nous n'avons pas eu besoin de positionner cette option au répertoire $LFS/usr.
Cette option ne devrait être utilisée que pour une plateforme de compilation
croisée (par exemple compiler un package sur une machine Intel qui génère un
code exécutable sur des PowerPC).</para>
 
</sect2>
 
/tags/cvs/lfs/chapter05/diffutils-exp.xml
0,0 → 1,18
<sect2>
<title>Command explanations</title>
 
<para><userinput>CPPFLAGS=-Dre_max_failures=re_max_failures2:</userinput> The
CPPFLAGS variable is a variable that's read by the cpp program (C
PreProcessor). The value of this variable tells the preprocessor to
replace every instance of re_max_failures it finds by re_max_failures2
before handing the source file to the compiler itself for compilation. This
package has problems linking statically on systems that run an older
Glibc version and this construction fixes that problem.</para>
 
<para><userinput>PR_PROGRAM=/usr/bin/pr:</userinput> When 'diff' is called
with the '-l' flag, it tries to find 'pr' at the location specified with the
PR_PROGRAM variable. By default, this variable points to '/bin/pr', but since
we install 'pr' in /usr/bin, we need to change this.</para>
 
</sect2>
 
/tags/cvs/lfs/chapter05/sed-inst.xml
0,0 → 1,24
<sect2>
<title>Installation de Sed</title>
 
<para>Lors de l'installation de Sed avec glic-2.1.x à partir de votre système de base,
il peut être nécessaire d'utiliser une correction pour empêcher un conflit de noms de
variables. Les commandes suivantes peuvent être utilisées dans ce cas. Notez que ces
commandes peuvent aussi être utilisées avec d'autres versions de glibc, donc si vous
n'êtes pas sûr, essayez la première version.</para>
 
<para><screen><userinput>export CPPFLAGS=-Dre_max_failures=re_max_failures2 &amp;&amp;
./configure --prefix=$LFS/usr --bindir=$LFS/bin &amp;&amp;
unset CPPFLAGS &amp;&amp;
make LDFLAGS=-static &amp;&amp;
make install</userinput></screen></para>
<para>Si vous utilisez une version plus récente de glibc (2.2.x), vous pouvez utiliser
les commandes suivantes pour installer Sed:</para>
<para><screen><userinput>./configure --prefix=$LFS/usr --bindir=$LFS/bin &amp;&amp;
make LDFLAGS=-static &amp;&amp;
make install</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter05/texinfo-inst.xml
0,0 → 1,11
<sect2>
<title>Installation de Texinfo</title>
 
<para>Installez Texinfo en lançant les commandes suivantes:</para>
 
<para><screen><userinput>./configure --prefix=$LFS/usr --disable-nls &amp;&amp;
make LDFLAGS=-static &amp;&amp;
make install</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter05/shellutils.xml
0,0 → 1,13
<sect1 id="ch05-shutils">
<title>Installing Sh-utils-&sh-utils-version;</title>
<?dbhtml filename="sh-utils.html" dir="chapter05"?>
 
<screen>Estimated build time: &sh-utils-time-static;
Estimated required disk space: &sh-utils-compsize-static;</screen>
 
&c5-shellutils-inst;
&aa-shellutils-desc;
&aa-shellutils-dep;
 
</sect1>
 
/tags/cvs/lfs/chapter05/make-inst.xml
0,0 → 1,11
<sect2>
<title>Installation de Make</title>
 
<para>Installez Make en exécutant les commandes suivantes:</para>
 
<para><screen><userinput>./configure --prefix=$LFS/usr --disable-nls &amp;&amp;
make LDFLAGS=-static &amp;&amp;
make install</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter05/mawk-exp.xml
0,0 → 1,8
<sect2>
<title>Explication des commandes</title>
 
<para><userinput>make CC="gcc -static"</userinput> Ceci est utilisé pour construire
mawk de manière statique.</para>
 
</sect2>
 
/tags/cvs/lfs/chapter05/oldnsslib.xml
0,0 → 1,21
<sect1 id="ch05-oldnsslib">
<title>Copie des anciennes bibliothèques NSS</title>
<?dbhtml filename="oldnsslib.html" dir="chapter05"?>
 
<para>Si votre système Linux de base utilise Glibc-2.0, vous avez besoin de copier
les bibliothèques NSS dans la partition LFS. Certains programmes liés statiquement
dépendent des bibliothèques NSS, spécialement les programmes qui ont besoin de
récupérer les noms, les ID des utilisateurs et des groupes. Vous pouvez vérifier
la version de la bibliothèque C que votre système Linux utilise en exécutant
simplement la bibliothèque ainsi:</para>
 
<para><screen><userinput>/lib/libc.so.6</userinput></screen></para>
 
<para>La première ligne vous donne le numéro de version. Les lignes suivantes
contiennent d'autres informations intéressantes. Si Glibc-2.0.x est installé sur
votre système de base, copiez les bibliothèques NSS en lançant:</para>
 
<para><screen><userinput>cp -av /lib/libnss* $LFS/lib</userinput></screen></para>
 
</sect1>
 
/tags/cvs/lfs/chapter05/kernel-inst.xml
0,0 → 1,21
<sect2>
<title>Installation of the Linux Kernel</title>
 
<para>We won't be compiling a new kernel image yet. We'll do that after we
have finished the installation of the basic system software in this
chapter. But because certain software needs the kernel header files, we're
going to unpack the kernel archive now and set it up so that we can
compile the packages that need the kernel.</para>
 
<para>The kernel configuration file is created by running the following
command:</para>
 
<para><screen><userinput>make mrproper &amp;&amp;
yes "" | make config &amp;&amp;
make dep &amp;&amp;
mkdir $LFS/usr/include/asm &amp;&amp;
cp include/asm/* $LFS/usr/include/asm &amp;&amp;
cp -R include/linux $LFS/usr/include</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter05/gcc.xml
0,0 → 1,14
<sect1 id="ch05-gcc">
<title>Installing GCC-&gcc-version;</title>
<?dbhtml filename="gcc.html" dir="chapter05"?>
 
<screen>Estimated build time: &gcc-time-static;
Estimated required disk space: &gcc-compsize-static;</screen>
 
&c5-gcc-inst;
&c5-gcc-exp;
&aa-gcc-desc;
&aa-gcc-dep;
 
</sect1>
 
/tags/cvs/lfs/chapter05/patch.xml
0,0 → 1,14
<sect1 id="ch05-patch">
<title>Installing Patch-&patch-version;</title>
<?dbhtml filename="patch.html" dir="chapter05"?>
 
<screen>Estimated build time: &patch-time-static;
Estimated required disk space: &patch-compsize-static;</screen>
 
&c5-patch-inst;
&c5-patch-exp;
&aa-patch-desc;
&aa-patch-dep;
 
</sect1>
 
/tags/cvs/lfs/chapter05/fileutils.xml
0,0 → 1,14
<sect1 id="ch05-fileutils">
<title>Installing Fileutils-&fileutils-version;</title>
<?dbhtml filename="fileutils.html" dir="chapter05"?>
 
<screen>Estimated build time: &fileutils-time-static;
Estimated required disk space: &fileutils-compsize-static;</screen>
 
&c5-fileutils-inst;
&c5-fileutils-exp;
&aa-fileutils-desc;
&aa-fileutils-dep;
 
</sect1>
 
/tags/cvs/lfs/chapter05/proc.xml
0,0 → 1,20
<sect1 id="ch05-proc">
<title>Mounting $LFS/proc file system</title>
<?dbhtml filename="proc.html" dir="chapter05"?>
 
<para>In order for certain programs to function properly, the proc file
system must be mounted and available from within the chroot'ed environment
as well. It's not a problem to mount the proc file system (or any other
file system for that matter) twice or even more than that.</para>
 
<para>If you're still logged in as user "lfs", you should log out and log
in again as user root. The reason for this is simple: only root is allowed
to mount filesystems and to run chroot.</para>
 
<para>The proc file system is mounted under $LFS/proc by running the
following command:</para>
 
<para><screen><userinput>mount proc $LFS/proc -t proc</userinput></screen></para>
 
</sect1>
 
/tags/cvs/lfs/chapter05/gzip-exp.xml
0,0 → 1,16
<sect2>
<title>Command explanations</title>
 
<para><userinput>cp $LFS/usr/bin/gunzip $LFS/usr/bin/gzip $LFS/bin &&
rm $LFS/usr/bin/gunzip $LFS/usr/bin/gzip:</userinput> The reason we don't
simply use <quote>mv</quote> to move the files to the new location is
because gunzip is a hardlink to gzip. On older distributions you can't
move a hardlink to another partition (and it's very possible that $LFS and
$LFS/usr are separate partitions). With more recent distributions this
isn't a problem. If you run mv to move hardlinks across partitions it'll
just do a regular <quote>cp</quote> and discard the hardlink. But, we
can't assume that every host distribution has a new enough kernel and
fileutils that works this way.</para>
 
</sect2>
 
/tags/cvs/lfs/chapter05/shellutils-inst.xml
0,0 → 1,37
<sect2>
<title>Installation of Sh-utils</title>
 
<para>Before Sh-utils is installed, the sh-utils patch file may need to
be applied. This patch is needed to avoid a conflict of variable names
with certain Glibc versions (usually glibc-2.1.x) when compiling sh-utils
statically. It is however safe to apply the patch even if you are
running a different glibc version, so if you aren't sure, it's
best to apply it.</para>
 
<para>Apply the patch by running the following command:</para>
 
<para><screen><userinput>patch -Np1 -i ../sh-utils-&sh-utils-version;.patch</userinput></screen></para>
 
<para>Install Sh-utils by running the following commands:</para>
 
<para><screen><userinput>./configure --prefix=$LFS/usr --disable-nls &amp;&amp;
make LDFLAGS=-static &amp;&amp;
make install &amp;&amp;
cd $LFS/usr/bin &amp;&amp;
mv basename date echo false hostname $LFS/bin &amp;&amp;
mv pwd sleep stty test true uname $LFS/bin &amp;&amp;
mv chroot ../sbin</userinput></screen></para>
 
<para>During the make install stage you will see the following warning:</para>
 
<blockquote><screen>WARNING: insufficient access; not installing su
NOTE: to install su, run 'make install-root' as root</screen></blockquote>
 
<para>You can safely ignore that warning. You need to be logged in as root
in order to install su the way sh-utils wants to install it, that being
suid root. Because we don't need su during chapter 6, and su will be properly
installed when we re-install sh-utils in chapter 6 anyways, you can just
pretend you didn't see it.</para>
 
</sect2>
 
/tags/cvs/lfs/chapter05/diffutils-inst.xml
0,0 → 1,24
<sect2>
<title>Installation of Diffutils</title>
 
<para>When installing Diffutils using glibc-2.1.x on your base system, it may
be necessary to use a fix to prevent a variable name conflict. The
following commands can be used in this case. Note that these commands
can also be used for other glibc versions so if you aren't sure, then
use the first version.</para>
 
<para><screen><userinput>export CPPFLAGS=-Dre_max_failures=re_max_failures2 &amp;&amp;
./configure --prefix=$LFS/usr &amp;&amp;
unset CPPFLAGS &amp;&amp;
make LDFLAGS=-static PR_PROGRAM=/usr/bin/pr &amp;&amp;
make install</userinput></screen></para>
 
<para>If you are using a newer glibc version (2.2.x), you can use the following
commands to install Diffutils:</para>
 
<para><screen><userinput>./configure --prefix=$LFS/usr &amp;&amp;
make LDFLAGS=-static PR_PROGRAM=/usr/bin/pr &amp;&amp;
make install</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter05/binutils-inst.xml
0,0 → 1,20
<sect2>
<title>Installation of Binutils</title>
 
<para>This package is known to behave badly when you have changed its default
optimization flags (including the -march and -mcpu options). Binutils is
best left alone, so we recommend you unsetting CFLAGS, CXXFLAGS and other
such variables/settings that would change the default optimization that
it comes with.</para>
 
<para>Install Binutils by running the following commands:</para>
 
 
<para><screen><userinput>mkdir ../binutils-build &amp;&amp;
cd ../binutils-build &amp;&amp;
../binutils-&binutils-version;/configure --prefix=$LFS/usr --disable-nls &amp;&amp;
make LDFLAGS=-all-static tooldir=$LFS/usr &amp;&amp;
make tooldir=$LFS/usr install</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter05/textutils.xml
0,0 → 1,13
<sect1 id="ch05-textutils">
<title>Installing Textutils-&textutils-version;</title>
<?dbhtml filename="textutils.html" dir="chapter05"?>
 
<screen>Estimated build time: &textutils-time-static;
Estimated required disk space: &textutils-compsize-static;</screen>
 
&c5-textutils-inst;
&aa-textutils-desc;
&aa-textutils-dep;
 
</sect1>
 
/tags/cvs/lfs/chapter05/pwdgroup.xml
0,0 → 1,41
<sect1 id="ch05-pwdgroup">
<title>Creating passwd and group files</title>
<?dbhtml filename="pwdgroup.html" dir="chapter05"?>
 
<para>In order for the user and group root to be recognized and to be able to
login, there needs to be an entry in the /etc/passwd and /etc/group file.
Besides the group root, a couple of other groups are recommended and needed by
packages. The groups with their GID's below aren't part of any standard.
The LSB only recommends a group bin with GID 1 to be present besides
group root. Other group names and GID's can be chosen by the user. Well
written packages don't depend on GID numbers but just use the group
name, so it doesn't matter which GID a group has. Since there
aren't any standards for groups the groups created here are the groups the
MAKEDEV script (the script that creates the device files in the /dev
directory) mentions.</para>
 
<para>Create a new file <filename>$LFS/etc/passwd</filename> by running the
following command:</para>
 
<para><screen><userinput>echo "root:x:0:0:root:/root:/bin/bash" &gt; $LFS/etc/passwd</userinput></screen></para>
 
<para>Create a new file <filename>$LFS/etc/group</filename> by running the
following command:</para>
 
<para><screen><userinput>cat &gt; $LFS/etc/group &lt;&lt; "EOF"</userinput>
root:x:0:
bin:x:1:
sys:x:2:
kmem:x:3:
tty:x:4:
tape:x:5:
daemon:x:6:
floppy:x:7:
disk:x:8:
lp:x:9:
dialout:x:10:
audio:x:11:
<userinput>EOF</userinput></screen></para>
 
</sect1>
 
/tags/cvs/lfs/chapter05/gcc-inst.xml
0,0 → 1,27
<sect2>
<title>Installation de GCC</title>
 
<para>Ce package est connu pour se comporter bizarrement si vous avez changer les
options d'optimisation par défaut (y compris les options -march et -mcpu). GCC se
comporte mieux sans, donc nous vous recommendons de supprimer CFLAGS, CXXFLAGS et
toute autre variable/option qui pourrait changer l'optimisation par défaut du
package.</para>
 
<para>Installez GCC en lançant les commandes suivantes:</para>
 
<para><screen><userinput>patch -Np1 -i ../gcc-&gcc-patch-version;.patch &amp;&amp;
mkdir ../gcc-build &amp;&amp;
cd ../gcc-build &amp;&amp;
../gcc-&gcc-version;/configure --prefix=/usr --enable-languages=c,c++ \
&nbsp;&nbsp;&nbsp;--disable-nls --disable-shared --enable-threads=posix &amp;&amp;
make BOOT_LDFLAGS=-static bootstrap &amp;&amp;
make prefix=$LFS/usr install &amp;&amp;
cd $LFS/lib &amp;&amp;
ln -sf ../usr/bin/cpp &amp;&amp;
cd $LFS/usr/lib &amp;&amp;
ln -sf ../bin/cpp &amp;&amp;
cd $LFS/usr/bin &amp;&amp;
ln -sf gcc cc</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter05/bash-exp.xml
0,0 → 1,45
<sect2>
<title>Détail de la commande</title>
 
<para><userinput>--enable-static-link:</userinput> Cette option
permet au Bash d'être lié statiquement</para>
 
<para><userinput>--prefix=$LFS/usr:</userinput> Cette option installe
tous les fichiers Bash dans le répertoire $LFS/usr, qui devient alors le répertoire
/usr lors d'un chroot ou d'un reboot dans LFS.</para>
 
<para><userinput>--bindir=$LFS/bin:</userinput> Ceci installe les fichiers
executables dans $LFS/bin. Nous faisons ceci pour que bash soit dans /bin, et non
pas dans /usr/bin. Une des raisons d'être: /usr devrait être dans une partition
différente et, avant d'être montée vous aurez besoin de bash (il serait difficile
d'exécuter les scripts au boot sans un shell de disponible).</para>
 
<para><userinput>--with-curses:</userinput> Ceci permet à Bash d'être lié à la
bibliothèque curses plutôt qu'à la bibliothèque termcap par défaut, laquelle devient
obsolète.</para>
 
<para>Il n'est pas nécessaire au sens strict que le bash statique soit lié à
libncurses (il peut être lié à la bibliothèque statique termcap dans un premier temps
car nous réinstallerons Bash dans le chapître 6 de toute façon, où là nous
utiliserons libncurses), cependant c'est un bon test pour être sûr que le package
ncurses a été correctement installé. S'il ne l'a pas été, vous aurez quelques
problèmes plus loin dans ce chapître lorsqu'il s'agira d'installer le package
Texinfo. Ce package requiert ncurses et termcap ne peut plus alors être utilisé.</para>
 
<para><userinput>ln -sf bash sh:</userinput> Cette commande crée le lien symbolique
sh qui pointe sur bash. La plupart des scripts se lance eux-même via 'sh'
(par #!/bin/sh en première ligne du script) qui invoque un mode spécial de bash.
Bash ce comportera alors (aussi fidèlement que possible) comme le Bourne shell
original.</para>
 
<para>Les caractères <userinput>&amp;&amp;</userinput> à la fin de chaque ligne
permettent de n'exécuter la prochaine commande que si la commande précédente existe
et retourne 0 indiquant qu'elle s'est exécutée sans erreur. Dans ce cas, toutes les
commandes sont copiées&amp;collées dans le shell, il est important de s'assurer que
si ./configure échoue, make ne sera pas exécuté et, de ce fait, si make échoue,
alors make install ne doit pas être exécuté, et ainsi de suite.</para>
 
</sect2>
 
 
<!-- This document source from http://traduc.lfs.tuxfamily.org/fichiers/LFS-BOOK-3.1-XML/chapter5/bash-exp.xml -->
/tags/cvs/lfs/chapter05/grep-inst.xml
0,0 → 1,25
<sect2>
<title>Installation of Grep</title>
 
<para>When installing Grep using glibc-2.1.x on your base system,
it may be necessary to use a fix to prevent a variable name conflict. The
following commands can be used in this case. Note that these commands
can also be used for other glibc versions so if you aren't sure, then
use the first version.</para>
 
<para><screen><userinput>export CPPFLAGS=-Dre_max_failures=re_max_failures2 &amp;&amp;
./configure --prefix=$LFS/usr --disable-nls --bindir=$LFS/bin &amp;&amp;
unset CPPFLAGS &amp;&amp;
make LDFLAGS=-static &amp;&amp;
make install</userinput></screen></para>
<para>If you are using a newer glibc version (2.2.x), you can use the
following commands to install Grep:</para>
<para><screen><userinput>./configure --prefix=$LFS/usr --disable-nls \
&nbsp;&nbsp;&nbsp;--bindir=$LFS/bin &amp;&amp;
make LDFLAGS=-static &amp;&amp;
make install</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter05/kernel-exp.xml
0,0 → 1,36
<sect2>
<title>Command explanations</title>
 
<para><userinput>make mrproper:</userinput> This will ensure that the kernel
tree is absolutely clean. We do this because the kernel team recommend
that this is done prior to <emphasis>each</emphasis> kernel compilation,
and that we shouldn't rely on the source tree being automatically clean
after untarring.</para>
 
<para><userinput>yes "" | make config:</userinput> This runs make config and
answers with the default answer to every question the config script asks
the user (it does this by simply doing the equivalent of hitting the
Enter key, thus accepting the default Y and N answers to the questions).
We're not configuring the real kernel here, we just need to have some sort
of configure file created so that we can run make dep next that will
create a few header files in <filename>include/linux</filename>, like
version.h, among others, that we will need to compile Glibc and other
packages later in chroot.</para>
 
<para><userinput>make dep:</userinput> make dep checks dependencies and sets
up the dependencies file. We don't really care about the dependency
checks, but what we do care about is that make dep creates those
aforementioned files in <filename>include/linux</filename> we will be
needing later on.</para>
 
<para><userinput>mkdir $LFS/usr/include/asm</userinput>
and <userinput>cp include/asm/* $LFS/usr/include/asm</userinput>:
This copies the platform-specific assembler kernel header files to
<filename>$LFS/usr/include/asm</filename>.</para>
 
<para><userinput>cp -R include/linux $LFS/usr/include</userinput>:
This command copies the cross-platform kernel header files to
<filename>$LFS/usr/include</filename>.</para>
 
</sect2>
 
/tags/cvs/lfs/chapter05/mawk-inst.xml
0,0 → 1,12
<sect2>
<title>Installation de Mawk</title>
 
<para>Installez Mawk en lançant les commandes suivantes:</para>
 
<para><screen><userinput>./configure &amp;&amp;
make CC="gcc -static" &amp;&amp;
make BINDIR=$LFS/usr/bin \
&nbsp;&nbsp;&nbsp;MANDIR=$LFS/usr/share/man/man1 install</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter05/fileutils-inst.xml
0,0 → 1,46
<sect2>
<title>Installation of Fileutils</title>
 
<para>The programs from a statically linked fileutils package may cause
segmentation faults on certain systems, if your distribution has
Glibc-2.2.3 or higher installed. It also seems to happen mostly on machines
powered by an AMD CPU, but there is a case or two where an Intel system
is affected as well. If your system falls under this category, try the
following fix.</para>
 
<para>Note that in some cases using these sed commands will result in
problems not being able to compile this package at all, even when your
system has an AMD CPU and has Glibc-2.2.3 (or higher) installed. If that's
the case, you'll need to remove the fileutils-&fileutils-version; directory
and unpack it again from the tarball before continuing. We believe this
may be the case when your distribution has altered Glibc-2.2.3 somehow,
but details are unavailable at the time.</para>
 
<para>To fix this package to compile properly on AMD/Glibc-2.2.3
machines, run the following commands. Do <emphasis>not</emphasis>
attempt this fix if you don't have Glibc-2.2.3 installed. It will more
than likely result in all kinds of compile time problems.</para>
 
<para><screen><userinput>cp lib/Makefile.in lib/Makefile.in.backup &amp;&amp;
sed -e 's/\(.*\)\(fopen-safer\.c \)\\/\1\2atexit.c \\/' \
&nbsp;&nbsp;&nbsp;-e 's/\(.*\)\(idcache\$U\.\$.*\)\\/\1\2atexit$U.$(OBJEXT) \\/' \
&nbsp;&nbsp;&nbsp;lib/Makefile.in.backup &gt; lib/Makefile.in</userinput></screen></para>
 
<para>Install fileutils by running the following commands:</para>
 
<para><screen><userinput>./configure --disable-nls \
&nbsp;&nbsp;&nbsp;--prefix=$LFS/usr --bindir=$LFS/bin &amp;&amp;
make LDFLAGS=-static &amp;&amp;
make install &amp;&amp;
cd $LFS/usr/bin &amp;&amp;
ln -sf ../../bin/install</userinput></screen></para>
 
<para>Once you have installed fileutils, you can test whether the
segmentation fault problem has been avoided by running
<userinput>$LFS/bin/ls</userinput>. If this works, then you are OK. If
not, then you need to re-do the installation using the sed commands if
you didn't use them, or without the sed commands if you did use
them.</para>
 
</sect2>
 
/tags/cvs/lfs/chapter05/chapter5.xml
0,0 → 1,31
<chapter id="chapter05">
<title>Preparing the LFS system</title>
<?dbhtml filename="chapter05.html" dir="chapter05"?>
 
&c5-introduction;
&c5-whystatic;
&c5-installasuser;
&c5-creatingdirs;
&c5-bash;
&c5-binutils;
&c5-bzip2;
&c5-diffutils;
&c5-fileutils;
&c5-gcc;
&c5-grep;
&c5-gzip;
&c5-kernel;
&c5-make;
&c5-mawk;
&c5-patch;
&c5-sed;
&c5-shellutils;
&c5-tar;
&c5-texinfo;
&c5-textutils;
&c5-pwdgroup;
&c5-oldnsslib;
&c5-proc;
 
</chapter>
 
/tags/cvs/lfs/chapter05/sed.xml
0,0 → 1,13
<sect1 id="ch05-sed">
<title>Installing Sed-&sed-version;</title>
<?dbhtml filename="sed.html" dir="chapter05"?>
 
<screen>Estimated build time: &sed-time-static;
Estimated required disk space: &sed-compsize-static;</screen>
 
&c5-sed-inst;
&aa-sed-desc;
&aa-sed-dep;
 
</sect1>
 
/tags/cvs/lfs/chapter05/make.xml
0,0 → 1,13
<sect1 id="ch05-make">
<title>Installing Make-&make-version;</title>
<?dbhtml filename="make.html" dir="chapter05"?>
 
<screen>Estimated build time: &make-time-static;
Estimated required disk space: &make-compsize-static;</screen>
 
&c5-make-inst;
&aa-make-desc;
&aa-make-dep;
 
</sect1>
 
/tags/cvs/lfs/chapter06/aboutdebug.xml
0,0 → 1,55
<sect1 id="ch06-aboutdebug">
<title>A propos des symboles de débogage</title>
<?dbhtml filename="aboutdebug.html" dir="chapter06"?>
 
<para>La plupart des programmes et des bibliothèques sont compilés par défaut avec
des symboles de débogage (gcc option -g).</para>
 
<para>Un programme compilé avec des symboles de débogage permet à un
utilisateur d'exécuter un programme ou une bibliothèque via un débogueur et
d'utiliser facilement les résultats obtenus. Ces symboles de débogage augmentent
également la taille du programme de façon significative.</para>
 
<para>Avant de que vous ne commenciez à vous demander si ces symboles de débogage font
réellement
une grande différence, voici quelques statistiques. Utilisez-les pour en tirer vos
propres conclusions.</para>
 
<itemizedlist>
 
<listitem><para>Un binaire Bash dynamique avec symboles de débogage: 1,2Mo.</para></listitem>
 
<listitem><para>Un binaire Bash dynamique sans symboles de débogage: 478Ko.</para></listitem>
 
<listitem><para>/lib et /usr/lib (fichiers glibc
et gcc) avec symboles de débogage: 87Mo.</para></listitem>
 
<listitem><para>/lib et /usr/lib (fichiers glibc
et gcc) sans symboles de débogage: 16Mo.</para></listitem>
 
</itemizedlist>
 
<para>Les tailles varient selon le compilateur utilisé et la version de la
bibliothèque C utilisée
pour les liens dynamiques entre les programmes, mais les résultats seront similaires si vous
comparez des programmes avec ou sans symboles de débogage.</para>
 
<para>Pour enlever les symboles de débogage d'un binaire (qui doit être de type a.out
ou ELF)
exécutez<userinput>strip --strip-debug filename</userinput>. Les jokers peuvent être
utilisés pour supprimer les symboles de débogage dans plusieurs fichiers (utilisez
quelque chose comme<userinput>strip --strip-debug $LFS/usr/bin/*</userinput>). La plupart des
gens n'utiliseront probablement jamais un débogueur sur leur logiciels, vous gagnerez donc
beaucoup de place sur le disque en supprimant ces symboles.</para>
 
<para>Pour vous faciliter l'opération, le chapitre 9 comprend une commande unique pour
supprimer
tous les symboles de débogage de tous les programmes et bibliothèques de votre
système.</para>
 
<para>Vous obtiendrez des informations supplémentaires dans le guide de l'optimisation qui
peut être trouvé à <ulink url="&hints-root;optimization.txt">&hints-root;optimization.txt</ulink>
.</para>
 
</sect1>
 
/tags/cvs/lfs/chapter06/reiserfs.xml
0,0 → 1,13
<sect1 id="ch06-reiserfs">
<title>Installing Reiserfsprogs-&reiserfs-version;</title>
<?dbhtml filename="reiserfs.html" dir="chapter06"?>
 
<screen>Estimated build time: &reiserfs-time;
Estimated required disk space: &reiserfs-compsize;</screen>
 
&c6-reiserfs-inst;
&c6-reiserfs-exp;
&aa-reiserfs-desc;
&aa-reiserfs-dep;
 
</sect1>
/tags/cvs/lfs/chapter06/gettext.xml
0,0 → 1,12
<sect1 id="ch06-gettext">
<title>Installing Gettext-&gettext-version;</title>
<?dbhtml filename="gettext.html" dir="chapter06"?>
 
<screen>Estimated build time: &gettext-time;
Estimated required disk space: &gettext-compsize;</screen>
 
&c6-gettext-inst;
&aa-gettext-desc;
&aa-gettext-dep;
 
</sect1>
/tags/cvs/lfs/chapter06/bison-inst.xml
0,0 → 1,29
<sect2>
<title>Installation of Bison</title>
 
<para>Install Bison by running the following commands:</para>
 
<para><screen><userinput>./configure --prefix=/usr &amp;&amp;
make &amp;&amp;
make install</userinput></screen></para>
 
<para>Some programs don't know about bison and try to find the yacc program
(bison is a (better) alternative for yacc). So to please those few
programs out there we'll create a yacc script that calls bison and have
it emulate yacc's output file name conventions.</para>
 
<para>Create a new file <filename>/usr/bin/yacc</filename> by running the
following:</para>
 
<para><screen><userinput>cat &gt; /usr/bin/yacc &lt;&lt; "EOF"</userinput>
#!/bin/sh
# Begin /usr/bin/yacc
 
exec /usr/bin/bison -y "$@"
 
# End /usr/bin/yacc
<userinput>EOF
chmod 755 /usr/bin/yacc</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/e2fsprogs-inst.xml
0,0 → 1,15
<sect2>
<title>Installation of E2fsprogs</title>
 
<para>Install E2fsprogs by running the following commands:</para>
 
<para><screen><userinput>mkdir ../e2fsprogs-build &amp;&amp;
cd ../e2fsprogs-build &amp;&amp;
../e2fsprogs-&e2fsprogs-version;/configure --prefix=/usr --with-root-prefix="" \
&nbsp;&nbsp;&nbsp;--enable-elf-shlibs &amp;&amp;
make &amp;&amp;
make install &amp;&amp;
make install-libs</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/netkitbase.xml
0,0 → 1,13
<sect1 id="ch06-netkitbase">
<title>Installing Netkit-base-&netkit-base-version;</title>
<?dbhtml filename="netkit-base.html" dir="chapter06"?>
 
<screen>Estimated build time: &netkit-base-time;
Estimated required disk space: &netkit-base-compsize;</screen>
 
&c6-netkitbase-inst;
&aa-netkitbase-desc;
&aa-netkitbase-dep;
 
</sect1>
 
/tags/cvs/lfs/chapter06/autoconf-inst.xml
0,0 → 1,16
<sect2>
<title>Installation de Autoconf</title>
 
<para>Autoconf-&autoconf-version; est connu pour être trop récent pour quelques applications.
KDE-CVS est souvent repporté comme ne fonctionnant pas bien avec cette version et
il est recommandé de rétrograder à la version 2.13 si vous commencez à expérimenter quelques
problèmes avec cette version.</para>
 
<para>Installez Autoconf en exécutant les commandes suivantes:</para>
 
<para><screen><userinput>./configure --prefix=/usr &amp;&amp;
make &amp;&amp;
make install</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/diffutils.xml
0,0 → 1,12
<sect1 id="ch06-diffutils">
<title>Installing Diffutils-&diffutils-version;</title>
<?dbhtml filename="diffutils.html" dir="chapter06"?>
 
<screen>Estimated build time: &diffutils-time;
Estimated required disk space: &diffutils-compsize;</screen>
 
&c6-diffutils-inst;
&aa-diffutils-desc;
&aa-diffutils-dep;
 
</sect1>
/tags/cvs/lfs/chapter06/shadowpwd-exp.xml
0,0 → 1,24
<sect2>
<title>Command explanations</title>
 
<para><userinput>sed 's/\(.*\) (nflg || \(.*\))\(.*\)/\1\2\3/'
src/useradd.c.backup &gt; src/useradd.c &amp;&amp;</userinput>:
This sed is used to fix a compilation bug which occurs due to a
variable (nflg) being used but not defined.</para>
 
<para><userinput>cp limits login.access /etc:</userinput> These files
were not installed during the installation of the package so we copy
them manually as those files are used to configure authentication
details on the system.</para>
 
<para><userinput>sed "s%/var/spool/mail%/var/mail%" login.defs.linux &gt;
/etc/login.defs</userinput>: /var/spool/mail is the old location of the
user mailboxes. The location that is used nowadays is /var/mail.</para>
 
<para><userinput>ln -sf vipw vigr</userinput> and
<userinput>ln -sf vipw.8 vigr.8</userinput>: According to the manpage of
vipw, vigr should be a symlink to it. Because the shadow installation
procedure doesn't create these symlinks, we create them manually.</para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/reiserfs-inst.xml
0,0 → 1,12
<sect2>
<title>Installation de Reiserfsprogs</title>
 
<para>Reiserfsprogs ne doivent être installés seulement si vous comptez utiliser le système de fichiers reiserfs.
Installez Reiserfsprogs en exécutant les commandes suivantes:</para>
 
<para><screen><userinput>./configure --mandir=/usr/share/man &amp;&amp;
make &amp;&amp;
make install</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/mawk.xml
0,0 → 1,13
<sect1 id="ch06-mawk">
<title>Installing Mawk-&mawk-version;</title>
<?dbhtml filename="mawk.html" dir="chapter06"?>
 
<screen>Estimated build time: &mawk-time;
Estimated required disk space: &mawk-compsize;</screen>
 
&c6-mawk-inst;
&aa-mawk-desc;
&aa-mawk-dep;
 
</sect1>
 
/tags/cvs/lfs/chapter06/kbd.xml
0,0 → 1,14
<sect1 id="ch06-kbd">
<title>Installing Kbd-&kbd-version;</title>
<?dbhtml filename="kbd.html" dir="chapter06"?>
 
<screen>Estimated build time: &kbd-time;
Estimated required disk space: &kbd-compsize;</screen>
 
&c6-kbd-inst;
&c6-kbd-exp;
&aa-kbd-desc;
&aa-kbd-dep;
 
</sect1>
 
/tags/cvs/lfs/chapter06/perl.xml
0,0 → 1,13
<sect1 id="ch06-perl">
<title>Installing Perl-&perl-version;</title>
<?dbhtml filename="perl.html" dir="chapter06"?>
 
<screen>Estimated build time: &perl-time;
Estimated required disk space: &perl-compsize;</screen>
 
&c6-perl-inst;
&aa-perl-desc;
&aa-perl-dep;
 
</sect1>
 
/tags/cvs/lfs/chapter06/ed-inst.xml
0,0 → 1,22
<sect2>
<title>Installation of Ed</title>
 
<para>Ed isn't something you would personally use. It's installed here
because it can be used by the patch program if you encounter an ed-based patch
file. This happens rarely because diff-based patches are preferred these
days.</para>
 
<para>Install Ed by running the following commands:</para>
 
<para><screen><userinput>cp buf.c buf.c.backup &amp;&amp;
sed 's/int u/int u, sfd/' buf.c.backup | \
&nbsp;&nbsp;&nbsp;sed '/.*\*mktemp.*/d' | \
&nbsp;&nbsp;&nbsp;sed 's/.*if (mktemp.*/ sfd = mkstemp(sfn);\
&nbsp;&nbsp;&nbsp;if ((sfd == -1) || (sfp = fopen (sfn, "w+")) == NULL)/' &gt; buf.c &amp;&amp;
./configure --prefix=/usr &amp;&amp;
make &amp;&amp;
make install &amp;&amp;
mv /usr/bin/ed /usr/bin/red /bin</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/e2fsprogs-exp.xml
0,0 → 1,18
<sect2>
<title>Explication des commandes</title>
 
<para><userinput>--with-root-prefix="":</userinput>La raison de fournir cette option est dûe
à la configuration du Makefile de e2fsprogs. Certains programmes sont essentiels pour
l'utilisation du système quand, par exemple, /usr n'est pas monté (comme le programme
e2fsck). Ces programmes et bibliothèques appartiennent donc à des répertoires tel que /lib et
/sbin. Si l'option n'est pas déclarée à la configuration de e2fsprog, il va placer ces
programmes dans /usr, ce que nous ne voulons pas.</para>
 
<para><userinput>--enable-elf-shlibs:</userinput> Cela crée des bibliothèques partagées que
quelques programmes dans ce package peuvent utiliser.</para>
 
<para><userinput>make install-libs:</userinput> Cela installe les bibliothèques partagées
qui sont construites.</para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/makedev.xml
0,0 → 1,14
<sect1 id="ch06-makedev">
<title>Creating devices (Makedev-&makedev-version;)</title>
<?dbhtml filename="makedev.html" dir="chapter06"?>
 
<screen>Estimated build time: &makedev-time;
Estimated required disk space: &makedev-compsize;</screen>
 
&c6-makedev-inst;
&c6-makedev-exp;
&aa-makedev-desc;
&aa-makedev-dep;
 
</sect1>
 
/tags/cvs/lfs/chapter06/reiserfs-exp.xml
0,0 → 1,9
<sect2>
<title>Explication des Commandes</title>
 
<para><userinput>--mandir=/usr/share/man:</userinput> Ceci assure
que les pages de man sont installées dans le répertoire correct,
tandis que les programmes seront toujours installés dans <filename>/sbin</filename> comme ils devraient l'être.</para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/perl-inst.xml
0,0 → 1,17
<sect2>
<title>Installation of Perl</title>
 
<para>Install Perl by running the following commands:</para>
 
<para><screen><userinput>./configure.gnu --prefix=/usr &amp;&amp;
make &amp;&amp;
make install</userinput></screen></para>
 
<para>If you want more control over the way perl sets itself up to be
build, you can run the interactive <userinput>Configure</userinput> script
and modify the way perl is built. If you think you can live with the
(sensible) defaults perl auto-detects, then just use the commands listed
above.</para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/m4.xml
0,0 → 1,13
<sect1 id="ch06-m4">
<title>Installing M4-&m4-version;</title>
<?dbhtml filename="m4.html" dir="chapter06"?>
 
<screen>Estimated build time: &m4-time;
Estimated required disk space: &m4-compsize;</screen>
 
&c6-m4-inst;
&aa-m4-desc;
&aa-m4-dep;
 
</sect1>
 
/tags/cvs/lfs/chapter06/configure.xml
0,0 → 1,17
<sect1 id="ch06-configure">
<title>Configurer les logiciels essentiels</title>
<?dbhtml filename="configure.html" dir="chapter06"?>
 
<para>Maintenant que tous les logiciels sont installés, tout ce dont nous avons besoin pour
que les programmes tournent correctemment est de créer leurs fichiers de configuration.</para>
 
&c6-cf-vim;
&c6-cf-glibc;
&c6-cf-ldso;
&c6-cf-sysklogd;
&c6-cf-shadowpwd;
&c6-cf-sysvinit;
&c6-cf-utmp;
&c6-cf-password;
 
</sect1>
/tags/cvs/lfs/chapter06/utillinux-exp.xml
0,0 → 1,8
<sect2>
<title>Explication des commandes</title>
 
<para><userinput>HAVE_SLN=yes</userinput>: Nous ne construisons
pas ce programme car il est déjà installé par Glibc.</para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/shellutils.xml
0,0 → 1,12
<sect1 id="ch06-shutils">
<title>Installing Sh-utils-&sh-utils-version;</title>
<?dbhtml filename="sh-utils.html" dir="chapter06"?>
 
<screen>Estimated build time: &sh-utils-time;
Estimated required disk space: &sh-utils-compsize;</screen>
 
&c6-shellutils-inst;
&aa-shellutils-desc;
&aa-shellutils-dep;
 
</sect1>
/tags/cvs/lfs/chapter06/file-inst.xml
0,0 → 1,12
<sect2>
<title>Installation of File</title>
 
<para>Install File by running the following commands:</para>
 
<para><screen><userinput>touch aclocal.m4 configure Makefile.in stamp-h.in &amp;&amp;
./configure --prefix=/usr --datadir=/usr/share/misc &amp;&amp;
make &amp;&amp;
make install</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/kbd-exp.xml
0,0 → 1,13
<sect2>
<title>Command explanations</title>
 
<para><userinput>patch -Np1 -i ../kbd-&kbd-patch-version;.patch</userinput>:
This patch fixes two problems. The first one is the <userinput>loadkeys -d</userinput>
behaviour which is broken in current kbd versions. It is necessary to fix this,
because the boot scripts rely on a proper <userinput>loadkeys -d</userinput>.
The second part of the patch changes a Makefile so some utilities (setlogcons,
setvesablank and getunimap) that are not installed by default, are installed as
well.</para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/glibc-inst.xml
0,0 → 1,58
<sect2>
<title>Installation of Glibc</title>
 
<para>Before starting to install glibc, you must cd into the
glibc-&glibc-version; directory and unpack glibc-linuxthreads inside
the glibc-&glibc-version; directory, not in /usr/src as you normally
would do.</para>
 
<para>This package is known to behave badly when you have changed its default
optimization flags (including the -march and -mcpu options). Glibc is
best left alone, so we recommend you unsetting CFLAGS, CXXFLAGS and other
such variables/settings that would change the default optimization that
it comes with. Also, don't pass the --enable-kernel option to the configure
script. It's known to cause segmentation faults when other packages like
fileutils, make and tar are linked against it.</para>
 
<para>Basically, compiling Glibc in any other way than the book suggests
is putting your system at very high risk.</para>
 
<para>Install Glibc by running the following commands:</para>
 
<para><screen><userinput>mknod -m 0666 /dev/null c 1 3 &amp;&amp;
touch /etc/ld.so.conf &amp;&amp;
cp malloc/Makefile malloc/Makefile.backup &amp;&amp;
sed 's%\$(PERL)%/usr/bin/perl%' malloc/Makefile.backup &gt; malloc/Makefile &amp;&amp;
cp login/Makefile login/Makefile.backup &amp;&amp;
sed 's/root/0/' login/Makefile.backup &gt; login/Makefile &amp;&amp;
mkdir ../glibc-build &amp;&amp;
cd ../glibc-build &amp;&amp;
../glibc-&glibc-version;/configure --prefix=/usr \
&nbsp;&nbsp;&nbsp;--enable-add-ons --libexecdir=/usr/bin &amp;&amp;
echo "cross-compiling = no" &gt; configparms &amp;&amp;
make &amp;&amp;
make install &amp;&amp;
make localedata/install-locales &amp;&amp;
exec /bin/bash --login</userinput></screen></para>
 
<para>An alternative to running <userinput>make
localedata/install-locales</userinput> is to only install those locales
which you need or want. This can be achieved using the localedef
command. Information on this can be found in the INSTALL
file in the glibc-&glibc-version; tree.</para>
 
<para>During the configure stage you will see the following warning:</para>
 
<blockquote><screen>configure: warning:
*** These auxiliary programs are missing or too old: msgfmt
*** some features will be disabled.
*** Check the INSTALL file for required versions.</screen></blockquote>
 
<para>The missing msgfmt (from the gettext package which we will install
later in this chapter) is not fatal. The files msgfmt would create are
already pre-built, so you won't be missing out on anything. You would
only need it if you make changes to the Glibc internationalization (i18n)
files. Since we don't do this by default, we can safely ignore it.</para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/gcc.xml
0,0 → 1,13
<sect1 id="ch06-gcc">
<title>Installing GCC-&gcc-version;</title>
<?dbhtml filename="gcc.html" dir="chapter06"?>
 
<screen>Estimated build time: &gcc-time;
Estimated required disk space: &gcc-compsize;</screen>
 
&c6-gcc-inst;
&aa-gcc-desc;
&aa-gcc-dep;
 
</sect1>
 
/tags/cvs/lfs/chapter06/patch.xml
0,0 → 1,13
<sect1 id="ch06-patch">
<title>Installing Patch-&patch-version;</title>
<?dbhtml filename="patch.html" dir="chapter06"?>
 
<screen>Estimated build time: &patch-time;
Estimated required disk space: &patch-compsize;</screen>
 
&c6-patch-inst;
&aa-patch-desc;
&aa-patch-dep;
 
</sect1>
 
/tags/cvs/lfs/chapter06/modutils.xml
0,0 → 1,12
<sect1 id="ch06-modutils">
<title>Installing Modutils-&modutils-version;</title>
<?dbhtml filename="modutils.html" dir="chapter06"?>
 
<screen>Estimated build time: &modutils-time;
Estimated required disk space: &modutils-compsize;</screen>
 
&c6-modutils-inst;
&aa-modutils-desc;
&aa-modutils-dep;
 
</sect1>
/tags/cvs/lfs/chapter06/mtablink.xml
0,0 → 1,24
<sect1 id="ch06-mtablink">
<title>Creating the /etc/mtab symlink</title>
<?dbhtml filename="mtablink.html" dir="chapter06"?>
 
<para>The next thing to do is to create a symlink pointing from
/etc/mtab to /proc/mounts. This is done using the following
command:</para>
 
<para><screen><userinput>ln -s /proc/mounts /etc/mtab</userinput></screen></para>
 
<para>Creating this symlink avoids problems which can occur if / is
mounted read-only and the information in /etc/mtab is stale (i.e. out of
date). By creating the symlink to /proc/mounts, we ensure that
/etc/mtab will always be up-to-date.</para>
 
<para>Note that using this symlink requires that you have /proc
filesystem support compiled into your kernel. This is included by
default and should not be removed unless you <emphasis>really</emphasis>
know what you are doing as many more things than just the /etc/mtab
symlink depend on /proc being present. In summary, make sure you have
/proc filesystem support in your kernel.</para>
 
</sect1>
 
/tags/cvs/lfs/chapter06/create-password.xml
0,0 → 1,10
<sect2>
<title>Créer un mot de passe pour root</title>
 
<para>Choisissez un mot de passe pour l'utilisateur root et créez-le en exécutant la commande
suivante:</para>
 
<para><screen><userinput>passwd root</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/groff.xml
0,0 → 1,13
<sect1 id="ch06-groff">
<title>Installing Groff-&groff-version;</title>
<?dbhtml filename="groff.html" dir="chapter06"?>
 
<screen>Estimated build time: &groff-time;
Estimated required disk space: &groff-compsize;</screen>
 
&c6-groff-inst;
&aa-groff-desc;
&aa-groff-dep;
 
</sect1>
 
/tags/cvs/lfs/chapter06/binutils-inst.xml
0,0 → 1,20
<sect2><title>Installation of Binutils</title>
 
<para>This package is known to behave badly when you have changed its
default optimization flags (including the -march and -mcpu options). Binutils
is best left alone, so we recommend you unsetting CFLAGS, CXXFLAGS and other
such variables/settings that would change the default optimization that
it comes with.</para>
 
<para>Install Binutils by running the following commands:</para>
 
 
<para><screen><userinput>mkdir ../binutils-build &amp;&amp;
cd ../binutils-build &amp;&amp;
../binutils-&binutils-version;/configure --prefix=/usr --enable-shared &amp;&amp;
make tooldir=/usr &amp;&amp;
make tooldir=/usr install &amp;&amp;
make tooldir=/usr install-info</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/makedev-exp.xml
0,0 → 1,13
<sect2>
<title>Explication des commandes</title>
 
<para><userinput>./MAKEDEV -v generic:</userinput> Ceci crée les
périphériques génériques. Normalement ces périphériques sont tous ceux
dont vous avez besoin. Il est possible qu'il vous manque certains
périphériques spéciaux, qui sont nécessaires pour votre configuration
matérielle. Créez-les avec ./MAKEDEV -v &lt;device&gt;.
L'option <userinput>generic-nopty</userinput> effectue un travail similaire
mais évite certains périphériques inutiles si vous utilisez devpts.</para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/nettools.xml
0,0 → 1,14
<sect1 id="ch06-nettools">
<title>Installing Net-tools-&net-tools-version;</title>
<?dbhtml filename="net-tools.html" dir="chapter06"?>
 
<screen>Estimated build time: &net-tools-time;
Estimated required disk space: &net-tools-compsize;</screen>
 
&c6-nettools-inst;
&c6-nettools-exp;
&aa-nettools-desc;
&aa-nettools-dep;
 
</sect1>
 
/tags/cvs/lfs/chapter06/mawk-inst.xml
0,0 → 1,14
<sect2>
<title>Installation de Mawk</title>
 
<para>Installez Mawk en exécutant les commandes suivantes:</para>
 
<para><screen><userinput>./configure &amp;&amp;
make &amp;&amp;
make BINDIR=/usr/bin \
&nbsp;&nbsp;&nbsp;MANDIR=/usr/share/man/man1 install &amp;&amp;
cd /usr/bin &amp;&amp;
ln -sf mawk awk</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/fileutils-inst.xml
0,0 → 1,13
<sect2>
<title>Installation of Fileutils</title>
 
<para>Install Fileutils by running the following commands:</para>
 
<para><screen><userinput>./configure --prefix=/usr --bindir=/bin &amp;&amp;
make &amp;&amp;
make install &amp;&amp;
cd /usr/bin &amp;&amp;
ln -sf ../../bin/install</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/chapter6.xml
0,0 → 1,66
<chapter id="chapter06">
<title>Installing basic system software</title>
<?dbhtml filename="chapter06.html" dir="chapter06"?>
 
&c6-introduction;
&c6-aboutdebug;
&c6-bashprofile;
&c6-chroot;
&c6-changingowner;
&c6-mtablink;
&c6-glibc;
&c6-makedev;
&c6-manpages;
&c6-findutils;
&c6-mawk;
&c6-ncurses;
&c6-vim;
&c6-gcc;
&c6-bison;
&c6-less;
&c6-groff;
&c6-man;
&c6-perl;
&c6-m4;
&c6-texinfo;
&c6-autoconf;
&c6-automake;
&c6-bash;
&c6-flex;
&c6-file;
&c6-libtool;
&c6-bin86;
&c6-binutils;
&c6-bzip2;
&c6-ed;
&c6-gettext;
&c6-kbd;
&c6-diffutils;
&c6-e2fsprogs;
&c6-fileutils;
&c6-grep;
&c6-gzip;
&c6-lilo;
&c6-make;
&c6-modutils;
&c6-netkitbase;
&c6-patch;
&c6-procinfo;
&c6-procps;
&c6-psmisc;
&c6-reiserfs;
&c6-sed;
&c6-shellutils;
&c6-nettools;
&c6-shadowpwd;
&c6-sysklogd;
&c6-sysvinit;
&c6-tar;
&c6-textutils;
&c6-utillinux;
&c6-bootscripts;
&c6-removeoldnss;
&c6-configure;
 
</chapter>
 
/tags/cvs/lfs/chapter06/findutils-inst.xml
0,0 → 1,28
<sect2>
<title>Installer Findutils</title>
 
<para>Avant que Findutils ne soit installé, il faut que le fichier patch de findutils soit
appliqué..</para>
 
<para>Installez Findutils en exécutant les commandes suivantes:</para>
 
<para><screen><userinput>patch -Np1 -i ../findutils-4.1.patch &amp;&amp;
./configure --prefix=/usr &amp;&amp;
make &amp;&amp;
make libexecdir=/usr/bin install</userinput></screen></para>
 
</sect2>
<sect2>
<title>Note de conformité FHS</title>
 
<para>Par défaut, la localisation de la base de donnée de updatedb est dans /usr/var. Si vous
préférez être conforme pour FHS, vous devriez utiliser une autre localisation. La commande suivante
utilise le fichier de base de donnée<filename>/var/lib/misc/locatedb</filename> qui est
compatible FHS.</para>
 
<para><screen><userinput>patch -Np1 -i ../findutils-4.1.patch &amp;&amp;
./configure --prefix=/usr &amp;&amp;
make localstatedir=/var/lib/misc &amp;&amp;
make localstatedir=/var/lib/misc libexecdir=/usr/bin install</userinput></screen></para>
 
</sect2>
/tags/cvs/lfs/chapter06/introduction.xml
0,0 → 1,22
<sect1 id="ch06-introduction">
<title>Introduction</title>
<?dbhtml filename="introduction.html" dir="chapter06"?>
<para>The installation of all the software is pretty straightforward and
you will probably think it's so much easier and shorter to give the generic
installation instructions for each package and only explain how to
install something if a certain package requires an alternate installation
method. Although I agree on that, I choose to give the
full instructions for each and every package. This is simply to avoid any
possible confusion and errors.</para>
 
<para>Now would be a good time to take a look at the optimization hint at <ulink
url="&hints-root;optimization.txt">&hints-root;optimization.txt</ulink>
if you plan on using compiler optimization for the packages
installed in the following chapter. Compiler optimization can make a program run
faster, but may also cause some compilation problems. If you run into problems
after having used optimization, always try it without optimizing to see if
the problem persists.</para>
 
</sect1>
 
/tags/cvs/lfs/chapter06/less-inst.xml
0,0 → 1,11
<sect2>
<title>Installation de Less</title>
 
<para>Installez Less en exécutant les commandes suivantes:</para>
 
<para><screen><userinput>./configure --prefix=/usr --bindir=/bin &amp;&amp;
make &amp;&amp;
make install</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/tar.xml
0,0 → 1,12
<sect1 id="ch06-tar">
<title>Installing Tar-&tar-version;</title>
<?dbhtml filename="tar.html" dir="chapter06"?>
 
<screen>Estimated build time: &tar-time;
Estimated required disk space: &tar-compsize;</screen>
 
&c6-tar-inst;
&aa-tar-desc;
&aa-tar-dep;
 
</sect1>
/tags/cvs/lfs/chapter06/create-utmp.xml
0,0 → 1,18
<sect2>
<title>Creating the /var/run/utmp, /var/log/wtmp and /var/log/btmp
files</title>
 
<para>Programs like login, shutdown, uptime and others want to read from and
write to the /var/run/utmp /var/log/btmp and /var/log/wtmp. These files contain
information about who is currently logged in. It also contains information
on when the computer was last booted and shutdown and a record of the
bad login attempts.</para>
 
<para>Create these files with their proper permissions by running the
following commands:</para>
 
<para><screen><userinput>touch /var/run/utmp /var/log/{btmp,lastlog,wtmp} &&
chmod 644 /var/run/utmp /var/log/{btmp,lastlog,wtmp}</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/bash-inst.xml
0,0 → 1,15
<sect2>
<title>Installation of Bash</title>
 
<para>Install Bash by running the following commands:</para>
 
<para><screen><userinput>./configure --prefix=/usr --with-curses \
&nbsp;&nbsp;&nbsp;--bindir=/bin &amp;&amp;
make &amp;&amp;
make install &amp;&amp;
cd /bin &amp;&amp;
ln -sf bash sh &amp;&amp;
exec /bin/bash --login</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/ed.xml
0,0 → 1,15
<sect1 id="ch06-ed">
<title>Installing Ed-&ed-version;</title>
<?dbhtml filename="ed.html" dir="chapter06"?>
 
<screen>Estimated build time: &ed-time;
Estimated required disk space: &ed-compsize;</screen>
 
&c6-ed-inst;
&c6-ed-exp;
&aa-ed-desc;
&aa-ed-dep;
 
</sect1>
 
 
/tags/cvs/lfs/chapter06/changingowner.xml
0,0 → 1,25
<sect1 id="ch06-changingowner">
<title>Changing ownership of the LFS partition</title>
<?dbhtml filename="changingowner.html" dir="chapter06"?>
 
<para>Now we're in chroot, it is a good time to change the ownership of
all files and directories that were installed in chapter 5 back to root.
Run the following commands to do so:</para>
 
<para><screen><userinput>cd / &amp;&amp;
chown 0.0 . proc &amp;&amp;
chown -R 0.0 bin boot dev etc home lib mnt opt root sbin tmp usr var</userinput></screen></para>
 
<para>Depending on the filesystem you created on the LFS partition, you may
have a /lost+found directory. If so, run:</para>
 
<para><screen><userinput>chown 0.0 lost+found</userinput></screen></para>
 
<para>These commands will change the ownership of the root partition and
the <filename>/proc</filename> directory to root, plus everything under
the directories mentioned in the second line. In these commands, 0.0 is
used instead of the usual root.root, because the username root can't be
resolved because glibc is not yet installed.</para>
 
</sect1>
 
/tags/cvs/lfs/chapter06/manpages.xml
0,0 → 1,12
<sect1 id="ch06-manpages">
<title>Installing Man-pages-&man-pages-version;</title>
<?dbhtml filename="man-pages.html" dir="chapter06"?>
 
<screen>Estimated build time: &man-pages-time;
Estimated required disk space: &man-pages-compsize;</screen>
 
&c6-manpages-inst;
&aa-manpages-desc;
&aa-manpages-dep;
 
</sect1>
/tags/cvs/lfs/chapter06/vim.xml
0,0 → 1,13
<sect1 id="ch06-vim">
<title>Installing Vim-&vim-version;</title>
<?dbhtml filename="vim.html" dir="chapter06"?>
 
<screen>Estimated build time: &vim-time;
Estimated required disk space: &vim-compsize;</screen>
 
&c6-vim-inst;
&c6-vim-exp;
&aa-vim-desc;
&aa-vim-dep;
 
</sect1>
/tags/cvs/lfs/chapter06/lilo.xml
0,0 → 1,12
<sect1 id="ch06-lilo">
<title>Installing Lilo-&lilo-version;</title>
<?dbhtml filename="lilo.html" dir="chapter06"?>
 
<screen>Estimated build time: &lilo-time;
Estimated required disk space: &lilo-compsize;</screen>
 
&c6-lilo-inst;
&aa-lilo-desc;
&aa-lilo-dep;
 
</sect1>
/tags/cvs/lfs/chapter06/gettext-inst.xml
0,0 → 1,11
<sect2>
<title>Installation de Gettext</title>
 
<para>Installez Gettext en exécutant les commandes suivantes:</para>
 
<para><screen><userinput>./configure --prefix=/usr &amp;&amp;
make &amp;&amp;
make install</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/bzip2-inst.xml
0,0 → 1,38
<sect2>
<title>Installation de Bzip2</title>
 
<para>Installez Bzip2 en exécutant les commandes suivantes:</para>
 
<para><screen><userinput>make -f Makefile-libbz2_so &amp;&amp;
make bzip2recover libbz2.a &amp;&amp;
ln -s libbz2.so.1.0.1 libbz2.so &amp;&amp;
cp bzip2-shared /bin/bzip2 &amp;&amp;
cp bzip2recover /bin &amp;&amp;
cp bzip2.1 /usr/share/man/man1 &amp;&amp;
cp bzlib.h /usr/include &amp;&amp;
cp -a libbz2.so* /lib &amp;&amp;
rm /usr/lib/libbz2.a &amp;&amp;
cp libbz2.a /usr/lib &amp;&amp;
cd /usr/lib &amp;&amp;
ln -sf ../../lib/libbz2.so &amp;&amp;
cd /bin &amp;&amp;
ln -sf bzip2 bunzip2 &amp;&amp;
ln -sf bzip2 bzcat &amp;&amp;
cd /usr/share/man/man1 &amp;&amp;
ln -sf bzip2.1 bunzip2.1 &amp;&amp;
ln -sf bzip2.1 bzcat.1 &amp;&amp;
ln -sf bzip2.1 bzip2recover.1</userinput></screen></para>
 
<para>Bien que ce ne soit pas, à proprement parler, une partie du système
LFS de base, il vaut la peine de mentionner que vous pouvez télécharger
un patch pour Tar qui permet au programme tar de compresser et
décompresser facilement en utilisant bzip2/bunzip2. Avec un tar normal,
un utilisateur doit utiliser des constructions telles que
bzcat fichier.tar.bz | tar xv ou tar --use-compress-prog=bunzip2 -xvf fichier.tar.bz2
pour utiliser bzip2 et bunzip2 avec tar. Ce patch vous fournit l'option -y pour
qu'un utilisateur puisse décompacter des archives Bzip2 avec tar xvfy fichier.tar.bz2.
L'application de ce patch sera décrite plus tard quand vous réinstallerez
le package Tar.</para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/automake.xml
0,0 → 1,12
<sect1 id="ch06-automake">
<title>Installing Automake-&automake-version;</title>
<?dbhtml filename="automake.html" dir="chapter06"?>
 
<screen>Estimated build time: &automake-time;
Estimated required disk space: &automake-compsize;</screen>
 
&c6-automake-inst;
&aa-automake-desc;
&aa-automake-dep;
 
</sect1>
/tags/cvs/lfs/chapter06/procinfo-exp.xml
0,0 → 1,7
<sect2>
<title>Explication des Commandes</title>
 
<para><userinput>make LDLIBS=-lncurses :</userinput> Ceci utilisera -lncurses à la place de -ltermcap lors de la construction de procinfo. Ceci est fait car libtermcap est déclarée obsolète en faveur de libncurses.</para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/gzip.xml
0,0 → 1,12
<sect1 id="ch06-gzip">
<title>Installing Gzip-&gzip-version;</title>
<?dbhtml filename="gzip.html" dir="chapter06"?>
 
<screen>Estimated build time: &gzip-time;
Estimated required disk space: &gzip-compsize;</screen>
 
&c6-gzip-inst;
&aa-gzip-desc;
&aa-gzip-dep;
 
</sect1>
/tags/cvs/lfs/chapter06/patch-inst.xml
0,0 → 1,13
<sect2>
<title>Installation of Patch</title>
 
<para>Install Patch by running the following commands:</para>
 
<para><screen><userinput>export CPPFLAGS=-D_GNU_SOURCE &amp;&amp;
./configure --prefix=/usr &amp;&amp;
unset CPPFLAGS &amp;&amp;
make &amp;&amp;
make install</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/bash.xml
0,0 → 1,12
<sect1 id="ch06-bash">
<title>Installing Bash-&bash-version;</title>
<?dbhtml filename="bash.html" dir="chapter06"?>
 
<screen>Estimated build time: &bash-time;
Estimated required disk space: &bash-compsize;</screen>
 
&c6-bash-inst;
&aa-bash-desc;
&aa-bash-dep;
 
</sect1>
/tags/cvs/lfs/chapter06/removeoldnss.xml
0,0 → 1,12
<sect1 id="ch06-removeoldnss">
<title>Désinstaller les anciennes librairies NSS</title>
<?dbhtml filename="removeoldnss.html" dir="chapter06"?>
 
<para>Si vous avez copié les fichiers des librairies NSS depuis le système Linux normal
vers le système LFS (car le système normal utilise Glibc-2.0) il est temps de les
désinstaller en exécutant:</para>
 
<para><screen><userinput>rm /lib/libnss*.so.1 /lib/libnss*2.0*</userinput></screen></para>
 
</sect1>
 
/tags/cvs/lfs/chapter06/glibc.xml
0,0 → 1,14
<sect1 id="ch06-glibc">
<title>Installing Glibc-&glibc-version;</title>
<?dbhtml filename="glibc.html" dir="chapter06"?>
 
<screen>Estimated build time: &glibc-time;
Estimated required disk space: &glibc-compsize;</screen>
 
&c6-glibc-inst;
&c6-glibc-exp;
&aa-glibc-desc;
&aa-glibc-dep;
 
</sect1>
 
/tags/cvs/lfs/chapter06/procps-inst.xml
0,0 → 1,11
<sect2>
<title>Installation de Procps</title>
 
<para>Installez Procps en exécutant les commandes suivantes:</para>
 
<para><screen><userinput>make &amp;&amp;
make XSCPT='' install &amp;&amp;
mv /usr/bin/kill /bin</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/nettools-inst.xml
0,0 → 1,10
<sect2>
<title>Installation de Net-tools</title>
 
<para>Installez Net-tools en exécutant les commandes suivantes:</para>
 
<para><screen><userinput>make &amp;&amp;
make update</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/ed-exp.xml
0,0 → 1,10
<sect2>
<title>Explication des commandes</title>
 
<para>Les commandes sed réparent une vulnérabilité dans ed. Les exécutables de ed créent
dans /tmp des fichiers dont les noms sont prévisibles. En utilisant diverses attaques sur les
liens symboliques, il est possible de faire écrire à ed des fichiers qu'il ne devrait pas, de
changer des permissions de divers fichiers, etc. </para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/config-glibc.xml
0,0 → 1,56
<sect2><title>Configurer Glibc</title>
 
<para>Nous avons besoin de créer le fichier /etc/nsswitch.conf. Bien que glibc puisse fournir
un paramétrage par défault lorsque ce fichier manque ou est corrompu, celle-ci ne
fonctionne pas correctement avec les réseaux, que nous traiterons dans un prochain
chapitre. Notre zone horaire a également besoin d'être configurée </para>
 
<para>Créez un nouveau fichier<filename>/etc/nsswitch.conf</filename> en exécutant ce qui
suit:</para>
 
<para><screen><userinput>cat &gt; /etc/nsswitch.conf &lt;&lt; "EOF"</userinput>
# Debut de /etc/nsswitch.conf
 
passwd: files
group: files
shadow: files
 
publickey: files
 
hosts: files dns
networks: files
 
protocols: db files
services: db files
ethers: db files
rpc: db files
 
netgroup: db files
 
# Fin de /etc/nsswitch.conf
<userinput>EOF</userinput></screen></para>
 
<para>Le script <userinput>tzselect</userinput> doit être lancé et vous devez répondre aux
questions correspondant à votre zone horaire. Lorsque vous l'aurez fait, le script vous
donnera l'adresse du fichier de zone horaire nécessaire</para>
 
<para> Créer le lien symbolique <filename class="directory">/etc/localtime</filename> en
exécutant:</para>
 
<para><screen><userinput>cd /etc &amp;&amp;
ln -sf ../usr/share/zoneinfo/&lt;tzselect's output&gt; localtime</userinput></screen></para>
 
<para>Les sorties de tzselect peuvent être du style <emphasis>EST5EDT</emphasis>
ou <emphasis>Canada/Eastern</emphasis>.</para>
 
<para>Le lien symbolique que vous avez créé serait:</para>
 
<para><screen><userinput>ln -sf ../usr/share/zoneinfo/EST5EDT localtime</userinput></screen></para>
 
<para>Ou:</para>
 
<para><screen><userinput>ln -sf ../usr/share/zoneinfo/Canada/Eastern localtime
</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/binutils-exp.xml
0,0 → 1,8
<sect2>
<title>Explication des commandes</title>
 
<para><userinput>make tooldir=/usr install-info:</userinput> cela vous installera les pages
d'information de binutil.</para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/bin86.xml
0,0 → 1,12
<sect1 id="ch06-bin86">
<title>Installing Bin86-&bin86-version;</title>
<?dbhtml filename="bin86.html" dir="chapter06"?>
 
<screen>Estimated build time: &bin86-time;
Estimated required disk space: &bin86-compsize;</screen>
 
&c6-bin86-inst;
&aa-bin86-desc;
&aa-bin86-dep;
 
</sect1>
/tags/cvs/lfs/chapter06/makedev-inst.xml
0,0 → 1,34
<sect2>
<title>Créer les périphériques</title>
 
<para>Note: le fichier MAKEDEV-&makedev-version;.bz2 que vous avez déballé
n'est pas une archive, alors il ne créera pas de répertoire dans lequel vous
pourrez entrer.</para>
 
<para>Créez les fichiers périphériques en exécutant les commandes suivantes:</para>
 
<para><screen><userinput>cp MAKEDEV-&makedev-version; /dev/MAKEDEV &amp;&amp;
cd /dev &amp;&amp;
chmod 754 MAKEDEV</userinput></screen></para>
 
<para>Maintenant, suivant que vous allez utiliser devpts ou non, vous pouvez
exécuter l'une des commandes:</para>
 
<para>Si vous ne comptez pas utiliser devpts, lancez:</para>
<para><screen><userinput>./MAKEDEV -v generic</userinput></screen></para>
 
<para>Si vous comptez utiliser devpts, alors lancez:</para>
<para><screen><userinput>./MAKEDEV -v generic-nopty</userinput></screen></para>
 
<para>Notez qui si vous n'êtes pas sûr, il vaut mieux utiliser la commande
<userinput>./MAKEDEV -v generic</userinput> qui assure que vous disposez des
périphériques dont vous avez besoin. Si vous êtes toutefois sûr que vous
allez utiliser devpts, l'autre commande assure que vous ne créiez pas un jeu
de périphériques dont vous n'avez pas besoin.</para>
 
<para>MAKEDEV créera hda[1-20] à hdh[1-20] et d'autres périphériques de la sorte,
mais gardez à l'esprit que vous ne pourrez pas tous les utiliser à cause des
limitations du noyau sur le nombre max. de partitions.</para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/make-inst.xml
0,0 → 1,11
<sect2>
<title>Installation de Make</title>
 
<para>Installez Make en exécutant les commandes suivantes:</para>
 
<para><screen><userinput>./configure --prefix=/usr &amp;&amp;
make &amp;&amp;
make install</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/findutils-exp.xml
0,0 → 1,9
<sect2>
<title>Explication des commandes</title>
 
<para><userinput>patch -Np1 -i ../findutils-4.1.patch</userinput>:Ce patch est là pour réparer quelques
erreurs de compilation en évitant des conflits de variables et en changeant de mauvaises
syntaxes.</para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/flex.xml
0,0 → 1,12
<sect1 id="ch06-flex">
<title>Installing Flex-&flex-version;</title>
<?dbhtml filename="flex.html" dir="chapter06"?>
 
<screen>Estimated build time: &flex-time;
Estimated required disk space: &flex-compsize;</screen>
 
&c6-flex-inst;
&aa-flex-desc;
&aa-flex-dep;
 
</sect1>
/tags/cvs/lfs/chapter06/psmisc.xml
0,0 → 1,13
<sect1 id="ch06-psmisc">
<title>Installing Psmisc-&psmisc-version;</title>
<?dbhtml filename="psmisc.html" dir="chapter06"?>
 
<screen>Estimated build time: &psmisc-time;
Estimated required disk space: &psmisc-compsize;</screen>
 
&c6-psmisc-inst;
&c6-psmisc-exp;
&aa-psmisc-desc;
&aa-psmisc-dep;
 
</sect1>
/tags/cvs/lfs/chapter06/fileutils.xml
0,0 → 1,12
<sect1 id="ch06-fileutils">
<title>Installing Fileutils-&fileutils-version;</title>
<?dbhtml filename="fileutils.html" dir="chapter06"?>
 
<screen>Estimated build time: &fileutils-time;
Estimated required disk space: &fileutils-compsize;</screen>
 
&c6-fileutils-inst;
&aa-fileutils-desc;
&aa-fileutils-dep;
 
</sect1>
/tags/cvs/lfs/chapter06/config-shadowpwd.xml
0,0 → 1,17
<sect2><title>Configuring Shadow Password Suite</title>
 
<para>This package contains the utilities to modify user's passwords, add new
users/groups, delete users/groups and more. We're not going to explain
what 'password shadowing' means. All about that can be read in the doc/HOWTO
file within the unpacked shadow password suite's source tree. There's one
thing you should keep in mind, if you decide to use shadow support, that
programs that need to verify passwords (examples are xdm, ftp daemons,
pop3 daemons, etc) need to be 'shadow-compliant', e.g. they need to
be able to work with shadow'ed passwords.</para>
 
<para>To enable shadow'ed passwords, run the following command:</para>
 
<para><screen><userinput>/usr/sbin/pwconv</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/sysvinit-inst.xml
0,0 → 1,24
<sect2>
<title>Installation of Sysvinit</title>
 
<para>When run levels are changed (for example when going to shutdown
the system) the init program is going to send the TERM and KILL signals
to all the processes that init started. But init prints a message to the
screen saying "sending all processes the TERM signal" and the same for the
KILL signal. This implies that init sends this signal to all the currently
running processes, which isn't the case. To avoid this confusion, you
change the init.c file so that the sentence reads "sending all
processes started by init the TERM signal" by running the following
commands. If you don't want to change it, skip it.</para>
 
<para><screen><userinput>cp src/init.c src/init.c.backup &amp;&amp;
sed 's/\(.*\)\(Sending processes\)\(.*\)/\1\2 started by init\3/' \
&nbsp;&nbsp;&nbsp;src/init.c.backup &gt; src/init.c</userinput></screen></para>
 
<para>Install Sysvinit by running the following commands:</para>
 
<para><screen><userinput>make -C src &amp;&amp;
make -C src install</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/diffutils-inst.xml
0,0 → 1,11
<sect2>
<title>Installation of Diffutils</title>
 
<para>Install Diffutils by running the following commands:</para>
 
<para><screen><userinput>./configure --prefix=/usr &amp;&amp;
make PR_PROGRAM=/usr/bin/pr &amp;&amp;
make install</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/netkitbase-inst.xml
0,0 → 1,16
<sect2>
<title>Installation de Netkit-base</title>
 
<para>Installez Netkit-base en exécutant les commandes suivantes:</para>
 
<para><screen><userinput>./configure &amp;&amp;
make &amp;&amp;
make install &amp;&amp;
cd etc.sample &amp;&amp;
cp services protocols /etc</userinput></screen></para>
 
<para>Il y a d'autres fichiers dans le répertoire <filename
class="directory">etc.sample</filename> qui pourraient vous intéresser.</para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/gcc-inst.xml
0,0 → 1,35
<sect2>
<title>Installation of GCC</title>
 
<para>This package is known to behave badly when you have changed its default
optimization flags (including the -march and -mcpu options). GCC is best
left alone, so we recommend you unsetting CFLAGS, CXXFLAGS and other
such variables/settings that would change the default optimization that
it comes with.</para>
 
<para>Install GCC by running the following commands. These commands will build
the C and C++ compiler. Other compilers are available within the gcc
package. If you want to build all the other available compilers too,
leave out the --enable-languages=c,c++ option in the configure command.
See the GCC documentation for more details on which additional compilers
are available.</para>
 
<para>Note: the build of other compilers is not tested by the people
who actively work on LFS.</para>
 
<para><screen><userinput>patch -Np1 -i ../gcc-&gcc-patch-version;.patch &amp;&amp;
mkdir ../gcc-build &amp;&amp;
cd ../gcc-build &amp;&amp;
../gcc-&gcc-version;/configure --prefix=/usr --enable-shared \
&nbsp;&nbsp;&nbsp;--enable-languages=c,c++ --enable-threads=posix &amp;&amp;
make bootstrap &amp;&amp;
make install &amp;&amp;
cd /lib &amp;&amp;
ln -sf ../usr/bin/cpp &amp;&amp;
cd /usr/lib &amp;&amp;
ln -sf ../bin/cpp &amp;&amp;
cd /usr/bin &amp;&amp;
ln -sf gcc cc</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/utillinux-inst.xml
0,0 → 1,25
<sect2>
<title>FHS compliance notes</title>
 
<para>The FHS recommends that we use /var/lib/hwclock as the location of the
adjtime file, instead of the usual /etc. To make hwclock, which is part of the
util-linux package, FHS-compliant, run the following.</para>
 
<para><screen><userinput>cp hwclock/hwclock.c hwclock/hwclock.c.backup &amp;&amp;
sed 's%etc/adjtime%var/lib/hwclock/adjtime%' \
&nbsp;&nbsp;&nbsp;hwclock/hwclock.c.backup &gt; hwclock/hwclock.c &amp;&amp;
mkdir -p /var/lib/hwclock</userinput></screen></para>
 
</sect2>
 
<sect2>
<title>Installation of Util-Linux</title>
 
<para>Install Util-Linux by running the following commands:</para>
 
<para><screen><userinput>./configure &amp;&amp;
make HAVE_SLN=yes &amp;&amp;
make HAVE_SLN=yes install</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/glibc-exp.xml
0,0 → 1,52
<sect2>
<title>Command explanations</title>
 
<para><userinput>mknod -m 0666 /dev/null c 1 3:</userinput> Glibc needs a
null device to compile properly. All other devices will be created in the
next section.</para>
 
<para><userinput>touch /etc/ld.so.conf</userinput> One of the final steps
of the Glibc installation is running ldconfig to update the dynamic loader
cache. If this file doesn't exist, the installation will abort with an error
that it can't read the file, so we simply create an empty file (the empty file
will have Glibc default to using /lib and /usr/lib which is fine).</para>
 
<para><userinput>sed 's%\$(PERL)%/usr/bin/perl%'
malloc/Makefile.backup &gt; malloc/Makefile:</userinput> This sed command
searches through <filename>malloc/Makefile.backup</filename> and
converts all occurrences of <filename>$(PERL)</filename> to
<filename>/usr/bin/perl</filename>. The output is then written to the
original <filename>malloc/Makefile.in</filename> which is used during
configuration. This is done because Glibc can't autodetect perl since
it hasn't been installed yet.</para>
 
<para><userinput>sed 's/root/0' login/Makefile.backup &gt;
login/Makefile:</userinput> This sed command replaces all occurrences of
<filename>root</filename> in <filename>login/Makefile.backup</filename>
with 0. This is because we don't have glibc on the LFS system yet, so
usernames can't be resolved to their user id's. Therefore, we replace
the username root with user id 0.</para>
 
<para><userinput>--enable-add-ons:</userinput> This enables the add-on that
we install with Glibc: linuxthreads</para>
 
<para><userinput>--libexecdir=/usr/bin:</userinput> This will cause the
pt_chown program to be installed in the /usr/bin directory.</para>
 
<para><userinput>echo "cross-compiling = no" &gt; configparms:</userinput>
We do this because we are only building for our own system. Cross-compiling
is used, for instance, to build a package for an Apple Power PC on an
Intel system. The reason Glibc thinks we're cross-compiling is that it
can't compile a test program to determine this, so it automatically defaults
to a cross-compiler. Compiling the test program fails because Glibc hasn't
been installed yet.</para>
 
<para><userinput>exec /bin/bash:</userinput>This command will
start a new bash shell which will replace the current shell. This is
done to get rid of the "I have no name!" message in the command
prompt, which was caused by bash's inability to resolve a userid to
a username (which in turn was caused by the missing Glibc
installation).</para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/lilo-inst.xml
0,0 → 1,34
<sect2>
<title>Installation de Lilo</title>
 
<para>Nous avons choisi Lilo car nous nous sentons à l'aise avec,
mais vous désirez peut-être regarder ailleurs. Quelqu'un a écrit
une astuce sur GRUB, un chargeur alternatif, dans <ulink
url="&hints-root;grub-howto.txt">&hints-root;grub-howto.txt</ulink>.
</para>
 
<para>Installez Lilo en exécutant les commandes suivantes:</para>
 
<para><screen><userinput>make &amp;&amp;
make install</userinput></screen></para>
 
<para>Il semble que la compilation de ce package échoue sur certaines
machines quand l'option de compilation -g est utilisée. Si vous ne
pouvez pas compiler Lilo du tout, vous devriez essayer de retirer la
valeur -g de la variable CFLAGS dans le fichier
<filename>Makefile</filename>.</para>
 
<para>A la fin de l'installtion le processus make install écrira un
message disant que /sbin/lilo doit être exécuté pour complèter la
mise à jour. Ne le faites pas car c'est inutile. Le fichier /etc/lilo.conf
n'est pas encore présent. Nous terminerons l'installation de Lilo
au chapitre 8.</para>
 
<para>Peut-être serez vous intéressé de savoir que quelqu'un a écrit une
astuce sur la manière d'avoir un logo à la place du prompt ou du menu
standard de Lilo. Jetez un oeil dessus à <ulink
url="&hints-root;bootlogo.txt">&hints-root;bootlogo.txt</ulink>
.</para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/make.xml
0,0 → 1,12
<sect1 id="ch06-make">
<title>Installing Make-&make-version;</title>
<?dbhtml filename="make.html" dir="chapter06"?>
 
<screen>Estimated build time: &make-time;
Estimated required disk space: &make-compsize;</screen>
 
&c6-make-inst;
&aa-make-desc;
&aa-make-dep;
 
</sect1>
/tags/cvs/lfs/chapter06/autoconf.xml
0,0 → 1,12
<sect1 id="ch06-autoconf">
<title>Installing Autoconf-&autoconf-version;</title>
<?dbhtml filename="autoconf.html" dir="chapter06"?>
 
<screen>Estimated build time: &autoconf-time;
Estimated required disk space: &autoconf-compsize;</screen>
 
&c6-autoconf-inst;
&aa-autoconf-desc;
&aa-autoconf-dep;
 
</sect1>
/tags/cvs/lfs/chapter06/bin86-exp.xml
0,0 → 1,11
<sect2>
<title>Explications de la commande</title>
 
<para><userinput>make INSTALL_OPTS="-m 755"...</userinput>: le Makefile déclare
INSTALL_OPTS="-m 755 -s". Le paramètre -s pousse le programme d'installation à invoquer
le programme de nettoyage afin d'enlever les symboles de débogage du programme. Cela ne
fonctionne pas proprement parce que certains fichiers ne sont pas des scripts. Le programme de
nettoyage fait des erreurs sur ceux-là.</para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/psmisc-exp.xml
0,0 → 1,12
<sect2>
<title>Explication des Commandes</title>
 
<para><userinput>--exec-prefix=/:</userinput> Cela fera que les
programmes seront installés dans <filename class="directory">/bin</filename>
plutôt que dans <filename class="directory">/usr/bin</filename>. Les
programmes de ce package sont souvent utilisés dans des scripts de boot, alors ils devraient être dans le répertoire <filename class="directory">/bin</filename> afin qu'ils
puissent être utilisés quand la partition <filename class="directory">/usr</filename>
n'est pas encore montée.</para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/utillinux.xml
0,0 → 1,13
<sect1 id="ch06-utillinux">
<title>Installing Util-linux-&util-linux-version;</title>
<?dbhtml filename="util-linux.html" dir="chapter06"?>
 
<screen>Estimated build time: &util-linux-time;
Estimated required disk space: &util-linux-compsize;</screen>
 
&c6-utillinux-inst;
&c6-utillinux-exp;
&aa-utillinux-desc;
&aa-utillinux-dep;
 
</sect1>
/tags/cvs/lfs/chapter06/config-vim.xml
0,0 → 1,18
<sect2><title>Configurer Vim</title>
 
<para>Par défault Vim fonctionne en mode compatible vi. Certaines personnes l'aiment comme
cela, mais nous avons une forte préférence pour faire tourner Vim en mode Vim (autrement nous
n'aurions pas inclu Vim dans ce livre mais l'original Vi). Créez <filename>/root/.vimrc</filename>
en exécutant ce qui suit:</para>
 
<para><screen><userinput>cat &gt; /root/.vimrc &lt;&lt; "EOF"</userinput>
" Debut de /root/.vimrc
 
set nocompatible
set bs=2
 
" Fin de /root/.vimrc
<userinput>EOF</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/config-ldso.xml
0,0 → 1,30
<sect2>
<title>Configurer le chargeur dynamique</title>
 
<para>Par défault le chargeur dynamique cherche quelques chemins par défaut pour les bibliothèques
dynamiques, donc il n'y en a normalement pas besoin pour le fichier
<filename>/etc/ld.so.conf</filename> à moins que le système n'ait des répertoires supplémentaires
dans lesquels il doit y chercher des bibliothèques. Le répertoire <filename
class="directory">/usr/local/lib</filename> n'est pas utilisé par défaut pour les
bibliothèques dynamiques, ne soyez donc pas surpris si lors de l'installation de nouveaux
logiciels, ceux-ci ne fonctionnent pas, et sans raison apparente.</para>
 
<para>Créer un nouveau fichier <filename>/etc/ld.so.conf</filename> en exécutant ce qui suit:</para>
 
<para><screen><userinput>cat &gt; /etc/ld.so.conf &lt;&lt; "EOF"</userinput>
# Begin /etc/ld.so.conf
 
/lib
/usr/lib
/usr/local/lib
 
# End /etc/ld.so.conf
<userinput>EOF</userinput></screen></para>
 
<para>Même s'il n'est pas nécessaire d'ajouter les répertoires <filename
class="directory">/lib</filename> et <filename class="directory">/usr/lib</filename>, cela
ne mange pas de pain. De cette façon, ce qui est cherché peut être trouvé immédiatement sans pour
autant que vous ayez à vous rappeller le chemin par défault si vous n'en n'avez pas envie.</para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/libtool.xml
0,0 → 1,12
<sect1 id="ch06-libtool">
<title>Installing Libtool-&libtool-version;</title>
<?dbhtml filename="libtool.html" dir="chapter06"?>
 
<screen>Estimated build time: &libtool-time;
Estimated required disk space: &libtool-compsize;</screen>
 
&c6-libtool-inst;
&aa-libtool-desc;
&aa-libtool-dep;
 
</sect1>
/tags/cvs/lfs/chapter06/file-exp.xml
0,0 → 1,11
<sect2>
<title>Command explanations</title>
 
<para><userinput>touch aclocal.m4 configure Makefile.in stamp-h.in</userinput>:
This command works around an error which occurs when compiling file with
automake-1.5 installed by changing the modification dates of some files to
the current date. Changing the date will cause make to think the files are
already up-to-date so they're not recreated.</para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/texinfo.xml
0,0 → 1,13
<sect1 id="ch06-texinfo">
<title>Installing Texinfo-&texinfo-version;</title>
<?dbhtml filename="texinfo.html" dir="chapter06"?>
 
<screen>Estimated build time: &texinfo-time;
Estimated required disk space: &texinfo-compsize;</screen>
 
&c6-texinfo-inst;
&c6-texinfo-exp;
&aa-texinfo-desc;
&aa-texinfo-dep;
 
</sect1>
/tags/cvs/lfs/chapter06/bootscripts-inst.xml
0,0 → 1,10
<sect2>
<title>Installation of LFS-Bootscripts</title>
 
<para>Install LFS-Bootscripts by running the following command:</para>
 
<para><screen><userinput>cp -a rc.d sysconfig /etc &&
chown -R root.root /etc/rc.d /etc/sysconfig</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/man-inst.xml
0,0 → 1,14
<sect2>
<title>Installation de Man</title>
 
<para>Exécutez les commandes suivantes pour installer man:</para>
 
<para><screen><userinput>./configure -default &amp;&amp;
make &amp;&amp;
make install</userinput></screen></para>
 
<para>Vous voudrez peut-être jeter un oeil à l'astuce man à <ulink
url="&hints-root;man.txt">&hints-root;man.txt</ulink>
qui traite du formatage et de la compression pour les pages de manuel.</para>
 
</sect2>
/tags/cvs/lfs/chapter06/sed-inst.xml
0,0 → 1,11
<sect2>
<title>Installation de Sed</title>
 
<para>Installez Sed en exécutant les commandes suivantes:</para>
 
<para><screen><userinput>./configure --prefix=/usr --bindir=/bin &amp;&amp;
make &amp;&amp;
make install</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/sysvinit.xml
0,0 → 1,12
<sect1 id="ch06-sysvinit">
<title>Installing Sysvinit-&sysvinit-version;</title>
<?dbhtml filename="sysvinit.html" dir="chapter06"?>
 
<screen>Estimated build time: &sysvinit-time;
Estimated required disk space: &sysvinit-compsize;</screen>
 
&c6-sysvinit-inst;
&aa-sysvinit-desc;
&aa-sysvinit-dep;
 
</sect1>
/tags/cvs/lfs/chapter06/chroot.xml
0,0 → 1,43
<sect1 id="ch06-chroot">
<title>Entering the chroot'ed environment</title>
<?dbhtml filename="chroot.html" dir="chapter06"?>
 
<para>It's time to enter our chroot'ed environment in order to install the
rest of the software we need.</para>
 
<para>Enter the following commands to enter the chroot'ed environment. From
this point on there's no need to use the $LFS variable anymore, because
everything a user does will be restricted to the LFS partition (since / is
actually /mnt/lfs but the shell doesn't know that).</para>
 
<para><screen>&c6-chrootcmd;</screen></para>
 
<para>The -i option will clear all environment variables for as long as you
are in the chroot'ed environment and only the HOME and TERM variables
are set. The TERM=$TERM construction will set the TERM variable inside
chroot to the same value as outside chroot which is needed for programs
like vim and less to operate properly. If you need other variables
present, such as CFLAGS or CXXFLAGS, you need to set them again.</para>
 
<para>The reason we do <userinput>cd $LFS</userinput> before running the
<userinput>chroot</userinput> command is that older sh-utils packages
have a chroot program which doesn't do the cd by itself, therefore
meaning that we have to perform it manually. While this isn't an issue
with most modern distributions, it does no harm anyways and ensures that
the command works for everyone.</para>
 
<para>Now that we are inside a chroot'ed environment, we can continue to
install all the basic system software. You have to make sure all the
following commands in this and following chapters are run from within the
chroot'ed environment. If you ever leave this environment for any reason
(when rebooting for example) please remember to mount $LFS/proc
again and re-enter chroot before continuing with the
book.</para>
 
<para>Note that the bash prompt will contain "I have no name!" This is
normal because Glibc hasn't been installed yet.</para>
 
&aa-chroot-dep;
 
</sect1>
 
/tags/cvs/lfs/chapter06/sysklogd.xml
0,0 → 1,12
<sect1 id="ch06-sysklogd">
<title>Installing Sysklogd-&sysklogd-version;</title>
<?dbhtml filename="sysklogd.html" dir="chapter06"?>
 
<screen>Estimated build time: &sysklogd-time;
Estimated required disk space: &sysklogd-compsize;</screen>
 
&c6-sysklogd-inst;
&aa-sysklogd-desc;
&aa-sysklogd-dep;
 
</sect1>
/tags/cvs/lfs/chapter06/less.xml
0,0 → 1,13
<sect1 id="ch06-less">
<title>Installing Less-&less-version;</title>
<?dbhtml filename="less.html" dir="chapter06"?>
 
<screen>Estimated build time: &less-time;
Estimated required disk space: &less-compsize;</screen>
 
&c6-less-inst;
&aa-less-desc;
&aa-less-dep;
 
</sect1>
 
/tags/cvs/lfs/chapter06/texinfo-exp.xml
0,0 → 1,10
<sect2>
<title>Command explanations</title>
 
<para><userinput>make TEXMF=/usr/share/texmf install-tex:</userinput>
This installs the texinfo components that belong in a TeX
installation. Although TeX isn't installed on LFS, it's installed here
to complete the texinfo installation. </para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/grep-inst.xml
0,0 → 1,11
<sect2>
<title>Installation of Grep</title>
 
<para>Install Grep by running the following commands:</para>
 
<para><screen><userinput>./configure --prefix=/usr --bindir=/bin &amp;&amp;
make &amp;&amp;
make install</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/shadowpwd-inst.xml
0,0 → 1,32
<sect2>
<title>Installation of Shadow Password Suite</title>
 
<para>Before you install this package, you may want to have a look at the
<ulink url="http://hints.linuxfromscratch.org/hints/shadowpasswd_plus.txt">http://hints.linuxfromscratch.org/hints/shadowpasswd_plus.txt</ulink>
lfs hint. It discusses how you can make your system more secure regarding
passwords and how to get the most out of this Shadow package.</para>
 
<para>Install the Shadow Password Suite by running the
following commands:</para>
 
<para><screen><userinput>cp src/useradd.c src/useradd.c.backup &amp;&amp;
sed 's/\(.*\) (nflg || \(.*\))\(.*\)/\1\2\3/' \
&nbsp;&nbsp;&nbsp;src/useradd.c.backup &gt; src/useradd.c &amp;&amp;
./configure --prefix=/usr &amp;&amp;
make &amp;&amp;
make install &amp;&amp;
cd etc &amp;&amp;
cp limits login.access /etc &amp;&amp;
sed 's%/var/spool/mail%/var/mail%' login.defs.linux &gt; /etc/login.defs &amp;&amp;
cd /lib &amp;&amp;
mv libshadow.*a /usr/lib &amp;&amp;
ln -sf libshadow.so.0 libshadow.so &amp;&amp;
cd /usr/lib &amp;&amp;
ln -sf ../../lib/libshadow.so &amp;&amp;
cd /usr/sbin &amp;&amp;
ln -sf vipw vigr &amp;&amp;
cd /usr/share/man/man8 &amp;&amp;
ln -sf vipw.8 vigr.8</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/procinfo.xml
0,0 → 1,13
<sect1 id="ch06-procinfo">
<title>Installing Procinfo-&procinfo-version;</title>
<?dbhtml filename="procinfo.html" dir="chapter06"?>
 
<screen>Estimated build time: &procinfo-time;
Estimated required disk space: &procinfo-compsize;</screen>
 
&c6-procinfo-inst;
&c6-procinfo-exp;
&aa-procinfo-desc;
&aa-procinfo-dep;
 
</sect1>
/tags/cvs/lfs/chapter06/gzip-inst.xml
0,0 → 1,20
<sect2>
<title>Installation of Gzip</title>
 
<para>Install Gzip by running the following commands:</para>
 
<para><screen><userinput>./configure --prefix=/usr &amp;&amp;
cp gzexe.in gzexe.in.backup &amp;&amp;
sed 's%"BINDIR"%/bin%' gzexe.in.backup &gt; gzexe.in &amp;&amp;
make &amp;&amp;
make install &amp;&amp;
cd /usr/bin &amp;&amp;
mv gzip /bin &amp;&amp;
rm gunzip zcat &amp;&amp;
cd /bin &amp;&amp;
ln -sf gzip gunzip &amp;&amp;
ln -sf gzip zcat &amp;&amp;
ln -sf gunzip uncompress</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/bzip2.xml
0,0 → 1,13
<sect1 id="ch06-bzip2">
<title>Installing Bzip2-&bzip2-version;</title>
<?dbhtml filename="bzip2.html" dir="chapter06"?>
 
<screen>Estimated build time: &bzip2-time;
Estimated required disk space: &bzip2-compsize;</screen>
 
&c6-bzip2-inst;
&c6-bzip2-exp;
&aa-bzip2-desc;
&aa-bzip2-dep;
 
</sect1>
/tags/cvs/lfs/chapter06/binutils.xml
0,0 → 1,13
<sect1 id="ch06-binutils">
<title>Installing Binutils-&binutils-version;</title>
<?dbhtml filename="binutils.html" dir="chapter06"?>
 
<screen>Estimated build time: &binutils-time;
Estimated required disk space: &binutils-compsize;</screen>
 
&c6-binutils-inst;
&c6-binutils-exp;
&aa-binutils-desc;
&aa-binutils-dep;
 
</sect1>
/tags/cvs/lfs/chapter06/config-sysvinit.xml
0,0 → 1,36
<sect2><title>Configuring Sysvinit</title>
 
<para>Create a new file <filename>/etc/inittab</filename> by running the
following:</para>
 
<para><screen><userinput>cat &gt; /etc/inittab &lt;&lt; "EOF"</userinput>
# Begin /etc/inittab
 
id:3:initdefault:
 
si::sysinit:/etc/rc.d/init.d/rc sysinit
 
l0:0:wait:/etc/rc.d/init.d/rc 0
l1:S1:wait:/etc/rc.d/init.d/rc 1
l2:2:wait:/etc/rc.d/init.d/rc 2
l3:3:wait:/etc/rc.d/init.d/rc 3
l4:4:wait:/etc/rc.d/init.d/rc 4
l5:5:wait:/etc/rc.d/init.d/rc 5
l6:6:wait:/etc/rc.d/init.d/rc 6
 
ca:12345:ctrlaltdel:/sbin/shutdown -t1 -a -r now
 
su:S016:respawn:/sbin/sulogin
 
1:2345:respawn:/sbin/agetty tty1 9600
2:2345:respawn:/sbin/agetty tty2 9600
3:2345:respawn:/sbin/agetty tty3 9600
4:2345:respawn:/sbin/agetty tty4 9600
5:2345:respawn:/sbin/agetty tty5 9600
6:2345:respawn:/sbin/agetty tty6 9600
 
# End /etc/inittab
<userinput>EOF</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/grep.xml
0,0 → 1,12
<sect1 id="ch06-grep">
<title>Installing Grep-&grep-version;</title>
<?dbhtml filename="grep.html" dir="chapter06"?>
 
<screen>Estimated build time: &grep-time;
Estimated required disk space: &grep-compsize;</screen>
 
&c6-grep-inst;
&aa-grep-desc;
&aa-grep-dep;
 
</sect1>
/tags/cvs/lfs/chapter06/bashprofile.xml
0,0 → 1,31
<sect1 id="ch06-bashprofile">
<title>Création de $LFS/root/.bash_profile</title>
<?dbhtml filename="bashprofile.html" dir="chapter06"?>
 
<para>Lorsque nous serons dans l'environnement chroot de la prochaine section nous voudrons exporter
deux variables d'environnement dans ce shell comme PS1, PATH et d'autres variables qu'il sera bon
d'avoir parémétré. Dans cet objectif nous allons créer le fichier
$LFS/root/.bash_profile qui sera lu par bash lorsque nous entrerons dans l'environnement
chroot.</para>
 
<para>Créer un nouveau fichier <filename>$LFS/root/.bash_profile</filename>
en exécutant ce qui suit.</para>
 
<para><screen><userinput>cat &gt; $LFS/root/.bash_profile &lt;&lt; "EOF"</userinput>
# Début /root/.bash_profile
 
PS1='\u:\w\$ '
PATH=/bin:/usr/bin:/sbin:/usr/sbin
 
export PS1 PATH
 
# Fin /root/.bash_profile
<userinput>EOF</userinput></screen></para>
 
<para> La variable PS1 est une variable d'environnement qui contrôle l'apparence de l'invite
de commande. Voyez les pages man de bash pour les détails de la construction de cette
variable. D'autres variables d'environnement, alias et aussi tout ce dont vous avez besoin et/ou
voulez peuvent être ajouter à votre discrétion.</para>
 
</sect1>
 
/tags/cvs/lfs/chapter06/findutils.xml
0,0 → 1,14
<sect1 id="ch06-findutils">
<title>Installing Findutils-&findutils-version;</title>
<?dbhtml filename="findutils.html" dir="chapter06"?>
 
<screen>Estimated build time: &findutils-time;
Estimated required disk space: &findutils-compsize;</screen>
 
&c6-findutils-inst;
&c6-findutils-exp;
&aa-findutils-desc;
&aa-findutils-dep;
 
</sect1>
 
/tags/cvs/lfs/chapter06/nettools-exp.xml
0,0 → 1,16
<sect2>
<title>Explication des commandes</title>
 
<para><userinput>make update:</userinput> Réalise la même chose qu'un
<userinput>make install</userinput> avec la différence que make update
n'effectue pas de sauvegardes des fichiers qu'il remplace. Une des choses
que net-tools remplace est la version sh-utils de
<filename>/bin/hostname</filename> (la version net-tools est de loin
meilleure que celle de sh-utils).</para>
 
<para>De même, si vous décidez dans le futur de réinstaller ce package,
un <userinput>make update</userinput> ne sauvegardera pas les fichiers
d'une précédente installation de net-tools.</para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/tar-inst.xml
0,0 → 1,22
<sect2>
<title>Installation de Tar</title>
 
<para>Si vous voulez pouvoir utiliser directement des fichiers bzip2 avec tar,
vous pouvez utiliser le patch tar disponible depuis le site FTP de LFS.
Ce patch ajoutera l'option -j à tar, qui fonctionne comme l'option -z de tar
(qui peut être utilisée pour les fichiers gzip).</para>
<para>Appliquez le patch en exécutant la commande suivante:</para>
 
<para><screen><userinput>patch -Np1 -i ../tar-1.13.patch</userinput></screen></para>
 
<para>Installez Tar en exécutant les commandes suivantes depuis le répertoire de
plus haut niveau:</para>
 
<para><screen><userinput>./configure --prefix=/usr --libexecdir=/usr/bin \
&nbsp;&nbsp;&nbsp;--bindir=/bin &amp;&amp;
make &amp;&amp;
make install</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/config-sysklogd.xml
0,0 → 1,21
<sect2><title>Configurer Sysklogd</title>
 
<para>Créez un nouveau fichier <filename>/etc/syslog.conf</filename> en éxécutant ce qui
suit:</para>
 
<para><screen><userinput>cat &gt; /etc/syslog.conf &lt;&lt; "EOF"</userinput>
# Debut de /etc/syslog.conf
 
auth,authpriv.* -/var/log/auth.log
*.*;auth,authpriv.none -/var/log/sys.log
daemon.* -/var/log/daemon.log
kern.* -/var/log/kern.log
mail.* -/var/log/mail.log
user.* -/var/log/user.log
*.emerg *
 
# Fin de /etc/syslog.conf
<userinput>EOF</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/procps.xml
0,0 → 1,13
<sect1 id="ch06-procps">
<title>Installing Procps-&procps-version;</title>
<?dbhtml filename="procps.html" dir="chapter06"?>
 
<screen>Estimated build time: &procps-time;
Estimated required disk space: &procps-compsize;</screen>
 
&c6-procps-inst;
&c6-procps-exp;
&aa-procps-desc;
&aa-procps-dep;
 
</sect1>
/tags/cvs/lfs/chapter06/sysklogd-inst.xml
0,0 → 1,10
<sect2>
<title>Installation de Sysklogd</title>
 
<para>Installez Sysklogd en exécutant les commandes suivantes:</para>
 
<para><screen><userinput>make &amp;&amp;
make install</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/kbd-inst.xml
0,0 → 1,12
<sect2>
<title>Installation of Kbd</title>
 
<para>Install Kbd by running the following commands:</para>
 
<para><screen><userinput>patch -Np1 -i ../kbd-&kbd-patch-version;.patch &amp;&amp;
./configure &amp;&amp;
make &amp;&amp;
make install</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/groff-inst.xml
0,0 → 1,11
<sect2>
<title>Installation de Groff</title>
 
<para>Installez Groff en exécutant les commandes suivantes:</para>
 
<para><screen><userinput>./configure --prefix=/usr &amp;&amp;
make &amp;&amp;
make install</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/libtool-inst.xml
0,0 → 1,11
<sect2>
<title>Installation de Libtool</title>
 
<para>Installez Libtool en exécutant les commandes suivantes:</para>
 
<para><screen><userinput>./configure --prefix=/usr &amp;&amp;
make &amp;&amp;
make install</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/textutils-inst.xml
0,0 → 1,12
<sect2>
<title>Installation of Textutils</title>
 
<para>Install Textutils by running the following commands:</para>
 
<para><screen><userinput>./configure --prefix=/usr &amp;&amp;
make &amp;&amp;
make install &amp;&amp;
mv /usr/bin/cat /usr/bin/head /bin</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/bzip2-exp.xml
0,0 → 1,14
<sect2>
<title>Explication de la commande</title>
 
<para><userinput>make -f Makefile-libbz2_so:</userinput> cela provoque la construction de bzip2 en
utilisant un fichier Makefile différent, dans ce cas le fichier Makefile-libbz2_so qui crée une
bibliothèque dynamique libbz2.so et la lie avec les utilitaires de bzip2.</para>
 
<para>La raison pour laquelle nous n'utilisons pas <userinput>make install</userinput> est que le
make install de bzip2 n'installe pas la libbz2.so partagée, ni les binaires de bzip2 qui sont liés à
cette bibliothèque. Donc nous n'avons pas d'autres choix que d'installer les fichiers
manuellement.</para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/automake-inst.xml
0,0 → 1,14
<sect2>
<title>Installation d'Automake</title>
 
<para>Automake-&automake-version; est connu pour être trop récent pour quelques applications.
KDE-CVS est repporté comme ne fonctionnant pas bien avec cette version il est recommandé de
rétrograder à la version 1.4-p5 si vous commencez à avoir des problèmes avec cette version.</para>
 
<para>Installez Automake en exécutant les commandes suivantes:</para>
 
<para><screen><userinput>./configure --prefix=/usr &amp;&amp;
make install</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/chrootcmd.xml
0,0 → 1,3
<userinput>cd $LFS &amp;&amp;
chroot $LFS /usr/bin/env -i HOME=/root \
&nbsp;&nbsp;&nbsp;TERM=$TERM /bin/bash --login</userinput>
/tags/cvs/lfs/chapter06/ncurses.xml
0,0 → 1,14
<sect1 id="ch06-ncurses">
<title>Installing Ncurses-&ncurses-version;</title>
<?dbhtml filename="ncurses.html" dir="chapter06"?>
 
<screen>Estimated build time: &ncurses-time;
Estimated required disk space: &ncurses-compsize;</screen>
 
&c6-ncurses-inst;
&c6-ncurses-exp;
&aa-ncurses-desc;
&aa-ncurses-dep;
 
</sect1>
 
/tags/cvs/lfs/chapter06/vim-exp.xml
0,0 → 1,17
<sect2>
<title>Explication des commandes</title>
 
<para><userinput>sed '/shUntil\|link shRepeat/{...:</userinput> Cette commande sed
fixe un bogue dans le fichier <filename>syntax/sh.vim</filename> qui
causera un message d'erreur lorsque vous éditerez un script shell
en utilisant le surlignage de la syntaxe.</para>
 
<para><userinput>make
CPPFLAGS=-DSYS_VIMRC_FILE=\\\"/etc/vimrc\\\":</userinput> Positionner cette
variable imposera à vim d'utiliser le fichier <filename>/etc/vimrc</filename>
pour les paramètres globaux de vim. Normalement ce fichier est
situé dans <filename class="directory">/usr/share/vim</filename>, mais
<filename class="directory">/etc</filename> est un endroit plus logique pour ce genre de fichiers.</para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/texinfo-inst.xml
0,0 → 1,12
<sect2>
<title>Installation de Texinfo</title>
 
<para>Installez Texinfo en exécutant les commandes suivantes:</para>
 
<para><screen><userinput>./configure --prefix=/usr &amp;&amp;
make &amp;&amp;
make install &amp;&amp;
make TEXMF=/usr/share/texmf install-tex</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/procinfo-inst.xml
0,0 → 1,10
<sect2>
<title>Installation de Procinfo</title>
 
<para>Installez Procinfo en exécutant les commandes suivantes:</para>
 
<para><screen><userinput>make LDLIBS=-lncurses &amp;&amp;
make install</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/m4-inst.xml
0,0 → 1,11
<sect2>
<title>Installation de M4</title>
 
<para>Installez M4 en exécutant les commandes suivantes:</para>
 
<para><screen><userinput>./configure --prefix=/usr &amp;&amp;
make &amp;&amp;
make install</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/ncurses-inst.xml
0,0 → 1,21
<sect2>
<title>Installation de Ncurses</title>
 
<para>Installez Ncurses en exécutant les commandes suivantes:</para>
 
<para><screen><userinput>./configure --prefix=/usr --libdir=/lib \
&nbsp;&nbsp;&nbsp;--with-shared --disable-termcap &amp;&amp;
make &amp;&amp;
make install &amp;&amp;
cd /lib &amp;&amp;
mv *.a /usr/lib &amp;&amp;
chmod 755 *.5.2 &amp;&amp;
cd /usr/lib &amp;&amp;
ln -sf libncurses.a libcurses.a &amp;&amp;
ln -sf ../../lib/libncurses.so &amp;&amp;
ln -sf ../../lib/libcurses.so &amp;&amp;
ln -sf ../../lib/libform.so &amp;&amp;
ln -sf ../../lib/libpanel.so &amp;&amp;
ln -sf ../../lib/libmenu.so</userinput></screen></para>
</sect2>
 
/tags/cvs/lfs/chapter06/procps-exp.xml
0,0 → 1,11
<sect2>
<title>Command explanations</title>
 
<para><userinput>make XSCPT='' install:</userinput>
This will set the Makefile variable XSCPT to an empty value so that
the XConsole installation is disabled. Otherwise "Make install" tries to
copy the file XConsole to /usr/X11R6/lib/X11/app-defaults. And that directory
does not exist, because X is not installed.</para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/shadowpwd.xml
0,0 → 1,13
<sect1 id="ch06-shadow">
<title>Installing Shadow-&shadow-version;</title>
<?dbhtml filename="shadow.html" dir="chapter06"?>
 
<screen>Estimated build time: &shadow-time;
Estimated required disk space: &shadow-compsize;</screen>
 
&c6-shadowpwd-inst;
&c6-shadowpwd-exp;
&aa-shadowpwd-desc;
&aa-shadowpwd-dep;
 
</sect1>
/tags/cvs/lfs/chapter06/bin86-inst.xml
0,0 → 1,19
<sect2>
<title>Installation de Bin86</title>
 
<para>Ce package est nécessaire seulement si vous décidez d'utiliser Lilo sur votre système
LFS. Si vous escomptez utiliser un autre outil tel que Grub vous n'aurez pas besoin de
bin86. Vérifiez la documentation de votre chargeur préféré pour voir si vous avez besoin du
package bin86 (habituellement seulement ld86 et/ou as86 de ce package sont requis).</para>
 
<para>Gardez à l'esprit qu'il n'y a pas seulement les chargeurs qui utilisent le package
bin86. Il y a toujours une chance qu'un autre package ait besoin de programmes de ce package, donc
garder tout ça à l'esprit si vous décidez de le sauter.</para>
 
<para>Installez Bin86 en exécutant les commandes suivantes:</para>
 
<para><screen><userinput>make &amp;&amp;
make PREFIX=/usr install</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/shellutils-inst.xml
0,0 → 1,30
<sect2>
<title>Installation of Sh-utils</title>
 
<para>Install Shellutils by running the following commands:</para>
 
<para><screen><userinput>./configure --prefix=/usr &amp;&amp;
make &amp;&amp;
make install &amp;&amp;
cd /usr/bin &amp;&amp;
mv basename date echo false hostname /bin &amp;&amp;
mv pwd sleep stty su test true uname /bin &amp;&amp;
mv chroot ../sbin</userinput></screen></para>
 
</sect2>
 
<sect2>
<title>FHS compliance notes</title>
 
<para>There is a command installed in this package which is named test. It is
often used in shell scripts to evaluate conditions, but is more often
encountered in the form of <command>[ condition ]</command>. These brackets
are built into the bash interpreter, but the FHS dictates that there should be a
<filename>[</filename> binary. We create that in this way, while still in the
<filename>/usr/bin</filename> directory:</para>
 
<para><screen><userinput>cd /bin &amp;&amp;
ln -sf test [</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/textutils.xml
0,0 → 1,12
<sect1 id="ch06-textutils">
<title>Installing Textutils-&textutils-version;</title>
<?dbhtml filename="textutils.html" dir="chapter06"?>
 
<screen>Estimated build time: &textutils-time;
Estimated required disk space: &textutils-compsize;</screen>
 
&c6-textutils-inst;
&aa-textutils-desc;
&aa-textutils-dep;
 
</sect1>
/tags/cvs/lfs/chapter06/manpages-inst.xml
0,0 → 1,9
<sect2>
<title>Installation of Man-pages</title>
 
<para>Install Man-pages by running the following commands:</para>
 
<para><screen><userinput>make install</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/vim-inst.xml
0,0 → 1,61
<sect2>
<title>Installation of Vim</title>
 
<para>If you don't like vim to be installed as an editor on the LFS system,
you may want to download an alternative and install an editor you
prefer. There are a few hints how to install different editors
available at <ulink url="&hints-root;">&hints-root;</ulink>. The hints
which are currently available are for Emacs, Joe and nano.</para>
 
<para>Install Vim by running the following commands:</para>
 
<para><screen><userinput>cp runtime/syntax/sh.vim runtime/syntax/sh.vim.backup &amp;&amp;
sed '/shUntil\|link shRepeat/{
&nbsp;&nbsp;&nbsp;/shUntil/N
&nbsp;&nbsp;&nbsp;/^/i\
&nbsp;&nbsp;&nbsp;if exists("b:is_kornshell") || exists("b:is_bash")
&nbsp;&nbsp;&nbsp;p
&nbsp;&nbsp;&nbsp;/$/i\
&nbsp;&nbsp;&nbsp;endif
&nbsp;&nbsp;&nbsp;d
&nbsp;&nbsp;&nbsp;}' runtime/syntax/sh.vim.backup &gt; runtime/syntax/sh.vim &amp;&amp;
./configure --prefix=/usr &amp;&amp;
make CPPFLAGS=-DSYS_VIMRC_FILE=\\\"/etc/vimrc\\\" &amp;&amp;
make install &amp;&amp;
cd /usr/bin &amp;&amp;
ln -sf vim vi</userinput></screen></para>
 
<para>If you plan on installing the X Window system on your LFS
system, you might want to re-compile Vim after you have installed X. Vim
comes with a nice GUI version of the editor which requires X and a few
other libraries to be installed. For more information read the Vim
documentation.</para>
 
</sect2>
 
<sect2>
<title>FHS compliance notes</title>
 
<para>The FHS says that editors like vim should use /var/lib/&lt;editor&gt;
for their temporary state files, like temporary save files for example.
If you wish vim to conform to the FHS, you should use this command set
instead of the one presented above:</para>
 
<para><screen><userinput>cp runtime/syntax/sh.vim runtime/syntax/sh.vim.backup &amp;&amp;
sed '/shUntil\|link shRepeat/{
&nbsp;&nbsp;&nbsp;/shUntil/N
&nbsp;&nbsp;&nbsp;/^/i\
&nbsp;&nbsp;&nbsp;if exists("b:is_kornshell") || exists("b:is_bash")
&nbsp;&nbsp;&nbsp;p
&nbsp;&nbsp;&nbsp;/$/i\
&nbsp;&nbsp;&nbsp;endif
&nbsp;&nbsp;&nbsp;d
&nbsp;&nbsp;&nbsp;}' runtime/syntax/sh.vim.backup &gt; runtime/syntax/sh.vim &amp;&amp;
./configure --prefix=/usr --localstatedir=/var/lib/vim &amp;&amp;
make CPPFLAGS=-DSYS_VIMRC_FILE=\\\"/etc/vimrc\\\" &amp;&amp;
make install &amp;&amp;
cd /usr/bin &amp;&amp;
ln -sf vim vi</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/psmisc-inst.xml
0,0 → 1,30
<sect2>
<title>Installation de Psmisc</title>
 
<para>Installez Psmisc en exécutant les commandes suivantes:</para>
 
<para><screen><userinput>./configure --prefix=/usr --exec-prefix=/ &amp;&amp;
make &amp;&amp;
make install</userinput></screen></para>
 
<para>psmisc installe la page de man
<filename>/usr/share/man/man1/pidof.1</filename>, mais le programme pidof
de psmisc n'est pas installé par défaut. Généralement ceci n'est pas un problème
car nous installerons le package sysvinit plus tard, qui nous fournit un meilleur
programme pidof.</para>
 
<para>C'est à vous de décider maintenant si vous allez utiliser le package sysvinit
qui fournit un programme pidof, ou non. Si vous le souhaitez, vous
devriez enlever la page man pidof de psmisc en exécutant:</para>
 
<para><screen><userinput>rm /usr/share/man/man1/pidof.1</userinput></screen></para>
 
<para>Si vous n'utilisez pas sysvinit, vous devriez complèter l'installation
de ce package en créant le lien symbolique <filename>/bin/pidof</filename>
en exécutant:</para>
 
<para><screen><userinput>cd /bin
ln -s killall pidof</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/flex-inst.xml
0,0 → 1,27
<sect2>
<title>Installation de Flex</title>
 
<para>Installez Flex en exécutant les commandes suivante:</para>
 
<para><screen><userinput>./configure --prefix=/usr &amp;&amp;
make &amp;&amp;
make install</userinput></screen></para>
 
<para>Quelques programmes ne reconnaissent pas flex et essaient de trouver le programme lex
(flex est une (meilleure) alternative à lex). Donc pour satisfaire ces quelques programmes
nous devrons créer un script lex, qui appelle flex et qui induit que celui-ci imite lex.</para>
 
<para>Créez un nouveau fichier <filename>/usr/bin/lex</filename> en exécutant ce qui suit:</para>
 
<para><screen><userinput>cat &gt; /usr/bin/lex &lt;&lt; "EOF"</userinput>
#!/bin/sh
# Debut /usr/bin/lex
 
exec /usr/bin/flex -l "$@"
 
# Fin /usr/bin/lex
<userinput>EOF
chmod 755 /usr/bin/lex</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/bison.xml
0,0 → 1,13
<sect1 id="ch06-bison">
<title>Installing Bison-&bison-version;</title>
<?dbhtml filename="bison.html" dir="chapter06"?>
 
<screen>Estimated build time: &bison-time;
Estimated required disk space: &bison-compsize;</screen>
 
&c6-bison-inst;
&aa-bison-desc;
&aa-bison-dep;
 
</sect1>
 
/tags/cvs/lfs/chapter06/e2fsprogs.xml
0,0 → 1,13
<sect1 id="ch06-e2fsprogs">
<title>Installing E2fsprogs-&e2fsprogs-version;</title>
<?dbhtml filename="e2fsprogs.html" dir="chapter06"?>
 
<screen>Estimated build time: &e2fsprogs-time;
Estimated required disk space: &e2fsprogs-compsize;</screen>
 
&c6-e2fsprogs-inst;
&c6-e2fsprogs-exp;
&aa-e2fsprogs-desc;
&aa-e2fsprogs-dep;
 
</sect1>
/tags/cvs/lfs/chapter06/sed.xml
0,0 → 1,12
<sect1 id="ch06-sed">
<title>Installing Sed-&sed-version;</title>
<?dbhtml filename="sed.html" dir="chapter06"?>
 
<screen>Estimated build time: &sed-time;
Estimated required disk space: &sed-compsize;</screen>
 
&c6-sed-inst;
&aa-sed-desc;
&aa-sed-dep;
 
</sect1>
/tags/cvs/lfs/chapter06/modutils-inst.xml
0,0 → 1,11
<sect2>
<title>Installation de Modutils</title>
 
<para>Installez Modutils en exécutant les commandes suivantes:</para>
 
<para><screen><userinput>./configure &amp;&amp;
make &amp;&amp;
make install</userinput></screen></para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/man.xml
0,0 → 1,13
<sect1 id="ch06-man">
<title>Installing Man-&man-version;</title>
<?dbhtml filename="man.html" dir="chapter06"?>
 
<screen>Estimated build time: &man-time;
Estimated required disk space: &man-compsize;</screen>
 
&c6-man-inst;
&aa-man-desc;
&aa-man-dep;
 
</sect1>
 
/tags/cvs/lfs/chapter06/bootscripts.xml
0,0 → 1,13
<sect1 id="ch06-bootscripts">
<title>Installing LFS-Bootscripts-&bootscripts-version;</title>
<?dbhtml filename="bootscripts.html" dir="chapter06"?>
 
<screen>Estimated build time: &bootscripts-time;
Estimated required disk space: &bootscripts-compsize;</screen>
 
&c6-bootscripts-inst;
&aa-bootscripts-desc;
&aa-bootscripts-dep;
 
</sect1>
 
/tags/cvs/lfs/chapter06/ncurses-exp.xml
0,0 → 1,29
<sect2>
<title>Command explanations</title>
 
<para><userinput>--with-shared:</userinput> This enables the build of the
shared ncurses library files.</para>
 
<para><userinput>--disable-termcap:</userinput> Disabled the compilation of
termcap fall back support.</para>
 
<para><userinput>cd /lib &amp;&amp; mv *.a /usr/lib :</userinput> This
moves all of the static ncurses library files from /lib to /usr/lib.
/lib should only contain the shared files which are essential to the
system when /usr may not be mounted.</para>
 
<para><userinput>chmod 755 *.5.2:</userinput> Shared libraries should be
executable. Ncurses install routine doesn't set the permissions
properly so we do it manually instead.</para>
 
<para><userinput>ln -sf libncurses.a libcurses.a:</userinput> Some
programs try to link using -lcurses instead of -lncurses. This symlink
ensures that such programs will link without errors.</para>
 
<para><userinput>ln -sf ../../lib/libncurses.so etc:</userinput> These
symlinks are created so the linker will use the dynamic versions of these
libraries instead of the static ones, which happens if the linker can't
find the dynamic versions.</para>
 
</sect2>
 
/tags/cvs/lfs/chapter06/file.xml
0,0 → 1,14
<sect1 id="ch06-file">
<title>Installing File-&file-version;</title>
<?dbhtml filename="file.html" dir="chapter06"?>
 
<screen>Estimated build time: &file-time;
Estimated required disk space: &file-compsize;</screen>
 
&c6-file-inst;
&c6-file-exp;
&aa-file-desc;
&aa-file-dep;
 
</sect1>
 
/tags/cvs/lfs/README
0,0 → 1,45
How do I convert these XML files to other formats like HTML, PF, PS
and TXT? You need to have some software installed that deal with these
conversions. Please read the INSTALL file how to install that software.
Then come back to this file for examples how to convert these files
into various other formats.
 
XML to HTML:
------------
Create a directory in which you want to store the HTML files and cd into
that directory. Now run:
/usr/bin/openjade -t xml \
-d /usr/share/dsssl/docbook/html/lfs.dsl \
/usr/share/dsssl/docbook/dtds/decls/xml.dcl \
/path/to/index.xml
 
 
 
XML to NOCHUNKS-HTML:
--------------------
The NOCHUNKS HTML version is one big HTML file:
/usr/bin/openjade -t sgml \
-V nochunks \
-d /usr/share/dsssl/docbook/html/lfs.dsl \
/usr/share/dsssl/docbook/dtds/decls/xml.dcl \
/path/to/index.xml > nochunks.html
 
XML to TXT:
-----------
First create the NOCHUNKS HTML file, then convert by running:
/usr/bin/lynx -dump nochunks.html > output.txt
 
XML to PS and PDF:
------------------
First create the NOCHUNKS HTML file, then convert by starting
htmldoc. You can use the GUI and select the options. If you're
satisfied with the default options you can run this command:
 
/usr/bin/htmldoc --book --firstpage p1 -v -t <type> \
-f <output> nochunks.html
 
replace <type> by pdf13 to create a pdf file or replace <type> by ps3 to
create a ps file. There are other pdf and ps levels, see the man page for
possible other options. Replace <output> with the filename of the ps or
pdf file that is to be generated.
 
/tags/cvs/lfs/chapter07/hosts.xml
0,0 → 1,55
<sect1 id="ch07-hosts">
<title>Creating the /etc/hosts file</title>
<?dbhtml filename="hosts.html" dir="chapter07"?>
 
<para>If a network card is to be configured, you have to decide on the
IP-address, FQDN and possible aliases for use in the /etc/hosts file. The
syntax is:</para>
 
<para><screen>&lt;IP address&gt; myhost.mydomain.org aliases</screen></para>
 
<para>You should made sure that the IP-address is in the private network
IP-address range. Valid ranges are:</para>
 
<para><screen> Class Networks
A 10.0.0.0
B 172.16.0.0 through 172.31.0.0
C 192.168.0.0 through 192.168.255.0</screen></para>
 
<para>A valid IP address could be 192.168.1.1. A valid FQDN for this IP could
be www.linuxfromscratch.org</para>
 
<para>If you aren't going to use a network card, you still need to
come up with a FQDN. This is necessary for certain programs to operate
correctly.</para>
 
<para>If a network card is not going to be configured, create the
<filename>/etc/hosts</filename> file by running:</para>
 
<para><screen><userinput>cat &gt; /etc/hosts &lt;&lt; "EOF"</userinput>
# Begin /etc/hosts (no network card version)
 
127.0.0.1 www.mydomain.com &lt;value of HOSTNAME&gt; localhost
 
# End /etc/hosts (no network card version)
<userinput>EOF</userinput></screen></para>
 
<para>If a network card is to be configured, create the
<filename>/etc/hosts</filename> file by running:</para>
 
<para><screen><userinput>cat &gt; /etc/hosts &lt;&lt; "EOF"</userinput>
# Begin /etc/hosts (network card version)
 
127.0.0.1 localhost.localdomain localhost
192.168.1.1 www.mydomain.org &lt;value of HOSTNAME&gt;
 
# End /etc/hosts (network card version)
<userinput>EOF</userinput></screen></para>
 
<para>Of course, the 192.168.1.1 and www.mydomain.org have to be changed
to your liking (or requirements if assigned an IP-address by a network/system
administrator and this machine is planned to be connected to am existing
network).</para>
 
</sect1>
 
/tags/cvs/lfs/chapter07/introduction.xml
0,0 → 1,18
<sect1 id="ch07-introduction">
<title>Introduction</title>
<?dbhtml filename="introduction.html" dir="chapter07"?>
 
<para>This chapter will setup the bootscripts that you installed in chapter
6. Most of these scripts will work without needing to modify them, but a
few do require additional configuration files setup as they deal with
hardware dependant information.</para>
 
<para>We will be using SysV style init scripts. We have chosen this style
because it is widely used and we feel comfortable with it. If you want to
try something else, someone has written an LFS-Hint on BSD style init scripts
at <ulink
url="&hints-root;bsd-init.txt">&hints-root;bsd-init.txt</ulink>
.</para>
 
</sect1>
 
/tags/cvs/lfs/chapter07/usage.xml
0,0 → 1,88
<sect1 id="ch07-usage">
<title>How does the booting process with these scripts work?</title>
<?dbhtml filename="usage.html" dir="chapter07"?>
 
<para>Linux uses a special booting facility named SysVinit. It's based on a
concept of <emphasis>runlevels</emphasis>. It can be widely different
from one system to another, so it can't be assumed that because things
worked in &lt;insert distro name&gt; they should work like that in LFS
too. LFS has its own way of doing things, but it respects generally
accepted standards.</para>
 
<para>SysVinit (which we'll call <emphasis>init</emphasis> from now on) works
using a runlevels scheme. There are 7 (from 0 to 6) runlevels
(actually, there are more runlevels but they are for special cases and
generally not used. The init man page describes those details), and each
one of those corresponds to the things the computer is supposed to do when
it starts up. The default runlevel is 3. Here are the descriptions of the
different runlevels as they are often implemented:</para>
 
<literallayout>0: halt the computer
1: single-user mode
2: multi-user mode without networking
3: multi-user mode with networking
4: reserved for customization, otherwise does the same as 3
5: same as 4, it is usually used for GUI login (like X's xdm or KDE's kdm)
6: reboot the computer</literallayout>
 
<para>The command used to change runlevels is <userinput>init
&lt;runlevel&gt;</userinput> where &lt;runlevel&gt; is
the target runlevel. For example, to reboot the computer, a user would issue
the init 6 command. The reboot command is just an alias, as is the halt
command an alias to init 0.</para>
 
<para>There are a number of directories under /etc/rc.d that look like
like rc?.d where ? is the number of the runlevel and rcsysinit.d which
contain a number of symbolic links. Some begin with an K, the others
begin with an S, and all of them have three numbers following the initial
letter. The K means to stop (kill) a service, and the S means to start a
service. The numbers determine the order in which the scripts are run,
from 00 to 99; the lower the number the sooner it gets executed. When init
switches to another runlevel, the appropriate services get killed and
others get started.</para>
 
<para>The real scripts are in /etc/rc.d/init.d. They do all the work, and the
symlinks all point to them. Killing links and starting links point to
the same script in /etc/rc.d/init.d. That's because the scripts can be
called with different parameters like start, stop, restart, reload,
status. When a K link is encountered, the appropriate script is run with
the stop argument. When a S link is encountered, the appropriate script
is run with the start argument.</para>
 
<para>There is one exception. Links that start with an S in the
rc0.d and rc6.d directories will not cause anything to be started. They
will be called with the parameter <emphasis>stop</emphasis> to stop
something. The logic behind it is that when you are going to reboot or
halt the system, you don't want to start anything, only stop the
system.</para>
 
<para>These are descriptions of what the arguments make the
scripts do:</para>
 
<itemizedlist>
 
<listitem><para><emphasis>start</emphasis>: The service is
started.</para></listitem>
 
<listitem><para><emphasis>stop</emphasis>: The service is
stopped.</para></listitem>
 
<listitem><para><emphasis>restart</emphasis>: The service is
stopped and then started again.</para></listitem>
 
<listitem><para><emphasis>reload</emphasis>: The configuration
of the service is updated.
This is used after the configuration file of a service was modified, when
the service doesn't need to be restarted.</para></listitem>
 
<listitem><para><emphasis>status</emphasis>: Tells if the service
is running and with which PID's.</para></listitem>
 
</itemizedlist>
 
<para>Feel free to modify the way the boot process works (after all it's your
LFS system, not ours). The files here are just an example of how it can be
done in a nice way (well what we consider nice anyway. You may hate it).</para>
 
</sect1>
 
/tags/cvs/lfs/chapter07/setclock.xml
0,0 → 1,38
<sect1 id="ch07-setclock">
<title>Configuring the setclock script</title>
<?dbhtml filename="setclock.html" dir="chapter07"?>
 
 
<para>The setclock script is only for real use when the hardware clock (also
known as BIOS or CMOS clock) isn't set to GMT time. The recommended
setup is setting the hardware clock to GMT and having the time converted
to localtime using the /etc/localtime symbolic link. But if an
OS is run that doesn't understand a clock set to GMT (most notable are
Microsoft OS'es) you may want to set the clock to localtime so that
the time is properly displayed on those OS'es. This script will then
set the kernel time to the hardware clock without converting the time using
the /etc/localtime symlink.</para>
 
<para>If you want to use this script on your system even if the
hardware clock is set to GMT, then the UTC variable below has to be
changed to the value of <emphasis>1</emphasis>.</para>
 
<para>Create a new file <filename>/etc/sysconfig/clock</filename> by running
the following:</para>
 
<para><screen><userinput>cat &gt; /etc/sysconfig/clock &lt;&lt; "EOF"</userinput>
# Begin /etc/sysconfig/clock
 
UTC=0
 
# End /etc/sysconfig/clock
<userinput>EOF</userinput></screen></para>
 
<para>Now, you may want to take a look at a very good hint explaining how we
deal with time on LFS at <ulink
url="&hints-root;time.txt">&hints-root;time.txt</ulink>.
It explains issues such as timezones, UTC, and the TZ environment
variable.</para>
 
</sect1>
 
/tags/cvs/lfs/chapter07/network.xml
0,0 → 1,58
<sect1 id="ch07-network">
<title>Configuring the network script</title>
<?dbhtml filename="network.html" dir="chapter07"?>
 
<para>This section only applies if you're going to configure a network
card.</para>
 
<sect2>
<title>Configuring default gateway</title>
 
<para>If you're on a network you may need to setup the default gateway for
this machine. This is done by adding the proper values to the
/etc/sysconfig/network file by running the following:</para>
 
<para><screen><userinput>cat &gt;&gt; /etc/sysconfig/network &lt;&lt; "EOF"</userinput>
GATEWAY=192.168.1.2
GATEWAY_IF=eth0
<userinput>EOF</userinput></screen></para>
 
<para>The values for GATEWAY and GATEWAY_IF need to be changed to match
your network setup. GATEWAY contains the IP address of the default
gateway, and GATEWAY_IF contains the network interface through which the
default gateway can be reached.</para>
 
</sect2>
 
<sect2>
<title>Creating network interface configuration files</title>
 
<para>Which interfaces are brought up and down by the network script depends on
the files in the /etc/sysconfig/network-devices directory. This
directory should contain files in the form of ifconfig.xyz, where xyz is a
network interface name (such as eth0 or eth0:1)</para>
 
<para>If you decide to rename or move this /etc/sysconfig/network-devices
directory, make sure you update the /etc/sysconfig/rc file as well and
update the network_devices by providing it with the new path.</para>
 
<para>Now, new files are created in that directory containing the following.
The following command creates a sample ifconfig.eth0 file:</para>
 
<para><screen><userinput>cat &gt; /etc/sysconfig/network-devices/ifconfig.eth0 &lt;&lt; "EOF"</userinput>
ONBOOT=yes
IP=192.168.1.1
NETMASK=255.255.255.0
BROADCAST=192.168.1.255
<userinput>EOF</userinput></screen></para>
 
<para>Of course, the values of those variables have to be changed
in every file to match the proper setup. If the ONBOOT variable is set
to yes, the network script will bring it up during boot up of the system.
If set to anything else but yes it will be ignored by the network script
and thus not brought up.</para>
 
</sect2>
 
</sect1>
 
/tags/cvs/lfs/chapter07/loadkeys.xml
0,0 → 1,31
<sect1 id="ch07-loadkeys">
<title>Configuring the loadkeys script</title>
<?dbhtml filename="loadkeys.html" dir="chapter07"?>
 
<para>You only need to use the loadkeys script if you don't have a
default 101 keys US keyboard layout.</para>
 
<para>The /etc/sysconfig/keyboard file contains the information the
loadkeys script needs to operate. This file contains the LAYOUT variable
which tells loadkeys what keymap to load that corresponds with your
keyboard.</para>
 
<para>Create a new file <filename>/etc/sysconfig/keyboard</filename>
by running the following:</para>
<para><screen><userinput>cat &gt; /etc/sysconfig/keyboard &lt;&lt; "EOF"</userinput
>
# Begin /etc/sysconfig/keyboard
LAYOUT=&lt;path-to-keymap&gt;
# End /etc/sysconfig/keyboard
<userinput>EOF</userinput></screen></para>
 
<para>Replace <userinput>&lt;path-to-keymap&gt;</userinput> with the
path to the keymap you have selected. For example, if you have chosen the
US keymap, you would replace it with
<userinput>/usr/share/kbd/keymaps/i386/qwerty/us.map.gz</userinput></para>
 
</sect1>
 
/tags/cvs/lfs/chapter07/chapter7.xml
0,0 → 1,14
<chapter id="chapter07">
<title>Setting up system boot scripts</title>
<?dbhtml filename="chapter07.html" dir="chapter07"?>
 
&c7-introduction;
&c7-usage;
&c7-loadkeys;
&c7-setclock;
&c7-hostname;
&c7-hosts;
&c7-network;
 
</chapter>
 
/tags/cvs/lfs/chapter07/hostname.xml
0,0 → 1,19
<sect1 id="ch07-hostname">
<title>Configuring the localnet script</title>
<?dbhtml filename="hostname.html" dir="chapter07"?>
 
<para>Part of the localnet script is setting up the system's hostname. This
needs to be configured in the /etc/sysconfig/network.</para>
 
<para>Create the /etc/sysconfig/network file and enter a hostname by
running:</para>
 
<para><screen><userinput>echo "HOSTNAME=lfs" &gt; /etc/sysconfig/network</userinput></screen></para>
 
<para><quote>lfs</quote> needs to be replaced with the name the computer is
to be called. You should not enter the FQDN (Fully Qualified Domain
Name) here. That information will be put in the
<filename>/etc/hosts</filename> file later on.</para>
 
</sect1>
 
/tags/cvs/lfs/chapter08/kernel.xml
0,0 → 1,39
<sect1 id="ch08-kernel">
<title>Installation de linux-&kernel-version;</title>
<?dbhtml filename="kernel.html" dir="chapter08"?>
 
<screen>Temps de construction estimé: &kernel-time;
Espace disque nécessaire estimé: &kernel-compsize;</screen>
 
<para>Construire un noyau implique quelques étapes: le configurer et
le compiler. Il y a plusieurs façons de configurer un noyau. Si la manière
décrite dans ce livre ne vous convient pas, lisez le fichier <filename>README</filename>
qui est inclus dans l'arborescence des sources du noyau, et cherchez à quoi
servent les autres options.</para>
 
<para>Une chose que vous pourriez faire, est de prendre le fichier .config
des sources du noyau de votre distribution hôte et le copier dans $LFS/usr/src/linux.
De cette façon vous n'avez pas à configurer la totalité du noyau depuis le début et
pouvez utiliser vos valeurs actuelles. Si vous choisissez de le faire, commencez par
lancer la commande make mrproper, ensuite copiez le fichier .config par dessus, ensuite
lancez make menuconfig (make oldconfig peut être préférable dans certaines situations.
Voir le fichier <filename>README</filename> pour plus de détails sur l'utilisation du
make oldconfig).</para>
 
<para>Les commandes suivantes sont utilisées pour construire le noyau:</para>
 
<para><screen><userinput>cd /usr/src/linux &amp;&amp;</userinput>
<userinput>make mrproper &amp;&amp;</userinput>
<userinput>make menuconfig &amp;&amp;</userinput>
<userinput>make dep &amp;&amp;</userinput>
<userinput>make bzImage &amp;&amp;</userinput>
<userinput>make modules &amp;&amp;</userinput>
<userinput>make modules_install &amp;&amp;</userinput>
<userinput>cp arch/i386/boot/bzImage /boot/lfskernel &amp;&amp;</userinput>
<userinput>cp System.map /boot</userinput></screen></para>
 
<para>Note: le chemin arch/i386/boot/bzImage peut varier suivant la plateforme.</para>
 
&aa-kernel-dep;
 
</sect1>
/tags/cvs/lfs/chapter08/introduction.xml
0,0 → 1,10
<sect1 id="ch08-introduction">
<title>Introduction</title>
<?dbhtml filename="introduction.html" dir="chapter08"?>
 
<para>Ce chapitre permettra de rendre LFS démarrable. Ce chapitre traite de la
création d'un nouveau fichier fstab, de la construction d'un nouveau noyau pour le
nouveau système LFS et de l'ajout d'entrées propres à LILO afin que le système LFS puisse
être sélectionné lors du démarrage de LILO.</para>
 
</sect1>
/tags/cvs/lfs/chapter08/chapter8.xml
0,0 → 1,10
<chapter id="chapter08">
<title>Rendre le système LFS démarrable</title>
<?dbhtml filename="chapter08.html" dir="chapter08"?>
 
&c8-introduction;
&c8-fstab;
&c8-kernel;
&c8-lilo;
 
</chapter>
/tags/cvs/lfs/chapter08/fstab.xml
0,0 → 1,44
<sect1 id="ch08-fstab">
<title>Création du fichier /etc/fstab</title>
<?dbhtml filename="fstab.html" dir="chapter08"?>
 
<para>On utilise le fichier /etc/fstab afin que certains programmes puissent
déterminer où certaines partitions sont supposées être montées par défaut.
Créez un nouveau fichier <filename>/etc/fstab</filename> en lançant cette
commande:</para>
 
<para><screen><userinput>cat &gt; /etc/fstab &lt;&lt; "EOF"</userinput>
# Début de /etc/fstab
 
# emplacement du système de fichier point de montage type de système options
 
/dev/*périphérique partition-LFS* / *fs-type* defaults 1 1
/dev/*périphérique partition-swap* swap swap pri=1 0 0
proc /proc proc defaults 0 0
 
# Fin de /etc/fstab
<userinput>EOF</userinput></screen></para>
 
<para><userinput>*périphérique partition-LFS*</userinput>,
<userinput>*périphérique partition-swap*</userinput>
et <userinput>*fs-type*</userinput> doit être remplacé par les
valeurs adéquates (/dev/hda2, /dev/hda5 et reiserfs par exemple).</para>
 
<para>Lorsqu'on ajoute une partition reiserfs, le <userinput>1 1</userinput> à
la fin de la ligne doit être remplacé par <userinput>0 0</userinput>.</para>
 
<para>Pour plus d'informations sur les différents champs présents dans le fichier
fstab, voir <userinput>man 5 fstab</userinput>.</para>
 
<para>Il y a d'autres lignes que vous pourriez ajouter à votre fichier fstab.
L'exemple suivant est la ligne que vous devriez avoir si vous utilisez devpts:</para>
<para><screen>devpts /dev/pts devpts gid=4,mode=620 0 0</screen></para>
 
<para>Un autre exemple est la ligne à utiliser pour employer des périphériques USB:</para>
<para><screen>usbdevfs /proc/bus/usb usbdevfs defaults 0 0</screen></para>
 
<para>Ces deux options ne fonctionneront que si vous avez compilé le support adéquat dans votre
noyau.</para>
 
</sect1>
 
/tags/cvs/lfs/chapter08/lilo.xml
0,0 → 1,55
<sect1 id="ch08-lilo">
<title>Rendre son système LFS démarrable</title>
<?dbhtml filename="lilo.html" dir="chapter08"?>
 
<para>Afin de pouvoir démarrer son système LFS, nous avons besoin de
mettre à jour notre chargeur de démarrage. Nous avons supposé que votre
système hôte utilise LILO (car c'est le chargeur le plus commun pour
le moment).</para>
 
<para>Nous n'allons pas lancer le programme LILO à l'intérieur du chroot.
Lancer lilo à l'intérieur du chroot peut avoir comme conséquence de rendre
votre MBR inutile et vous auriez besoin d'une disquette de démarrage pour
être capable de lancer tout système Linux (le système de base ainsi que le
système LFS).</para>
 
<para>Premièrement nous sortirons du chroot et copirons le fichier lfskernel
sur le système de base:</para>
 
<para><screen><userinput>logout</userinput>
<userinput>cp $LFS/boot/lfskernel /boot</userinput></screen></para>
 
<para>L'étape suivante est d'ajouter l'entrée dans /etc/lilo.conf ce qui
nous permettra de choisir LFS lorsque nous démarrerons l'ordinateur:</para>
 
<para><screen><userinput>cat &gt;&gt; /etc/lilo.conf &lt;&lt; "EOF"</userinput>
image=/boot/lfskernel
label=lfs
root=&lt;partition&gt;
read-only
<userinput>EOF</userinput></screen></para>
 
<para>&lt;partition&gt; doit être remplacé par l'emplacement de la partition.</para>
 
<para>Notez également que si vous utilisez reiserfs comme partition racine, la ligne
<userinput>read-only</userinput> devra être changée en <userinput>read-write</userinput>.
</para>
 
 
<para>Maintenant, mettez à jour le chargeur en lancant:</para>
 
<para><screen><userinput>/sbin/lilo -v</userinput></screen></para>
 
<para>La dernière étape est la synchronisation des fichiers de
configuration du système de base avec ceux du système LFS:</para>
 
<para><screen><userinput>cp /etc/lilo.conf $LFS/etc &amp;&amp;</userinput>
<userinput>cp &lt;kernel images&gt; $LFS/boot</userinput></screen></para>
 
<para>Pour savoir laquelle des images du noyau est utilisée, regardez dans
le fichier /etc/lilo.conf les lignes commencant par <emphasis>image=</emphasis>.
Si les fichiers noyaux du système de base se trouvent ailleurs que dans le répertoire
/boot, soyez certain de mettre à jour les chemins dans le fichier $LFS/etc/lilo.conf
afin qu'il puisse les trouver dans le répertoire /boot.</para>
 
</sect1>
/tags/cvs/lfs/chapter09/getcounted.xml
0,0 → 1,14
<sect1 id="ch09-getcounted">
<title>Enregistrez-vous</title>
<?dbhtml filename="getcounted.html" dir="chapter09"?>
 
<para>Vous voulez être enregistré comme utilisateur de LFS maintenant
que vous avez terminé le livre ? Allez directement à
<ulink url="http://linuxfromscratch.org/cgi-bin/lfscounter.cgi">
http://linuxfromscratch.org/cgi-bin/lfscounter.cgi</ulink> et
enregistrez-vous comme utilisateur LFS en entrant votre nom et la première version de LFS que vous ayez utilisée.</para>
 
<para>Replongeons nous maintenant dans LFS...</para>
 
</sect1>
 
/tags/cvs/lfs/chapter09/theend.xml
0,0 → 1,44
<sect1 id="ch09-theend">
<title>La fin</title>
<?dbhtml filename="theend.html" dir="chapter09"?>
 
<para>Bien joué! Vous avez terminé d'installer votre système LFS. Cela vous a peut-être
pris du temps, mais c'est un bonne chose que de l'avoir fait. Nous vous souhaitons de
bien vous amuser avec votre nouveau système Linux rutilant.</para>
 
<para>Maintenant c'est le bon moment pour nettoyer les binaires de tous les symboles de
débogage sur votre système LFS. Si vous n'êtes pas une programmeur et ne prévoyez pas de
déboguer vos logiciels, alors vous serez certainement content de savoir que l'on peut gagner
quelques dizaines de megas en enlevant les symboles de débogage. Ce processus n'a pas d'autre
inconvénient que de vous empêcher de deboguer votre logiciel à l'avenir, ce qui n'a
pas d'importance si vous ne saviez pas comment faire.</para>
 
<para>Précision: 98% des personnes qui utilisent la commande ci-dessous
n'ont jamais eu de problème. Mais faites une sauvegarde de votre système LFS avant
de lancer cette commande. Il y a une chance infime que cela se retourne contre vous
et rende votre système instable (essentiellement en détruisant les modules du noyau et les
librairies dynamiques partagées). Cela est plus souvent dû à des erreurs de frappes
qu'à des problèmes avec les commandes utilisées.</para>
 
<para>Cela étant dit, l'option --strip-debug que nous utilisons est plutôt sans dommage
dans des circonstances normales. Cela ne débarasse pas les fichiers de quoique ce soit de
vital. Il n'est sûr d'utiliser --strip-all que sur des programmes classiques
(ne pas utiliser sur des librairies - elles seraient détruites) mais pas aussi sûr et
l'espace gagné n'est pas plus grand. Mais si vous êtes limité en espace disque, quelques
octets de plus peuvent aider, alors décidez vous-même.
Référez vous, s'il vous plait, à la page de man pour d'autres options de strip que vous
pourriez utiliser. L'idée générale est de ne pas lancer strip sur des librairies (autre
que --strip-debug) pour rester su côté sûr.</para>
 
<para><screen><userinput>find $LFS/{,usr,usr/local}/{bin,sbin,lib} -type f \</userinput>
<userinput>&nbsp;&nbsp;&nbsp;-exec /usr/bin/strip --strip-debug '{}' ';'</userinput></screen></para>
 
<para>Cela peut être une bonne idée de créer le fichier $LFS/etc/lfs-&version;.
Avec ce fichier, il devient très facile pour vous (et pour nous si vous venez à nous demander
de l'aide sur quelque chose) de trouver quelle version de LFS vous avez
d'installée sur votre système. Cela peut être un fichier vide en lançant:</para>
 
<para><screen><userinput>touch $LFS/etc/lfs-&version;</userinput></screen></para>
 
</sect1>
 
/tags/cvs/lfs/chapter09/reboot.xml
0,0 → 1,51
<sect1 id="ch09-reboot">
<title>Redémarrer le système</title>
<?dbhtml filename="reboot.html" dir="chapter09"?>
 
<para>Maintenant que tous les logiciels ont été installés, les scripts de démarrage créés,
il est temps de redémarrer l'ordinateur. Avant de redémarrer, démontons
$LFS/proc et la partition LFS elle-même en exécutant:</para>
 
<para><screen><userinput>umount $LFS/proc &amp;&amp;</userinput>
<userinput>umount $LFS</userinput></screen></para>
 
<para>Et vous pouvez redémarrer votre système en lançant quelque chose comme:</para>
 
<para><screen><userinput>/sbin/shutdown -r now</userinput></screen></para>
 
<para>Au prompt LILO: assurez-vous que vous lui dites de démarrer
<emphasis>lfs</emphasis> et pas l'option par défaut qui redémarrera votre système
hôte.</para>
 
<para>Après avoir redémarré, votre système LFS est prêt à l'emploi et vous pouvez
commencer à ajouter vos propres logiciels.</para>
 
<para>Une dernière chose que vous voudriez peut-etre faire est de lancer lilo,
maintenant que vous avez démarré avec LFS.
Ainsi vous placerez la version LFS de LILO dans le MBR plutôt
que celle qu'il y a sur votre sysème hôte.
En fonction de l'âge de la distribution de votre hôte, la version LFS peut disposer
de fonctionnalités plus avancées que vous pourriez ou devriez utiliser.</para>
<para>Dans tous les cas, lancer ce qui suit pour activer la version LFS de lilo: </para>
<para><screen><userinput>/sbin/lilo</userinput></screen></para>
<para>Si vous vous demandez: "Bien, où aller maintenant?" vous serez heureux d'apprendre
que quelqu'un à écrit un topo LFS sur le sujet à <ulink
url="&hints-root;afterlfs.txt">&hints-root;afterlfs.txt</ulink>.
Sur la même note, si vous n'êtes pas seulement débutant avec LFS, mais
aussi débutant Linux en général, vous pouvez trouver un topo très intéressant pour
débutant à: <ulink
url="&hints-root;newbie.txt">&hints-root;newbie.txt</ulink>
</para>
<para>N'oubliez pas qu'il y a plusieurs listes de diffusions LFS auxquelles vous pouvez
vous inscrire en cas de besoin d'aide, conseils, etc. Pour plus d'informations, se référer
à <xref linkend="ch01-maillists"/> </para>
<para>Nous vous remercions encore d'avoir utilisé le livre LFS et espérons que
vous l'avez trouvé utile et qu'il vous a fait gagner du temps.</para>
 
</sect1>
 
/tags/cvs/lfs/chapter09/chapter9.xml
0,0 → 1,10
<chapter id="chapter09">
<title>La fin</title>
<?dbhtml filename="chapter09.html" dir="chapter09"?>
 
&c9-theend;
&c9-getcounted;
&c9-reboot;
 
</chapter>
 
/tags/cvs/lfs/dedication/dedication.xml
0,0 → 1,8
<dedication>
<title>Dédicace</title>
 
&dc-dedicated;
 
</dedication>
 
 
/tags/cvs/lfs/dedication/dedicated.xml
0,0 → 1,4
<para>Ce livre est dédié à ma femme aimante au soutien indéfectible
<emphasis>Beverly Beekmans</emphasis>.</para>
 
 
/tags/cvs/lfs/preface/organpart3.xml
0,0 → 1,5
<sect2 id="pre-organ3">
<title>Partie III - Annexes</title>
 
<para>La troisième partie contient différentes annexes.</para>
</sect2>
/tags/cvs/lfs/preface/organization.xml
0,0 → 1,16
<sect1 id="pre-organization">
<title>Organization</title>
<?dbhtml filename="organization.html" dir="preface"?>
 
<para>This book is divided into the following parts. Although most of
the appendices is copied into part II (which enlarges the book somewhat),
we believe it's the easiest way to read it like this. It simply saves
you from having to click to an Appendix, then back to where you were in
part II. That's a real chore especially if you're reading the TXT
version of this book.</para>
 
&pf-oz-organpart1;
&pf-oz-organpart2;
&pf-oz-organpart3;
 
</sect1>
/tags/cvs/lfs/preface/preface.xml
0,0 → 1,10
<preface id="preface">
<title>Préface</title>
<?dbhtml filename="preface.html" dir="preface"?>
 
&pf-foreword;
&pf-whoread;
&pf-whonotread;
&pf-organization;
 
</preface>
/tags/cvs/lfs/preface/foreword.xml
0,0 → 1,14
<sect1 id="pf-foreword">
<title>Avant-propos</title>
<?dbhtml filename="foreword.html" dir="preface"?>
<para>Ayant utilisé certaines distributions de Linux, je n'ai jamais été satisfait par aucune d'entre elles. Je n'aimais pas la façon dont les scripts
de boot étaient arrangés , je n'aimais pas la manière dont certains programmes étaient configurés par défaut, et d'autres choses de ce genre.
J'en suis venu au fait que si je voulais être entièrement satisfait d'un système linux, il me fallait créer mon propre système depuis le début,
idéalement en n'utilisant que le code-source. Sans utiliser de package pré-compilé. Sans aide d'aucun CD-ROM ni de disquette d'amorce qui installerait
quelques utilitaires de base. J'utiliserais mon système Linux actuel et m'en servirais pour construire le mien.</para>
<para>Ceci, au premier abord, peut sembler très difficile et parfois impossible. Après avoir réglé les problèmes de dépendance, problèmes de compilation,
etcetera, un système Linux personalisé a été créé avec succès. J'ai nommé ce système le système LFS, c'est à dire "Linux From Scratch" (Linux Par Le
Début).</para>
<para>J'espère que vous passerez du bon temps en travaillant sur LFS !</para>
<literallayout>-- Gerard Beekmans gerard@linuxfromscratch.org</literallayout>
</sect1>
/tags/cvs/lfs/preface/whoread.xml
0,0 → 1,59
<sect1 id="pre-whoread">
<title>Qui voudrait lire ce livre</title>
<?dbhtml filename="whoread.html" dir="preface"?>
 
<para>Il y a beaucoup de raisons qui pousseraient quelqu'un à vouloir lire
ce livre afin d'installer un système LFS. La question que beaucoup de
personnes se posent est "pourquoi se fatiguer à installer manuellement un
système Linux depuis le début alors qu'il suffit de télécharger une
distribution existante?". C'est une question censée
que j'espère pouvoir vous répondre.</para>
 
<para>La raison principale de l'existence de LFS est d'apprendre comment
fonctionne un système Linux à l'intérieur. Construire un système LFS vous
apprend tout ce qui fait que Linux fonctionne, comment les choses
travaillent ensemble, et dépendent les une des autres. Et le plus important,
comment le personnaliser afin qu'il soit à votre goût et réponde à vos besoins.
</para>
 
<para>Un autre avantage clé de LFS est que vous êtes maître de votre système sans
avoir à dépendre d'une implémentation créée par quelqu'un d'autre.
Vous êtes sur le siège conducteur maintenant et êtes capable de décider chaque
chose comme la disposition des répertoires ainsi que la configuration des fichiers
de démarrage. Vous saurez également exactement où, pourquoi et comment les programmes
sont installés.</para>
 
<para>Un autre avantage de LFS est que vous pouvez créer un système Linux compact.
Quand vous installez une distribution courante, vous finirez par
installer beaucoup de programmes que vous n'utiliserez jamais de votre vie. Ils
sont juste là et prennent un espace disque précieux. Il n'est pas difficile
d'avoir un système LFS installé pour moins de 100 MB. Celà vous semble-t-il beaucoup ?
Certains d'entre nous ont travaillés afin de créer un système LFS minuscule. Nous
avons installé un système juste suffisant pour faire fonctionner le serveur web Apache;
l'espace disque total était approximativement 8 MB. Avec plus de dépouillement, cela
peut être ramené à 5 MB ou moins. Essayez de faire pareil avec une distribution
courante.</para>
 
<para>Si nous devions comparer une distribution Linux avec un hamburger que vous
achetez au supermarché ou au restaurant fast-food, vous le mangeriez sans précisément
savoir ce que vous mangez, alors que LFS vous donne tous les ingrédients pour faire un
hamburger. Cela vous permet de prudemment l'inspecter, d'enlever les ingrédients
non désirés, et par la même manière vous permettre de rajouter des ingrédients qui
correspondent mieux à la saveur que vous attendez de votre hamburger. Quand vous êtes
satisfait des ingrédients, vous passez à la partie suivante en les combinant ensemble.
Vous avez désormais la chance de le faire de la façon dont vous le voulez : grillez-le,
faites-le cuire au four, faites-le frire, au barbecue, ou mangez-le cru.</para>
 
<para>Une autre analogie que nous pouvons utiliser est de comparer LFS avec une maison
construite. LFS vous donnera le squelette de la maison, mais c'est à vous de faire la
plomberie, le système électrique, la cuisine, la baignoire, le papier-peint, etc.</para>
 
<para>Un autre avantage d'un système Linux personalisé est l'ajout de sécurité. Vous
compilerez le système complet à partir de la base, ce qui vous permet de tout vérifier,
si vous le voulez, et d'appliquer tous les patchs de sécurité que vous voulez ou devez
appliquer. Vous n'avez pas à attendre quelqu'un d'autre pour vous fournir un package
fixant un trou de sécurité. Cependant, vous n'avez aucune garantie que le nouveau
package résoud le problème (adéquatement). Vous ne pourrez jamais savoir si un trou de
sécurité est fixé si vous ne le faites pas vous-même.</para>
</sect1>
/tags/cvs/lfs/preface/whonotread.xml
0,0 → 1,29
<sect1 id="pre-whonotread">
<title>Qui ne voudrait pas lire ce livre</title>
<?dbhtml filename="whonotread.html" dir="preface"?>
 
<para>
Les personnes ne voulant pas construire un système linux en entier depuis le début ne
voudront probablement pas lire ce livre. Si cependant vous voulez en apprendre plus au
sujet de ce qui se produit dans les coulisses, en particulier ce qui se passe entre le
moment où vous allumez un ordinateur et le moment où la ligne de commande apparait,
vous pouvez vouloir lire le <quote>From-PowerUp-To-Bash-Prompt-HOWTO</quote>.
Ce HOWTO construit un système de base, d'une manière similaire à ce que ce
livre-ci utilise, mais il se concentre plus sur l'installation d'un système de démarrage
au lieu d'un système complet.
</para>
<para>Afin de décider de lire ce livre ou le From-PowerUp-To-Bash-Prompt-HOWTO,
posez-vous cette question : "Mon objectif principal est-il d'avoir un système Linux
opérationnel que je vais construire moi-même, et ainsi apprendre ce que chaque composant
d'un système fait ? Ou alors mon objectif principal juste est d'apprendre ?".
Si vous voulez construire et apprendre, lisez ce livre. Si vous voulez
simplement apprendre les bases, alors le From-PowerUp-To-Bash-Prompt-HOWTO
est probablement un meilleur choix.
</para>
 
<para>Le <quote>From-PowerUp-To-Bash-Prompt-HOWTO</quote> est disponible sur
<ulink url="http://www.netspace.net.au/~gok/power2bash/">http://www.netspace.net.au/~gok/power2bash/</ulink>
</para>
 
</sect1>
/tags/cvs/lfs/preface/organpart1.xml
0,0 → 1,8
<sect2 id="pre-organ1">
<title>Partie I - Introduction</title>
 
<para>La première partie donne les informations générales à propos de ce livre (les versions, où se le procurer,
changelog, listes de diffusions, et comment nous contacter).
Elle va également vous expliquer certains aspects importants qu'il vous faut lire avant de commencer à créer
son système LFS.</para>
</sect2>
/tags/cvs/lfs/preface/organpart2.xml
0,0 → 1,7
<sect2 id="pre-organ2">
<title>Partie II - Installation du système LFS</title>
 
<para>La seconde partie va vous guider à travers l'installation du sustème LFS lequel sera
le fondation du reste du système. Quelque soit votre choix d'utilisation de votre nouveau
système LFS, il devra être construit sur les fondations installées dans cette partie.</para>
</sect2>
/tags/cvs/lfs/lfs.dsl
0,0 → 1,68
<!DOCTYPE style-sheet PUBLIC "-//James Clark//DTD DSSSL Style Sheet//EN" [
<!ENTITY docbook.dsl SYSTEM "docbook.dsl" CDATA dsssl>
]>
 
<style-sheet>
 
<style-specification use="docbook">
<style-specification-body>
 
(define %generate-legalnotice-link%
;; put the legal notice in a separate file
#t)
 
(define ($legalnotice-link-file$ legalnotice)
;; filename of the legalnotice file
(string-append "legalnotice"%html-ext%))
 
(define %html-ext%
;; html extenstion
".html")
 
(define %root-filename%
;; index file of the book
"index")
 
(define %use-id-as-filename%
;; filenames same as id attribute in title tags
#t)
 
(define %body-attr%
;; html body settings
(list
(list "BGCOLOR" "#FFFFFF")
(list "TEXT" "#000000")
(list "LINK" "#0000FF")
(list "VLINK" "#840084")
(list "ALINK" "#006000")))
 
(define (chunk-skip-first-element-list)
;; forces the Table of Contents on separate page
'())
 
(define (list-element-list)
;; fixes bug in Table of Contents generation
'())
 
(define %shade-verbatim%
;; verbatim sections will be shaded if t(rue)
#t)
 
;;(define %section-autolabel%
;; For enumerated sections (1.1, 1.1.1, 1.2, etc.)
;;#t)
 
(element emphasis
;; make role=strong equate to bold for emphasis tag
(if (equal? (attribute-string "role") "strong")
(make element gi: "STRONG" (process-children))
(make element gi: "EM" (process-children))))
 
 
</style-specification-body>
</style-specification>
 
<external-specification id="docbook" document="docbook.dsl">
 
</style-sheet>
 
/tags/cvs/lfs/index.xml
0,0 → 1,1098
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
"/usr/share/docbook/docbookx.dtd" [
 
<!ENTITY book SYSTEM "book/book.xml">
 
<!ENTITY version "20020219">
<!ENTITY releasedate "February 19th, 2002">
 
<!ENTITY ftp-root "ftp://ftp.linuxfromscratch.org">
<!ENTITY http-root "http://ftp.linuxfromscratch.org">
<!ENTITY ftp "ftp://ftp.linuxfromscratch.org/lfs-packages/cvs">
<!ENTITY http "http://ftp.linuxfromscratch.org/lfs-packages/cvs">
<!ENTITY hints-root "http://hints.linuxfromscratch.org/hints/">
 
<!ENTITY part1 SYSTEM "book/part1.xml">
<!ENTITY part2 SYSTEM "book/part2.xml">
<!ENTITY part3 SYSTEM "book/part3.xml">
 
<!ENTITY bookinfo SYSTEM "bookinfo/bookinfo.xml">
<!ENTITY bi-authorgroup SYSTEM "bookinfo/authorgroup.xml">
<!ENTITY bi-copyright SYSTEM "bookinfo/copyright.xml">
<!ENTITY bi-legalnotice SYSTEM "bookinfo/legalnotice.xml">
<!ENTITY bi-abstract SYSTEM "bookinfo/abstract.xml">
 
<!ENTITY dedication SYSTEM "dedication/dedication.xml">
<!ENTITY dc-dedicated SYSTEM "dedication/dedicated.xml">
 
<!ENTITY preface SYSTEM "preface/preface.xml">
<!ENTITY pf-foreword SYSTEM "preface/foreword.xml">
<!ENTITY pf-whoread SYSTEM "preface/whoread.xml">
<!ENTITY pf-whonotread SYSTEM "preface/whonotread.xml">
<!ENTITY pf-organization SYSTEM "preface/organization.xml">
<!ENTITY pf-oz-organpart1 SYSTEM "preface/organpart1.xml">
<!ENTITY pf-oz-organpart2 SYSTEM "preface/organpart2.xml">
<!ENTITY pf-oz-organpart3 SYSTEM "preface/organpart3.xml">
 
<!ENTITY chapter01 SYSTEM "chapter01/chapter01.xml">
<!ENTITY c1-how SYSTEM "chapter01/how.xml">
<!ENTITY c1-conventions SYSTEM "chapter01/conventions.xml">
<!ENTITY c1-version SYSTEM "chapter01/versions.xml">
<!ENTITY c1-mirrors SYSTEM "chapter01/mirrors.xml">
<!ENTITY c1-acknowledgments SYSTEM "chapter01/acknowledgments.xml">
<!ENTITY c1-changelog SYSTEM "chapter01/changelog.xml">
<!ENTITY c1-maillists SYSTEM "chapter01/maillists.xml">
<!ENTITY c1-ma-lfsdev SYSTEM "chapter01/lfsdev.xml">
<!ENTITY c1-ma-lfsannounce SYSTEM "chapter01/lfsannounce.xml">
<!ENTITY c1-ma-lfssecurity SYSTEM "chapter01/lfssecurity.xml">
<!ENTITY c1-ma-lfssupport SYSTEM "chapter01/lfssupport.xml">
<!ENTITY c1-ma-lfsbook SYSTEM "chapter01/lfsbook.xml">
<!ENTITY c1-ma-alfsdiscuss SYSTEM "chapter01/alfsdiscuss.xml">
<!ENTITY c1-ma-blfsbook SYSTEM "chapter01/blfsbook.xml">
<!ENTITY c1-ma-blfssupport SYSTEM "chapter01/blfssupport.xml">
<!ENTITY c1-ma-blfsdev SYSTEM "chapter01/blfsdev.xml">
<!ENTITY c1-ma-howtopost SYSTEM "chapter01/howtopost.xml">
<!ENTITY c1-ma-subscribe SYSTEM "chapter01/subscribe.xml">
<!ENTITY c1-ma-unsubscribe SYSTEM "chapter01/unsubscribe.xml">
<!ENTITY c1-ma-mailarchive SYSTEM "chapter01/mailarchive.xml">
<!ENTITY c1-ma-othermodes SYSTEM "chapter01/othermodes.xml">
<!ENTITY c1-newsserver SYSTEM "chapter01/newsserver.xml">
<!ENTITY c1-contactinfo SYSTEM "chapter01/contactinfo.xml">
 
<!ENTITY chapter02 SYSTEM "chapter02/chapter02.xml">
<!ENTITY c2-aboutlfs SYSTEM "chapter02/aboutlfs.xml">
<!ENTITY c2-download SYSTEM "chapter02/download.xml">
<!ENTITY c2-install SYSTEM "chapter02/install.xml">
<!ENTITY c2-platform SYSTEM "chapter02/platform.xml">
<!ENTITY c2-askforhelp SYSTEM "chapter02/askforhelp.xml">
<!ENTITY c2-commands SYSTEM "chapter02/commands.xml">
 
<!ENTITY chapter03 SYSTEM "chapter03/chapter03.xml">
<!ENTITY c3-introduction SYSTEM "chapter03/introduction.xml">
<!ENTITY c3-packages SYSTEM "chapter03/packages.xml">
<!ENTITY c3-toplevel SYSTEM "chapter03/toplevel.xml">
<!ENTITY c3-all SYSTEM "chapter03/all.xml">
<!ENTITY c3-bash SYSTEM "chapter03/bash.xml">
<!ENTITY c3-binutils SYSTEM "chapter03/binutils.xml">
<!ENTITY c3-bzip2 SYSTEM "chapter03/bzip2.xml">
<!ENTITY c3-diffutils SYSTEM "chapter03/diffutils.xml">
<!ENTITY c3-fileutils SYSTEM "chapter03/fileutils.xml">
<!ENTITY c3-gcc SYSTEM "chapter03/gcc.xml">
<!ENTITY c3-gcc-patch SYSTEM "chapter03/gcc-patch.xml">
<!ENTITY c3-kernel SYSTEM "chapter03/kernel.xml">
<!ENTITY c3-grep SYSTEM "chapter03/grep.xml">
<!ENTITY c3-gzip SYSTEM "chapter03/gzip.xml">
<!ENTITY c3-gzip-patch SYSTEM "chapter03/gzip-patch.xml">
<!ENTITY c3-make SYSTEM "chapter03/make.xml">
<!ENTITY c3-sed SYSTEM "chapter03/sed.xml">
<!ENTITY c3-shellutils SYSTEM "chapter03/shellutils.xml">
<!ENTITY c3-shellutils-patch SYSTEM "chapter03/shellutils-patch.xml">
<!ENTITY c3-tar SYSTEM "chapter03/tar.xml">
<!ENTITY c3-tar-patch SYSTEM "chapter03/tar-patch.xml">
<!ENTITY c3-textutils SYSTEM "chapter03/textutils.xml">
<!ENTITY c3-mawk SYSTEM "chapter03/mawk.xml">
<!ENTITY c3-texinfo SYSTEM "chapter03/texinfo.xml">
<!ENTITY c3-gettext SYSTEM "chapter03/gettext.xml">
<!ENTITY c3-makedev SYSTEM "chapter03/makedev.xml">
<!ENTITY c3-glibc SYSTEM "chapter03/glibc.xml">
<!ENTITY c3-glibc-threads SYSTEM "chapter03/glibc-threads.xml">
<!ENTITY c3-manpages SYSTEM "chapter03/manpages.xml">
<!ENTITY c3-ed SYSTEM "chapter03/ed.xml">
<!ENTITY c3-patch SYSTEM "chapter03/patch.xml">
<!ENTITY c3-findutils SYSTEM "chapter03/findutils.xml">
<!ENTITY c3-findutils-patch SYSTEM "chapter03/findutils-patch.xml">
<!ENTITY c3-ncurses SYSTEM "chapter03/ncurses.xml">
<!ENTITY c3-vim SYSTEM "chapter03/vim.xml">
<!ENTITY c3-bison SYSTEM "chapter03/bison.xml">
<!ENTITY c3-less SYSTEM "chapter03/less.xml">
<!ENTITY c3-groff SYSTEM "chapter03/groff.xml">
<!ENTITY c3-man SYSTEM "chapter03/man.xml">
<!ENTITY c3-perl SYSTEM "chapter03/perl.xml">
<!ENTITY c3-m4 SYSTEM "chapter03/m4.xml">
<!ENTITY c3-autoconf SYSTEM "chapter03/autoconf.xml">
<!ENTITY c3-automake SYSTEM "chapter03/automake.xml">
<!ENTITY c3-flex SYSTEM "chapter03/flex.xml">
<!ENTITY c3-file SYSTEM "chapter03/file.xml">
<!ENTITY c3-libtool SYSTEM "chapter03/libtool.xml">
<!ENTITY c3-bin86 SYSTEM "chapter03/bin86.xml">
<!ENTITY c3-kbd SYSTEM "chapter03/kbd.xml">
<!ENTITY c3-kbd-patch SYSTEM "chapter03/kbd-patch.xml">
<!ENTITY c3-e2fsprogs SYSTEM "chapter03/e2fsprogs.xml">
<!ENTITY c3-reiserfs SYSTEM "chapter03/reiserfs.xml">
<!ENTITY c3-lilo SYSTEM "chapter03/lilo.xml">
<!ENTITY c3-modutils SYSTEM "chapter03/modutils.xml">
<!ENTITY c3-procinfo SYSTEM "chapter03/procinfo.xml">
<!ENTITY c3-procps SYSTEM "chapter03/procps.xml">
<!ENTITY c3-psmisc SYSTEM "chapter03/psmisc.xml">
<!ENTITY c3-shadowpwd SYSTEM "chapter03/shadowpwd.xml">
<!ENTITY c3-sysklogd SYSTEM "chapter03/sysklogd.xml">
<!ENTITY c3-sysvinit SYSTEM "chapter03/sysvinit.xml">
<!ENTITY c3-utillinux SYSTEM "chapter03/utillinux.xml">
<!ENTITY c3-netkitbase SYSTEM "chapter03/netkitbase.xml">
<!ENTITY c3-nettools SYSTEM "chapter03/nettools.xml">
<!ENTITY c3-bootscripts SYSTEM "chapter03/bootscripts.xml">
 
<!ENTITY chapter04 SYSTEM "chapter04/chapter04.xml">
<!ENTITY c4-introduction SYSTEM "chapter04/introduction.xml">
<!ENTITY c4-creatingpart SYSTEM "chapter04/creatingpart.xml">
<!ENTITY c4-creatingfs SYSTEM "chapter04/creatingfs.xml">
<!ENTITY c4-mounting SYSTEM "chapter04/mounting.xml">
 
<!ENTITY chapter05 SYSTEM "chapter05/chapter05.xml">
<!ENTITY c5-introduction SYSTEM "chapter05/introduction.xml">
<!ENTITY c5-whystatic SYSTEM "chapter05/whystatic.xml">
<!ENTITY c5-installasuser SYSTEM "chapter05/installasuser.xml">
<!ENTITY c5-creatingdirs SYSTEM "chapter05/creatingdirs.xml">
<!ENTITY c5-bash SYSTEM "chapter05/bash.xml">
<!ENTITY c5-bash-inst SYSTEM "chapter05/bash-inst.xml">
<!ENTITY c5-bash-exp SYSTEM "chapter05/bash-exp.xml">
<!ENTITY c5-binutils SYSTEM "chapter05/binutils.xml">
<!ENTITY c5-binutils-inst SYSTEM "chapter05/binutils-inst.xml">
<!ENTITY c5-binutils-exp SYSTEM "chapter05/binutils-exp.xml">
<!ENTITY c5-bzip2 SYSTEM "chapter05/bzip2.xml">
<!ENTITY c5-bzip2-inst SYSTEM "chapter05/bzip2-inst.xml">
<!ENTITY c5-bzip2-exp SYSTEM "chapter05/bzip2-exp.xml">
<!ENTITY c5-diffutils SYSTEM "chapter05/diffutils.xml">
<!ENTITY c5-diffutils-inst SYSTEM "chapter05/diffutils-inst.xml">
<!ENTITY c5-diffutils-exp SYSTEM "chapter05/diffutils-exp.xml">
<!ENTITY c5-fileutils SYSTEM "chapter05/fileutils.xml">
<!ENTITY c5-fileutils-inst SYSTEM "chapter05/fileutils-inst.xml">
<!ENTITY c5-fileutils-exp SYSTEM "chapter05/fileutils-exp.xml">
<!ENTITY c5-gcc SYSTEM "chapter05/gcc.xml">
<!ENTITY c5-gcc-inst SYSTEM "chapter05/gcc-inst.xml">
<!ENTITY c5-gcc-exp SYSTEM "chapter05/gcc-exp.xml">
<!ENTITY c5-grep SYSTEM "chapter05/grep.xml">
<!ENTITY c5-grep-inst SYSTEM "chapter05/grep-inst.xml">
<!ENTITY c5-gzip SYSTEM "chapter05/gzip.xml">
<!ENTITY c5-gzip-inst SYSTEM "chapter05/gzip-inst.xml">
<!ENTITY c5-gzip-exp SYSTEM "chapter05/gzip-exp.xml">
<!ENTITY c5-kernel SYSTEM "chapter05/kernel.xml">
<!ENTITY c5-kernel-inst SYSTEM "chapter05/kernel-inst.xml">
<!ENTITY c5-kernel-exp SYSTEM "chapter05/kernel-exp.xml">
<!ENTITY c5-kernel-exp-headers SYSTEM "chapter05/kernel-exp-headers.xml">
<!ENTITY c5-make SYSTEM "chapter05/make.xml">
<!ENTITY c5-make-inst SYSTEM "chapter05/make-inst.xml">
<!ENTITY c5-mawk SYSTEM "chapter05/mawk.xml">
<!ENTITY c5-mawk-exp SYSTEM "chapter05/mawk-exp.xml">
<!ENTITY c5-mawk-inst SYSTEM "chapter05/mawk-inst.xml">
<!ENTITY c5-patch SYSTEM "chapter05/patch.xml">
<!ENTITY c5-patch-inst SYSTEM "chapter05/patch-inst.xml">
<!ENTITY c5-patch-exp SYSTEM "chapter05/patch-exp.xml">
<!ENTITY c5-sed SYSTEM "chapter05/sed.xml">
<!ENTITY c5-sed-inst SYSTEM "chapter05/sed-inst.xml">
<!ENTITY c5-shellutils SYSTEM "chapter05/shellutils.xml">
<!ENTITY c5-shellutils-inst SYSTEM "chapter05/shellutils-inst.xml">
<!ENTITY c5-tar SYSTEM "chapter05/tar.xml">
<!ENTITY c5-tar-inst SYSTEM "chapter05/tar-inst.xml">
<!ENTITY c5-texinfo SYSTEM "chapter05/texinfo.xml">
<!ENTITY c5-texinfo-inst SYSTEM "chapter05/texinfo-inst.xml">
<!ENTITY c5-textutils SYSTEM "chapter05/textutils.xml">
<!ENTITY c5-textutils-inst SYSTEM "chapter05/textutils-inst.xml">
<!ENTITY c5-pwdgroup SYSTEM "chapter05/pwdgroup.xml">
<!ENTITY c5-oldnsslib SYSTEM "chapter05/oldnsslib.xml">
<!ENTITY c5-proc SYSTEM "chapter05/proc.xml">
 
<!ENTITY chapter06 SYSTEM "chapter06/chapter06.xml">
<!ENTITY c6-introduction SYSTEM "chapter06/introduction.xml">
<!ENTITY c6-aboutdebug SYSTEM "chapter06/aboutdebug.xml">
<!ENTITY c6-bashprofile SYSTEM "chapter06/bashprofile.xml">
<!ENTITY c6-chrootcmd SYSTEM "chapter06/chrootcmd.xml">
<!ENTITY c6-chroot SYSTEM "chapter06/chroot.xml">
<!ENTITY c6-changingowner SYSTEM "chapter06/changingowner.xml">
<!ENTITY c6-mtablink SYSTEM "chapter06/mtablink.xml">
<!ENTITY c6-glibc SYSTEM "chapter06/glibc.xml">
<!ENTITY c6-glibc-inst SYSTEM "chapter06/glibc-inst.xml">
<!ENTITY c6-glibc-exp SYSTEM "chapter06/glibc-exp.xml">
<!ENTITY c6-makedev SYSTEM "chapter06/makedev.xml">
<!ENTITY c6-makedev-inst SYSTEM "chapter06/makedev-inst.xml">
<!ENTITY c6-makedev-exp SYSTEM "chapter06/makedev-exp.xml">
<!ENTITY c6-ed SYSTEM "chapter06/ed.xml">
<!ENTITY c6-ed-inst SYSTEM "chapter06/ed-inst.xml">
<!ENTITY c6-ed-exp SYSTEM "chapter06/ed-exp.xml">
<!ENTITY c6-patch SYSTEM "chapter06/patch.xml">
<!ENTITY c6-patch-inst SYSTEM "chapter06/patch-inst.xml">
<!ENTITY c6-gcc SYSTEM "chapter06/gcc.xml">
<!ENTITY c6-gcc-inst SYSTEM "chapter06/gcc-inst.xml">
<!ENTITY c6-bison SYSTEM "chapter06/bison.xml">
<!ENTITY c6-bison-inst SYSTEM "chapter06/bison-inst.xml">
<!ENTITY c6-mawk SYSTEM "chapter06/mawk.xml">
<!ENTITY c6-mawk-inst SYSTEM "chapter06/mawk-inst.xml">
<!ENTITY c6-findutils SYSTEM "chapter06/findutils.xml">
<!ENTITY c6-findutils-exp SYSTEM "chapter06/findutils-exp.xml">
<!ENTITY c6-findutils-inst SYSTEM "chapter06/findutils-inst.xml">
<!ENTITY c6-ncurses SYSTEM "chapter06/ncurses.xml">
<!ENTITY c6-ncurses-inst SYSTEM "chapter06/ncurses-inst.xml">
<!ENTITY c6-ncurses-exp SYSTEM "chapter06/ncurses-exp.xml">
<!ENTITY c6-less SYSTEM "chapter06/less.xml">
<!ENTITY c6-less-inst SYSTEM "chapter06/less-inst.xml">
<!ENTITY c6-perl SYSTEM "chapter06/perl.xml">
<!ENTITY c6-perl-inst SYSTEM "chapter06/perl-inst.xml">
<!ENTITY c6-m4 SYSTEM "chapter06/m4.xml">
<!ENTITY c6-m4-inst SYSTEM "chapter06/m4-inst.xml">
<!ENTITY c6-texinfo SYSTEM "chapter06/texinfo.xml">
<!ENTITY c6-texinfo-inst SYSTEM "chapter06/texinfo-inst.xml">
<!ENTITY c6-texinfo-exp SYSTEM "chapter06/texinfo-exp.xml">
<!ENTITY c6-autoconf SYSTEM "chapter06/autoconf.xml">
<!ENTITY c6-autoconf-inst SYSTEM "chapter06/autoconf-inst.xml">
<!ENTITY c6-automake SYSTEM "chapter06/automake.xml">
<!ENTITY c6-automake-inst SYSTEM "chapter06/automake-inst.xml">
<!ENTITY c6-bash SYSTEM "chapter06/bash.xml">
<!ENTITY c6-bash-inst SYSTEM "chapter06/bash-inst.xml">
<!ENTITY c6-flex SYSTEM "chapter06/flex.xml">
<!ENTITY c6-flex-inst SYSTEM "chapter06/flex-inst.xml">
<!ENTITY c6-binutils SYSTEM "chapter06/binutils.xml">
<!ENTITY c6-binutils-inst SYSTEM "chapter06/binutils-inst.xml">
<!ENTITY c6-binutils-exp SYSTEM "chapter06/binutils-exp.xml">
<!ENTITY c6-bzip2 SYSTEM "chapter06/bzip2.xml">
<!ENTITY c6-bzip2-inst SYSTEM "chapter06/bzip2-inst.xml">
<!ENTITY c6-bzip2-exp SYSTEM "chapter06/bzip2-exp.xml">
<!ENTITY c6-diffutils SYSTEM "chapter06/diffutils.xml">
<!ENTITY c6-diffutils-inst SYSTEM "chapter06/diffutils-inst.xml">
<!ENTITY c6-e2fsprogs SYSTEM "chapter06/e2fsprogs.xml">
<!ENTITY c6-e2fsprogs-inst SYSTEM "chapter06/e2fsprogs-inst.xml">
<!ENTITY c6-e2fsprogs-exp SYSTEM "chapter06/e2fsprogs-exp.xml">
<!ENTITY c6-reiserfs SYSTEM "chapter06/reiserfs.xml">
<!ENTITY c6-reiserfs-inst SYSTEM "chapter06/reiserfs-inst.xml">
<!ENTITY c6-reiserfs-exp SYSTEM "chapter06/reiserfs-exp.xml">
<!ENTITY c6-file SYSTEM "chapter06/file.xml">
<!ENTITY c6-file-inst SYSTEM "chapter06/file-inst.xml">
<!ENTITY c6-file-exp SYSTEM "chapter06/file-exp.xml">
<!ENTITY c6-fileutils SYSTEM "chapter06/fileutils.xml">
<!ENTITY c6-fileutils-inst SYSTEM "chapter06/fileutils-inst.xml">
<!ENTITY c6-gettext SYSTEM "chapter06/gettext.xml">
<!ENTITY c6-gettext-inst SYSTEM "chapter06/gettext-inst.xml">
<!ENTITY c6-grep SYSTEM "chapter06/grep.xml">
<!ENTITY c6-grep-inst SYSTEM "chapter06/grep-inst.xml">
<!ENTITY c6-groff SYSTEM "chapter06/groff.xml">
<!ENTITY c6-groff-inst SYSTEM "chapter06/groff-inst.xml">
<!ENTITY c6-gzip SYSTEM "chapter06/gzip.xml">
<!ENTITY c6-gzip-inst SYSTEM "chapter06/gzip-inst.xml">
<!ENTITY c6-libtool SYSTEM "chapter06/libtool.xml">
<!ENTITY c6-libtool-inst SYSTEM "chapter06/libtool-inst.xml">
<!ENTITY c6-bin86 SYSTEM "chapter06/bin86.xml">
<!ENTITY c6-bin86-inst SYSTEM "chapter06/bin86-inst.xml">
<!ENTITY c6-lilo SYSTEM "chapter06/lilo.xml">
<!ENTITY c6-lilo-inst SYSTEM "chapter06/lilo-inst.xml">
<!ENTITY c6-make SYSTEM "chapter06/make.xml">
<!ENTITY c6-make-inst SYSTEM "chapter06/make-inst.xml">
<!ENTITY c6-shellutils SYSTEM "chapter06/shellutils.xml">
<!ENTITY c6-shellutils-inst SYSTEM "chapter06/shellutils-inst.xml">
<!ENTITY c6-shadowpwd SYSTEM "chapter06/shadowpwd.xml">
<!ENTITY c6-shadowpwd-inst SYSTEM "chapter06/shadowpwd-inst.xml">
<!ENTITY c6-shadowpwd-exp SYSTEM "chapter06/shadowpwd-exp.xml">
<!ENTITY c6-man SYSTEM "chapter06/man.xml">
<!ENTITY c6-man-inst SYSTEM "chapter06/man-inst.xml">
<!ENTITY c6-modutils SYSTEM "chapter06/modutils.xml">
<!ENTITY c6-modutils-inst SYSTEM "chapter06/modutils-inst.xml">
<!ENTITY c6-procinfo SYSTEM "chapter06/procinfo.xml">
<!ENTITY c6-procinfo-exp SYSTEM "chapter06/procinfo-exp.xml">
<!ENTITY c6-procinfo-inst SYSTEM "chapter06/procinfo-inst.xml">
<!ENTITY c6-procps SYSTEM "chapter06/procps.xml">
<!ENTITY c6-procps-inst SYSTEM "chapter06/procps-inst.xml">
<!ENTITY c6-procps-exp SYSTEM "chapter06/procps-exp.xml">
<!ENTITY c6-psmisc SYSTEM "chapter06/psmisc.xml">
<!ENTITY c6-psmisc-inst SYSTEM "chapter06/psmisc-inst.xml">
<!ENTITY c6-psmisc-exp SYSTEM "chapter06/psmisc-exp.xml">
<!ENTITY c6-sed SYSTEM "chapter06/sed.xml">
<!ENTITY c6-sed-inst SYSTEM "chapter06/sed-inst.xml">
<!ENTITY c6-sysklogd SYSTEM "chapter06/sysklogd.xml">
<!ENTITY c6-sysklogd-inst SYSTEM "chapter06/sysklogd-inst.xml">
<!ENTITY c6-sysvinit SYSTEM "chapter06/sysvinit.xml">
<!ENTITY c6-sysvinit-inst SYSTEM "chapter06/sysvinit-inst.xml">
<!ENTITY c6-tar SYSTEM "chapter06/tar.xml">
<!ENTITY c6-tar-inst SYSTEM "chapter06/tar-inst.xml">
<!ENTITY c6-textutils SYSTEM "chapter06/textutils.xml">
<!ENTITY c6-textutils-inst SYSTEM "chapter06/textutils-inst.xml">
<!ENTITY c6-vim SYSTEM "chapter06/vim.xml">
<!ENTITY c6-vim-inst SYSTEM "chapter06/vim-inst.xml">
<!ENTITY c6-vim-exp SYSTEM "chapter06/vim-exp.xml">
<!ENTITY c6-utillinux SYSTEM "chapter06/utillinux.xml">
<!ENTITY c6-utillinux-inst SYSTEM "chapter06/utillinux-inst.xml">
<!ENTITY c6-utillinux-exp SYSTEM "chapter06/utillinux-exp.xml">
<!ENTITY c6-kbd SYSTEM "chapter06/kbd.xml">
<!ENTITY c6-kbd-inst SYSTEM "chapter06/kbd-inst.xml">
<!ENTITY c6-kbd-exp SYSTEM "chapter06/kbd-exp.xml">
<!ENTITY c6-manpages SYSTEM "chapter06/manpages.xml">
<!ENTITY c6-manpages-inst SYSTEM "chapter06/manpages-inst.xml">
<!ENTITY c6-netkitbase SYSTEM "chapter06/netkitbase.xml">
<!ENTITY c6-netkitbase-inst SYSTEM "chapter06/netkitbase-inst.xml">
<!ENTITY c6-nettools SYSTEM "chapter06/nettools.xml">
<!ENTITY c6-nettools-inst SYSTEM "chapter06/nettools-inst.xml">
<!ENTITY c6-nettools-exp SYSTEM "chapter06/nettools-exp.xml">
<!ENTITY c6-bootscripts SYSTEM "chapter06/bootscripts.xml">
<!ENTITY c6-bootscripts-inst SYSTEM "chapter06/bootscripts-inst.xml">
<!ENTITY c6-removeoldnss SYSTEM "chapter06/removeoldnss.xml">
<!ENTITY c6-configure SYSTEM "chapter06/configure.xml">
<!ENTITY c6-cf-glibc SYSTEM "chapter06/config-glibc.xml">
<!ENTITY c6-cf-ldso SYSTEM "chapter06/config-ldso.xml">
<!ENTITY c6-cf-sysklogd SYSTEM "chapter06/config-sysklogd.xml">
<!ENTITY c6-cf-shadowpwd SYSTEM "chapter06/config-shadowpwd.xml">
<!ENTITY c6-cf-sysvinit SYSTEM "chapter06/config-sysvinit.xml">
<!ENTITY c6-cf-utmp SYSTEM "chapter06/create-utmp.xml">
<!ENTITY c6-cf-vim SYSTEM "chapter06/config-vim.xml">
<!ENTITY c6-cf-password SYSTEM "chapter06/create-password.xml">
 
<!ENTITY chapter07 SYSTEM "chapter07/chapter07.xml">
<!ENTITY c7-introduction SYSTEM "chapter07/introduction.xml">
<!ENTITY c7-usage SYSTEM "chapter07/usage.xml">
<!ENTITY c7-loadkeys SYSTEM "chapter07/loadkeys.xml">
<!ENTITY c7-setclock SYSTEM "chapter07/setclock.xml">
<!ENTITY c7-hostname SYSTEM "chapter07/hostname.xml">
<!ENTITY c7-hosts SYSTEM "chapter07/hosts.xml">
<!ENTITY c7-network SYSTEM "chapter07/network.xml">
 
<!ENTITY chapter08 SYSTEM "chapter08/chapter08.xml">
<!ENTITY c8-introduction SYSTEM "chapter08/introduction.xml">
<!ENTITY c8-fstab SYSTEM "chapter08/fstab.xml">
<!ENTITY c8-kernel SYSTEM "chapter08/kernel.xml">
<!ENTITY c8-lilo SYSTEM "chapter08/lilo.xml">
 
<!ENTITY chapter09 SYSTEM "chapter09/chapter09.xml">
<!ENTITY c9-theend SYSTEM "chapter09/theend.xml">
<!ENTITY c9-getcounted SYSTEM "chapter09/getcounted.xml">
<!ENTITY c9-reboot SYSTEM "chapter09/reboot.xml">
 
<!ENTITY appendixa SYSTEM "appendixa/appendixa.xml">
<!ENTITY aa-introduction SYSTEM "appendixa/introduction.xml">
<!ENTITY aa-autoconf SYSTEM "appendixa/autoconf.xml">
<!ENTITY aa-autoconf-desc SYSTEM "appendixa/autoconf-desc.xml">
<!ENTITY aa-autoconf-dep SYSTEM "appendixa/autoconf-dep.xml">
<!ENTITY aa-autoconf-down SYSTEM "appendixa/autoconf-down.xml">
<!ENTITY aa-automake SYSTEM "appendixa/automake.xml">
<!ENTITY aa-automake-desc SYSTEM "appendixa/automake-desc.xml">
<!ENTITY aa-automake-dep SYSTEM "appendixa/automake-dep.xml">
<!ENTITY aa-automake-down SYSTEM "appendixa/automake-down.xml">
<!ENTITY aa-bash SYSTEM "appendixa/bash.xml">
<!ENTITY aa-bash-desc SYSTEM "appendixa/bash-desc.xml">
<!ENTITY aa-bash-dep SYSTEM "appendixa/bash-dep.xml">
<!ENTITY aa-bash-down SYSTEM "appendixa/bash-down.xml">
<!ENTITY aa-bin86 SYSTEM "appendixa/bin86.xml">
<!ENTITY aa-bin86-desc SYSTEM "appendixa/bin86-desc.xml">
<!ENTITY aa-bin86-dep SYSTEM "appendixa/bin86-dep.xml">
<!ENTITY aa-bin86-down SYSTEM "appendixa/bin86-down.xml">
<!ENTITY aa-binutils SYSTEM "appendixa/binutils.xml">
<!ENTITY aa-binutils-desc SYSTEM "appendixa/binutils-desc.xml">
<!ENTITY aa-binutils-dep SYSTEM "appendixa/binutils-dep.xml">
<!ENTITY aa-binutils-down SYSTEM "appendixa/binutils-down.xml">
<!ENTITY aa-bison SYSTEM "appendixa/bison.xml">
<!ENTITY aa-bison-desc SYSTEM "appendixa/bison-desc.xml">
<!ENTITY aa-bison-dep SYSTEM "appendixa/bison-dep.xml">
<!ENTITY aa-bison-down SYSTEM "appendixa/bison-down.xml">
<!ENTITY aa-bzip2 SYSTEM "appendixa/bzip2.xml">
<!ENTITY aa-bzip2-desc SYSTEM "appendixa/bzip2-desc.xml">
<!ENTITY aa-bzip2-dep SYSTEM "appendixa/bzip2-dep.xml">
<!ENTITY aa-bzip2-down SYSTEM "appendixa/bzip2-down.xml">
<!ENTITY aa-chroot SYSTEM "appendixa/chroot.xml">
<!ENTITY aa-chroot-dep SYSTEM "appendixa/chroot-dep.xml">
<!ENTITY aa-diffutils SYSTEM "appendixa/diffutils.xml">
<!ENTITY aa-diffutils-desc SYSTEM "appendixa/diffutils-desc.xml">
<!ENTITY aa-diffutils-dep SYSTEM "appendixa/diffutils-dep.xml">
<!ENTITY aa-diffutils-down SYSTEM "appendixa/diffutils-down.xml">
<!ENTITY aa-e2fsprogs SYSTEM "appendixa/e2fsprogs.xml">
<!ENTITY aa-e2fsprogs-desc SYSTEM "appendixa/e2fsprogs-desc.xml">
<!ENTITY aa-e2fsprogs-dep SYSTEM "appendixa/e2fsprogs-dep.xml">
<!ENTITY aa-e2fsprogs-down SYSTEM "appendixa/e2fsprogs-down.xml">
<!ENTITY aa-ed SYSTEM "appendixa/ed.xml">
<!ENTITY aa-ed-desc SYSTEM "appendixa/ed-desc.xml">
<!ENTITY aa-ed-dep SYSTEM "appendixa/ed-dep.xml">
<!ENTITY aa-ed-down SYSTEM "appendixa/ed-down.xml">
<!ENTITY aa-file SYSTEM "appendixa/file.xml">
<!ENTITY aa-file-desc SYSTEM "appendixa/file-desc.xml">
<!ENTITY aa-file-dep SYSTEM "appendixa/file-dep.xml">
<!ENTITY aa-file-down SYSTEM "appendixa/file-down.xml">
<!ENTITY aa-fileutils SYSTEM "appendixa/fileutils.xml">
<!ENTITY aa-fileutils-desc SYSTEM "appendixa/fileutils-desc.xml">
<!ENTITY aa-fileutils-dep SYSTEM "appendixa/fileutils-dep.xml">
<!ENTITY aa-fileutils-down SYSTEM "appendixa/fileutils-down.xml">
<!ENTITY aa-findutils SYSTEM "appendixa/findutils.xml">
<!ENTITY aa-findutils-desc SYSTEM "appendixa/findutils-desc.xml">
<!ENTITY aa-findutils-dep SYSTEM "appendixa/findutils-dep.xml">
<!ENTITY aa-findutils-down SYSTEM "appendixa/findutils-down.xml">
<!ENTITY aa-flex SYSTEM "appendixa/flex.xml">
<!ENTITY aa-flex-desc SYSTEM "appendixa/flex-desc.xml">
<!ENTITY aa-flex-dep SYSTEM "appendixa/flex-dep.xml">
<!ENTITY aa-flex-down SYSTEM "appendixa/flex-down.xml">
<!ENTITY aa-gcc SYSTEM "appendixa/gcc.xml">
<!ENTITY aa-gcc-desc SYSTEM "appendixa/gcc-desc.xml">
<!ENTITY aa-gcc-dep SYSTEM "appendixa/gcc-dep.xml">
<!ENTITY aa-gcc-down SYSTEM "appendixa/gcc-down.xml">
<!ENTITY aa-gettext SYSTEM "appendixa/gettext.xml">
<!ENTITY aa-gettext-desc SYSTEM "appendixa/gettext-desc.xml">
<!ENTITY aa-gettext-dep SYSTEM "appendixa/gettext-dep.xml">
<!ENTITY aa-gettext-down SYSTEM "appendixa/gettext-down.xml">
<!ENTITY aa-glibc SYSTEM "appendixa/glibc.xml">
<!ENTITY aa-glibc-desc SYSTEM "appendixa/glibc-desc.xml">
<!ENTITY aa-glibc-dep SYSTEM "appendixa/glibc-dep.xml">
<!ENTITY aa-glibc-down SYSTEM "appendixa/glibc-down.xml">
<!ENTITY aa-grep SYSTEM "appendixa/grep.xml">
<!ENTITY aa-grep-desc SYSTEM "appendixa/grep-desc.xml">
<!ENTITY aa-grep-dep SYSTEM "appendixa/grep-dep.xml">
<!ENTITY aa-grep-down SYSTEM "appendixa/grep-down.xml">
<!ENTITY aa-groff SYSTEM "appendixa/groff.xml">
<!ENTITY aa-groff-desc SYSTEM "appendixa/groff-desc.xml">
<!ENTITY aa-groff-dep SYSTEM "appendixa/groff-dep.xml">
<!ENTITY aa-groff-down SYSTEM "appendixa/groff-down.xml">
<!ENTITY aa-gzip SYSTEM "appendixa/gzip.xml">
<!ENTITY aa-gzip-desc SYSTEM "appendixa/gzip-desc.xml">
<!ENTITY aa-gzip-dep SYSTEM "appendixa/gzip-dep.xml">
<!ENTITY aa-gzip-down SYSTEM "appendixa/gzip-down.xml">
<!ENTITY aa-kbd SYSTEM "appendixa/kbd.xml">
<!ENTITY aa-kbd-desc SYSTEM "appendixa/kbd-desc.xml">
<!ENTITY aa-kbd-dep SYSTEM "appendixa/kbd-dep.xml">
<!ENTITY aa-kbd-down SYSTEM "appendixa/kbd-down.xml">
<!ENTITY aa-kernel SYSTEM "appendixa/kernel.xml">
<!ENTITY aa-kernel-desc SYSTEM "appendixa/kernel-desc.xml">
<!ENTITY aa-kernel-dep SYSTEM "appendixa/kernel-dep.xml">
<!ENTITY aa-kernel-down SYSTEM "appendixa/kernel-down.xml">
<!ENTITY aa-less SYSTEM "appendixa/less.xml">
<!ENTITY aa-less-desc SYSTEM "appendixa/less-desc.xml">
<!ENTITY aa-less-dep SYSTEM "appendixa/less-dep.xml">
<!ENTITY aa-less-down SYSTEM "appendixa/less-down.xml">
<!ENTITY aa-libtool SYSTEM "appendixa/libtool.xml">
<!ENTITY aa-libtool-desc SYSTEM "appendixa/libtool-desc.xml">
<!ENTITY aa-libtool-dep SYSTEM "appendixa/libtool-dep.xml">
<!ENTITY aa-libtool-down SYSTEM "appendixa/libtool-down.xml">
<!ENTITY aa-lilo SYSTEM "appendixa/lilo.xml">
<!ENTITY aa-lilo-desc SYSTEM "appendixa/lilo-desc.xml">
<!ENTITY aa-lilo-dep SYSTEM "appendixa/lilo-dep.xml">
<!ENTITY aa-lilo-down SYSTEM "appendixa/lilo-down.xml">
<!ENTITY aa-m4 SYSTEM "appendixa/m4.xml">
<!ENTITY aa-m4-desc SYSTEM "appendixa/m4-desc.xml">
<!ENTITY aa-m4-dep SYSTEM "appendixa/m4-dep.xml">
<!ENTITY aa-m4-down SYSTEM "appendixa/m4-down.xml">
<!ENTITY aa-make SYSTEM "appendixa/make.xml">
<!ENTITY aa-make-desc SYSTEM "appendixa/make-desc.xml">
<!ENTITY aa-make-dep SYSTEM "appendixa/make-dep.xml">
<!ENTITY aa-make-down SYSTEM "appendixa/make-down.xml">
<!ENTITY aa-makedev SYSTEM "appendixa/makedev.xml">
<!ENTITY aa-makedev-desc SYSTEM "appendixa/makedev-desc.xml">
<!ENTITY aa-makedev-dep SYSTEM "appendixa/makedev-dep.xml">
<!ENTITY aa-makedev-down SYSTEM "appendixa/makedev-down.xml">
<!ENTITY aa-man SYSTEM "appendixa/man.xml">
<!ENTITY aa-man-desc SYSTEM "appendixa/man-desc.xml">
<!ENTITY aa-man-dep SYSTEM "appendixa/man-dep.xml">
<!ENTITY aa-man-down SYSTEM "appendixa/man-down.xml">
<!ENTITY aa-manpages SYSTEM "appendixa/manpages.xml">
<!ENTITY aa-manpages-desc SYSTEM "appendixa/manpages-desc.xml">
<!ENTITY aa-manpages-dep SYSTEM "appendixa/manpages-dep.xml">
<!ENTITY aa-manpages-down SYSTEM "appendixa/manpages-down.xml">
<!ENTITY aa-mawk SYSTEM "appendixa/mawk.xml">
<!ENTITY aa-mawk-desc SYSTEM "appendixa/mawk-desc.xml">
<!ENTITY aa-mawk-dep SYSTEM "appendixa/mawk-dep.xml">
<!ENTITY aa-mawk-down SYSTEM "appendixa/mawk-down.xml">
<!ENTITY aa-modutils SYSTEM "appendixa/modutils.xml">
<!ENTITY aa-modutils-desc SYSTEM "appendixa/modutils-desc.xml">
<!ENTITY aa-modutils-dep SYSTEM "appendixa/modutils-dep.xml">
<!ENTITY aa-modutils-down SYSTEM "appendixa/modutils-down.xml">
<!ENTITY aa-ncurses SYSTEM "appendixa/ncurses.xml">
<!ENTITY aa-ncurses-desc SYSTEM "appendixa/ncurses-desc.xml">
<!ENTITY aa-ncurses-dep SYSTEM "appendixa/ncurses-dep.xml">
<!ENTITY aa-ncurses-down SYSTEM "appendixa/ncurses-down.xml">
<!ENTITY aa-netkitbase SYSTEM "appendixa/netkitbase.xml">
<!ENTITY aa-netkitbase-desc SYSTEM "appendixa/netkitbase-desc.xml">
<!ENTITY aa-netkitbase-dep SYSTEM "appendixa/netkitbase-dep.xml">
<!ENTITY aa-netkitbase-down SYSTEM "appendixa/netkitbase-down.xml">
<!ENTITY aa-nettools SYSTEM "appendixa/nettools.xml">
<!ENTITY aa-nettools-desc SYSTEM "appendixa/nettools-desc.xml">
<!ENTITY aa-nettools-dep SYSTEM "appendixa/nettools-dep.xml">
<!ENTITY aa-nettools-down SYSTEM "appendixa/nettools-down.xml">
<!ENTITY aa-patch SYSTEM "appendixa/patch.xml">
<!ENTITY aa-patch-desc SYSTEM "appendixa/patch-desc.xml">
<!ENTITY aa-patch-dep SYSTEM "appendixa/patch-dep.xml">
<!ENTITY aa-patch-down SYSTEM "appendixa/patch-down.xml">
<!ENTITY aa-perl SYSTEM "appendixa/perl.xml">
<!ENTITY aa-perl-desc SYSTEM "appendixa/perl-desc.xml">
<!ENTITY aa-perl-dep SYSTEM "appendixa/perl-dep.xml">
<!ENTITY aa-perl-down SYSTEM "appendixa/perl-down.xml">
<!ENTITY aa-procinfo SYSTEM "appendixa/procinfo.xml">
<!ENTITY aa-procinfo-desc SYSTEM "appendixa/procinfo-desc.xml">
<!ENTITY aa-procinfo-dep SYSTEM "appendixa/procinfo-dep.xml">
<!ENTITY aa-procinfo-down SYSTEM "appendixa/procinfo-down.xml">
<!ENTITY aa-procps SYSTEM "appendixa/procps.xml">
<!ENTITY aa-procps-desc SYSTEM "appendixa/procps-desc.xml">
<!ENTITY aa-procps-dep SYSTEM "appendixa/procps-dep.xml">
<!ENTITY aa-procps-down SYSTEM "appendixa/procps-down.xml">
<!ENTITY aa-psmisc SYSTEM "appendixa/psmisc.xml">
<!ENTITY aa-psmisc-desc SYSTEM "appendixa/psmisc-desc.xml">
<!ENTITY aa-psmisc-dep SYSTEM "appendixa/psmisc-dep.xml">
<!ENTITY aa-psmisc-down SYSTEM "appendixa/psmisc-down.xml">
<!ENTITY aa-reiserfs SYSTEM "appendixa/reiserfs.xml">
<!ENTITY aa-reiserfs-desc SYSTEM "appendixa/reiserfs-desc.xml">
<!ENTITY aa-reiserfs-dep SYSTEM "appendixa/reiserfs-dep.xml">
<!ENTITY aa-reiserfs-down SYSTEM "appendixa/reiserfs-down.xml">
<!ENTITY aa-sed SYSTEM "appendixa/sed.xml">
<!ENTITY aa-sed-desc SYSTEM "appendixa/sed-desc.xml">
<!ENTITY aa-sed-dep SYSTEM "appendixa/sed-dep.xml">
<!ENTITY aa-sed-down SYSTEM "appendixa/sed-down.xml">
<!ENTITY aa-shadowpwd SYSTEM "appendixa/shadowpwd.xml">
<!ENTITY aa-shadowpwd-desc SYSTEM "appendixa/shadowpwd-desc.xml">
<!ENTITY aa-shadowpwd-dep SYSTEM "appendixa/shadowpwd-dep.xml">
<!ENTITY aa-shadowpwd-down SYSTEM "appendixa/shadowpwd-down.xml">
<!ENTITY aa-shellutils SYSTEM "appendixa/shellutils.xml">
<!ENTITY aa-shellutils-desc SYSTEM "appendixa/shellutils-desc.xml">
<!ENTITY aa-shellutils-dep SYSTEM "appendixa/shellutils-dep.xml">
<!ENTITY aa-shellutils-down SYSTEM "appendixa/shellutils-down.xml">
<!ENTITY aa-sysklogd SYSTEM "appendixa/sysklogd.xml">
<!ENTITY aa-sysklogd-desc SYSTEM "appendixa/sysklogd-desc.xml">
<!ENTITY aa-sysklogd-dep SYSTEM "appendixa/sysklogd-dep.xml">
<!ENTITY aa-sysklogd-down SYSTEM "appendixa/sysklogd-down.xml">
<!ENTITY aa-sysvinit SYSTEM "appendixa/sysvinit.xml">
<!ENTITY aa-sysvinit-desc SYSTEM "appendixa/sysvinit-desc.xml">
<!ENTITY aa-sysvinit-dep SYSTEM "appendixa/sysvinit-dep.xml">
<!ENTITY aa-sysvinit-down SYSTEM "appendixa/sysvinit-down.xml">
<!ENTITY aa-tar SYSTEM "appendixa/tar.xml">
<!ENTITY aa-tar-desc SYSTEM "appendixa/tar-desc.xml">
<!ENTITY aa-tar-dep SYSTEM "appendixa/tar-dep.xml">
<!ENTITY aa-tar-down SYSTEM "appendixa/tar-down.xml">
<!ENTITY aa-texinfo SYSTEM "appendixa/texinfo.xml">
<!ENTITY aa-texinfo-desc SYSTEM "appendixa/texinfo-desc.xml">
<!ENTITY aa-texinfo-dep SYSTEM "appendixa/texinfo-dep.xml">
<!ENTITY aa-texinfo-down SYSTEM "appendixa/texinfo-down.xml">
<!ENTITY aa-textutils SYSTEM "appendixa/textutils.xml">
<!ENTITY aa-textutils-desc SYSTEM "appendixa/textutils-desc.xml">
<!ENTITY aa-textutils-dep SYSTEM "appendixa/textutils-dep.xml">
<!ENTITY aa-textutils-down SYSTEM "appendixa/textutils-down.xml">
<!ENTITY aa-utillinux SYSTEM "appendixa/utillinux.xml">
<!ENTITY aa-utillinux-desc SYSTEM "appendixa/utillinux-desc.xml">
<!ENTITY aa-utillinux-dep SYSTEM "appendixa/utillinux-dep.xml">
<!ENTITY aa-utillinux-down SYSTEM "appendixa/utillinux-down.xml">
<!ENTITY aa-vim SYSTEM "appendixa/vim.xml">
<!ENTITY aa-vim-desc SYSTEM "appendixa/vim-desc.xml">
<!ENTITY aa-vim-dep SYSTEM "appendixa/vim-dep.xml">
<!ENTITY aa-vim-down SYSTEM "appendixa/vim-down.xml">
<!ENTITY aa-bootscripts SYSTEM "appendixa/bootscripts.xml">
<!ENTITY aa-bootscripts-desc SYSTEM "appendixa/bootscripts-desc.xml">
<!ENTITY aa-bootscripts-dep SYSTEM "appendixa/bootscripts-dep.xml">
<!ENTITY aa-bootscripts-down SYSTEM "appendixa/bootscripts-down.xml">
 
<!ENTITY appendixb SYSTEM "appendixb/appendixb.xml">
<!ENTITY ab-introduction SYSTEM "appendixb/introduction.xml">
<!ENTITY ab-books SYSTEM "appendixb/books.xml">
<!ENTITY ab-howtoguides SYSTEM "appendixb/howtoguides.xml">
<!ENTITY ab-other SYSTEM "appendixb/other.xml">
 
<!ENTITY all-version "cvs-20020202-1236">
<!ENTITY all-size-kb "81,170 KB">
<!ENTITY all-size-mb "79.27 MB">
 
<!ENTITY bash-version "2.05a">
<!ENTITY bash-depversion "2.05a">
<!ENTITY bash-contversion "2.05a">
<!ENTITY bash-size "1,400 KB">
<!ENTITY bash-compsize-static "20 MB">
<!ENTITY bash-time-static "3 minutes">
<!ENTITY bash-compsize "19 MB">
<!ENTITY bash-time "3 minutes">
<!ENTITY bash-package "bash-&bash-version;.tar.bz2">
<!ENTITY bash-dir "bash-&bash-version;">
 
<!ENTITY binutils-version "2.11.2">
<!ENTITY binutils-depversion "2.11.2">
<!ENTITY binutils-contversion "2.11.2">
<!ENTITY binutils-size "7,641 KB">
<!ENTITY binutils-compsize-static "96 MB">
<!ENTITY binutils-time-static "6 minutes">
<!ENTITY binutils-compsize "85 MB">
<!ENTITY binutils-time "6 minutes">
<!ENTITY binutils-package "binutils-&binutils-version;.tar.bz2">
<!ENTITY binutils-dir "binutils-&binutils-version;">
 
<!ENTITY bzip2-version "1.0.1">
<!ENTITY bzip2-depversion "1.0.1">
<!ENTITY bzip2-contversion "1.0.1">
<!ENTITY bzip2-size "410 KB">
<!ENTITY bzip2-compsize-static "3 MB">
<!ENTITY bzip2-time-static "1 minute">
<!ENTITY bzip2-compsize "2 MB">
<!ENTITY bzip2-time "1 minute">
<!ENTITY bzip2-package "bzip2-&bzip2-version;.tar.bz2">
<!ENTITY bzip2-dir "bzip2-&bzip2-version;">
 
<!ENTITY diffutils-version "2.7">
<!ENTITY diffutils-depversion "2.7">
<!ENTITY diffutils-contversion "2.7">
<!ENTITY diffutils-size "247 KB">
<!ENTITY diffutils-compsize-static "4 MB">
<!ENTITY diffutils-time-static "1 minute">
<!ENTITY diffutils-compsize "2 MB">
<!ENTITY diffutils-time "1 minute">
<!ENTITY diffutils-package "diffutils-&diffutils-version;.tar.bz2">
<!ENTITY diffutils-dir "diffutils-&diffutils-version;">
 
<!ENTITY fileutils-version "4.1">
<!ENTITY fileutils-depversion "4.1">
<!ENTITY fileutils-contversion "4.1">
<!ENTITY fileutils-size "1217 KB">
<!ENTITY fileutils-compsize-static "25 MB">
<!ENTITY fileutils-time-static "3 minutes">
<!ENTITY fileutils-compsize "16 MB">
<!ENTITY fileutils-time "3 minutes">
<!ENTITY fileutils-package "fileutils-&fileutils-version;.tar.bz2">
<!ENTITY fileutils-dir "fileutils-&fileutils-version;">
 
<!ENTITY gcc-version "2.95.3">
<!ENTITY gcc-depversion "2.95.3">
<!ENTITY gcc-contversion "2.95.3">
<!ENTITY gcc-size "9,618 KB">
<!ENTITY gcc-patch-version "2.95.3-2">
<!ENTITY gcc-patch-size "8 KB">
<!ENTITY gcc-compsize-static "168 MB">
<!ENTITY gcc-time-static "22 minutes">
<!ENTITY gcc-compsize "148 MB">
<!ENTITY gcc-time "22 minutes">
<!ENTITY gcc-package "gcc-&gcc-version;.tar.bz2">
<!ENTITY gcc-dir "gcc-&gcc-version;">
 
<!ENTITY kernel-version "2.4.17">
<!ENTITY kernel-depversion "2.4.17">
<!ENTITY kernel-contversion "2.4.17">
<!ENTITY kernel-size "23,282 KB">
<!ENTITY kernel-compsize-static "132 MB">
<!ENTITY kernel-time-static "3 minutes">
<!ENTITY kernel-compsize "Depends on options selected">
<!ENTITY kernel-time "Depends on options selected">
<!ENTITY kernel-package "linux-&kernel-version;.tar.bz2">
<!ENTITY kernel-dir "linux">
 
<!ENTITY grep-version "2.4.2">
<!ENTITY grep-depversion "2.4.2">
<!ENTITY grep-contversion "2.4.2">
<!ENTITY grep-size "382 KB">
<!ENTITY grep-compsize-static "4 MB">
<!ENTITY grep-time-static "1 minute">
<!ENTITY grep-compsize "3 MB">
<!ENTITY grep-time "1 minute">
<!ENTITY grep-package "grep-&grep-version;.tar.bz2">
<!ENTITY grep-dir "grep-&grep-version;">
 
<!ENTITY gzip-version "1.2.4a">
<!ENTITY gzip-depversion "1.2.4a">
<!ENTITY gzip-contversion "1.2.4a">
<!ENTITY gzip-size "178 KB">
<!ENTITY gzip-patch-size "1 KB">
<!ENTITY gzip-compsize-static "2 MB">
<!ENTITY gzip-time-static "1 minute">
<!ENTITY gzip-compsize "1 MB">
<!ENTITY gzip-time "1 minute">
<!ENTITY gzip-package "gzip-&gzip-version;.tar.bz2">
<!ENTITY gzip-dir "gzip-&gzip-version;">
 
<!ENTITY make-version "3.79.1">
<!ENTITY make-depversion "3.79.1">
<!ENTITY make-contversion "3.79.1">
<!ENTITY make-size "794 KB">
<!ENTITY make-patch-size "1 KB">
<!ENTITY make-compsize-static "6 MB">
<!ENTITY make-time-static "1 minute">
<!ENTITY make-compsize "6 MB">
<!ENTITY make-time "1 minute">
<!ENTITY make-package "make-&make-version;.tar.bz2">
<!ENTITY make-dir "make-&make-version;">
 
<!ENTITY sed-version "3.02">
<!ENTITY sed-depversion "3.02">
<!ENTITY sed-contversion "3.02">
<!ENTITY sed-size "221 KB">
<!ENTITY sed-compsize-static "2 MB">
<!ENTITY sed-time-static "1 minute">
<!ENTITY sed-compsize "2 MB">
<!ENTITY sed-time "1 minute">
<!ENTITY sed-package "sed-&sed-version;.tar.bz2">
<!ENTITY sed-dir "sed-&sed-version;">
 
<!ENTITY sh-utils-version "2.0">
<!ENTITY sh-utils-depversion "2.0">
<!ENTITY sh-utils-contversion "2.0">
<!ENTITY sh-utils-size "824 KB">
<!ENTITY sh-utils-patch-size "1 KB">
<!ENTITY sh-utils-compsize-static "23 MB">
<!ENTITY sh-utils-time-static "2 minutes">
<!ENTITY sh-utils-compsize "11 MB">
<!ENTITY sh-utils-time "2 minutes">
<!ENTITY sh-utils-package "sh-utils-&sh-utils-version;.tar.bz2">
<!ENTITY sh-utils-dir "sh-utils-&sh-utils-version;">
 
<!ENTITY tar-version "1.13">
<!ENTITY tar-depversion "1.13">
<!ENTITY tar-contversion "1.13">
<!ENTITY tar-size "730 KB">
<!ENTITY tar-patch-size "1 KB">
<!ENTITY tar-compsize-static "7 MB">
<!ENTITY tar-time-static "1 minute">
<!ENTITY tar-compsize "7 MB">
<!ENTITY tar-time "1 minute">
<!ENTITY tar-package "tar-&tar-version;.tar.bz2">
<!ENTITY tar-dir "tar-&tar-version;">
 
<!ENTITY textutils-version "2.0">
<!ENTITY textutils-depversion "2.0">
<!ENTITY textutils-contversion "2.0">
<!ENTITY textutils-size "1,040 KB">
<!ENTITY textutils-compsize-static "24 MB">
<!ENTITY textutils-time-static "2 minutes">
<!ENTITY textutils-compsize "15 MB">
<!ENTITY textutils-time "1 minute">
<!ENTITY textutils-package "textutils-&textutils-version;.tar.bz2">
<!ENTITY textutils-dir "textutils-&textutils-version;">
 
<!ENTITY mawk-version "1.3.3">
<!ENTITY mawk-depversion "1.3.3">
<!ENTITY mawk-contversion "1.3.3">
<!ENTITY mawk-size "168 KB">
<!ENTITY mawk-compsize-static "2 MB">
<!ENTITY mawk-time-static "1 minute">
<!ENTITY mawk-compsize "2 MB">
<!ENTITY mawk-time "1 minute">
<!ENTITY mawk-package "mawk&mawk-version;.tar.bz2">
<!ENTITY mawk-dir "mawk-&mawk-version;">
 
<!ENTITY texinfo-version "4.0">
<!ENTITY texinfo-depversion "4.0">
<!ENTITY texinfo-contversion "4.0">
<!ENTITY texinfo-size "812 KB">
<!ENTITY texinfo-compsize-static "11 MB">
<!ENTITY texinfo-time-static "1 minute">
<!ENTITY texinfo-compsize "10 MB">
<!ENTITY texinfo-time "1 minute">
<!ENTITY texinfo-package "texinfo-&texinfo-version;.tar.bz2">
<!ENTITY texinfo-dir "texinfo-&texinfo-version;">
 
<!ENTITY patch-version "2.5.4">
<!ENTITY patch-depversion "2.5.4">
<!ENTITY patch-contversion "2.5.4">
<!ENTITY patch-size "149 KB">
<!ENTITY patch-compsize-static "2 MB">
<!ENTITY patch-time-static "1 minute">
<!ENTITY patch-compsize "2 MB">
<!ENTITY patch-time "1 minute">
<!ENTITY patch-package "patch-&patch-version;.tar.bz2">
<!ENTITY patch-dir "patch-&patch-version;">
 
<!ENTITY gettext-version "0.10.40">
<!ENTITY gettext-depversion "0.10.40">
<!ENTITY gettext-contversion "0.10.40">
<!ENTITY gettext-size "941 KB">
<!ENTITY gettext-compsize "11MB">
<!ENTITY gettext-time "1 minute">
<!ENTITY gettext-package "gettext-&gettext-version;.tar.bz2">
<!ENTITY gettext-dir "gettext-&gettext-version;">
 
<!ENTITY glibc-version "2.2.5">
<!ENTITY glibc-depversion "2.2.5">
<!ENTITY glibc-contversion "2.2.5">
<!ENTITY glibc-size "12,114 KB">
<!ENTITY glibc-threads-size "164 KB">
<!ENTITY glibc-compsize "350 MB">
<!ENTITY glibc-time "46 minutes">
<!ENTITY glibc-package "glibc-&glibc-version;.tar.bz2">
<!ENTITY glibc-dir "glibc-&glibc-version;">
<!ENTITY glibc-threads-package "glibc-linuxthreads-&glibc-version;.tar.bz2">
<!ENTITY glibc-threads-dir "linuxthreads, linuxthreads_db">
 
<!ENTITY makedev-version "1.4">
<!ENTITY makedev-depversion "1.4">
<!ENTITY makedev-contversion "1.4">
<!ENTITY makedev-size "7 KB">
<!ENTITY makedev-compsize "57 KB">
<!ENTITY makedev-time "1 minute">
<!ENTITY makedev-package "MAKEDEV-&makedev-version;.tar.bz2">
 
<!ENTITY man-pages-version "1.47">
<!ENTITY man-pages-depversion "1.47">
<!ENTITY man-pages-contversion "1.47">
<!ENTITY man-pages-size "534 KB">
<!ENTITY man-pages-compsize "5 MB">
<!ENTITY man-pages-time "1 minute">
<!ENTITY man-pages-package "man-pages-&man-pages-version;.tar.bz2">
<!ENTITY man-pages-dir "man-pages-&man-pages-version;">
 
<!ENTITY ed-version "0.2">
<!ENTITY ed-depversion "0.2">
<!ENTITY ed-contversion "0.2">
<!ENTITY ed-size "158 KB">
<!ENTITY ed-compsize "2 MB">
<!ENTITY ed-time "1 minute">
<!ENTITY ed-package "ed-&ed-version;.tar.bz2">
<!ENTITY ed-dir "ed-&ed-version;">
 
<!ENTITY findutils-version "4.1">
<!ENTITY findutils-depversion "4.1">
<!ENTITY findutils-contversion "4.1">
<!ENTITY findutils-size "226 KB">
<!ENTITY findutils-patch-size "1 KB">
<!ENTITY findutils-compsize "3 MB">
<!ENTITY findutils-time "1 minute">
<!ENTITY findutils-package "findutils-&findutils-version;.tar.bz2">
<!ENTITY findutils-dir "findutils-&findutils-version;">
 
<!ENTITY ncurses-version "5.2">
<!ENTITY ncurses-depversion "5.2">
<!ENTITY ncurses-contversion "5.2">
<!ENTITY ncurses-size "1,308 KB">
<!ENTITY ncurses-compsize "29 MB">
<!ENTITY ncurses-time "6 minutes">
<!ENTITY ncurses-package "ncurses-&ncurses-version;.tar.bz2">
<!ENTITY ncurses-dir "ncurses-&ncurses-version;">
 
<!ENTITY vim-version "6.0">
<!ENTITY vim-depversion "6.0">
<!ENTITY vim-contversion "6.0">
<!ENTITY vim-size "2,711 KB">
<!ENTITY vim-compsize "15 MB">
<!ENTITY vim-time "2 minutes">
<!ENTITY vim-package "vim-&vim-version;-rt.tar.bz2, vim-&vim-version;-src.tar.bz2">
<!ENTITY vim-dir "vim-&vim-version;">
 
<!ENTITY bison-version "1.31">
<!ENTITY bison-depversion "1.31">
<!ENTITY bison-contversion "1.31">
<!ENTITY bison-size "510 KB">
<!ENTITY bison-compsize "3 MB">
<!ENTITY bison-time "1 minute">
<!ENTITY bison-package "bison-&bison-version;.tar.bz2">
<!ENTITY bison-dir "bison-&bison-version;">
 
<!ENTITY less-version "358">
<!ENTITY less-depversion "358">
<!ENTITY less-contversion "358">
<!ENTITY less-size "178 KB">
<!ENTITY less-compsize "2 MB">
<!ENTITY less-time "1 minute">
<!ENTITY less-package "less-&less-version;.tar.bz2">
<!ENTITY less-dir "less-&less-version;">
 
<!ENTITY groff-version "1.17.2">
<!ENTITY groff-depversion "1.17.2">
<!ENTITY groff-contversion "1.17.2">
<!ENTITY groff-size "1,214 KB">
<!ENTITY groff-compsize "16 MB">
<!ENTITY groff-time "2 minutes">
<!ENTITY groff-package "groff-&groff-version;.tar.bz2">
<!ENTITY groff-dir "groff-&groff-version;">
 
<!ENTITY man-version "1.5j">
<!ENTITY man-depversion "1.5i2">
<!ENTITY man-contversion "1.5j">
<!ENTITY man-size "167 KB">
<!ENTITY man-compsize "1 MB">
<!ENTITY man-time "1 minute">
<!ENTITY man-package "man-&man-version;.tar.bz2">
<!ENTITY man-dir "man-&man-version;">
 
<!ENTITY perl-version "5.6.1">
<!ENTITY perl-depversion "5.6.1">
<!ENTITY perl-contversion "5.6.1">
<!ENTITY perl-size "4,750 KB">
<!ENTITY perl-compsize "35 MB">
<!ENTITY perl-time "6 minutes">
<!ENTITY perl-package "perl-&perl-version;.tar.bz2">
<!ENTITY perl-dir "perl-&perl-version;">
 
<!ENTITY m4-version "1.4">
<!ENTITY m4-depversion "1.4">
<!ENTITY m4-contversion "1.4">
<!ENTITY m4-size "249 KB">
<!ENTITY m4-compsize "3 MB">
<!ENTITY m4-time "1 minute">
<!ENTITY m4-package "m4-&m4-version;.tar.bz2">
<!ENTITY m4-dir "m4-&m4-version;">
 
<!ENTITY autoconf-version "2.52">
<!ENTITY autoconf-depversion "2.52">
<!ENTITY autoconf-contversion "2.52">
<!ENTITY autoconf-size "618 KB">
<!ENTITY autoconf-compsize "4 MB">
<!ENTITY autoconf-time "1 minute">
<!ENTITY autoconf-package "autoconf-&autoconf-version;.tar.bz2">
<!ENTITY autoconf-dir "autoconf-&autoconf-version;">
 
<!ENTITY automake-version "1.5">
<!ENTITY automake-depversion "1.5">
<!ENTITY automake-contversion "1.5">
<!ENTITY automake-size "409 KB">
<!ENTITY automake-compsize "3 MB">
<!ENTITY automake-time "1 minute">
<!ENTITY automake-package "automake-&automake-version;.tar.bz2">
<!ENTITY automake-dir "automake-&automake-version;">
 
<!ENTITY flex-version "2.5.4a">
<!ENTITY flex-depversion "2.5.4a">
<!ENTITY flex-contversion "2.5.4a">
<!ENTITY flex-size "278 KB">
<!ENTITY flex-compsize "3MB">
<!ENTITY flex-time "1 minute">
<!ENTITY flex-package "flex-&flex-version;.tar.bz2">
<!ENTITY flex-dir "flex-&flex-version;">
 
<!ENTITY file-version "3.37">
<!ENTITY file-depversion "3.37">
<!ENTITY file-contversion "3.37">
<!ENTITY file-size "140 KB">
<!ENTITY file-compsize "2 MB">
<!ENTITY file-time "1 minute">
<!ENTITY file-package "file-&file-version;.tar.bz2">
<!ENTITY file-dir "file-&file-version;">
 
<!ENTITY libtool-version "1.4.2">
<!ENTITY libtool-depversion "1.4.2">
<!ENTITY libtool-contversion "1.4.2">
<!ENTITY libtool-size "653 KB">
<!ENTITY libtool-compsize "5 MB">
<!ENTITY libtool-time "1 minute">
<!ENTITY libtool-package "libtool-&libtool-version;.tar.bz2">
<!ENTITY libtool-dir "libtool-&libtool-version;">
 
<!ENTITY bin86-version "0.16.0">
<!ENTITY bin86-depversion "0.16.0">
<!ENTITY bin86-contversion "0.16.0">
<!ENTITY bin86-size "113 KB">
<!ENTITY bin86-compsize "1 MB">
<!ENTITY bin86-time "1 minute">
<!ENTITY bin86-package "bin86-&bin86-version;.tar.bz2">
<!ENTITY bin86-dir "bin86-&bin86-version;">
 
<!ENTITY kbd-version "1.06">
<!ENTITY kbd-depversion "1.06">
<!ENTITY kbd-contversion "1.06">
<!ENTITY kbd-size "559 KB">
<!ENTITY kbd-patch-version "1.06-2">
<!ENTITY kbd-patch-size "3 KB">
<!ENTITY kbd-compsize "8 MB">
<!ENTITY kbd-time "1 minute">
<!ENTITY kbd-package "kbd-&kbd-version;.tar.bz2">
<!ENTITY kbd-dir "kbd-&kbd-version;">
 
<!ENTITY e2fsprogs-version "1.25">
<!ENTITY e2fsprogs-depversion "1.25">
<!ENTITY e2fsprogs-contversion "1.25">
<!ENTITY e2fsprogs-size "1,029 KB">
<!ENTITY e2fsprogs-compsize "21 MB">
<!ENTITY e2fsprogs-time "2 minutes">
<!ENTITY e2fsprogs-package "e2fsprogs-&e2fsprogs-version;.tar.bz2">
<!ENTITY e2fsprogs-dir "e2fsprogs-&e2fsprogs-version;">
 
<!ENTITY reiserfs-version "3.x.0j">
<!ENTITY reiserfs-depversion "3.x.0j">
<!ENTITY reiserfs-contversion "3.x.0j">
<!ENTITY reiserfs-size "196 KB">
<!ENTITY reiserfs-compsize "TBD">
<!ENTITY reiserfs-time "TBD">
<!ENTITY reiserfs-package "reiserfs-&reiserfs-version;.tar.bz2">
<!ENTITY reiserfs-dir "reiserfs-&reiserfs-version;">
 
<!ENTITY lilo-version "22.1">
<!ENTITY lilo-depversion "22.1">
<!ENTITY lilo-contversion "22.1">
<!ENTITY lilo-size "262 KB">
<!ENTITY lilo-compsize "3 MB">
<!ENTITY lilo-time "1 minute">
<!ENTITY lilo-package "lilo-&lilo-version;.tar.bz2">
<!ENTITY lilo-dir "lilo-&lilo-version;">
 
<!ENTITY modutils-version "2.4.12">
<!ENTITY modutils-depversion "2.4.12">
<!ENTITY modutils-contversion "2.4.12">
<!ENTITY modutils-size "209 KB">
<!ENTITY modutils-compsize "2 MB">
<!ENTITY modutils-time "1 minute">
<!ENTITY modutils-package "modutils-&modutils-version;.tar.bz2">
<!ENTITY modutils-dir "modutils-&modutils-version;">
 
<!ENTITY procinfo-version "18">
<!ENTITY procinfo-depversion "18">
<!ENTITY procinfo-contversion "18">
<!ENTITY procinfo-size "22 KB">
<!ENTITY procinfo-compsize "170 KB">
<!ENTITY procinfo-time "1 minute">
<!ENTITY procinfo-package "procinfo-&procinfo-version;.tar.bz2">
<!ENTITY procinfo-dir "procinfo-&procinfo-version;">
 
<!ENTITY procps-version "2.0.7">
<!ENTITY procps-depversion "2.0.7">
<!ENTITY procps-contversion "2.0.7">
<!ENTITY procps-size "153 KB">
<!ENTITY procps-compsize "2 MB">
<!ENTITY procps-time "1 minute">
<!ENTITY procps-package "procps-&procps-version;.tar.bz2">
<!ENTITY procps-dir "procps-&procps-version;">
 
<!ENTITY psmisc-version "20.2">
<!ENTITY psmisc-depversion "20.2">
<!ENTITY psmisc-contversion "20.2">
<!ENTITY psmisc-size "123 KB">
<!ENTITY psmisc-compsize "500 KB">
<!ENTITY psmisc-time "1 minute">
<!ENTITY psmisc-package "psmisc-&psmisc-version;.tar.bz2">
<!ENTITY psmisc-dir "psmisc-&psmisc-version;">
 
<!ENTITY shadow-version "20001016">
<!ENTITY shadow-depversion "20001016">
<!ENTITY shadow-contversion "20001016">
<!ENTITY shadow-size "551 KB">
<!ENTITY shadow-compsize "6 MB">
<!ENTITY shadow-time "3 minutes">
<!ENTITY shadow-package "shadow-&shadow-version;.tar.bz2">
<!ENTITY shadow-dir "shadow-&shadow-version;">
 
<!ENTITY sysklogd-version "1.4.1">
<!ENTITY sysklogd-depversion "1.4.1">
<!ENTITY sysklogd-contversion "1.4.1">
<!ENTITY sysklogd-size "67 KB">
<!ENTITY sysklogd-compsize "710 KB">
<!ENTITY sysklogd-time "1 minute">
<!ENTITY sysklogd-package "sysklogd-&sysklogd-version;.tar.bz2">
<!ENTITY sysklogd-dir "sysklogd-&sysklogd-version;">
 
<!ENTITY sysvinit-version "2.84">
<!ENTITY sysvinit-depversion "2.84">
<!ENTITY sysvinit-contversion "2.84">
<!ENTITY sysvinit-size "76 KB">
<!ENTITY sysvinit-compsize "630 KB">
<!ENTITY sysvinit-time "1 minute">
<!ENTITY sysvinit-package "sysvinit-&sysvinit-version;.tar.bz2">
<!ENTITY sysvinit-dir "sysvinit-&sysvinit-version;">
 
<!ENTITY util-linux-version "2.11n">
<!ENTITY util-linux-depversion "2.11n">
<!ENTITY util-linux-contversion "2.11n">
<!ENTITY util-linux-size "998 KB">
<!ENTITY util-linux-compsize "9 MB">
<!ENTITY util-linux-time "1 minute">
<!ENTITY util-linux-package "util-linux-&util-linux-version;.tar.bz2">
<!ENTITY util-linux-dir "util-linux-&util-linux-version;">
 
<!ENTITY netkit-base-version "0.17">
<!ENTITY netkit-base-depversion "0.17">
<!ENTITY netkit-base-contversion "0.17">
<!ENTITY netkit-base-size "49 KB">
<!ENTITY netkit-base-compsize "1 MB">
<!ENTITY netkit-base-time "1 minute">
<!ENTITY netkit-base-package "netkit-base-&net-kit-version;.tar.bz2">
<!ENTITY netkit-base-dir "netkit-base-&net-kit-version;">
 
<!ENTITY net-tools-version "1.60">
<!ENTITY net-tools-depversion "1.60">
<!ENTITY net-tools-contversion "1.60">
<!ENTITY net-tools-size "194 KB">
<!ENTITY net-tools-compsize "5 MB">
<!ENTITY net-tools-time "1 minute">
<!ENTITY net-tools-package "net-tools-&net-tools-version;.tar.bz2">
<!ENTITY net-tools-dir "net-tools-&net-tools-version;">
 
<!ENTITY bootscripts-version "1.5">
<!ENTITY bootscripts-depversion "1.5">
<!ENTITY bootscripts-contversion "1.5">
<!ENTITY bootscripts-size "5 KB">
<!ENTITY bootscripts-compsize "5 KB">
<!ENTITY bootscripts-time "1 minute">
<!ENTITY bootscripts-package "lfs-bootscripts-&bootscripts-version;.tar.bz2">
<!ENTITY bootscripts-dir "lfs-bootscritps-&bootscripts-version;">
 
]>
 
<book>
 
&book;
 
</book>
/tags/cvs/lfs/bookinfo/abstract.xml
0,0 → 1,10
<abstract>
 
<para>
Ce livre décrit le processus de création d'un système Linux
depuis rien à partir d'une distribution Linux déjà installée, en utilisant uniquement
les sources des logiciels utilisés.
</para>
 
</abstract>
 
/tags/cvs/lfs/bookinfo/bookinfo.xml
0,0 → 1,10
<bookinfo>
<title>Linux From Scratch</title>
<subtitle>Version &version;</subtitle>
 
&bi-authorgroup;
&bi-copyright;
&bi-legalnotice;
&bi-abstract;
 
</bookinfo>
/tags/cvs/lfs/bookinfo/legalnotice.xml
0,0 → 1,38
<legalnotice>
 
<para>Copyright (c) 1999-2002, Gerard Beekmans</para>
 
<para>All rights reserved.</para>
 
<para>Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:</para>
 
<itemizedlist>
 
<listitem><para>Redistributions in any form must retain the above copyright
notice, this list of conditions and the following disclaimer.</para></listitem>
 
<listitem><para>Neither the name of "Linux From Scratch" nor the names of
its contributors may be used to endorse or promote products derived from
this material without specific prior written permission.</para></listitem>
 
<listitem><para>Any material derived from Linux From Scratch must contain
a reference to the "Linux From Scratch" project.</para></listitem>
 
</itemizedlist>
 
<para>THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS
IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.</para>
 
</legalnotice>
 
/tags/cvs/lfs/bookinfo/copyright.xml
0,0 → 1,7
<copyright id="copyright">
 
<year>1999-2002</year>
<holder>Gerard Beekmans</holder>
 
</copyright>
 
/tags/cvs/lfs/bookinfo/authorgroup.xml
0,0 → 1,6
<authorgroup>
 
<author><firstname>Gerard</firstname><surname>Beekmans</surname></author>
 
</authorgroup>
 
/tags/cvs/lfs/INSTALL
0,0 → 1,110
Ok, so you have downloaded the XML source. Now what? You are probably
wanting to convert these XML files to easier to read HTML, PS, PDF, txt
or other formatted files. All that can be read below.
 
Let's start by downloading some software.
 
If all you want to do is being able to convert XML to HTML download the
following:
 
OpenJade - http://openjade.sourceforge.net/
DocBook-XML DTD - http://www.docbook.org/xml/4.1.2/
Modified DocBook Entities - http://www2.linuxfromscratch.org/
DSSSL DocBook Stylesheets - http://www.nwalsh.com/docbook/dsssl/
 
As the DocBook DTD and Stylesheets are made available as a zip achives you
may need to download the unzip package as well if your Linux system doesn't
have one:
 
Unzip - ftp://ftp.uu.net/pub/archiving/zip/src/
 
If you want to be able to convert the book into PS and PDF as well I
recommend using the Htmldoc program. This takes a html file (created
with openjade which you already downloaded) and converts it to PS or
PDF:
 
HTMLDOC - http://www.easysw.com/htmldoc/
FLTK (X front-end) - http://sourceforge.net/projects/fltk
 
If you want to be able to convert the book into TXT as well I recommend
using links to convert HTML to TXT using the -dump option to links.
 
Links - http://artax.karlin.mff.cuni.cz/~mikulas/links/
 
You have everything you need now. Let's install this stuff.
 
Create the /usr/share/docbook directory, cd into it and unpack the
docbook-xml dtd archive there.
 
Remove the ent directory and unpack the docbook-4.1.2-newent.tar.bz2 file.
This will create a new ent directory with entity files that work better
with XML.
 
Create the /usr/share/dsssl directory, cd into it and unpack the dsssl
stylesheet archive in there. Rename the directory that's created by tar
into 'docbook'. Now copy the lfs.dsl file you will find in
the LFS-BOOK XML archive into /usr/share/dsssl/docbook/html
 
The last step is installing OpenJade.
 
In order for openjade to be able to convert the DocBook based documents
into other formats, it needs to know where the DocBook DTD related
files are located. This is sort of the DocBook equivalent for the $PATH
variable. You have two ways of doing this:
 
1) You can set the $SGML_CATALOG_FILES variable and include the full
paths to the catalog files in it
or
2) You can hard-code the paths into the openjade binary.
 
If you choose option 1, add the following to your bash configuration
file, system wide profile or wherever you wish to include it:
 
export SGML_CATALOG_FILES=/usr/share/docbook/docbook.cat:/usr/share/dsssl/docbook/catalog:/usr/share/dsssl/openjade/catalog
 
Followed by installing openjade by running:
./configure --prefix=/usr
make
make install
cp -av dsssl /usr/share/dsssl/openjade
 
If you choose option 2, install OpenJade as follows:
 
./configure --prefix=/usr \
> --enable-default-catalog=/usr/share/docbook/docbook.cat:/usr/share/dsssl/docbook/catalog:/usr/share/dsssl/openjade/catalog
make
make install
cp -av dsssl /usr/share/dsssl/openjade
 
And you don't have to worry about the $SGML_CATALOG_FILES variable in
this case.
 
 
You're all set to convert XML to HTML (among a few other formats
supported by openjade) now. If you want to convert to PS and PDF as
well, install the following two packages.
 
FLTK (you can skip this one if you don't want the X front-end):
./configure --prefix=/usr
make
make install
 
HTMLDOC:
Install by running:
 
./configure --prefix=/usr
make
make install
 
 
 
The last package is Links which will be used for the HTML to TXT
conversion. Install it by running:
 
./configure --prefix=/usr
make
make install
 
There, all set now. Go back to the README file for some examples how to
convert this XML to the various other formats.
 
/tags/cvs/lfs/appendixa/reiserfs.xml
0,0 → 1,10
<sect1 id="aa-reiserfs">
<title>Reiserfsprogs</title>
<?dbhtml filename="reiserfs.html" dir="appendixa"?>
 
&aa-reiserfs-down;
&aa-reiserfs-desc;
&aa-reiserfs-dep;
 
</sect1>
 
/tags/cvs/lfs/appendixa/texinfo-dep.xml
0,0 → 1,21
<sect2>
<title>Dependencies</title>
 
<para>Texinfo-&texinfo-depversion; needs the following to be installed:</para>
 
<literallayout>
bash: sh
binutils: ar, as, ld, ranlib
diffutils: cmp
fileutils: chmod, install, ln, ls, mkdir, mv, rm
gcc: cc1, collect2, cpp0, gcc
grep: egrep, fgrep, grep
make: make
sed: sed
sh-utils: basename, echo, expr, hostname, sleep
texinfo: makeinfo
textutils: cat, tr
</literallayout>
 
</sect2>
 
/tags/cvs/lfs/appendixa/file-down.xml
0,0 → 1,6
<sect2>
<title>Official Download Location</title>
 
<para><literallayout>File (&file-version;):
<ulink url="ftp://ftp.gw.com/mirrors/pub/unix/file/">ftp://ftp.gw.com/mirrors/pub/unix/file/</ulink></literallayout></para>
</sect2>
/tags/cvs/lfs/appendixa/gettext.xml
0,0 → 1,10
<sect1 id="aa-gettext">
<title>Gettext</title>
<?dbhtml filename="gettext.html" dir="appendixa"?>
 
&aa-gettext-down;
&aa-gettext-desc;
&aa-gettext-dep;
 
</sect1>
 
/tags/cvs/lfs/appendixa/gzip-desc.xml
0,0 → 1,53
<sect2><title>Contents of gzip-&gzip-contversion;</title>
 
<sect3><title>Program Files</title>
<para>gunzip (link to gzip), gzexe, gzip,
uncompress (link to gunzip), zcat (link to gzip), zcmp, zdiff, zforce,
zgrep, zmore and znew</para></sect3>
 
<sect3><title>Description</title>
 
<sect4><title>gunzip, uncompress</title>
<para>gunzip and uncompress decompress files which are compressed with
gzip.</para></sect4>
 
<sect4><title>gzexe</title>
<para>gzexe allows you to compress executables in place and have them
automatically uncompress and execute when they are run (at a penalty in
performance).</para></sect4>
 
<sect4><title>gzip</title>
<para>gzip reduces the size of the named files using
Lempel-Ziv coding (LZ77).</para></sect4>
 
<sect4><title>zcat</title>
<para>zcat uncompresses either a list of files on the command line or its
standard input and writes the uncompressed data on
standard output</para></sect4>
 
<sect4><title>zcmp</title>
<para>zcmp invokes the cmp program on compressed files.</para></sect4>
 
<sect4><title>zdiff</title>
<para>zdiff invokes the diff program on compressed files.</para></sect4>
 
<sect4><title>zforce</title>
<para>zforce forces a .gz extension on all gzip files so that gzip will not
compress them twice. This can be useful for files with names truncated
after a file transfer.</para></sect4>
 
<sect4><title>zgrep</title>
<para>zgrep invokes the grep program on compressed files.</para></sect4>
 
<sect4><title>zmore</title>
<para>zmore is a filter which allows examination of compressed or plain text
files one screen at a time on a soft-copy terminal (similar to the
more program).</para></sect4>
 
<sect4><title>znew</title>
<para>znew re-compresses files from .Z (compress) format to
.gz (gzip) format.</para></sect4>
 
</sect3>
 
</sect2>
/tags/cvs/lfs/appendixa/glibc-down.xml
0,0 → 1,9
<sect2>
<title>Official Download Location</title>
 
<para><literallayout>Glibc (&glibc-version;):
<ulink url="ftp://ftp.gnu.org/gnu/glibc/">ftp://ftp.gnu.org/gnu/glibc/</ulink>
 
Glibc-linuxthreads (&glibc-version;):
<ulink url="ftp://ftp.gnu.org/gnu/glibc/">ftp://ftp.gnu.org/gnu/glibc/</ulink></literallayout></para>
</sect2>
/tags/cvs/lfs/appendixa/kernel-dep.xml
0,0 → 1,24
<sect2>
<title>Dependencies</title>
 
<para>Linux-&kernel-depversion; needs the following to be installed:</para>
 
<literallayout>
bash: sh
binutils: ar, as, ld, nm, objcopy
fileutils: cp, ln, mkdir, mv, rm
findutils: find, xargs
gcc: cc1, collect2, cpp0, gcc
grep: grep
gzip: gzip
make: make
mawk: awk
modutils: depmod, genksyms
net-tools: dnsdomainname, hostname
sed: sed
sh-utils: basename, date, expr, pwd, stty, uname, whoami, yes
textutils: cat, md5sum, sort, tail, touch
</literallayout>
 
</sect2>
 
/tags/cvs/lfs/appendixa/diffutils.xml
0,0 → 1,10
<sect1 id="aa-diffutils">
<title>Diffutils</title>
<?dbhtml filename="diffutils.html" dir="appendixa"?>
 
&aa-diffutils-down;
&aa-diffutils-desc;
&aa-diffutils-dep;
 
</sect1>
 
/tags/cvs/lfs/appendixa/netkitbase.xml
0,0 → 1,10
<sect1 id="aa-ns-netkitbase">
<title>Netkit-base</title>
<?dbhtml filename="netkit-base.html" dir="appendixa"?>
 
&aa-netkitbase-down;
&aa-netkitbase-desc;
&aa-netkitbase-dep;
 
</sect1>
 
/tags/cvs/lfs/appendixa/binutils-down.xml
0,0 → 1,7
<sect2>
<title>Official Download Location</title>
 
<para><literallayout>Binutils (&binutils-version;):
<ulink url="ftp://ftp.gnu.org/gnu/binutils/">ftp://ftp.gnu.org/gnu/binutils/</ulink></literallayout></para>
</sect2>
 
/tags/cvs/lfs/appendixa/sysvinit-dep.xml
0,0 → 1,16
<sect2>
<title>Dependencies</title>
 
<para>Sysvinit-&sysvinit-depversion; needs the following to be installed:</para>
 
<literallayout>
bash: sh
binutils: as, ld
fileutils: chown, cp, install, ln, mknod, rm
gcc: cc, cc1, collect2, cpp0
make: make
sed: sed
</literallayout>
 
</sect2>
 
/tags/cvs/lfs/appendixa/mawk.xml
0,0 → 1,10
<sect1 id="aa-mawk">
<title>Mawk</title>
<?dbhtml filename="mawk.html" dir="appendixa"?>
 
&aa-mawk-down;
&aa-mawk-desc;
&aa-mawk-dep;
 
</sect1>
 
/tags/cvs/lfs/appendixa/kbd.xml
0,0 → 1,10
<sect1 id="aa-kbd">
<title>Kbd</title>
<?dbhtml filename="kbd.html" dir="appendixa"?>
 
&aa-kbd-down;
&aa-kbd-desc;
&aa-kbd-dep;
 
</sect1>
 
/tags/cvs/lfs/appendixa/perl.xml
0,0 → 1,10
<sect1 id="aa-perl">
<title>Perl</title>
<?dbhtml filename="perl.html" dir="appendixa"?>
 
&aa-perl-down;
&aa-perl-desc;
&aa-perl-dep;
 
</sect1>
 
/tags/cvs/lfs/appendixa/tar-desc.xml
0,0 → 1,20
<sect2><title>Contents of tar-&tar-contversion;</title>
 
<sect3><title>Program Files</title>
<para>rmt and tar</para></sect3>
 
<sect3><title>Descriptions</title>
 
<sect4><title>rmt</title>
<para>rmt is a program used by the remote dump and restore programs in
manipulating a magnetic tape drive through an interprocess communication
connection.</para></sect4>
 
<sect4><title>tar</title>
<para>tar is an archiving program designed to store and extract files from
an archive file known as a tar file.</para></sect4>
 
</sect3>
 
</sect2>
 
/tags/cvs/lfs/appendixa/chroot-dep.xml
0,0 → 1,12
<sect2>
<title>Dependencies</title>
 
<para>Chroot needs the following to be installed:</para>
 
<literallayout>
bash: bash
sh-utils: env
</literallayout>
 
</sect2>
 
/tags/cvs/lfs/appendixa/mawk-down.xml
0,0 → 1,6
<sect2>
<title>Official Download Location</title>
 
<para><literallayout>Mawk (&mawk-version;):
<ulink url="ftp://ftp.whidbey.net/pub/brennan/">ftp://ftp.whidbey.net/pub/brennan/</ulink></literallayout></para>
</sect2>
/tags/cvs/lfs/appendixa/patch-dep.xml
0,0 → 1,21
<sect2>
<title>Dependencies</title>
 
<para>Patch-&patch-depversion; needs the following to be installed:</para>
 
<literallayout>
bash: sh
binutils: as, ld
diffutils: cmp
fileutils: chmod, install, mv, rm
gcc: cc, cc1, collect2, cpp0, gcc
glibc: getconf
grep: egrep, grep
make: make
sed: sed
sh-utils: echo, expr, hostname, uname
textutils: cat, tr
</literallayout>
 
</sect2>
 
/tags/cvs/lfs/appendixa/fileutils-down.xml
0,0 → 1,6
<sect2>
<title>Official Download Location</title>
 
<para><literallayout>File Utils (&fileutils-version;):
<ulink url="ftp://ftp.gnu.org/gnu/fileutils/">ftp://ftp.gnu.org/gnu/fileutils/</ulink></literallayout></para>
</sect2>
/tags/cvs/lfs/appendixa/findutils-down.xml
0,0 → 1,10
<sect2>
<title>Official Download Location</title>
 
<para><literallayout>Find Utils (&findutils-version;):
<ulink url="ftp://ftp.gnu.org/gnu/findutils/">ftp://ftp.gnu.org/gnu/findutils/</ulink>
 
Find Utils Patch (&findutils-version;):
<ulink url="&ftp;/">&ftp;/</ulink>
<ulink url="&http;/">&http;/</ulink></literallayout></para>
</sect2>
/tags/cvs/lfs/appendixa/groff-dep.xml
0,0 → 1,22
<sect2>
<title>Dependencies</title>
 
<para>Groff-&groff-depversion; needs the following to be installed:</para>
 
<literallayout>
bash: sh
binutils: ar, as, ld, ranlib
bison: bison
diffutils: cmp
fileutils: chmod, cp, install, ln, ls, mkdir, mv, rm, touch
gcc: cc1, cc1plus, collect2, cpp0, g++, gcc
grep: egrep, grep
make: make
mawk: awk
sed: sed
sh-utils: basename, date, echo, expr, hostname, uname
textutils: cat, tr
</literallayout>
 
</sect2>
 
/tags/cvs/lfs/appendixa/sysklogd-desc.xml
0,0 → 1,21
<sect2><title>Contents of sysklogd-&sysklogd-contversion;</title>
 
<sect3><title>Program Files</title>
<para>klogd and syslogd</para></sect3>
 
<sect3><title>Descriptions</title>
 
<sect4><title>klogd</title>
<para>klogd is a system daemon which intercepts and logs Linux kernel
messages.</para></sect4>
 
<sect4><title>syslogd</title>
<para>Syslogd provides a kind of logging that many modern programs use. Every
logged message contains at least a time and a hostname field, normally a
program name field, too, but that depends on how trusty the logging
program is.</para></sect4>
 
</sect3>
 
</sect2>
 
/tags/cvs/lfs/appendixa/less-down.xml
0,0 → 1,6
<sect2>
<title>Official Download Location</title>
 
<para><literallayout>Less (&less-version;):
<ulink url="ftp://ftp.gnu.org/gnu/less/">ftp://ftp.gnu.org/gnu/less/</ulink></literallayout></para>
</sect2>
/tags/cvs/lfs/appendixa/makedev.xml
0,0 → 1,10
<sect1 id="aa-makedev">
<title>MAKEDEV</title>
<?dbhtml filename="makedev.html" dir="appendixa"?>
 
&aa-makedev-down;
&aa-makedev-desc;
&aa-makedev-dep;
 
</sect1>
 
/tags/cvs/lfs/appendixa/less-dep.xml
0,0 → 1,20
<sect2>
<title>Dependencies</title>
 
<para>Less-&less-depversion; needs the following to be installed:</para>
 
<literallayout>
bash: sh
binutils: as, ld
diffutils: cmp
fileutils: chmod, install, mv, rm, touch
grep: egrep, grep
gcc: cc1, collect2, cpp0, gcc
make: make
sed: sed
sh-utils: expr, hostname, uname
textutils: cat, tr
</literallayout>
 
</sect2>
 
/tags/cvs/lfs/appendixa/kbd-desc.xml
0,0 → 1,101
<sect2><title>Contents of kbd-&kbd-contversion;</title>
 
<sect3><title>Program Files</title>
<para>chvt, deallocvt, dumpkeys, fgconsole,
getkeycodes, getunimap, kbd_mode, kbdrate, loadkeys, loadunimap,
mapscrn, openvt, psfaddtable (link to psfxtable), psfgettable (link to
psfxtable), psfstriptable (link to psfxtable), psfxtable, resizecons,
setfont, setkeycodes, setleds, setlogcons,
setmetamode, setvesablank, showfont, showkey, unicode_start, and
unicode_stop</para></sect3>
 
<sect3><title>Descriptions</title>
 
<sect4><title>chvt</title>
<para>chvt changes foreground virtual terminal.</para></sect4>
 
<sect4><title>deallocvt</title>
<para>deallocvt deallocates unused virtual terminals.</para></sect4>
 
<sect4><title>dumpkeys</title>
<para>dumpkeys dumps keyboard translation tables.</para></sect4>
 
<sect4><title>fgconsole</title>
<para>fgconsole prints the number of the active virtual terminal.</para></sect4>
 
<sect4><title>getkeycodes</title>
<para>getkeycodes prints the kernel scancode-to-keycode
mapping table.</para></sect4>
 
<sect4><title>getunimap</title>
<para>getunimap prints the currently used unimap.</para></sect4>
 
<sect4><title>kbd_mode</title>
<para>kbd_mode reports or sets the keyboard mode.</para></sect4>
 
<sect4><title>kbdrate</title>
<para>kbdrate sets the keyboard repeat and delay rates.</para></sect4>
 
<sect4><title>loadkeys</title>
<para>loadkeys loads keyboard translation tables.</para></sect4>
 
<sect4><title>loadunimap</title>
<para>loadunimap loads the kernel unicode-to-font mapping table.</para></sect4>
 
<sect4><title>mapscrn</title>
<para>mapscrn loads a user defined output character
mapping table into the console driver. Note that it is obsolete and that its
features are built into setfont.</para></sect4>
 
<sect4><title>openvt</title>
<para>openvt starts a program on a new virtual terminal (VT)</para></sect4>
 
<sect4><title>psfaddtable, psfgettable, psfstriptable, psfxtable</title>
<para>These are a set of tools for handling Unicode character tables for
console fonts.</para></sect4>
 
<sect4><title>resizecons</title>
<para>resizecons changes the kernel idea of the console size.</para></sect4>
 
<sect4><title>setfont</title>
<para>This lets you change the EGA/VGA fonts in console.</para></sect4>
 
<sect4><title>setkeycodes</title>
<para>setkeycodes loads kernel scancode-to-keycode mapping
table entries.</para></sect4>
 
<sect4><title>setleds</title>
<para>setleds sets the keyboard LEDs. Many people find it useful to have numlock
enabled by default, and it is by using this program that you can
achieve this.</para></sect4>
 
<sect4><title>setlogcons</title>
<para>setlogcons sends kernel messages to the console.</para></sect4>
 
<sect4><title>setmetamode</title>
<para>setmetamode defines the keyboard meta key handling.</para></sect4>
 
<sect4><title>setvesablank</title>
<para>This lets you fiddle with the built-in hardware screensaver
(not toasters, only a blank screen).</para></sect4>
 
<sect4><title>showfont</title>
<para>showfont displays data about a font. The information shown includes font
information, font properties, character metrics, and
character bitmaps.</para></sect4>
 
<sect4><title>showkey</title>
<para>showkey examines the scancodes and keycodes sent by
the keyboard.</para></sect4>
 
<sect4><title>unicode_start</title>
<para>unicode_start puts the console in Unicode mode.</para></sect4>
 
<sect4><title>unicode_stop</title>
<para>unicode_stop reverts keyboard and console from
unicode mode.</para></sect4>
 
</sect3>
 
</sect2>
 
/tags/cvs/lfs/appendixa/nettools-dep.xml
0,0 → 1,17
<sect2>
<title>Dependencies</title>
 
<para>Net-tools-&net-tools-depversion; needs the following to be
installed:</para>
 
<literallayout>
bash: bash, sh
binutils: ar, as, ld
fileutils: install, ln, ls, mv, rm
gcc: cc, cc1, collect2, cpp0
make: make
sh-utils: echo
</literallayout>
 
</sect2>
 
/tags/cvs/lfs/appendixa/groff-desc.xml
0,0 → 1,122
<sect2><title>Contents of groff-&groff-contversion;</title>
 
<sect3><title>Program Files</title>
<para>addftinfo, afmtodit, eqn, grn, grodvi, groff, grog, grolbp, grolj4,
grops, grotty, hpftodit, indxbib, lkbib, lookbib, mmroff, neqn, nroff,
pfbtops, pic, post-grohtml, pre-grohtml, refer, soelim, tbl,
tfmtodit and troff</para></sect3>
 
<sect3><title>Descriptions</title>
 
<sect4><title>addftinfo</title>
<para>addftinfo reads a troff font file and adds some additional font-metric
information that is used by the groff system.</para></sect4>
 
<sect4><title>afmtodit</title>
<para>afmtodit creates a font file for use with groff and grops.</para></sect4>
 
<sect4><title>eqn</title>
<para>eqn compiles descriptions of equations embedded within troff input files
into commands that are understood by troff.</para></sect4>
 
<sect4><title>grn</title>
<para>grn is a groff preprocessor for gremlin files.</para></sect4>
 
<sect4><title>grodvi</title>
<para>grodvi is a driver for groff that produces TeX dvi format.</para></sect4>
 
<sect4><title>groff</title>
<para>groff is a front-end to the groff document formatting system. Normally it
runs the troff program and a post-processor appropriate for the selected
device.</para></sect4>
 
<sect4><title>grog</title>
<para>grog reads files and guesses which of the groff options -e, -man, -me,
-mm, -ms, -p, -s, and -t are required for printing files, and prints the groff
command including those options on the standard output.</para></sect4>
 
<sect4><title>grolbp</title>
<para>grolbp is a groff driver for Canon CAPSL printers (LBP-4 and LBP-8
series laser printers).</para></sect4>
 
<sect4><title>grolj4</title>
<para>grolj4 is a driver for groff that produces output in PCL5 format suitable
for an HP Laserjet 4 printer.</para></sect4>
 
<sect4><title>grops</title>
<para>grops translates the output of GNU troff to Postscript.</para></sect4>
 
<sect4><title>grotty</title>
<para>grotty translates the output of GNU troff into a form suitable for
typewriter-like devices.</para></sect4>
 
<sect4><title>hpftodit</title>
<para>hpftodit creates a font file for use with groff -Tlj4 from an HP
tagged font metric file.</para></sect4>
 
<sect4><title>indxbib</title>
<para>indxbib makes an inverted index for the bibliographic databases a
specified file for use with refer, lookbib, and lkbib.</para></sect4>
 
<sect4><title>lkbib</title>
<para>lkbib searches bibliographic databases for references that contain
specified keys and prints any references found on the
standard output.</para></sect4>
 
<sect4><title>lookbib</title>
<para>lookbib prints a prompt on the standard error (unless the standard input
is not a terminal), reads from the standard input a line containing a set
of keywords, searches the bibliographic databases in a specified file for
references containing those keywords, prints any references found on the
standard output, and repeats this process until the end of input.</para></sect4>
 
<sect4><title>mmroff</title>
<para>mmroff is a simple preprocessor for groff.</para></sect4>
 
<sect4><title>neqn</title>
<para>The neqn script formats equations for ascii output.</para></sect4>
 
<sect4><title>nroff</title>
<para>The nroff script emulates the nroff command using groff.</para></sect4>
 
<sect4><title>pfbtops</title>
<para>pfbtops translates a Postscript font in .pfb format
to ASCII.</para></sect4>
 
<sect4><title>pic</title>
<para>pic compiles descriptions of pictures embedded within troff or TeX input
files into commands that are understood by TeX or troff.</para></sect4>
 
<sect4><title>pre-grohtml and post-grohtml</title>
<para>pre- and post-grohtml translate the output of GNU troff
to html.</para></sect4>
 
<sect4><title>refer</title>
<para>refer copies the contents of a file to the standard output, except that
lines between .[ and .] are interpreted as citations, and lines between .R1
and .R2 are interpreted as commands about how citations are to be
processed.</para></sect4>
 
<sect4><title>soelim</title>
<para>soelim reads files and replaces lines of the form
<emphasis>.so file</emphasis> by the contents of
<emphasis>file</emphasis>.</para></sect4>
 
<sect4><title>tbl</title>
<para>tbl compiles descriptions of tables embedded within troff input files
into commands that are understood by troff.</para></sect4>
 
<sect4><title>tfmtodit</title>
<para>tfmtodit creates a font file for use with <userinput>groff
-Tdvi</userinput></para></sect4>
 
<sect4><title>troff</title>
<para>troff is highly compatible with Unix troff. Usually it should be invoked
using the groff command, which will also run preprocessors and
post-processors in the appropriate order and with the appropriate
options.</para></sect4>
 
</sect3>
 
</sect2>
 
/tags/cvs/lfs/appendixa/m4.xml
0,0 → 1,10
<sect1 id="aa-m4">
<title>M4</title>
<?dbhtml filename="m4.html" dir="appendixa"?>
 
&aa-m4-down;
&aa-m4-desc;
&aa-m4-dep;
 
</sect1>
 
/tags/cvs/lfs/appendixa/libtool-desc.xml
0,0 → 1,30
<sect2><title>Contents of libtool-&libtool-contversion;</title>
 
<sect3><title>Program Files</title>
<para>libtool and libtoolize</para></sect3>
 
<sect3><title>Descriptions</title>
 
<sect4><title>libtool</title>
<para>Libtool provides generalized library-building
support services.</para></sect4>
 
<sect4><title>libtoolize</title>
<para>libtoolize provides a standard way to add libtool support to a
package.</para></sect4>
 
</sect3>
 
<sect3><title>Library Files</title>
<para>libltdl.[a,so]</para></sect3>
 
<sect3><title>Descriptions</title>
 
<sect4><title>libltdl</title>
<para>Libtool provides a small library, called `libltdl', that aims at hiding
the various difficulties of dlopening libraries from programmers.</para></sect4>
 
</sect3>
 
</sect2>
 
/tags/cvs/lfs/appendixa/textutils-desc.xml
0,0 → 1,112
<sect2><title>Contents of textutils-&textutils-contversion;</title>
 
<sect3><title>Program Files</title>
<para>cat, cksum, comm, csplit, cut, expand,
fmt, fold, head, join, md5sum, nl, od, paste, pr, ptx, sort, split, sum,
tac, tail, tr, tsort, unexpand, uniq and wc</para></sect3>
 
<sect3><title>Descriptions</title>
 
<sect4><title>cat</title>
<para>cat concatenates file(s) or standard input to
standard output.</para></sect4>
 
<sect4><title>cksum</title>
<para>cksum prints CRC checksum and byte counts of each specified
file.</para></sect4>
 
<sect4><title>comm</title>
<para>comm compares two sorted files line by line.</para></sect4>
 
<sect4><title>csplit</title>
<para>csplit outputs pieces of a file separated by (a) pattern(s) to files
xx01, xx02, ..., and outputs byte counts of each piece to standard
output.</para></sect4>
 
<sect4><title>cut</title>
<para>cut prints selected parts of lines from specified files to standard
output.</para></sect4>
 
<sect4><title>expand</title>
<para>expand converts tabs in files to spaces, writing to standard
output.</para></sect4>
 
<sect4><title>fmt</title>
<para>fmt reformats each paragraph in the specified file(s), writing to
standard output.</para></sect4>
 
<sect4><title>fold</title>
<para>fold wraps input lines in each specified file (standard input by default),
writing to standard output.</para></sect4>
 
<sect4><title>head</title>
<para>Print first xx (10 by default) lines of each specified file to standard
output.</para></sect4>
 
<sect4><title>join</title>
<para>join joins lines of two files on a common field.</para></sect4>
 
<sect4><title>md5sum</title>
<para>md5sum prints or checks MD5 checksums.</para></sect4>
 
<sect4><title>nl</title>
<para>nl writes each specified file to standard output, with line numbers
added.</para></sect4>
 
<sect4><title>od</title>
<para>od writes an unambiguous representation, octal bytes by default, of a
specified file to standard output.</para></sect4>
 
<sect4><title>paste</title>
<para>paste writes lines consisting of the sequentially corresponding
lines from each specified file, separated by TABs,
to standard output.</para></sect4>
 
<sect4><title>pr</title>
<para>pr paginates or columnates files for printing.</para></sect4>
 
<sect4><title>ptx</title>
<para>ptx produces a permuted index of file contents.</para></sect4>
 
<sect4><title>sort</title>
<para>sort writes sorted concatenation of files to standard
output.</para></sect4>
 
<sect4><title>split</title>
<para>split outputs fixed-size pieces of an input file to
PREFIXaa, PREFIXab, ...</para></sect4>
 
<sect4><title>sum</title>
<para>sum prints checksum and block counts for each specified
file.</para></sect4>
 
<sect4><title>tac</title>
<para>tac writes each specified file to standard output, last line
first.</para></sect4>
 
<sect4><title>tail</title>
<para>tail print the last xx (10 by default) lines of each specified file to
standard output.</para></sect4>
 
<sect4><title>tr</title>
<para>tr translates, squeezes, and/or deletes characters from standard
input, writing to standard output.</para></sect4>
 
<sect4><title>tsort</title>
<para>tsort writes totally ordered lists consistent with the partial ordering
in specified files.</para></sect4>
 
<sect4><title>unexpand</title>
<para>unexpand converts spaces in each file to tabs, writing to standard
output.</para></sect4>
 
<sect4><title>uniq</title>
<para>Uniq removes duplicate lines from a sorted file.</para></sect4>
 
<sect4><title>wc</title>
<para>wc prints line, word, and byte counts for each specified file, and a
total line if more than one file is specified.</para></sect4>
 
</sect3>
 
</sect2>
/tags/cvs/lfs/appendixa/bash-down.xml
0,0 → 1,6
<sect2>
<title>Official Download Location</title>
 
<para><literallayout>Bash (&bash-version;):
<ulink url="ftp://ftp.gnu.org/gnu/bash/">ftp://ftp.gnu.org/gnu/bash/</ulink></literallayout></para>
</sect2>
/tags/cvs/lfs/appendixa/automake-desc.xml
0,0 → 1,29
<sect2><title>Contents of automake-&automake-contversion;</title>
 
<sect3><title>Program Files</title>
<para>aclocal and automake</para></sect3>
 
<sect3><title>Descriptions</title>
 
<sect4><title>aclocal</title>
<para>Automake includes a number of Autoconf macros which can be used in
packages; some of them are actually required by Automake in certain
situations. These macros must be defined in the aclocal.m4-file;
otherwise they will not be seen by autoconf.</para>
 
<para>The aclocal program will automatically generate aclocal.m4 files
based on the contents of configure.in. This provides a convenient
way to get Automake-provided macros, without having to search around.
Also, the aclocal mechanism is extensible for use
by other packages.</para></sect4>
 
<sect4><title>automake</title>
<para>To create all the Makefile.in's for a package, run the automake
program in the top level directory, with no arguments. automake will
automatically find each appropriate Makefile.am (by scanning
configure.in) and generate the corresponding Makefile.in.</para></sect4>
 
</sect3>
 
</sect2>
 
/tags/cvs/lfs/appendixa/shellutils.xml
0,0 → 1,10
<sect1 id="aa-shutils">
<title>Sh-utils</title>
<?dbhtml filename="sh-utils.html" dir="appendixa"?>
 
&aa-shellutils-down;
&aa-shellutils-desc;
&aa-shellutils-dep;
 
</sect1>
 
/tags/cvs/lfs/appendixa/texinfo-desc.xml
0,0 → 1,36
<sect2><title>Contents of texinfo-&texinfo-contversion;</title>
 
<sect3><title>Program Files</title>
<para>info, install-info, makeinfo, texi2dvi and texindex</para></sect3>
 
<sect3><title>Descriptions</title>
 
<sect4><title>info</title>
<para>The info program reads Info documents, usually contained in the
/usr/share/info directory. Info documents are like man(ual) pages, but
they tend to be more in depth than just explaining the options to a
program.</para></sect4>
 
<sect4><title>install-info</title>
<para>The install-info program updates the info entries. When the info
program is run a list with available topics (ie: available info documents) will
be presented. The install-info program is used to maintain this list of
available topics. If info files are removed manually, it is also necessary
to delete the topic in the index file as well. This program is used for
that. It also works the other way around when info documents are
added.</para></sect4>
 
<sect4><title>makeinfo</title>
<para>The makeinfo program translates Texinfo source documents into various
formats. Available formats are: info files, plain text and HTML.</para></sect4>
 
<sect4><title>texi2dvi</title>
<para>The texi2dvi program prints Texinfo documents</para></sect4>
 
<sect4><title>texindex</title>
<para>The texindex program is used to sort Texinfo index files.</para></sect4>
 
</sect3>
 
</sect2>
 
/tags/cvs/lfs/appendixa/gettext-down.xml
0,0 → 1,6
<sect2>
<title>Official Download Location</title>
 
<para><literallayout>Gettext (&gettext-version;):
<ulink url="ftp://ftp.gnu.org/gnu/gettext/">ftp://ftp.gnu.org/gnu/gettext/</ulink></literallayout></para>
</sect2>
/tags/cvs/lfs/appendixa/bzip2-down.xml
0,0 → 1,6
<sect2>
<title>Official Download Location</title>
 
<para><literallayout>Bzip2 (&bzip2-version;):
<ulink url="ftp://sourceware.cygnus.com/pub/bzip2/">ftp://sourceware.cygnus.com/pub/bzip2/</ulink></literallayout></para>
</sect2>
/tags/cvs/lfs/appendixa/procinfo-desc.xml
0,0 → 1,27
<sect2><title>Contents of procinfo-&procinfo-contversion;</title>
 
<sect3><title>Program Files</title>
<para>lsdev, procinfo and socklist</para></sect3>
 
<sect3><title>Descriptions</title>
 
<sect4><title>lsdev</title>
<para>lsdev gathers information about your computer's installed hardware from
the interrupts, ioports and dma files in the /proc directory, thus giving
you a quick overview of which hardware uses what I/O addresses and what
IRQ and DMA channels.</para></sect4>
 
<sect4><title>procinfo</title>
<para>procinfo gathers some system data from the /proc directory
and prints it nicely formatted on the standard output
device.</para></sect4>
 
<sect4><title>socklist</title>
<para>is a Perl script that gives you a list of all open sockets, enumerating
types, port, inode, uid, pid, fd and the program to which it
belongs.</para></sect4>
 
</sect3>
 
</sect2>
 
/tags/cvs/lfs/appendixa/m4-desc.xml
0,0 → 1,20
<sect2><title>Contents of m4-&m4-contversion;</title>
 
<sect3><title>Program Files</title>
<para>m4</para></sect3>
 
<sect3><title>Descriptions</title>
 
<sect4><title>m4</title>
<para>M4 is a macro processor. It copies input to output expanding macros as it
goes. Macros are either built-in or user-defined and can take any number
of arguments. Besides just doing macro expansion m4 has built-in functions
for including named files, running UNIX commands, doing integer arithmetic,
manipulating text in various ways, recursion, etc. M4 can be used either
as a front-end to a compiler or as a macro processor in its own
right.</para></sect4>
 
</sect3>
 
</sect2>
 
/tags/cvs/lfs/appendixa/gcc.xml
0,0 → 1,10
<sect1 id="aa-gcc">
<title>GCC</title>
<?dbhtml filename="gcc.html" dir="appendixa"?>
 
&aa-gcc-down;
&aa-gcc-desc;
&aa-gcc-dep;
 
</sect1>
 
/tags/cvs/lfs/appendixa/bzip2-dep.xml
0,0 → 1,15
<sect2>
<title>Dependencies</title>
 
<para>Bzip2-&bzip2-depversion; needs the following to be installed:</para>
 
<literallayout>
bash: sh
binutils: ar, as, ld, ranlib
fileutils: cp, ln, rm
gcc: cc1, collect2, cpp0, gcc
make: make
</literallayout>
 
</sect2>
 
/tags/cvs/lfs/appendixa/ncurses-desc.xml
0,0 → 1,83
<sect2><title>Contents</title>
 
<sect3><title>Program Files</title>
<para>captoinfo (link to tic), clear, infocmp, infotocap (link to tic),
reset (link to tset), tack, tic, toe, tput and tset.</para></sect3>
 
<sect3><title>Descriptions</title>
 
<sect4><title>captoinfo</title>
<para>captoinfo converts a termcap description into a terminfo
description.</para></sect4>
 
<sect4><title>clear</title>
<para>clear clears the screen if this is possible. It looks in
the environment for the terminal type and then in the terminfo database
to figure out how to clear the screen.</para></sect4>
 
<sect4><title>infocmp</title>
<para>infocmp can be used to compare a binary terminfo entry with
other terminfo entries, rewrite a terminfo description to
take advantage of the use= terminfo field, or print out a
terminfo description from the binary file (term) in a variety of
formats (the opposite of what tic does).</para></sect4>
 
<sect4><title>infotocap</title>
<para>info to cap converts a terminfo description into a termcap
description.</para></sect4>
 
<sect4><title>reset</title>
<para>reset sets cooked and echo modes, turns off cbreak and raw modes,
turns on new-line translation and resets any unset special characters to
their default values before doing terminal initialization the same way
as tset.</para></sect4>
 
<sect4><title>tack</title>
<para>tack is the terminfo action checker.</para></sect4>
 
<sect4><title>tic</title>
<para>tic is the terminfo entry-description compiler. The program translates a
terminfo file from source format into the binary format for use with the
ncurses library routines. Terminfo files contain information about the
capabilities of a terminal.</para></sect4>
 
<sect4><title>toe</title>
<para>toe lists all available terminal types by primary name with
descriptions.</para></sect4>
 
<sect4><title>tput</title>
<para>tput uses the terminfo database to make the values of
terminal-dependent capabilities and information available to the shell,
to initialize or reset the terminal, or return the long name of the
requested terminal type.</para></sect4>
 
<sect4><title>tset</title>
<para>tset initializes terminals so they can be used, but it's not
widely used anymore. It's provided for 4.4BSD compatibility.</para></sect4>
 
</sect3>
 
<sect3><title>Library Files</title>
<para>libcurses.[a,so] (link to libncurses.[a,so]), libform.[a,so],
libform_g.a, libmenu.[a,so], libmenu_g.a, libncurses++.a,
libncurses.[a,so], libncurses_g.a, libpanel.[a,so] and
libpanel_g.a</para>
 
<sect4><title>libcurses, libncurses++, libncurses, libncurses_g</title>
<para>The libraries that make up the Ncurses library are used to display
text (often in a fancy way) on the screen. An example where ncurses is used
is in the kernel's <quote>make menuconfig</quote> process. The
libncurses libraries are the base of the system.</para></sect4>
 
<sect4><title>libform, libform_g</title>
<para>libform is used to implement forms in ncurses.</para></sect4>
 
<sect4><title>libmenu, libmenu_g</title>
<para>libmenu is used to implement menus in ncurses.</para></sect4>
 
<sect4><title>libpanel, libpanel_g</title>
<para>libpanel is used to implement panels in ncurses.</para></sect4>
 
</sect3>
 
</sect2>
/tags/cvs/lfs/appendixa/patch.xml
0,0 → 1,10
<sect1 id="aa-patch">
<title>Patch</title>
<?dbhtml filename="patch.html" dir="appendixa"?>
 
&aa-patch-down;
&aa-patch-desc;
&aa-patch-dep;
 
</sect1>
 
/tags/cvs/lfs/appendixa/modutils.xml
0,0 → 1,10
<sect1 id="aa-modutils">
<title>Modutils</title>
<?dbhtml filename="modutils.html" dir="appendixa"?>
 
&aa-modutils-down;
&aa-modutils-desc;
&aa-modutils-dep;
 
</sect1>
 
/tags/cvs/lfs/appendixa/manpages-dep.xml
0,0 → 1,14
<sect2>
<title>Dependencies</title>
 
<para>Man-pages-&man-pages-depversion; needs the following to be
installed:</para>
 
<literallayout>
bash: sh
fileutils: install
make: make
</literallayout>
 
</sect2>
 
/tags/cvs/lfs/appendixa/vim-dep.xml
0,0 → 1,22
<sect2>
<title>Dependencies</title>
 
<para>Vim-&vim-depversion; needs the following to be installed:</para>
 
<literallayout>
bash: sh
binutils: as, ld, strip
diffutils: cmp, diff
fileutils: chmod, cp, ln, mkdir, mv, rm, touch
find: find
gcc: cc1, collect2, cpp0, gcc
grep: egrep, grep
make: make
net-tools: hostname
sed: sed
sh-utils: echo, expr, uname, whoami
textutils: cat, tr, wc
</literallayout>
 
</sect2>
 
/tags/cvs/lfs/appendixa/bin86-desc.xml
0,0 → 1,35
<sect2><title>Contents of bin86-&bin86-contversion;</title>
 
<sect3><title>Program Files</title>
<para>as86, as86_encap, ld86, nm86 (link to objdump86), objdump86 and
size86 (link to objdump86)</para></sect3>
 
<sect3><title>Descriptions</title>
 
<sect4><title>as86</title>
<para>as86 is an assembler for the 8086...80386
processors.</para></sect4>
 
<sect4><title>as86_encap</title>
<para>as86_encap is a shell script to call as86 and convert the created binary
into a C file prog.v to be included in or linked with programs like boot
block installers.</para></sect4>
 
<sect4><title>ld86</title>
<para>ld86 understands only the object files produced by the as86 assembler, it
can link them into either an impure or a
separate I&amp;D executable.</para></sect4>
 
<sect4><title>nm86</title>
<para>No description is currently available.</para></sect4>
 
<sect4><title>objdump86</title>
<para>No description is currently available.</para></sect4>
 
<sect4><title>size86</title>
<para>No description is currently available.</para></sect4>
 
</sect3>
 
</sect2>
 
/tags/cvs/lfs/appendixa/groff.xml
0,0 → 1,10
<sect1 id="aa-groff">
<title>Groff</title>
<?dbhtml filename="groff.html" dir="appendixa"?>
 
&aa-groff-down;
&aa-groff-desc;
&aa-groff-dep;
 
</sect1>
 
/tags/cvs/lfs/appendixa/patch-down.xml
0,0 → 1,6
<sect2>
<title>Official Download Location</title>
 
<para><literallayout>Patch (&patch-version;):
<ulink url="ftp://ftp.gnu.org/gnu/patch/">ftp://ftp.gnu.org/gnu/patch/</ulink></literallayout></para>
</sect2>
/tags/cvs/lfs/appendixa/shellutils-desc.xml
0,0 → 1,132
<sect2><title>Contents of sh-utils-&sh-utils-contversion;</title>
 
<sect3><title>Program Files</title>
<para>basename, chroot, date, dirname,
echo, env, expr, factor, false, groups, hostid, hostname, id, logname,
nice, nohup, pathchk, pinky, printenv, printf, pwd, seq, sleep, stty,
su, tee, test, true, tty, uname, uptime, users, who, whoami and
yes</para></sect3>
 
<sect3><title>Descriptions</title>
 
<sect4><title>basename</title>
<para>basename strips directory and suffixes from filenames.</para></sect4>
 
<sect4><title>chroot</title>
<para>chroot runs a command or interactive shell with special
root directory.</para></sect4>
 
<sect4><title>date</title>
<para>date displays the current time in a specified format, or sets
the system date.</para></sect4>
 
<sect4><title>dirname</title>
<para>dirname strips non-directory suffixes from file name.</para></sect4>
 
<sect4><title>echo</title>
<para>echo displays a line of text.</para></sect4>
 
<sect4><title>env</title>
<para>env runs a program in a modified environment.</para></sect4>
 
<sect4><title>expr</title>
<para>expr evaluates expressions.</para></sect4>
 
<sect4><title>factor</title>
<para>factor prints the prime factors of all specified
integer numbers.</para></sect4>
 
<sect4><title>false</title>
<para>false always exits with a status code indicating failure.</para></sect4>
 
<sect4><title>groups</title>
<para>groups prints the groups a user is in.</para></sect4>
 
<sect4><title>hostid</title>
<para>hostid prints the numeric identifier (in hexadecimal) for the current
host.</para></sect4>
 
<sect4><title>hostname</title>
<para>hostname sets or prints the name of the current host system</para></sect4>
 
<sect4><title>id</title>
<para>id prints the real and effective UIDs and GIDs of a user or the current
user.</para></sect4>
 
<sect4><title>logname</title>
<para>logname prints the current user's login name.</para></sect4>
 
<sect4><title>nice</title>
<para>nice runs a program with modified scheduling priority.</para></sect4>
 
<sect4><title>nohup</title>
<para>nohup runs a command immune to hangups, with output to a
non-tty</para></sect4>
 
<sect4><title>pathchk</title>
<para>pathchk checks whether file names are valid or portable.</para></sect4>
 
<sect4><title>pinky</title>
<para>pinky is a lightweight finger utility which retrieves information about
a certain user</para></sect4>
 
<sect4><title>printenv</title>
<para>printenv prints all or part of the environment.</para></sect4>
 
<sect4><title>printf</title>
<para>printf formats and prints data (the same as the printf C
function).</para></sect4>
 
<sect4><title>pwd</title>
<para>pwd prints the name of the current/working directory</para></sect4>
 
<sect4><title>seq</title>
<para>seq prints numbers in a certain range with a certain
increment.</para></sect4>
 
<sect4><title>sleep</title>
<para>sleep delays for a specified amount of time.</para></sect4>
 
<sect4><title>stty</title>
<para>stty changes and prints terminal line settings.</para></sect4>
 
<sect4><title>su</title>
<para>su runs a shell with substitute user and group IDs</para></sect4>
 
<sect4><title>tee</title>
<para>tee reads from standard input and writes to standard output and
files.</para></sect4>
 
<sect4><title>test</title>
<para>test checks file types and compares values.</para></sect4>
 
<sect4><title>true</title>
<para>True always exits with a status code indicating success.</para></sect4>
 
<sect4><title>tty</title>
<para>tty prints the file name of the terminal connected to standard
input.</para></sect4>
 
<sect4><title>uname</title>
<para>uname prints system information.</para></sect4>
 
<sect4><title>uptime</title>
<para>uptime tells how long the system has been running.</para></sect4>
 
<sect4><title>users</title>
<para>users prints the user names of users currently logged in to the
current host.</para></sect4>
 
<sect4><title>who</title>
<para>who shows who is logged on.</para></sect4>
 
<sect4><title>whoami</title>
<para>whoami prints the user's effective userid.</para></sect4>
 
<sect4><title>yes</title>
<para>yes outputs a string repeatedly until killed.</para></sect4>
 
</sect3>
 
</sect2>
 
/tags/cvs/lfs/appendixa/lilo-dep.xml
0,0 → 1,18
<sect2>
<title>Dependencies</title>
 
<para>Lilo-&lilo-depversion; needs the following to be installed:</para>
 
<literallayout>
bash: sh
bin86: as86, ld86
binutils: as, ld, strip
fileutils: cp, dd, ln
gcc: cc, cc1, collect2, cpp0
make: make
sed: sed
textutils: cat
</literallayout>
 
</sect2>
 
/tags/cvs/lfs/appendixa/manpages-desc.xml
0,0 → 1,17
<sect2><title>Contents of manpages-&man-pages-contversion;</title>
 
<sect3><title>Support Files</title>
<para>various manual pages that don't come with the
packages.</para></sect3>
 
<sect3><title>Descriptions</title>
 
<sect4><title>manual pages</title>
<para>Examples of provided manual pages are the manual pages describing all
the C and C++ functions, a few important /dev/ files and
more.</para></sect4>
 
</sect3>
 
</sect2>
 
/tags/cvs/lfs/appendixa/nettools.xml
0,0 → 1,10
<sect1 id="aa-ns-nettools">
<title>Net-tools</title>
<?dbhtml filename="net-tools.html" dir="appendixa"?>
 
&aa-nettools-down;
&aa-nettools-desc;
&aa-nettools-dep;
 
</sect1>
 
/tags/cvs/lfs/appendixa/vim-desc.xml
0,0 → 1,43
<sect2><title>Contents</title>
 
<sect3><title>Program Files</title>
<para>ex (link to vim), rview (link to vim), rvim (link to vim), vi
(link to vim), view (link to vim), vim, vimdiff (link to vim), vimtutor
(link to vim) and xxd</para></sect3>
 
<sect3><title>Descriptions</title>
 
<sect4><title>ex</title>
<para>ex starts vim in Ex mode.</para></sect4>
 
<sect4><title>rview</title>
<para>rview is a restricted version of view. No shell commands can be started
and Vim can't be suspended.</para></sect4>
 
<sect4><title>rvim</title>
<para>rvim is the restricted version of vim. No shell commands can be started
and Vim can't be suspended.</para></sect4>
 
<sect4><title>vi</title>
<para>vi starst vim in vi-compatible mode.</para></sect4>
 
<sect4><title>view</title>
<para>view starts vim in read-only mode.</para></sect4>
 
<sect4><title>vim</title>
<para>vim starts vim in the normal, default way.</para></sect4>
 
<sect4><title>vimdiff</title>
<para>vimdiff edits two or three versions of a file with Vim and show
differences.</para></sect4>
 
<sect4><title>vimtutor</title>
<para>vimtutor starts the Vim tutor.</para></sect4>
 
<sect4><title>xxd</title>
<para>xxd makes a hexdump or does the reverse.</para></sect4>
 
</sect3>
 
</sect2>
 
/tags/cvs/lfs/appendixa/flex-desc.xml
0,0 → 1,39
<sect2><title>Contents of flex-&flex-contversion;</title>
 
<sect3><title>Program Files</title>
<para>flex, flex++ (link to flex) and lex</para></sect3>
 
<sect3><title>Descriptions</title>
 
<sect4><title>flex</title>
<para>flex is a tool for generating programs which recognize
patterns in text. Pattern recognition is very useful in many applications.
A user sets up rules
what to look for and flex will make a program that looks for those
patterns. The reason people use flex is that it is much easier to sets up
rules for what to look for than to write the actual program that finds
the text.</para></sect4>
 
<sect4><title>flex++</title>
<para>flex++ invokes a version of flex which is used exclusively for
C++ scanners.</para></sect4>
 
<sect4><title>lex</title>
<para>We create a yacc script which calls flex using the -l option.
This is for compatibility purposes for programs which use lex instead
of flex.</para></sect4>
 
</sect3>
 
<sect3><title>Library Files</title>
<para>libfl.a</para></sect3>
 
<sect3><title>Descriptions</title>
 
<sect4><title>libfl</title>
<para>No description is currently available.</para></sect4>
 
</sect3>
 
</sect2>
 
/tags/cvs/lfs/appendixa/psmisc-desc.xml
0,0 → 1,29
<sect2><title>Contents of psmisc-&psmisc-contversion;</title>
 
<sect3><title>Program Files</title>
<para>fuser, killall, pidof (link to killall) and pstree</para>
 
<para>Note that in LFS we don't install the pidof link by default
because we use pidof from sysvinit instead.</para></sect3>
 
<sect3><title>Descriptions</title>
 
<sect4><title>fuser</title>
<para>fuser displays the PIDs of processes using the specified files or file
systems.</para></sect4>
 
<sect4><title>killall</title>
<para>killall sends a signal to all processes running any of the specified
commands.</para></sect4>
 
<sect4><title>pidof</title>
<para>Pidof finds the process id's (pids) of the named programs and
prints those id's on standard output.</para></sect4>
 
<sect4><title>pstree</title>
<para>pstree shows running processes as a tree.</para></sect4>
 
</sect3>
 
</sect2>
 
/tags/cvs/lfs/appendixa/procps-down.xml
0,0 → 1,6
<sect2>
<title>Official Download Location</title>
 
<para><literallayout>Procps (&procps-version;):
<ulink url="ftp://people.redhat.com/johnsonm/procps/">ftp://people.redhat.com/johnsonm/procps/</ulink></literallayout></para>
</sect2>
/tags/cvs/lfs/appendixa/modutils-desc.xml
0,0 → 1,53
<sect2><title>Contents of modutils-&modutils-contversion;</title>
 
<sect3><title>Program Files</title>
<para>depmod, genksyms, insmod, insmod_ksymoops_clean, kallsyms (link to
insmod), kernelversion, ksyms, lsmod (link to insmod),
modinfo, modprobe (link to insmod) and rmmod</para></sect3>
 
<sect3><title>Descriptions</title>
 
<sect4><title>depmod</title>
<para>depmod handles dependency descriptions for loadable
kernel modules.</para></sect4>
 
<sect4><title>genksyms</title>
<para>genksyms reads (on standard input) the output from gcc -E source.c
and generates a file containing version information.</para></sect4>
 
<sect4><title>insmod</title>
<para>insmod installs a loadable module in the running kernel.</para></sect4>
 
<sect4><title>insmod_ksymoops_clean</title>
<para>insmod_ksymoops_clean deletes saved ksyms and modules not accessed in
2 days.</para></sect4>
 
<sect4><title>kallsyms</title>
<para>kallsyms extracts all kernel symbols for debugging.</para></sect4>
 
<sect4><title>kernelversion</title>
<para>kernelversion reports the major version of the
running kernel.</para></sect4>
 
<sect4><title>ksyms</title>
<para>ksyms displays exported kernel symbols.</para></sect4>
 
<sect4><title>lsmod</title>
<para>lsmod shows information about all loaded modules.</para></sect4>
 
<sect4><title>modinfo</title>
<para>modinfo examines an object file associated with a kernel module and
displays any information that it can glean.</para></sect4>
 
<sect4><title>modprobe</title>
<para>Modprobe uses a Makefile-like dependency file, created by depmod,
to automatically load the relevant module(s) from the set of modules
available in predefined directory trees.</para></sect4>
 
<sect4><title>rmmod</title>
<para>rmmod unloads loadable modules from the running kernel.</para></sect4>
 
</sect3>
 
</sect2>
 
/tags/cvs/lfs/appendixa/procps-dep.xml
0,0 → 1,20
<sect2>
<title>Dependencies</title>
 
<para>Procps-&procps-depversion; needs the following to be installed:</para>
 
<literallayout>
bash: sh
binutils: as, ld, strip
fileutils: install, ln, mv, rm
gcc: cc1, collect2, cpp0, gcc
grep: grep
make: make
mawk: awk
sed: sed
sh-utils: basename, pwd
textutils: sort, tr
</literallayout>
 
</sect2>
 
/tags/cvs/lfs/appendixa/nettools-down.xml
0,0 → 1,6
<sect2>
<title>Official Download Location</title>
 
<para><literallayout>Net-tools (&net-tools-version;):
<ulink url="http://www.tazenda.demon.co.uk/phil/net-tools/">http://www.tazenda.demon.co.uk/phil/net-tools/</ulink></literallayout></para>
</sect2>
/tags/cvs/lfs/appendixa/gzip-dep.xml
0,0 → 1,19
<sect2>
<title>Dependencies</title>
 
<para>Gzip-&gzip-depversion; needs the following to be installed:</para>
 
<literallayout>
bash: sh
binutils: as, ld, nm
fileutils: chmod, cp, install, ln, mv, rm
gcc: cc1, collect2, cpp, cpp0, gcc
grep: egrep, grep
make: make
sed: sed
sh-utils: hostname
textutils: cat, tr
</literallayout>
 
</sect2>
 
/tags/cvs/lfs/appendixa/introduction.xml
0,0 → 1,56
<sect1 id="aa-intro">
<title>Introduction</title>
<?dbhtml filename="introduction.html" dir="appendixa"?>
 
<para>This appendix describes the following aspects of every package
that is installed in this book:</para>
 
<itemizedlist>
 
<listitem><para>The official download location for the
package.</para></listitem>
 
<listitem><para>What the package contains.</para></listitem>
 
<listitem><para>What each program from a package does.</para></listitem>
 
<listitem><para>What each package needs to compile.</para></listitem>
 
</itemizedlist>
 
<para>Most information about these packages (especially the descriptions of
them) come from the man pages from those packages. We are not going to print
the entire man page, just the core elements to make it possible to
understand what a program does. To get knowledge of all details on a program,
we suggest you start by reading the complete man page in addition to
this appendix.</para>
 
<para>Certain packages are documented in more depth
than others, because we just happen to know more about certain
packages than I know about others. If anything should be added to the
following descriptions, please don't hesitate to email the mailing
lists. We intend that the list should contain an in-depth description
of every package installed, but we can't do it without help.</para>
 
<para>Please note that currently only what a package does is described and not
why it needs to be installed. This may be added later.</para>
 
<para>Also listed are all of the installation dependencies for all the
packages that are installed in this book. The listings will include
which programs from which packages are needed to successfully compile
the package to be installed.</para>
 
<para>These are not running dependencies, meaning they don't tell you
what programs are needed to use that packages programs. Just the ones
needed to compile it.</para>
 
<para>The dependency list can be, from time to time, outdated in regards
to the current used package version. Checking dependencies takes quite a
bit of work, so they may lag behind a bit on the package update. But
often with minor package updates, the installation dependencies hardly
change, so they'll be current in most cases. If we upgrade to a major
new release, we'll make sure the dependencies are checked too at the
same time.</para>
 
</sect1>
 
/tags/cvs/lfs/appendixa/makedev-down.xml
0,0 → 1,7
<sect2>
<title>Official Download Location</title>
 
<para><literallayout>MAKEDEV (&makedev-version;):
<ulink url="&ftp;/">&ftp;/</ulink>
<ulink url="&http;/">&http;/</ulink></literallayout></para>
</sect2>
/tags/cvs/lfs/appendixa/make-down.xml
0,0 → 1,6
<sect2>
<title>Official Download Location</title>
 
<para><literallayout>Make (&make-version;):
<ulink url="ftp://ftp.gnu.org/gnu/make/">ftp://ftp.gnu.org/gnu/make/</ulink></literallayout></para>
</sect2>
/tags/cvs/lfs/appendixa/bash-dep.xml
0,0 → 1,22
<sect2>
<title>Dependencies</title>
 
<para>Bash-&bash-depversion; needs the following to be installed:</para>
 
<literallayout>
bash: bash, sh
binutils: ar, as, ld, ranlib, size
diffutils: cmp
fileutils: chmod, cp, install, ln, ls, mkdir, mv, rm
gcc: cc, cc1, collect2, cpp0, gcc
grep: egrep, grep
make: make
mawk: awk
sed: sed
sh-utils: basename, echo, expr, hostname, sleep, uname
texinfo: install-info
textutils: cat, tr, uniq
</literallayout>
 
</sect2>
 
/tags/cvs/lfs/appendixa/kernel-down.xml
0,0 → 1,6
<sect2>
<title>Official Download Location</title>
 
<para><literallayout>Linux Kernel (&kernel-version;):
<ulink url="ftp://ftp.kernel.org/pub/linux/kernel/">ftp://ftp.kernel.org/pub/linux/kernel/</ulink></literallayout></para>
</sect2>
/tags/cvs/lfs/appendixa/tar.xml
0,0 → 1,10
<sect1 id="aa-tar">
<title>Tar</title>
<?dbhtml filename="tar.html" dir="appendixa"?>
 
&aa-tar-down;
&aa-tar-desc;
&aa-tar-dep;
 
</sect1>
 
/tags/cvs/lfs/appendixa/e2fsprogs-desc.xml
0,0 → 1,109
<sect2><title>Contents of e2fsprogs-&e2fsprogs-contversion;</title>
 
<sect3><title>Program Files</title>
 
<para>badblocks, chattr, compile_et, debugfs, dumpe2fs, e2fsck,
e2image, e2label, fsck, fsck.ext2, fsck.ext3, lsattr, mk_cmds, mke2fs,
mkfs.ext2, mklost+found, resize2fs, tune2fs and uuidgen</para></sect3>
 
<sect3><title>Descriptions</title>
 
<sect4><title>badblocks</title>
<para>badblocks is used to search for bad blocks on a device (usually a disk
partition).</para></sect4>
 
<sect4><title>chattr</title>
<para>chattr changes the file attributes on a Linux second extended file
system. </para></sect4>
 
<sect4><title>compile_et</title>
<para>compile_et is used to convert a table listing error-code names
and associated messages into a C source file suitable for use with the
com_err library</para></sect4>
 
<sect4><title>debugfs</title>
<para>The debugfs program is a file system debugger. It can be used to examine
and change the state of an ext2 file system.</para></sect4>
 
<sect4><title>dumpe2fs</title>
<para>dumpe2fs prints the super block and blocks group information for the
filesystem present on a specified device.</para></sect4>
 
<sect4><title>e2fsck and fsck.ext2</title>
<para>e2fsck is used to check and optionally repair Linux second
extended filesystems. fsck.ext2 does the same as e2fsck.</para></sect4>
 
<sect4><title>e2image</title>
<para>e2image is used to save critical ext2 filesystem data to
a file</para></sect4>
 
<sect4><title>e2label</title>
<para>e2label will display or change the filesystem label on the ext2
filesystem located on the specified device.</para></sect4>
 
<sect4><title>fsck</title>
<para>fsck is used to check and optionally repair a Linux
file system.</para></sect4>
 
<sect4><title>fsck.ext3</title>
<para>fsck.ext3 is used to check and optionally repair a Linux ext3
filesystems</para></sect4>
 
<sect4><title>lsattr</title>
<para>lsattr lists the file attributes on a second extended
file system.</para></sect4>
 
<sect4><title>mk_cmds</title>
<para>No description is currently available.</para></sect4>
 
<sect4><title>mke2fs and mkfs.ext2</title>
<para>mke2fs is used to create a Linux second extended file system on a device
(usually a disk partition). mkfs.ext2 does the same as mke2fs.</para></sect4>
 
<sect4><title>mklost+found</title>
<para>mklost+found is used to create a lost+found directory in the current
working directory on a Linux second extended file system. mklost+found
pre-allocates disk blocks to the directory to make it
usable by e2fsck.</para></sect4>
 
<sect4><title>resize2fs</title>
<para>resize2fs is used to resize ext2 file systems.</para></sect4>
 
<sect4><title>tune2fs</title>
<para>tune2fs adjusts tunable filesystem parameters on a Linux second extended
filesystem.</para></sect4>
 
<sect4><title>uuidgen</title>
<para>The uuidgen program creates a new universally unique identifier (UUID)
using the libuuid library. The new UUID can reasonably be considered unique
among all UUIDs created on the local system, and among UUIDs created on other
systems in the past and in the future.</para></sect4>
 
</sect3>
 
<sect3><title>Library Files</title>
 
<para>libcom_err.[a,so], libe2p.[a,so], libext2fs.[a,so], libss.[a,so],
libuuid.[a,so]</para></sect3>
 
<sect3><title>Descriptions</title>
 
<sect4><title>libcom_err</title>
<para>No description is currently available.</para></sect4>
 
<sect4><title>libe2p</title>
<para>No description is currently available.</para></sect4>
 
<sect4><title>libext2fs</title>
<para>No description is currently available.</para></sect4>
 
<sect4><title>libss</title>
<para>No description is currently available.</para></sect4>
 
<sect4><title>libuuid</title>
<para>No description is currently available.</para></sect4>
 
</sect3>
 
</sect2>
 
/tags/cvs/lfs/appendixa/bison-desc.xml
0,0 → 1,57
<sect2>
<title>Contents of bison-&bison-contversion;</title>
 
<sect3><title>Program Files</title>
 
<para>bison and yacc</para></sect3>
 
<sect3><title>Descriptions</title>
 
<sect4><title>bison</title>
 
<para>Bison is a parser generator, a replacement for YACC. YACC stands for Yet
Another Compiler Compiler. What is Bison then? It is a program that
generates a program that analyzes the structure of a text file. Instead of
writing the actual program a user specifies how things should be connected
and with those rules a program is constructed that analyzes the
text file. There are a lot of examples where structure is needed and
one of them is the calculator.</para>
 
<para>Given the string :</para>
 
<blockquote><literallayout> 1 + 2 * 3</literallayout></blockquote>
 
<para>A human can easily come to the result 7. Why? Because of the structure.
Our brain knows
how to interpret the string. The computer doesn't know that and Bison
is a
tool to help it understand by presenting the string in the following way
to the compiler:</para>
 
<blockquote><literallayout> +
/ \
* 1
/ \
2 3</literallayout></blockquote>
 
<para>Starting at the bottom of a tree and coming across the numbers 2 and
3 which are joined by the multiplication symbol, the computer
multiplies 2 and 3. The result of that multiplication is remembered and
the next thing that the computer sees is the result of 2*3 and the
number 1 which are joined by the add symbol. Adding 1 to the previous
result makes 7. In calculating the most complex calculations can be
broken down in this tree format and the computer just starts at the
bottom and works its way up to the top and comes with the correct
answer. Of course, Bison isn't only used for calculators
alone.</para></sect4>
 
<sect4><title>yacc</title>
 
<para>We create a yacc script which calls bison using the -y option.
This is for compatibility purposes for programs which use yacc instead
of bison.</para></sect4>
 
</sect3>
 
</sect2>
 
/tags/cvs/lfs/appendixa/ncurses-dep.xml
0,0 → 1,22
<sect2>
<title>Dependencies</title>
 
<para>Ncurses-&ncurses-depversion; needs the following to be installed:</para>
 
<literallayout>
bash: sh
binutils: ar, as, ld, ranlib
diffutils: cmp
fileutils: chmod, cp, install, ln, mkdir, mv, rm
gcc: c++, cc1, cc1plus, collect2, cpp0, gcc
glibc: ldconfig
grep: egrep, fgrep, grep
make: make
mawk: mawk
sed: sed
sh-utils: basename, date, echo, expr, hostname, uname
textutils: cat, sort, tr, wc
</literallayout>
 
</sect2>
 
/tags/cvs/lfs/appendixa/ed.xml
0,0 → 1,10
<sect1 id="aa-ed">
<title>Ed</title>
<?dbhtml filename="ed.html" dir="appendixa"?>
 
&aa-ed-down;
&aa-ed-desc;
&aa-ed-dep;
 
</sect1>
 
/tags/cvs/lfs/appendixa/autoconf-desc.xml
0,0 → 1,50
<sect2><title>Contents of autoconf-&autoconf-contversion;</title>
 
<sect3><title>Program Files</title>
<para>autoconf, autoheader, autoreconf, autoscan, autoupdate and
ifnames</para></sect3>
 
<sect3><title>Descriptions</title>
 
<sect4><title>autoconf</title>
<para>Autoconf is a tool for producing shell scripts that automatically
configure software source code packages to adapt to many kinds of
UNIX-like systems. The configuration scripts produced by Autoconf are
independent of Autoconf when they are run, so their users do not need to
have Autoconf.</para></sect4>
 
<sect4><title>autoheader</title>
<para>The autoheader program can create a template file of C #define
statements for configure to use</para></sect4>
 
<sect4><title>autoreconf</title>
<para>If there are a lot of Autoconf-generated configure scripts, the
autoreconf program can save some work. It runs autoconf (and
autoheader, where appropriate) repeatedly to remake the Autoconf
configure scripts and configuration header templates in the directory
tree rooted at the current directory.</para></sect4>
 
<sect4><title>autoscan</title>
<para>The autoscan program can help to create a configure.in file for
a software package. autoscan examines source files in the directory
tree rooted at a directory given as a command line argument, or the
current directory if none is given. It searches the source files for
common portability problems and creates a file configure.scan which
is a preliminary configure.in for that package.</para></sect4>
 
<sect4><title>autoupdate</title>
<para>The autoupdate program updates a configure.in file that calls
Autoconf macros by their old names to use the current
macro names.</para></sect4>
 
<sect4><title>ifnames</title>
<para>ifnames can help when writing a configure.in for a software
package. It prints the identifiers that the package already uses in C
preprocessor conditionals. If a package has already been set up to
have some portability, this program can help to figure out what its
configure needs to check for. It may help fill in some gaps in a
configure.in generated by autoscan.</para></sect4>
 
</sect3>
 
</sect2>
/tags/cvs/lfs/appendixa/vim.xml
0,0 → 1,10
<sect1 id="aa-vim">
<title>Vim</title>
<?dbhtml filename="vim.html" dir="appendixa"?>
 
&aa-vim-down;
&aa-vim-desc;
&aa-vim-dep;
 
</sect1>
 
/tags/cvs/lfs/appendixa/manpages.xml
0,0 → 1,10
<sect1 id="aa-man-pages">
<title>Man-pages</title>
<?dbhtml filename="man-pages.html" dir="appendixa"?>
 
&aa-manpages-down;
&aa-manpages-desc;
&aa-manpages-dep;
 
</sect1>
 
/tags/cvs/lfs/appendixa/sysvinit-down.xml
0,0 → 1,6
<sect2>
<title>Official Download Location</title>
 
<para><literallayout>Sysvinit (&sysvinit-version;):
<ulink url="ftp://ftp.cistron.nl/pub/people/miquels/sysvinit/">ftp://ftp.cistron.nl/pub/people/miquels/sysvinit/</ulink></literallayout></para>
</sect2>
/tags/cvs/lfs/appendixa/reiserfs-desc.xml
0,0 → 1,30
<sect2><title>Contents of reiserfsprogs-&reiserfs-contversion;</title>
 
<sect3><title>Program Files</title>
<para>debugreiserfs, mkreiserfs, reiserfsck, resize_reiserfs and
unpack</para></sect3>
 
<sect3><title>Descriptions</title>
 
<sect4><title>debugreiserfs</title>
<para>debugreiserfs can sometimes help to solve problems with reiserfs
filesystems. If it is called without options it prints the super block
of any reiserfs filesystem found on the device.</para></sect4>
 
<sect4><title>mkreiserfs</title>
<para>mkreiserfs creates a reiserfs file system.</para></sect4>
 
<sect4><title>reiserfsck</title>
<para>reiserfsck checks a reiserfs file system.</para></sect4>
 
<sect4><title>resize_reiserfs</title>
<para>resize_reiserfs is used to resize an unmounted reiserfs file
system</para></sect4>
 
<sect4><title>unpack</title>
<para>No description is currently available.</para></sect4>
 
</sect3>
 
</sect2>
 
/tags/cvs/lfs/appendixa/netkitbase-down.xml
0,0 → 1,6
<sect2>
<title>Official Download Location</title>
 
<para><literallayout>Netkit-base (&netkit-base-version;):
<ulink url="ftp://ftp.uk.linux.org/pub/linux/Networking/netkit/">ftp://ftp.uk.linux.org/pub/linux/Networking/netkit/</ulink></literallayout></para>
</sect2>
/tags/cvs/lfs/appendixa/diffutils-down.xml
0,0 → 1,6
<sect2>
<title>Official Download Location</title>
 
<para><literallayout>Diff Utils (&diffutils-version;):
<ulink url="ftp://ftp.gnu.org/gnu/diffutils/">ftp://ftp.gnu.org/gnu/diffutils/</ulink></literallayout></para>
</sect2>
/tags/cvs/lfs/appendixa/lilo.xml
0,0 → 1,10
<sect1 id="aa-lilo">
<title>Lilo</title>
<?dbhtml filename="lilo.html" dir="appendixa"?>
 
&aa-lilo-down;
&aa-lilo-desc;
&aa-lilo-dep;
 
</sect1>
 
/tags/cvs/lfs/appendixa/gcc-down.xml
0,0 → 1,10
<sect2>
<title>Official Download Location</title>
 
<para><literallayout>GCC (&gcc-version;):
<ulink url="ftp://ftp.gnu.org/pub/gnu/gcc/">ftp://ftp.gnu.org/pub/gnu/gcc/</ulink>
 
GCC Patch (&gcc-patch-version;):
<ulink url="&ftp;/">&ftp;/</ulink>
<ulink url="&http;/">&http;/</ulink></literallayout></para>
</sect2>
/tags/cvs/lfs/appendixa/utillinux-down.xml
0,0 → 1,6
<sect2>
<title>Official Download Location</title>
 
<para><literallayout>Util Linux (&util-linux-version;):
<ulink url="ftp://ftp.win.tue.nl/pub/linux-local/utils/util-linux/">ftp://ftp.win.tue.nl/pub/linux-local/utils/util-linux/</ulink></literallayout></para>
</sect2>
/tags/cvs/lfs/appendixa/ed-desc.xml
0,0 → 1,19
<sect2><title>Contents of ed-&ed-contversion;</title>
 
<sect3><title>Program Files</title>
<para>ed and red (link to ed)</para></sect3>
 
<sect3><title>Description</title>
 
<sect4><title>ed</title>
<para>Ed is a line-oriented text editor. It is used to create, display,
modify and otherwise manipulate text files.</para></sect4>
 
<sect4><title>red</title>
<para>red is a restricted ed: it can only edit files in the current
directory and cannot execute shell commands.</para></sect4>
 
</sect3>
 
</sect2>
 
/tags/cvs/lfs/appendixa/lilo-down.xml
0,0 → 1,8
<sect2>
<title>Official Download Location</title>
 
<para><literallayout>Lilo (&lilo-version;):
<ulink url="ftp://ibiblio.org/pub/Linux/system/boot/lilo/">ftp://ibiblio.org/pub/Linux/system/boot/lilo/</ulink>
<ulink
url="http://ibiblio.org/pub/Linux/system/boot/lilo/">http://ibiblio.org/pub/Linux/system/boot/lilo/</ulink></literallayout></para>
</sect2>
/tags/cvs/lfs/appendixa/shadowpwd-dep.xml
0,0 → 1,28
<sect2>
<title>Dependencies</title>
 
<para>Shadow-&shadow-depversion; needs the following to be installed:</para>
 
<literallayout>
autoconf: autoconf, autoheader
automake: aclocal, automake
bash: sh
binutils: ar, as, ld, nm, ranlib
diffutils: cmp
fileutils: chmod, cp, install, ln, ls, mkdir, mv, rm, rmdir
gettext: msgfmt, xgettext
gcc: cc1, collect2, cpp0, gcc
glibc: ldconfig
grep: egrep, grep
m4: m4
make: make
mawk: mawk
net-tools: hostname
sed: sed
sh-utils: basename, echo, expr, sleep, uname
texinfo: makeinfo
textutils: cat, sort, tr, uniq
</literallayout>
 
</sect2>
 
/tags/cvs/lfs/appendixa/automake.xml
0,0 → 1,10
<sect1 id="aa-automake">
<title>Automake</title>
<?dbhtml filename="automake.html" dir="appendixa"?>
 
&aa-automake-down;
&aa-automake-desc;
&aa-automake-dep;
 
</sect1>
 
/tags/cvs/lfs/appendixa/gzip.xml
0,0 → 1,10
<sect1 id="aa-gzip">
<title>Gzip</title>
<?dbhtml filename="gzip.html" dir="appendixa"?>
 
&aa-gzip-down;
&aa-gzip-desc;
&aa-gzip-dep;
 
</sect1>
 
/tags/cvs/lfs/appendixa/bash.xml
0,0 → 1,10
<sect1 id="aa-bash">
<title>Bash</title>
<?dbhtml filename="bash.html" dir="appendixa"?>
 
&aa-bash-down;
&aa-bash-desc;
&aa-bash-dep;
 
</sect1>
 
/tags/cvs/lfs/appendixa/perl-desc.xml
0,0 → 1,87
<sect2><title>Contents of perl-&perl-contversion;</title>
 
<sect3><title>Program Files</title>
<para>a2p, c2ph, dprofpp, find2perl, h2ph, h2xs, perl, perl5.6.1,
perlbug, perlcc, perldoc, pl2pm, pod2html, pod2latex, pod2man, pod2text,
pod2usage, podchecker, podselect, pstruct, s2p and splain</para></sect3>
 
<sect3><title>Descriptions</title>
 
<sect4><title>a2p</title>
<para>a2p is an awk to perl translator.</para></sect4>
 
<sect4><title>c2ph</title>
<para>c2ph dumps C structures as generated from "cc -g -S" stabs.</para></sect4>
 
<sect4><title>dprofpp</title>
<para>dprofpp displays perl profile data.</para></sect4>
 
<sect4><title>find2perl</title>
<para>find2perl translates find command lines to Perl code.</para></sect4>
 
<sect4><title>h2ph</title>
<para>h2ph converts .h C header files to .ph Perl header files.</para></sect4>
 
<sect4><title>h2xs</title>
<para>h2xs converts .h C header files to Perl extensions.</para></sect4>
 
<sect4><title>perl, perl5.6.1</title>
<para>perl is the Practical Extraction and Report Language. It combines
some of the best features of C, sed, awk, and sh into one powerful
language.</para></sect4>
 
<sect4><title>perlbug</title>
<para>perlbug helps to generate bug reports about perl or the
modules that come with it, and mail them.</para></sect4>
 
<sect4><title>perlcc</title>
<para>perlcc generates executables from Perl programs.</para></sect4>
 
<sect4><title>perldoc</title>
<para>perldoc looks up a piece of documentation in .pod format that is
embedded in the perl installation tree or in a perl script, and displays it
via "pod2man | nroff -man | $PAGER".</para></sect4>
 
<sect4><title>pl2pm</title>
<para>pl2pm is a tool to aid in the conversion of Perl4-style .pl library
files to Perl5-style library modules.</para></sect4>
 
<sect4><title>pod2html</title>
<para>pod2html converts files from pod format to HTML format.</para></sect4>
 
<sect4><title>pod2latex</title>
<para>pod2latex converts files from pod format to LaTeX format.</para></sect4>
 
<sect4><title>pod2man</title>
<para>pod2man converts pod data to formatted *roff input.</para></sect4>
 
<sect4><title>pod2text</title>
<para>pod2text converts pod data to formatted ASCII text.</para></sect4>
 
<sect4><title>pod2usage</title>
<para>pos2usage prints usage messages from embedded pod docs in
files.</para></sect4>
 
<sect4><title>podchecker</title>
<para>podchecker checks the syntax of pod format documentation
files.</para></sect4>
 
<sect4><title>podselect</title>
<para>podselect prints selected sections of pod documentation on
standard output.</para></sect4>
 
<sect4><title>pstruct</title>
<para>pstruct dumps C structures as generated from "cc -g -S"
stabs.</para></sect4>
 
<sect4><title>s2p</title>
<para>s2p is a sed to perl translator.</para></sect4>
 
<sect4><title>splain</title>
<para>splain is a program to force verbose warning diagnostics
in perl.</para></sect4>
 
</sect3>
 
</sect2>
 
/tags/cvs/lfs/appendixa/e2fsprogs-dep.xml
0,0 → 1,25
<sect2>
<title>Dependencies</title>
 
<para>E2fsprogs-&e2fsprogs-depversion; needs the following to be
installed:</para>
 
<literallayout>
bash: sh
binutils: ar, as, ld, ranlib, strip
diffutils: cmp
fileutils: chmod, cp, install, ln, mkdir, mv, rm, sync
gcc: cc, cc1, collect2, cpp0
glibc: ldconfig
grep: egrep, grep
gzip: gzip
make: make
mawk: awk
sed: sed
sh-utils: basename, echo, expr, hostname, uname
texinfo: makeinfo
textutils: cat, tr
</literallayout>
 
</sect2>
 
/tags/cvs/lfs/appendixa/bison-dep.xml
0,0 → 1,21
<sect2>
<title>Dependencies</title>
 
<para>Bison-&bison-depversion; needs the following to be installed:</para>
 
<literallayout>
bash: sh
binutils: ar, as, ld, ranlib
diffutils: cmp
fileutils: chmod, cp, install, ln, ls, mkdir, mv, rm, rmdir
gcc: cc, cc1, collect2, cpp0, gcc
grep: egrep, fgrep, grep
make: make
sed: sed
sh-utils: basename, dirname, echo, expr, hostname, sleep, uname
texinfo: install-info
textutils: cat, head, tr, uniq
</literallayout>
 
</sect2>
 
/tags/cvs/lfs/appendixa/glibc.xml
0,0 → 1,10
<sect1 id="aa-glibc">
<title>Glibc</title>
<?dbhtml filename="glibc.html" dir="appendixa"?>
 
&aa-glibc-down;
&aa-glibc-desc;
&aa-glibc-dep;
 
</sect1>
 
/tags/cvs/lfs/appendixa/make-dep.xml
0,0 → 1,26
<sect2>
<title>Dependencies</title>
 
<para>Make-&make-depversion; needs the following to be installed:</para>
 
<literallayout>
autoconf: autoconf, autoheader
automake: aclocal, automake
bash: sh
binutils: as, ld
diffutils: cmp
fileutils: chgrp, chmod, install, ls, mv, rm
gcc: cc, cc1, collect2, cpp0, gcc
glibc: getconf
grep: egrep, fgrep, grep
m4: m4
make: make
mawk: mawk
sed: sed
sh-utils: basename, echo, expr, hostname, sleep, uname
texinfo: install-info, makeinfo
textutils: cat, tr
</literallayout>
 
</sect2>
 
/tags/cvs/lfs/appendixa/bin86.xml
0,0 → 1,10
<sect1 id="aa-bin86">
<title>Bin86</title>
<?dbhtml filename="bin86.html" dir="appendixa"?>
 
&aa-bin86-down;
&aa-bin86-desc;
&aa-bin86-dep;
 
</sect1>
 
/tags/cvs/lfs/appendixa/reiserfs-dep.xml
0,0 → 1,26
<sect2>
<title>Dependencies</title>
 
<para>Reiserfs-&reiserfs-depversion; needs the following to be
installed:</para>
 
<literallayout>
autoconf: autoconf, autoheader
automake: aclocal, automake
bash: sh
binutils: ar, as, ld, ranlib
diffutils: cmp
fileutils: chmod, install, ls, rm
gcc: cc1, collect2, cpp0, gcc
grep: egrep, grep
m4: m4
make: make
mawk: mawk
sed: sed
sh-utils: echo, expr, hostname, sleep
texinfo: makeinfo
textutils: cat, tr
</literallayout>
 
</sect2>
 
/tags/cvs/lfs/appendixa/gettext-dep.xml
0,0 → 1,26
<sect2>
<title>Dependencies</title>
 
<para>Gettext-&gettext-depversion; needs the following to be installed:</para>
 
<literallayout>
autoconf: autoconf, autoheader
automake: aclocal, automake
bash: sh
binutils: ar, as, ld, nm, ranlib, strip
bison: bison
diffutils: cmp
fileutils: chmod, install, ln, ls, mkdir, mv, rm, rmdir
gcc: cc, cc1, collect2, cpp0, gcc
grep: egrep, fgrep, grep
m4: m4
make: make
mawk: mawk
sed: sed
sh-utils: basename, echo, expr, hostname, sleep, uname
texinfo: install-info, makeinfo
textutils: cat, sort, tr, uniq
</literallayout>
 
</sect2>
 
/tags/cvs/lfs/appendixa/file-desc.xml
0,0 → 1,17
<sect2><title>Contents of file-&file-contversion;</title>
 
<sect3><title>Program Files</title>
<para>file</para></sect3>
 
<sect3><title>Descriptions</title>
 
<sect4><title>file</title>
<para>File tests each specified file in an attempt to classify it. There are
three sets of tests, performed in this order: filesystem tests,
magic number tests, and language tests. The first test that succeeds
causes the file type to be printed.</para></sect4>
 
</sect3>
 
</sect2>
 
/tags/cvs/lfs/appendixa/glibc-desc.xml
0,0 → 1,202
<sect2><title>Contents of glibc-&glibc-contversion;</title>
 
<sect3><title>Program Files</title>
 
<para>catchsegv, gencat, getconf, getent, glibcbug, iconv, iconvconfig,
ldconfig, ldd, lddlibc4, locale, localedef, mtrace, nscd, nscd_nischeck,
pcprofiledump, pt_chown, rpcgen, rpcinfo, sln, sprof, tzselect, xtrace,
zdump and zic</para></sect3>
 
<sect3><title>Descriptions</title>
 
<sect4><title>catchsegv</title>
<para>No description is currently available.</para></sect4>
 
<sect4><title>gencat</title>
<para>gencat generates message catalogues.</para></sect4>
 
<sect4><title>getconf</title>
<para>No description is currently available.</para></sect4>
 
<sect4><title>getent</title>
<para>getent gets entries from an administrative database.</para></sect4>
 
<sect4><title>glibcbug</title>
<para>glibcbug creates a bug report about glibc and and mails it to the
bug email address.</para></sect4>
 
<sect4><title>iconv</title>
<para>iconv performs character set conversion.</para></sect4>
 
<sect4><title>iconvconfig</title>
<para>iconvconfig creates fastloading iconv module
configuration file.</para></sect4>
 
<sect4><title>ldconfig</title>
<para>ldconfig configures the dynamic linker run time bindings.</para></sect4>
 
<sect4><title>ldd</title>
<para>ldd prints the shared libraries required by each program or shared
library specified on the command line.</para></sect4>
 
<sect4><title>lddlibc4</title>
<para>No description is currently available.</para></sect4>
 
<sect4><title>locale</title>
<para>No description is currently available.</para></sect4>
 
<sect4><title>localedef</title>
<para>localedef compiles locale specifications.</para></sect4>
 
<sect4><title>mtrace</title>
<para>No description is currently available.</para></sect4>
 
<sect4><title>nscd</title>
<para>nscd is a daemon that provides a cache for the most common name
service requests.</para></sect4>
 
<sect4><title>nscd_nischeck</title>
<para>No description is currently available.</para></sect4>
 
<sect4><title>pcprofiledump</title>
<para>pcprofiledump dumps information generated by
PC profiling.</para></sect4>
 
<sect4><title>pt_chown</title>
<para>pt_chown sets the owner, group and access permission of the
slave pseudo terminal corresponding to the master pseudo terminal passed
on file descriptor `3'. This is the helper program for the `grantpt'
function. It is not intended to be run directly
from the command line.</para></sect4>
 
<sect4><title>rpcgen</title>
<para>No description is currently available.</para></sect4>
 
<sect4><title>rpcinfo</title>
<para>No description is currently available.</para></sect4>
 
<sect4><title>sln</title>
<para>sln symbolically links dest to source. It is statically linked,
needing no dynamic linking at all. Thus sln is useful to make symbolic
links to dynamic libraries if the dynamic linking system for some reason
is nonfunctional.</para></sect4>
 
<sect4><title>sprof</title>
<para>sprof reads and displays shared object profiling data.</para></sect4>
 
<sect4><title>tzselect</title>
<para>tzselect asks the user for information about the current location and
outputs the resulting time zone description to standard output.</para></sect4>
 
<sect4><title>xtrace</title>
<para>xtrace traces execution of program by printing the currently executed
function.</para></sect4>
 
<sect4><title>zdump</title>
<para>zdump is the time zone dumper.</para></sect4>
 
<sect4><title>zic</title>
<para>zic is the time zone compiler.</para></sect4>
 
</sect3>
 
<sect3><title>Library Files</title>
<para>ld.so, libBrokenLocale.[a,so], libBrokenLocale_p.a,
libSegFault.so, libanl.[a,so], libanl_p.a, libbsd-compat.a, libc.[a,so],
libc_nonshared.a, libc_p.a, libcrypt.[a,so], libcrypt_p.a, libdl.[a,so],
libdl_p.a, libg.a, libieee.a, libm.[a,so], libm_p.a, libmcheck.a,
libmemusage.so, libnsl.a, libnsl_p.a, libnss_compat.so, libnss_dns.so,
libnss_files.so, libnss_hesiod.so, libnss_nis.so, libnss_nisplus.so,
libpcprofile.so, libpthread.[a,so], libpthread_p.a, libresolv.[a,so],
libresolv_p.a, librpcsvc.a, librpcsvc_p.a, librt.[a,so], librt_p.a,
libthread_db.so, libutil.[a,so] and libutil_p.a</para></sect3>
 
<sect3><title>Descriptions</title>
 
<sect4><title>ld.so</title>
<para>ld.so is the helper program for shared library
executables.</para></sect4>
 
<sect4><title>libBrokenLocale, libBrokenLocale_p</title>
<para>No description is currently available.</para></sect4>
 
<sect4><title>libSegFault</title>
<para>No description is currently available.</para></sect4>
 
<sect4><title>libanl, libanl_p</title>
<para>No description is currently available.</para></sect4>
 
<sect4><title>libbsd-compat</title>
<para>No description is currently available.</para></sect4>
 
<sect4><title>libc, libc_nonshared, libc_p</title>
<para>These files constitute the main C library. The C Library is a
collection of commonly used functions in programs.
This way a programmer doesn't need to create his own functions for every
single task. The most common things like writing a string to the screen
are already present and at the disposal of the programmer.</para>
 
<para>The C library (actually almost every library) come in two flavors:
dynamic ones and static ones. In short when a program uses a static C
library, the code from the C library will be copied into the executable
file. When a program uses a dynamic library, that executable will not
contain the code from the C library, but instead a routine that loads
the functions from the library at the time the program is run. This
means a significant decrease in the file size of a program. The
documentation that comes with the C Library describes this in more
detail, as it is too complicated to explain here in one or two
lines.</para></sect4>
 
<sect4><title>libcrypt, libcrypt_p</title>
<para>libcrypt is the cryptography library.</para></sect4>
 
<sect4><title>libdl, libdl_p</title>
<para>No description is currently available.</para></sect4>
 
<sect4><title>libg</title>
<para>No description is currently available.</para></sect4>
 
<sect4><title>libieee</title>
<para>No description is currently available.</para></sect4>
 
<sect4><title>libm, libm_p</title>
<para>libm is the mathematical library.</para></sect4>
 
<sect4><title>libmcheck</title>
<para>No description is currently available.</para></sect4>
 
<sect4><title>libmemusage</title>
<para>No description is currently available.</para></sect4>
 
<sect4><title>libnsl, libnsl_p</title>
<para>No description is currently available.</para></sect4>
 
<sect4><title>libnss_compat, libnss_dns, libnss_files,
libnss_hesiod, libnss_nis, libnss_nisplus</title>
<para>No description is currently available.</para></sect4>
 
<sect4><title>libpcprofile</title>
<para>No description is currently available.</para></sect4>
 
<sect4><title>libpthread, libpthread_p</title>
<para>No description is currently available.</para></sect4>
 
<sect4><title>libresolv, libresolv_p</title>
<para>No description is currently available.</para></sect4>
 
<sect4><title>librpcsvc, librpcsvc_p</title>
<para>No description is currently available.</para></sect4>
 
<sect4><title>librt, librt_p</title>
<para>No description is currently available.</para></sect4>
 
<sect4><title>libthread_db</title>
<para>No description is currently available.</para></sect4>
 
<sect4><title>libutil, libutil</title>
<para>No description is currently available.</para></sect4>
 
</sect3>
 
</sect2>
 
/tags/cvs/lfs/appendixa/psmisc.xml
0,0 → 1,10
<sect1 id="aa-psmisc">
<title>Psmisc</title>
<?dbhtml filename="psmisc.html" dir="appendixa"?>
 
&aa-psmisc-down;
&aa-psmisc-desc;
&aa-psmisc-dep;
 
</sect1>
 
/tags/cvs/lfs/appendixa/flex.xml
0,0 → 1,10
<sect1 id="aa-flex">
<title>Flex</title>
<?dbhtml filename="flex.html" dir="appendixa"?>
 
&aa-flex-down;
&aa-flex-desc;
&aa-flex-dep;
 
</sect1>
 
/tags/cvs/lfs/appendixa/fileutils.xml
0,0 → 1,10
<sect1 id="aa-fileutils">
<title>Fileutils</title>
<?dbhtml filename="fileutils.html" dir="appendixa"?>
 
&aa-fileutils-down;
&aa-fileutils-desc;
&aa-fileutils-dep;
 
</sect1>
 
/tags/cvs/lfs/appendixa/utillinux-dep.xml
0,0 → 1,23
<sect2>
<title>Dependencies</title>
 
<para>Util-linux-&util-linux-depversion; needs the following to be
installed:</para>
 
<literallayout>
bash: sh
binutils: as, ld
diffutils: cmp
fileutils: chgrp, chmod, cp, install, ln, mv, rm
gettext: msgfmt, xgettext
gcc: cc, cc1, collect2, cpp, cpp0
glibc: rpcgen
grep: grep
make: make
sed: sed
sh-utils: uname, whoami
textutils: cat
</literallayout>
 
</sect2>
 
/tags/cvs/lfs/appendixa/binutils-desc.xml
0,0 → 1,112
<sect2>
<title>Contents of binutils-&binutils-contversion;</title>
 
<sect3><title>Program Files</title>
 
<para>addr2line, ar, as, c++filt, gasp, gprof, ld, nm, objcopy, objdump,
ranlib, readelf, size, strings and strip</para></sect3>
 
<sect3><title>Descriptions</title>
 
<sect4><title>addr2line</title>
<para>addr2line translates program addresses into file names and line numbers.
Given an address and an executable, it uses the debugging information in
the executable to figure out which file name and line number are associated
with a given address.</para></sect4>
 
<sect4><title>ar</title>
<para>The ar program creates, modifies, and extracts from archives. An archive
is a single file holding a collection of other files in a structure that makes
it possible to retrieve the original individual files (called members of
the archive).</para></sect4>
 
<sect4><title>as</title>
<para>as is primarily intended to assemble the output of the GNU C compiler gcc
for use by the linker ld.</para></sect4>
 
<sect4><title>c++filt</title>
<para>The C++ language provides function overloading, which means that it is
possible to
write many functions with the same name (providing each takes parameters
of different types). All C++ function names are encoded into a low-level
assembly label (this process is known as mangling). The c++filt program
does the inverse mapping: it decodes (demangles) low-level names into
user-level names so that the linker can keep these overloaded functions
from clashing.</para></sect4>
 
<sect4><title>gasp</title>
<para>Gasp is the Assembler Macro Preprocessor.</para></sect4>
 
<sect4><title>gprof</title>
<para>gprof displays call graph profile data.</para></sect4>
 
<sect4><title>ld</title>
<para>ld combines a number of object and archive files, relocates their data
and ties up symbol references. Often the last step in building a new compiled
program to run is a call to ld.</para></sect4>
 
<sect4><title>nm</title>
<para>nm lists the symbols from object files.</para></sect4>
 
<sect4><title>objcopy</title>
<para>objcopy utility copies the contents of an object file to another. objcopy
uses the GNU BFD Library to read and write the object files. It can write
the destination object file in a format different from that of the source
object file.</para></sect4>
 
<sect4><title>objdump</title>
<para>objdump displays information about one or more object files. The options
control what particular information to display. This information is mostly
useful to programmers who are working on the compilation tools, as opposed to
programmers who just want their program to compile and work.</para></sect4>
 
<sect4><title>ranlib</title>
<para>ranlib generates an index to the contents of an archive, and stores it in
the archive. The index lists each symbol defined by a member of an archive