diff -Naur BOOK/chapter04/.svn/entries BOOKfr/chapter04/.svn/entries
--- BOOK/chapter04/.svn/entries	2008-07-15 00:49:34.000000000 +0100
+++ BOOKfr/chapter04/.svn/entries	1970-01-01 01:00:00.000000000 +0100
@@ -1,112 +0,0 @@
-8
-
-dir
-8551
-svn://svn.linuxfromscratch.org/LFS/trunk/BOOK/chapter04
-svn://svn.linuxfromscratch.org/LFS
-
-
-
-2007-03-21T18:42:58.810750Z
-7970
-manuel
-
-
-svn:special svn:externals svn:needs-lock
-
-
-
-
-
-
-
-
-
-
-
-4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
-
-addinguser.xml
-file
-
-
-
-
-2008-07-14T23:49:34.000000Z
-f5ddaf533a5018bc235bc7d51bcc1097
-2007-03-21T18:42:58.810750Z
-7970
-manuel
-
-aboutsbus.xml
-file
-
-
-
-
-2008-07-14T23:49:34.000000Z
-10ddc71b9753b06b4ca3d6d8cd439ace
-2007-03-21T18:42:58.810750Z
-7970
-manuel
-
-abouttestsuites.xml
-file
-
-
-
-
-2008-07-14T23:49:34.000000Z
-40da60512bac10efa0108f206111f1d9
-2007-03-21T18:42:58.810750Z
-7970
-manuel
-
-chapter04.xml
-file
-
-
-
-
-2008-07-14T23:49:34.000000Z
-6e4ab18b946685d78493db05f945b405
-2007-03-21T18:42:58.810750Z
-7970
-manuel
-
-creatingtoolsdir.xml
-file
-
-
-
-
-2008-07-14T23:49:34.000000Z
-129275f63c3ea13afec2758f08ce8a6c
-2007-03-21T18:42:58.810750Z
-7970
-manuel
-
-settingenviron.xml
-file
-
-
-
-
-2008-07-14T23:49:34.000000Z
-9321a5a6de61d141c3aeb350bdf6695c
-2007-03-21T18:42:58.810750Z
-7970
-manuel
-
-aboutlfs.xml
-file
-
-
-
-
-2008-07-14T23:49:34.000000Z
-e0192ee93145ca607a21fe4060bdbcb3
-2007-03-21T18:42:58.810750Z
-7970
-manuel
-
diff -Naur BOOK/chapter04/.svn/format BOOKfr/chapter04/.svn/format
--- BOOK/chapter04/.svn/format	2008-07-15 00:49:34.000000000 +0100
+++ BOOKfr/chapter04/.svn/format	1970-01-01 01:00:00.000000000 +0100
@@ -1 +0,0 @@
-8
diff -Naur BOOK/chapter04/.svn/text-base/aboutlfs.xml.svn-base BOOKfr/chapter04/.svn/text-base/aboutlfs.xml.svn-base
--- BOOK/chapter04/.svn/text-base/aboutlfs.xml.svn-base	2008-07-15 00:49:34.000000000 +0100
+++ BOOKfr/chapter04/.svn/text-base/aboutlfs.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,39 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../general.ent">
-  %general-entities;
-]>
-
-<sect1 id="prepare-aboutlfs">
-  <?dbhtml filename="aboutlfs.html"?>
-
-  <title>About $LFS</title>
-
-  <para>Throughout this book, the environment variable <envar>LFS</envar> will
-  be used several times. It is paramount that this variable is always defined.
-  It should be set to the mount point chosen for the LFS partition.
-  Check that the <envar>LFS</envar> variable is set up properly with:</para>
-
-<screen role="nodump"><userinput>echo $LFS</userinput></screen>
-
-  <para>Make sure the output shows the path to the LFS partition's mount
-  point, which is <filename class="directory">/mnt/lfs</filename> if the
-  provided example was followed. If the output is incorrect, the
-  variable can be set with:</para>
-
-<screen role="nodump"><userinput>export LFS=/mnt/lfs</userinput></screen>
-
-  <para>Having this variable set is beneficial in that commands such as
-  <command>mkdir $LFS/tools</command> can be typed literally. The shell
-  will automatically replace <quote>$LFS</quote> with
-  <quote>/mnt/lfs</quote> (or whatever the variable was set to) when it
-  processes the command line.</para>
-
-  <para>Do not forget to check that <envar>$LFS</envar> is set whenever
-  you leave and reenter the current working environment (as when doing a
-  <command>su</command> to <systemitem class="username">root</systemitem>
-  or another user).</para>
-
-</sect1>
-
diff -Naur BOOK/chapter04/.svn/text-base/aboutsbus.xml.svn-base BOOKfr/chapter04/.svn/text-base/aboutsbus.xml.svn-base
--- BOOK/chapter04/.svn/text-base/aboutsbus.xml.svn-base	2008-07-15 00:49:34.000000000 +0100
+++ BOOKfr/chapter04/.svn/text-base/aboutsbus.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,45 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../general.ent">
-  %general-entities;
-]>
-
-<sect1 id="prepare-aboutsbus">
-  <?dbhtml filename="aboutsbus.html"?>
-
-  <title>About SBUs</title>
-
-  <para>Many people would like to know beforehand approximately how long
-  it takes to compile and install each package. Because Linux From
-  Scratch can be built on many different systems, it is impossible to
-  provide accurate time estimates. The biggest package (Glibc) will
-  take approximately 20 minutes on the fastest systems, but could take
-  up to three days on slower systems! Instead of providing actual times,
-  the Standard Build Unit (SBU) measure will be
-  used instead.</para>
-
-  <para>The SBU measure works as follows. The first package to be compiled
-  from this book is Binutils in <xref linkend="chapter-temporary-tools"/>. The
-  time it takes to compile this package is what will be referred to as the
-  Standard Build Unit or SBU. All other compile times will be expressed relative
-  to this time.</para>
-
-  <para>For example, consider a package whose compilation time is 4.5
-  SBUs. This means that if a system took 10 minutes to compile and
-  install the first pass of Binutils, it will take
-  <emphasis>approximately</emphasis> 45 minutes to build this example package.
-  Fortunately, most build times are shorter than the one for Binutils.</para>
-
-  <para>In general, SBUs are not entirely accurate because they depend on many
-  factors, including the host system's version of GCC. Note that on Symmetric
-  Multi-Processor (SMP)-based machines, SBUs are even less accurate. They are
-  provided here to give an estimate of how long it might take to install a
-  package, but the numbers can vary by as much as dozens of minutes in some
-  cases.</para>
-
-  <para>To view actual timings for a number of specific machines, we recommend
-  The LinuxFromScratch SBU Home Page at <ulink url="&lfs-root;~sbu/"/>.</para>
-
-</sect1>
-
diff -Naur BOOK/chapter04/.svn/text-base/abouttestsuites.xml.svn-base BOOKfr/chapter04/.svn/text-base/abouttestsuites.xml.svn-base
--- BOOK/chapter04/.svn/text-base/abouttestsuites.xml.svn-base	2008-07-15 00:49:34.000000000 +0100
+++ BOOKfr/chapter04/.svn/text-base/abouttestsuites.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,52 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../general.ent">
-  %general-entities;
-]>
-
-<sect1 id="prepare-abouttestsuites">
-  <?dbhtml filename="abouttestsuites.html"?>
-
-  <title>About the Test Suites</title>
-
-  <para>Most packages provide a test suite. Running the test suite for a
-  newly built package is a good idea because it can provide a <quote>sanity
-  check</quote> indicating that everything compiled correctly. A test suite
-  that passes its set of checks usually proves that the package is
-  functioning as the developer intended. It does not, however, guarantee
-  that the package is totally bug free.</para>
-
-  <para>Some test suites are more important than others. For example,
-  the test suites for the core toolchain packages&mdash;GCC, Binutils, and
-  Glibc&mdash;are of the utmost importance due to their central role in a
-  properly functioning system. The test suites for GCC and Glibc can
-  take a very long time to complete, especially on slower hardware, but
-  are strongly recommended.</para>
-
-  <note>
-    <para>Experience has shown that there is little to be gained from running
-    the test suites in <xref linkend="chapter-temporary-tools"/>. There can be
-    no escaping the fact that the host system always exerts some influence on
-    the tests in that chapter, often causing inexplicable failures. Because
-    the tools built in <xref linkend="chapter-temporary-tools"/> are temporary
-    and eventually discarded, we do not recommend running the test suites in
-    <xref linkend="chapter-temporary-tools"/> for the average reader. The
-    instructions for running those test suites are provided for the benefit of
-    testers and developers, but they are strictly optional.</para>
-  </note>
-
-  <para>A common issue with running the test suites for Binutils and GCC
-  is running out of pseudo terminals (PTYs). This can result in a high
-  number of failing tests. This may happen for several reasons, but the
-  most likely cause is that the host system does not have the
-  <systemitem class="filesystem">devpts</systemitem> file system set up
-  correctly. This issue is discussed in greater detail in <xref
-  linkend="chapter-temporary-tools"/>.</para>
-
-  <para>Sometimes package test suites will fail, but for reasons which the
-  developers are aware of and have deemed non-critical. Consult the logs located
-  at <ulink url="&test-results;"/> to verify whether or not these failures are
-  expected. This site is valid for all tests throughout this book.</para>
-
-</sect1>
diff -Naur BOOK/chapter04/.svn/text-base/addinguser.xml.svn-base BOOKfr/chapter04/.svn/text-base/addinguser.xml.svn-base
--- BOOK/chapter04/.svn/text-base/addinguser.xml.svn-base	2008-07-15 00:49:34.000000000 +0100
+++ BOOKfr/chapter04/.svn/text-base/addinguser.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,102 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../general.ent">
-  %general-entities;
-]>
-
-<sect1 id="ch-tools-addinguser">
-  <?dbhtml filename="addinguser.html"?>
-
-  <title>Adding the LFS User</title>
-
-  <para>When logged in as user <systemitem class="username">root</systemitem>,
-  making a single mistake can damage or destroy a system. Therefore, we
-  recommend building the packages in this chapter as an unprivileged user.
-  You could use your own user name, but to make it easier to set up a clean
-  working environment, create a new user called <systemitem
-  class="username">lfs</systemitem> as a member of a new group (also named
-  <systemitem class="groupname">lfs</systemitem>) and use this user during
-  the installation process. As <systemitem class="username">root</systemitem>,
-  issue the following commands to add the new user:</para>
-
-<screen><userinput>groupadd lfs
-useradd -s /bin/bash -g lfs -m -k /dev/null lfs</userinput></screen>
-
-  <variablelist>
-    <title>The meaning of the command line options:</title>
-
-    <varlistentry>
-      <term><parameter>-s /bin/bash</parameter></term>
-      <listitem>
-        <para>This makes <command>bash</command> the default shell for user
-        <systemitem class="username">lfs</systemitem>.</para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><parameter>-g lfs</parameter></term>
-      <listitem>
-        <para>This option adds user <systemitem class="username">lfs</systemitem>
-        to group <systemitem class="groupname">lfs</systemitem>.</para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><parameter>-m</parameter></term>
-      <listitem>
-        <para>This creates a home directory for <systemitem
-        class="username">lfs</systemitem>.</para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><parameter>-k /dev/null</parameter></term>
-      <listitem>
-        <para>This parameter prevents possible copying of files from a skeleton
-        directory (default is <filename class="directory">/etc/skel</filename>)
-        by changing the input location to the special null device.</para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><parameter>lfs</parameter></term>
-      <listitem>
-        <para>This is the actual name for the created group and user.</para>
-      </listitem>
-    </varlistentry>
-
-  </variablelist>
-
-  <para>To log in as <systemitem class="username">lfs</systemitem> (as opposed
-  to switching to user <systemitem class="username">lfs</systemitem> when logged
-  in as <systemitem class="username">root</systemitem>, which does not require
-  the <systemitem class="username">lfs</systemitem> user to have a password),
-  give <systemitem class="username">lfs</systemitem> a password:</para>
-
-<screen role="nodump"><userinput>passwd lfs</userinput></screen>
-
-  <para>Grant <systemitem class="username">lfs</systemitem> full access to
-  <filename class="directory">$LFS/tools</filename> by making
-  <systemitem class="username">lfs</systemitem> the directory owner:</para>
-
-<screen><userinput>chown -v lfs $LFS/tools</userinput></screen>
-
-  <para>If a separate working directory was created as suggested, give
-  user <systemitem class="username">lfs</systemitem> ownership of this
-  directory:</para>
-
-<screen><userinput>chown -v lfs $LFS/sources</userinput></screen>
-
-  <para>Next, login as user <systemitem class="username">lfs</systemitem>.
-  This can be done via a virtual console, through a display manager, or with
-  the following substitute user command:</para>
-
-<screen role="nodump"><userinput>su - lfs</userinput></screen>
-
-  <para>The <quote><parameter>-</parameter></quote> instructs
-  <command>su</command> to start a login shell as opposed to a non-login shell.
-  The difference between these two types of shells can be found in detail in
-  <filename>bash(1)</filename> and <command>info bash</command>.</para>
-
-</sect1>
diff -Naur BOOK/chapter04/.svn/text-base/chapter04.xml.svn-base BOOKfr/chapter04/.svn/text-base/chapter04.xml.svn-base
--- BOOK/chapter04/.svn/text-base/chapter04.xml.svn-base	2008-07-15 00:49:34.000000000 +0100
+++ BOOKfr/chapter04/.svn/text-base/chapter04.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,21 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../general.ent">
-  %general-entities;
-]>
-
-<chapter id="chapter-final-preps" xreflabel="Chapter 4">
-  <?dbhtml dir="chapter04"?>
-  <?dbhtml filename="chapter04.html"?>
-
-  <title>Final Preparations</title>
-
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="aboutlfs.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="creatingtoolsdir.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="addinguser.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="settingenviron.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="aboutsbus.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="abouttestsuites.xml"/>
-
-</chapter>
diff -Naur BOOK/chapter04/.svn/text-base/creatingtoolsdir.xml.svn-base BOOKfr/chapter04/.svn/text-base/creatingtoolsdir.xml.svn-base
--- BOOK/chapter04/.svn/text-base/creatingtoolsdir.xml.svn-base	2008-07-15 00:49:34.000000000 +0100
+++ BOOKfr/chapter04/.svn/text-base/creatingtoolsdir.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,48 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../general.ent">
-  %general-entities;
-]>
-
-<sect1 id="ch-tools-creatingtoolsdir">
-  <?dbhtml filename="creatingtoolsdir.html"?>
-
-  <title>Creating the $LFS/tools Directory</title>
-
-  <para>All programs compiled in <xref linkend="chapter-temporary-tools"/>
-  will be installed under <filename class="directory">$LFS/tools</filename>
-  to keep them separate from the programs compiled in <xref
-  linkend="chapter-building-system"/>. The programs compiled here are
-  temporary tools and will not be a part of the final LFS system. By keeping
-  these programs in a separate directory, they can easily be discarded later
-  after their use. This also prevents these programs from ending up in the
-  host production directories (easy to do by accident in <xref
-  linkend="chapter-temporary-tools"/>).</para>
-
-  <para>Create the required directory by running the following as
-  <systemitem class="username">root</systemitem>:</para>
-
-<screen><userinput>mkdir -v $LFS/tools</userinput></screen>
-
-  <para>The next step is to create a <filename class="symlink">/tools</filename>
-  symlink on the host system. This will point to the newly-created directory on
-  the LFS partition. Run this command as <systemitem
-  class="username">root</systemitem> as well:</para>
-
-<screen><userinput>ln -sv $LFS/tools /</userinput></screen>
-
-  <note>
-    <para>The above command is correct. The <command>ln</command> command
-    has a few syntactic variations, so be sure to check
-    <command>info coreutils ln</command> and <filename>ln(1)</filename>
-    before reporting what you may think is an error.</para>
-  </note>
-
-  <para>The created symlink enables the toolchain to be compiled so that it
-  always refers to <filename class="directory">/tools</filename>, meaning
-  that the compiler, assembler, and linker will work both in this chapter
-  (when we are still using some tools from the host) and in the next (when
-  we are <quote>chrooted</quote> to the LFS partition).</para>
-
-</sect1>
diff -Naur BOOK/chapter04/.svn/text-base/settingenviron.xml.svn-base BOOKfr/chapter04/.svn/text-base/settingenviron.xml.svn-base
--- BOOK/chapter04/.svn/text-base/settingenviron.xml.svn-base	2008-07-15 00:49:34.000000000 +0100
+++ BOOKfr/chapter04/.svn/text-base/settingenviron.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,91 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
-  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-  <!ENTITY % general-entities SYSTEM "../general.ent">
-  %general-entities;
-]>
-
-<sect1 id="ch-tools-settingenviron">
-  <?dbhtml filename="settingenvironment.html"?>
-
-  <title>Setting Up the Environment</title>
-
-  <para>Set up a good working environment by creating two new startup files
-  for the <command>bash</command> shell. While logged in as user
-  <systemitem class="username">lfs</systemitem>, issue the following command
-  to create a new <filename>.bash_profile</filename>:</para>
-
-<screen><userinput>cat &gt; ~/.bash_profile &lt;&lt; "EOF"
-<literal>exec env -i HOME=$HOME TERM=$TERM PS1='\u:\w\$ ' /bin/bash</literal>
-EOF</userinput></screen>
-
-  <para>When logged on as user <systemitem class="username">lfs</systemitem>,
-  the initial shell is usually a <emphasis>login</emphasis> shell which reads
-  the <filename>/etc/profile</filename> of the host (probably containing some
-  settings and environment variables) and then <filename>.bash_profile</filename>.
-  The <command>exec env -i.../bin/bash</command> command in the
-  <filename>.bash_profile</filename> file replaces the running shell with a new
-  one with a completely empty environment, except for the <envar>HOME</envar>,
-  <envar>TERM</envar>, and <envar>PS1</envar> variables. This ensures that no
-  unwanted and potentially hazardous environment variables from the host system
-  leak into the build environment. The technique used here achieves the goal of
-  ensuring a clean environment.</para>
-
-  <para>The new instance of the shell is a <emphasis>non-login</emphasis>
-  shell, which does not read the <filename>/etc/profile</filename> or
-  <filename>.bash_profile</filename> files, but rather reads the
-  <filename>.bashrc</filename> file instead. Create the
-  <filename>.bashrc</filename> file now:</para>
-
-<screen><userinput>cat &gt; ~/.bashrc &lt;&lt; "EOF"
-<literal>set +h
-umask 022
-LFS=/mnt/lfs
-LC_ALL=POSIX
-PATH=/tools/bin:/bin:/usr/bin
-export LFS LC_ALL PATH</literal>
-EOF</userinput></screen>
-
-  <para>The <command>set +h</command> command turns off
-  <command>bash</command>'s hash function. Hashing is ordinarily a useful
-  feature&mdash;<command>bash</command> uses a hash table to remember the
-  full path of executable files to avoid searching the <envar>PATH</envar>
-  time and again to find the same executable. However, the new tools should
-  be used as soon as they are installed. By switching off the hash function,
-  the shell will always search the <envar>PATH</envar> when a program is to
-  be run. As such, the shell will find the newly compiled tools in
-  <filename class="directory">$LFS/tools</filename> as soon as they are
-  available without remembering a previous version of the same program in a
-  different location.</para>
-
-  <para>Setting the user file-creation mask (umask) to 022 ensures that newly
-  created files and directories are only writable by their owner, but are
-  readable and executable by anyone (assuming default modes are used by the
-  <function>open(2)</function> system call, new files will end up with permission
-  mode 644 and directories with mode 755).</para>
-
-  <para>The <envar>LFS</envar> variable should be set to the chosen mount
-  point.</para>
-
-  <para>The <envar>LC_ALL</envar> variable controls the localization of certain
-  programs, making their messages follow the conventions of a specified country.
-  If the host system uses a version of Glibc older than 2.2.4, having
-  <envar>LC_ALL</envar> set to something other than <quote>POSIX</quote> or
-  <quote>C</quote> (during this chapter) may cause issues if you exit the chroot
-  environment and wish to return later. Setting <envar>LC_ALL</envar> to
-  <quote>POSIX</quote> or <quote>C</quote> (the two are equivalent) ensures that
-  everything will work as expected in the chroot environment.</para>
-
-  <para>By putting <filename class="directory">/tools/bin</filename> ahead of the
-  standard <envar>PATH</envar>, all the programs installed in <xref
-  linkend="chapter-temporary-tools"/> are picked up by the shell immediately after
-  their installation. This, combined with turning off hashing, limits the risk
-  that old programs are used from the host when the same programs are available in
-  the chapter 5 environment.</para>
-
-  <para>Finally, to have the environment fully prepared for building the
-  temporary tools, source the just-created user profile:</para>
-
-<screen><userinput>source ~/.bash_profile</userinput></screen>
-
-</sect1>
diff -Naur BOOK/chapter04/CVS/Entries BOOKfr/chapter04/CVS/Entries
--- BOOK/chapter04/CVS/Entries	1970-01-01 01:00:00.000000000 +0100
+++ BOOKfr/chapter04/CVS/Entries	2008-07-14 19:36:08.000000000 +0100
@@ -0,0 +1,8 @@
+/aboutlfs.xml/1.6/Sun Jun 22 21:27:06 2008//
+/aboutsbus.xml/1.8/Sun Jun 22 21:23:33 2008//
+/abouttestsuites.xml/1.10/Sun Jun 22 21:25:08 2008//
+/addinguser.xml/1.8/Sun Jun 22 21:24:24 2008//
+/chapter04.xml/1.19/Sun Jun 22 21:22:49 2008//
+/creatingtoolsdir.xml/1.7/Sun Jun 22 21:24:45 2008//
+/settingenviron.xml/1.9/Sun Jun 22 21:25:29 2008//
+D
diff -Naur BOOK/chapter04/CVS/Repository BOOKfr/chapter04/CVS/Repository
--- BOOK/chapter04/CVS/Repository	1970-01-01 01:00:00.000000000 +0100
+++ BOOKfr/chapter04/CVS/Repository	2008-07-14 18:47:46.000000000 +0100
@@ -0,0 +1 @@
+lfs/chapter04
diff -Naur BOOK/chapter04/CVS/Root BOOKfr/chapter04/CVS/Root
--- BOOK/chapter04/CVS/Root	1970-01-01 01:00:00.000000000 +0100
+++ BOOKfr/chapter04/CVS/Root	2008-07-14 18:47:46.000000000 +0100
@@ -0,0 +1 @@
+:ext:texou@traduc.org:/var/lib/cvs/lfs
diff -Naur BOOK/chapter04/aboutlfs.xml BOOKfr/chapter04/aboutlfs.xml
--- BOOK/chapter04/aboutlfs.xml	2008-07-15 00:49:34.000000000 +0100
+++ BOOKfr/chapter04/aboutlfs.xml	2008-06-22 22:27:06.000000000 +0100
@@ -8,32 +8,38 @@
 <sect1 id="prepare-aboutlfs">
   <?dbhtml filename="aboutlfs.html"?>
 
-  <title>About $LFS</title>
+  <title>À propos de $LFS</title>
 
-  <para>Throughout this book, the environment variable <envar>LFS</envar> will
-  be used several times. It is paramount that this variable is always defined.
-  It should be set to the mount point chosen for the LFS partition.
-  Check that the <envar>LFS</envar> variable is set up properly with:</para>
+  <para>Tout au long de ce livre, la variable d'environnement
+  <envar>LFS</envar> sera utilisée de nombreuses fois. Il est vitale que
+  cette variable soit toujours définie. Elle doit pointer vers le point
+  de montage choisi pour la partition LFS. Vérifiez que votre variable
+  <envar>LFS</envar> est correctement configurée avec&nbsp;:</para>
 
 <screen role="nodump"><userinput>echo $LFS</userinput></screen>
 
-  <para>Make sure the output shows the path to the LFS partition's mount
-  point, which is <filename class="directory">/mnt/lfs</filename> if the
-  provided example was followed. If the output is incorrect, the
-  variable can be set with:</para>
+  <para>Assurez-vous que la sortie affiche le chemin vers le point de
+  montage de la partition LFS, c'est-à-dire
+
+  <filename class="directory">/mnt/lfs</filename> si vous avez suivi
+  l'exemple fourni. Si cet affichage est mauvais, vous pouvez toujours
+  initialiser la variable avec&nbsp;:</para>
 
 <screen role="nodump"><userinput>export LFS=/mnt/lfs</userinput></screen>
 
-  <para>Having this variable set is beneficial in that commands such as
-  <command>mkdir $LFS/tools</command> can be typed literally. The shell
-  will automatically replace <quote>$LFS</quote> with
-  <quote>/mnt/lfs</quote> (or whatever the variable was set to) when it
-  processes the command line.</para>
-
-  <para>Do not forget to check that <envar>$LFS</envar> is set whenever
-  you leave and reenter the current working environment (as when doing a
-  <command>su</command> to <systemitem class="username">root</systemitem>
-  or another user).</para>
+  <para>Avoir cette variable initialisée est tout à votre bénéfice car
+  des commandes telles que <command>mkdir $LFS/tools</command> peuvent
+  être saisies de façon littérale. Votre shell remplacera
+  <quote>$LFS</quote> par <quote>/mnt/lfs</quote> (ou par ce chemin
+  avec lequel vous avez initialisé la variable) lorsqu'il exécutera la
+  ligne de commande.</para>
+
+  <para>N'oubliez pas de vérifier que <envar>$LFS</envar> est initialisé
+  à chaque fois que vous entrez dans l'environnement (par exemple, avec
+  <command>su</command> pour
+
+   <systemitem class="username">root</systemitem> ou un autre
+utilisateur).</para>
 
 </sect1>
 
diff -Naur BOOK/chapter04/aboutsbus.xml BOOKfr/chapter04/aboutsbus.xml
--- BOOK/chapter04/aboutsbus.xml	2008-07-15 00:49:34.000000000 +0100
+++ BOOKfr/chapter04/aboutsbus.xml	2008-06-22 22:23:33.000000000 +0100
@@ -8,38 +8,45 @@
 <sect1 id="prepare-aboutsbus">
   <?dbhtml filename="aboutsbus.html"?>
 
-  <title>About SBUs</title>
+  <title>À propos des SBU</title>
 
-  <para>Many people would like to know beforehand approximately how long
-  it takes to compile and install each package. Because Linux From
-  Scratch can be built on many different systems, it is impossible to
-  provide accurate time estimates. The biggest package (Glibc) will
-  take approximately 20 minutes on the fastest systems, but could take
-  up to three days on slower systems! Instead of providing actual times,
-  the Standard Build Unit (SBU) measure will be
-  used instead.</para>
-
-  <para>The SBU measure works as follows. The first package to be compiled
-  from this book is Binutils in <xref linkend="chapter-temporary-tools"/>. The
-  time it takes to compile this package is what will be referred to as the
-  Standard Build Unit or SBU. All other compile times will be expressed relative
-  to this time.</para>
-
-  <para>For example, consider a package whose compilation time is 4.5
-  SBUs. This means that if a system took 10 minutes to compile and
-  install the first pass of Binutils, it will take
-  <emphasis>approximately</emphasis> 45 minutes to build this example package.
-  Fortunately, most build times are shorter than the one for Binutils.</para>
-
-  <para>In general, SBUs are not entirely accurate because they depend on many
-  factors, including the host system's version of GCC. Note that on Symmetric
-  Multi-Processor (SMP)-based machines, SBUs are even less accurate. They are
-  provided here to give an estimate of how long it might take to install a
-  package, but the numbers can vary by as much as dozens of minutes in some
-  cases.</para>
+  <para>Beaucoup de personnes souhaitent savoir combien de temps la
+  compilation et l'installation de chaque paquet va prendre. Mais Linux
+  from Scratch est construit sur tant de systèmes différents qu'il est
+  impossible de donner des temps précis. Le plus gros paquet (Glibc)
+  prendra approximativement vingt minutes sur les systèmes les plus
+  rapides mais pourrait prendre environ trois jours sur les moins
+  rapides&nbsp;! Au lieu de donner les temps constatés, l'unité de
+  construction standard (<emphasis>Standard Build Unit</emphasis>) est
+  utilisée.</para>
+
+  <para>La mesure SBU fonctionne ainsi. Le premier paquet que vous
+  compilez dans ce livre est Binutils lors du <xref
+  linkend="chapter-temporary-tools"/>. Le temps que prend la compilation
+  de ce
+
+  paquet est ce que nous appelons <quote>SBU</quote>. Tous les autres
+  temps de compilation sont exprimés par rapport à celui-ci</para>
+
+  <para>Par exemple, considérez un paquet spécifique dont le temps de
+  compilation correspond à 4,5&nbsp;SBU. Ceci signifie que s'il vous a
+  fallu 10 minutes pour compiler et installer la première passe de
+  Binutils, alors vous savez que cela prendra <emphasis>45 minutes</emphasis>
+  pour construire ce paquet. Heureusement, la plupart des temps
+  de construction sont bien plus courts que celui de Binutils.</para>
+
+  <para>En général, les SBU ne sont pas vraiment précis car ils
+  dépendent de trop de facteurs, dont la version de GCC sur votre
+  machine hôte. Notez que les SBU sont encore moins précis sur les
+  machines multi-processeurs (SMP). Ils sont fournis ici pour donner une
+  estimation du temps nécessaire pour installer un paquetage mais ces
+  nombres peuvent varier de plusieurs dizaines de minutes dans certains
+  cas.</para>
 
-  <para>To view actual timings for a number of specific machines, we recommend
-  The LinuxFromScratch SBU Home Page at <ulink url="&lfs-root;~sbu/"/>.</para>
+  <para>Si vous souhaitez voir des chronométrages réels pour des
+  machines spécifiques, nous recommandons la page d'accueil de
+
+  <ulink url="&lfs-root;~sbu/"/>.</para>
 
 </sect1>
 
diff -Naur BOOK/chapter04/abouttestsuites.xml BOOKfr/chapter04/abouttestsuites.xml
--- BOOK/chapter04/abouttestsuites.xml	2008-07-15 00:49:34.000000000 +0100
+++ BOOKfr/chapter04/abouttestsuites.xml	2008-06-22 22:25:08.000000000 +0100
@@ -8,45 +8,56 @@
 <sect1 id="prepare-abouttestsuites">
   <?dbhtml filename="abouttestsuites.html"?>
 
-  <title>About the Test Suites</title>
+  <title>À propos des suites de tests</title>
 
-  <para>Most packages provide a test suite. Running the test suite for a
-  newly built package is a good idea because it can provide a <quote>sanity
-  check</quote> indicating that everything compiled correctly. A test suite
-  that passes its set of checks usually proves that the package is
-  functioning as the developer intended. It does not, however, guarantee
-  that the package is totally bug free.</para>
-
-  <para>Some test suites are more important than others. For example,
-  the test suites for the core toolchain packages&mdash;GCC, Binutils, and
-  Glibc&mdash;are of the utmost importance due to their central role in a
-  properly functioning system. The test suites for GCC and Glibc can
-  take a very long time to complete, especially on slower hardware, but
-  are strongly recommended.</para>
+  <para>La plupart des paquets disposent d'une suite de tests. Lancer
+  cette suite de tests pour un paquet nouvellement construit est
+  généralement une bonne idée car cela peut apporter une
+  <quote>vérification de propreté</quote> comme quoi tout a été compilé
+  correctement. Une suite de tests réussissant l'ensemble des
+  vérifications prouve généralement que le paquet fonctionne à peu près
+  comme le développeur en avait l'intention. Néanmoins, cela ne garantit
+  pas que le paquet ne contient pas de bogues.</para>
+
+  <para>Certaines des suites de tests sont plus importantes que
+  d'autres. Par exemple, les suites de tests des paquets formant le
+  c&oelig;ur de l'ensemble des outils&mdash;GCC, Binutils, and
+  Glibc&mdash;sont de la plus grande importance étant donné leur rôle
+  central dans un système fonctionnel. Les suites de tests pour GCC et
+  Glibc peuvent prendre beaucoup de temps pour se terminer, surtout sur
+  du matériel lent, mais ils sont fortement recommandés</para>
 
   <note>
-    <para>Experience has shown that there is little to be gained from running
-    the test suites in <xref linkend="chapter-temporary-tools"/>. There can be
-    no escaping the fact that the host system always exerts some influence on
-    the tests in that chapter, often causing inexplicable failures. Because
-    the tools built in <xref linkend="chapter-temporary-tools"/> are temporary
-    and eventually discarded, we do not recommend running the test suites in
-    <xref linkend="chapter-temporary-tools"/> for the average reader. The
-    instructions for running those test suites are provided for the benefit of
-    testers and developers, but they are strictly optional.</para>
+    <para>L'expérience nous a montré qu'il y a peu à gagner en lançant ces
+    suites de tests au <xref linkend="chapter-temporary-tools"/>. Il n'y a pas
+    d'échappatoire au fait que le système hôte exerce toujours une influence sur
+    les tests dans ce chapitre, occasionnant fréquemment des échecs étonnants et
+    inexplicables. Comme les outils construits dans le <xref linkend="chapter-temporary-tools"/> sont temporaires et éventuellement
+    supprimés, pour le lecteur habituel de ce livre, nous recommandons de ne pas
+    lancer les suites de tests dans le
+    <xref linkend="chapter-temporary-tools"/> pour l'utilisateur de base. Les instructions de lancement de ces suites de test
+    sont fournies pour les testeurs et les développeurs mais elles sont réellement
+    optionnelles pour tous les autres.</para>
   </note>
 
-  <para>A common issue with running the test suites for Binutils and GCC
-  is running out of pseudo terminals (PTYs). This can result in a high
-  number of failing tests. This may happen for several reasons, but the
-  most likely cause is that the host system does not have the
-  <systemitem class="filesystem">devpts</systemitem> file system set up
-  correctly. This issue is discussed in greater detail in <xref
-  linkend="chapter-temporary-tools"/>.</para>
-
-  <para>Sometimes package test suites will fail, but for reasons which the
-  developers are aware of and have deemed non-critical. Consult the logs located
-  at <ulink url="&test-results;"/> to verify whether or not these failures are
-  expected. This site is valid for all tests throughout this book.</para>
+  <para>Un problème commun lors du lancement des suites de test pour
+  Binutils et GCC est de manquer de pseudo-terminaux (PTY). Le symptôme
+  est un nombre inhabituellement élevé de tests ayant échoué. Ceci peut
+  arriver pour un certain nombre de raisons. La plus raisonnable est que
+  le système hôte ne dispose pas du système de fichiers <systemitem
+  class="filesystem">devpts</systemitem> configuré correctement. Ce
+  problème
+
+  est traité avec plus de détails dans le 
+
+  <xref linkend="chapter-temporary-tools"/>.</para>
+
+  <para>Quelquefois, les suites de test des paquets échoueront mais pour
+  des raisons dont les développeurs sont conscients et qu'ils ont
+  estimées non critique. Consultez les traces sur
+
+  <ulink url="&test-results;"/> pour vérifier si ces échecs sont
+  attendus. Ce site est valide pour tous les tests effectués dans ce
+  livre.</para>
 
 </sect1>
diff -Naur BOOK/chapter04/addinguser.xml BOOKfr/chapter04/addinguser.xml
--- BOOK/chapter04/addinguser.xml	2008-07-15 00:49:34.000000000 +0100
+++ BOOKfr/chapter04/addinguser.xml	2008-06-22 22:24:24.000000000 +0100
@@ -8,28 +8,32 @@
 <sect1 id="ch-tools-addinguser">
   <?dbhtml filename="addinguser.html"?>
 
-  <title>Adding the LFS User</title>
+  <title>Ajouter l'utilisateur LFS</title>
 
-  <para>When logged in as user <systemitem class="username">root</systemitem>,
-  making a single mistake can damage or destroy a system. Therefore, we
-  recommend building the packages in this chapter as an unprivileged user.
-  You could use your own user name, but to make it easier to set up a clean
-  working environment, create a new user called <systemitem
-  class="username">lfs</systemitem> as a member of a new group (also named
-  <systemitem class="groupname">lfs</systemitem>) and use this user during
-  the installation process. As <systemitem class="username">root</systemitem>,
-  issue the following commands to add the new user:</para>
+  <para>Lorsque vous êtes connecté en tant qu'utilisateur
+  <systemitem class="username">root</systemitem>, faire une simple
+  erreur peut endommager voire dévaster votre système. Donc, nous
+  recommandons de construire les paquets dans ce chapitre en tant
+  qu'utilisateur non privilégié. Vous pouvez bien sûr utiliser
+  votre propre nom d'utilisateur mais, pour faciliter l'établissement
+  d'un environnement de travail propre, créez un nouvel utilisateur
+  <systemitem class="username">lfs</systemitem> comme membre d'un
+  nouveau groupe <systemitem class="groupname">lfs</systemitem>)
+  utilisez-le lors du processus d'installation. En tant que <systemitem
+  class="username">root</systemitem>, lancez les commandes suivantes
+  pour créer le nouvel utilisateur&nbsp;:</para>
 
 <screen><userinput>groupadd lfs
 useradd -s /bin/bash -g lfs -m -k /dev/null lfs</userinput></screen>
 
   <variablelist>
-    <title>The meaning of the command line options:</title>
+    <title>Voici la signification des options en ligne de commande&nbsp;:</title>
 
     <varlistentry>
       <term><parameter>-s /bin/bash</parameter></term>
       <listitem>
-        <para>This makes <command>bash</command> the default shell for user
+        <para>Ceci fait de <command>bash</command> le shell par défaut de
+        l'utilisateur
         <systemitem class="username">lfs</systemitem>.</para>
       </listitem>
     </varlistentry>
@@ -37,66 +41,76 @@
     <varlistentry>
       <term><parameter>-g lfs</parameter></term>
       <listitem>
-        <para>This option adds user <systemitem class="username">lfs</systemitem>
-        to group <systemitem class="groupname">lfs</systemitem>.</para>
+        <para>Cette option ajoute l'utilisateur <systemitem class="username">lfs</systemitem>
+        au groupe <systemitem class="groupname">lfs</systemitem>.</para>
       </listitem>
     </varlistentry>
 
     <varlistentry>
       <term><parameter>-m</parameter></term>
       <listitem>
-        <para>This creates a home directory for <systemitem
-        class="username">lfs</systemitem>.</para>
+        <para>Ceci crée un répertoire personnel pour l'utilisateur
+
+        <systemitem class="username">lfs</systemitem>.</para>
       </listitem>
     </varlistentry>
 
     <varlistentry>
       <term><parameter>-k /dev/null</parameter></term>
       <listitem>
-        <para>This parameter prevents possible copying of files from a skeleton
-        directory (default is <filename class="directory">/etc/skel</filename>)
-        by changing the input location to the special null device.</para>
+        <para>Ce paramètre empêche tout copie possible de fichiers provenant
+        du répertoire squelette (par défaut, <filename class="directory">/etc/skel</filename>)
+        en modifiant son emplacement par le
+        périphérique spécial null.</para>
       </listitem>
     </varlistentry>
 
     <varlistentry>
       <term><parameter>lfs</parameter></term>
       <listitem>
-        <para>This is the actual name for the created group and user.</para>
+        <para>Ceci est le nom réel pour le groupe et l'utilisateur
+        créé.</para>
       </listitem>
     </varlistentry>
 
   </variablelist>
 
-  <para>To log in as <systemitem class="username">lfs</systemitem> (as opposed
-  to switching to user <systemitem class="username">lfs</systemitem> when logged
-  in as <systemitem class="username">root</systemitem>, which does not require
-  the <systemitem class="username">lfs</systemitem> user to have a password),
-  give <systemitem class="username">lfs</systemitem> a password:</para>
+  <para>Pour vous connecter en tant qu'utilisateur
+  <systemitem class="username">lfs</systemitem> (et non pas de passer à
+  l'utilisateur <systemitem class="username">lfs</systemitem> alors que
+  vous êtes connecté en tant que  
+  <systemitem class="username">root</systemitem>, ce qui ne requiert pas
+  de mot de passe pour l'utilisateur
+  <systemitem class="username">lfs</systemitem>, donnez un mot de passe
+  à <systemitem class="username">lfs</systemitem>&nbsp;:</para>
 
 <screen role="nodump"><userinput>passwd lfs</userinput></screen>
 
-  <para>Grant <systemitem class="username">lfs</systemitem> full access to
-  <filename class="directory">$LFS/tools</filename> by making
-  <systemitem class="username">lfs</systemitem> the directory owner:</para>
+  <para>Donnez à
+  <systemitem class="username">lfs</systemitem> un accès complet à
+  <filename class="directory">$LFS/tools</filename>  en indiquant que
+  <systemitem class="username">lfs</systemitem> est le propriétaire du
+  répertoire&nbsp;:</para>
 
 <screen><userinput>chown -v lfs $LFS/tools</userinput></screen>
 
-  <para>If a separate working directory was created as suggested, give
-  user <systemitem class="username">lfs</systemitem> ownership of this
-  directory:</para>
+  <para>Si un répertoire de travail séparé a été créé comme suggéré,
+  faites que l'utilisateur <systemitem class="username">lfs</systemitem>
+  soit aussi le propriétaire de ce répertoire&nbsp;:</para>
 
 <screen><userinput>chown -v lfs $LFS/sources</userinput></screen>
 
-  <para>Next, login as user <systemitem class="username">lfs</systemitem>.
-  This can be done via a virtual console, through a display manager, or with
-  the following substitute user command:</para>
+  <para>Ensuite, connectez-vous en tant que 
+
+  <systemitem class="username">lfs</systemitem>. Ceci peut se faire via
+  une console virtuelle, avec le gestionnaire d'affichage ou avec la
+  commande suivante de substitution d'utilisateur</para>
 
 <screen role="nodump"><userinput>su - lfs</userinput></screen>
 
-  <para>The <quote><parameter>-</parameter></quote> instructs
-  <command>su</command> to start a login shell as opposed to a non-login shell.
-  The difference between these two types of shells can be found in detail in
-  <filename>bash(1)</filename> and <command>info bash</command>.</para>
+  <para>Le <quote><parameter>-</parameter></quote> indique à
+  <command>su</command> de lancer un shell de connexion. Vous trouverez
+  la différence entre un shell de connexion et un autre dans la page man
+  <filename>bash(1)</filename> et <command>info bash</command>.</para>
 
 </sect1>
diff -Naur BOOK/chapter04/chapter04.xml BOOKfr/chapter04/chapter04.xml
--- BOOK/chapter04/chapter04.xml	2008-07-15 00:49:34.000000000 +0100
+++ BOOKfr/chapter04/chapter04.xml	2008-06-22 22:22:49.000000000 +0100
@@ -5,11 +5,11 @@
   %general-entities;
 ]>
 
-<chapter id="chapter-final-preps" xreflabel="Chapter 4">
+<chapter id="chapter-final-preps" xreflabel="Chapitre 4">
   <?dbhtml dir="chapter04"?>
   <?dbhtml filename="chapter04.html"?>
 
-  <title>Final Preparations</title>
+  <title>Dernières préparations</title>
 
   <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="aboutlfs.xml"/>
   <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="creatingtoolsdir.xml"/>
diff -Naur BOOK/chapter04/creatingtoolsdir.xml BOOKfr/chapter04/creatingtoolsdir.xml
--- BOOK/chapter04/creatingtoolsdir.xml	2008-07-15 00:49:34.000000000 +0100
+++ BOOKfr/chapter04/creatingtoolsdir.xml	2008-06-22 22:24:45.000000000 +0100
@@ -8,41 +8,58 @@
 <sect1 id="ch-tools-creatingtoolsdir">
   <?dbhtml filename="creatingtoolsdir.html"?>
 
-  <title>Creating the $LFS/tools Directory</title>
+  <title>Créer le répertoire $LFS/tools</title>
 
-  <para>All programs compiled in <xref linkend="chapter-temporary-tools"/>
-  will be installed under <filename class="directory">$LFS/tools</filename>
-  to keep them separate from the programs compiled in <xref
-  linkend="chapter-building-system"/>. The programs compiled here are
-  temporary tools and will not be a part of the final LFS system. By keeping
-  these programs in a separate directory, they can easily be discarded later
-  after their use. This also prevents these programs from ending up in the
-  host production directories (easy to do by accident in <xref
-  linkend="chapter-temporary-tools"/>).</para>
+  <para>Tous les programmes compilés dans
 
-  <para>Create the required directory by running the following as
-  <systemitem class="username">root</systemitem>:</para>
+  <xref linkend="chapter-temporary-tools"/> seront installés dans
+  <filename class="directory">$LFS/tools</filename> pour les tenir
+  séparés des programmes compilés dans le 
+
+  <xref linkend="chapter-building-system"/>. Les programmes compilés ici
+  sont seulement des outils temporaires et ne prendront pas part au
+  système LFS final. En les conservant dans un répertoire séparé, nous
+  pourrons facilement les supprimer plus tard. Ceci nous aide aussi à
+  les empêcher de finir dans les répertoires de production de votre hôte
+  (facile à faire par accident dans le 
+
+  <xref linkend="chapter-temporary-tools"/>).</para>
+
+  <para>Créez le répertoire requis en lançant la commande suivante en
+  tant qu'utilisateur
+
+  <systemitem class="username">root</systemitem>&nbsp;:</para>
 
 <screen><userinput>mkdir -v $LFS/tools</userinput></screen>
 
-  <para>The next step is to create a <filename class="symlink">/tools</filename>
-  symlink on the host system. This will point to the newly-created directory on
-  the LFS partition. Run this command as <systemitem
-  class="username">root</systemitem> as well:</para>
+  <para>La prochaine étape consiste en la création du lien symbolique
+  <filename class="symlink">/tools</filename> sur votre système hôte. Il
+  pointera vers le répertoire que vous venez de créer sur la partition
+  LFS. Lancez cette commande en tant
+
+  qu'utilisateur <systemitem class="username">root</systemitem>&nbsp;:</para>
 
 <screen><userinput>ln -sv $LFS/tools /</userinput></screen>
 
   <note>
-    <para>The above command is correct. The <command>ln</command> command
-    has a few syntactic variations, so be sure to check
-    <command>info coreutils ln</command> and <filename>ln(1)</filename>
-    before reporting what you may think is an error.</para>
+    <para>La commande ci-dessus est correcte. La commande <command>ln</command>
+    a quelques variations syntaxiques, assurez-vous de
+    vérifier <command>info coreutils ln</command> et <filename>ln(1)</filename>
+    avant de signaler ce que vous pensez être une
+    erreur.</para>
   </note>
 
-  <para>The created symlink enables the toolchain to be compiled so that it
-  always refers to <filename class="directory">/tools</filename>, meaning
-  that the compiler, assembler, and linker will work both in this chapter
-  (when we are still using some tools from the host) and in the next (when
-  we are <quote>chrooted</quote> to the LFS partition).</para>
+  <para>Le lien symbolique créé nous permet de compiler notre ensemble
+  d'outils de façon à ce qu'il se réfère à 
+
+  <filename class="directory">/tools</filename>, ce qui signifie que
+  le
+
+  compilateur, l'assembleur et l'éditeur de liens fonctionneront tous
+  dans ce
+
+  chapitre (alors que nous utilisons toujours quelques outils provenant
+  de l'hôte) et dans le suivant (lorsque nous serons en
+  <quote>chrooted</quote> sur la partition LFS).</para>
 
 </sect1>
diff -Naur BOOK/chapter04/settingenviron.xml BOOKfr/chapter04/settingenviron.xml
--- BOOK/chapter04/settingenviron.xml	2008-07-15 00:49:34.000000000 +0100
+++ BOOKfr/chapter04/settingenviron.xml	2008-06-22 22:25:29.000000000 +0100
@@ -8,34 +8,45 @@
 <sect1 id="ch-tools-settingenviron">
   <?dbhtml filename="settingenvironment.html"?>
 
-  <title>Setting Up the Environment</title>
+  <title>Configurer l'environnement</title>
 
-  <para>Set up a good working environment by creating two new startup files
-  for the <command>bash</command> shell. While logged in as user
-  <systemitem class="username">lfs</systemitem>, issue the following command
-  to create a new <filename>.bash_profile</filename>:</para>
+  <para>Configurez un bon environnement de travail en créant deux
+  nouveaux fichiers de démarrage pour le shell <command>bash</command>.
+  En étant connecté en tant qu'utilisateur
+
+  <systemitem class="username">lfs</systemitem>, lancez la commande
+  suivante pour créer un nouveau
+  <filename>.bash_profile</filename>&nbsp;:</para>
 
 <screen><userinput>cat &gt; ~/.bash_profile &lt;&lt; "EOF"
 <literal>exec env -i HOME=$HOME TERM=$TERM PS1='\u:\w\$ ' /bin/bash</literal>
 EOF</userinput></screen>
 
-  <para>When logged on as user <systemitem class="username">lfs</systemitem>,
-  the initial shell is usually a <emphasis>login</emphasis> shell which reads
-  the <filename>/etc/profile</filename> of the host (probably containing some
-  settings and environment variables) and then <filename>.bash_profile</filename>.
-  The <command>exec env -i.../bin/bash</command> command in the
-  <filename>.bash_profile</filename> file replaces the running shell with a new
-  one with a completely empty environment, except for the <envar>HOME</envar>,
-  <envar>TERM</envar>, and <envar>PS1</envar> variables. This ensures that no
-  unwanted and potentially hazardous environment variables from the host system
-  leak into the build environment. The technique used here achieves the goal of
-  ensuring a clean environment.</para>
-
-  <para>The new instance of the shell is a <emphasis>non-login</emphasis>
-  shell, which does not read the <filename>/etc/profile</filename> or
-  <filename>.bash_profile</filename> files, but rather reads the
-  <filename>.bashrc</filename> file instead. Create the
-  <filename>.bashrc</filename> file now:</para>
+  <para>Lorsque vous êtes connecté en tant que
+
+  <systemitem class="username">lfs</systemitem>, le shell
+  initial est habituellement un shell de <emphasis>login</emphasis> qui lit
+  le fichier
+  <filename>/etc/profile</filename> de l'hôte (contenant probablement
+  quelques configurations et variables d'environnement) et puis
+  <filename>.bash_profile</filename>. La commande
+
+  <command>exec env  -i.../bin/bash</command> dans le fichier
+  <filename>.bash_profile</filename> remplace le shell en cours avec un
+  nouveau ayant un environnement complètement vide sauf pour les
+  variables <envar>HOME</envar>, <envar>TERM</envar>, et
+  <envar>PS1</envar>. Ceci nous assure qu'aucune variable
+  d'environnement non souhaitée et potentiellement dangereuse, provenant
+  du système hôte, ne parvienne dans l'environnement de construction. La
+  technique utilisée ici s'assure de ce but d'environnement
+  propre.</para>
+
+  <para>La nouvelle instance du shell est un shell
+  <emphasis>non-login</emphasis>, qui ne lit donc pas les fichiers
+  <filename>/etc/profile</filename> ou
+  <filename>.bash_profile</filename>, mais plutôt le fichier
+  <filename>.bashrc</filename> file. Créez maintenant le fichier
+  <filename>.bashrc</filename>&nbsp;:</para>
 
 <screen><userinput>cat &gt; ~/.bashrc &lt;&lt; "EOF"
 <literal>set +h
@@ -46,45 +57,55 @@
 export LFS LC_ALL PATH</literal>
 EOF</userinput></screen>
 
-  <para>The <command>set +h</command> command turns off
-  <command>bash</command>'s hash function. Hashing is ordinarily a useful
-  feature&mdash;<command>bash</command> uses a hash table to remember the
-  full path of executable files to avoid searching the <envar>PATH</envar>
-  time and again to find the same executable. However, the new tools should
-  be used as soon as they are installed. By switching off the hash function,
-  the shell will always search the <envar>PATH</envar> when a program is to
-  be run. As such, the shell will find the newly compiled tools in
-  <filename class="directory">$LFS/tools</filename> as soon as they are
-  available without remembering a previous version of the same program in a
-  different location.</para>
-
-  <para>Setting the user file-creation mask (umask) to 022 ensures that newly
-  created files and directories are only writable by their owner, but are
-  readable and executable by anyone (assuming default modes are used by the
-  <function>open(2)</function> system call, new files will end up with permission
-  mode 644 and directories with mode 755).</para>
-
-  <para>The <envar>LFS</envar> variable should be set to the chosen mount
-  point.</para>
-
-  <para>The <envar>LC_ALL</envar> variable controls the localization of certain
-  programs, making their messages follow the conventions of a specified country.
-  If the host system uses a version of Glibc older than 2.2.4, having
-  <envar>LC_ALL</envar> set to something other than <quote>POSIX</quote> or
-  <quote>C</quote> (during this chapter) may cause issues if you exit the chroot
-  environment and wish to return later. Setting <envar>LC_ALL</envar> to
-  <quote>POSIX</quote> or <quote>C</quote> (the two are equivalent) ensures that
-  everything will work as expected in the chroot environment.</para>
-
-  <para>By putting <filename class="directory">/tools/bin</filename> ahead of the
-  standard <envar>PATH</envar>, all the programs installed in <xref
-  linkend="chapter-temporary-tools"/> are picked up by the shell immediately after
-  their installation. This, combined with turning off hashing, limits the risk
-  that old programs are used from the host when the same programs are available in
-  the chapter 5 environment.</para>
-
-  <para>Finally, to have the environment fully prepared for building the
-  temporary tools, source the just-created user profile:</para>
+  <para>La commande <command>set +h</command> désactive la fonction de
+  hachage de <command>bash</command>. D'habitude, le hachage est une
+  fonctionnalité utile&mdash;<command>bash</command> utilise une table
+  de hachage pour se rappeler le chemin complet des fichiers exécutables
+  pour éviter d'avoir à chercher dans <envar>PATH</envar> à chaque fois
+  qu'il doit trouver le même exécutable. Néanmoins, les nouveaux outils
+  devraient être utilisés dès leur installation. En désactivant la
+  fonction de hachage, le shell cherchera en permanence dans
+  <envar>PATH</envar> lorsqu'un programme doit être exécuté. Ainsi, le
+  shell
+
+  trouvera les nouveaux outils compilés dans 
+
+  <filename class="directory">$LFS/tools</filename> dès qu'ils sont
+  disponibles et sans se rappeler de la version précédente du même
+  programme mais dans un autre emplacement.</para>
+
+  <para>Configurer le masque de création de fichier (umask) à 022 nous
+  assure que les nouveaux fichiers et répertoires créés sont modifiables
+  uniquement par leurs propriétaires mais lisibles et exécutables par
+  tout le monde (en supposant que les modes par défaut sont utilisés par
+  l'appel système <function>open(2)</function> les nouveaux fichiers
+  finiront avec les droits 644 et les répertoires avec ceux 755).</para>
+
+  <para>La variable <envar>LFS</envar> devrait être configurée avec le
+  point de montage choisi.</para>
+
+  <para>La variable <envar>LC_ALL</envar>  contrôle la localisation de
+  certains programmes, faisant que leurs messages suivent les
+  conventions d'un pays spécifié. Si le système hôte utilise une version
+  de Glibc plus ancienne que la 2.2.4, avoir <envar>LC_ALL</envar>
+  initialisé à quelque chose d'autre que <quote>POSIX</quote> ou
+  <quote>C</quote> (pendant ce chapitre) pourrait poser des problèmes si
+  vous quittez l'environnement chroot et souhaitez y retourner plus
+  tard. Initialiser <envar>LC_ALL</envar> à <quote>POSIX</quote> ou
+  <quote>C</quote> (les deux sont équivalents) nous assure que tout
+  fonctionnera comme attendu dans l'environnement chroot.</para>
+
+  <para>En plaçant <filename class="directory">/tools/bin</filename> au
+  début du <envar>PATH</envar> standard, tous les programmes installées
+  dans <xref linkend="chapter-temporary-tools"/> sont récupérés par le
+  shell immédiatement après leur installation. Ceci, combiné avec la
+  désactivation du hachage, limite le risque que d'anciens programmes de
+  l'hôte soient utilisés alors que les mêmes programmes sont disponibles
+  depuis l'environnement du chapitre 5.</para>
+
+  <para>Enfin, pour avoir un environnement complètement préparé pour la
+  construction des outils temporaires, récupérez le source du profile de
+  l'utilisateur tout juste créé&nbsp;:</para>
 
 <screen><userinput>source ~/.bash_profile</userinput></screen>
 
