diff -Naur BOOK/chapter07/.svn/entries BOOKfr/chapter07/.svn/entries
--- BOOK/chapter07/.svn/entries	2008-07-15 00:49:41.000000000 +0100
+++ BOOKfr/chapter07/.svn/entries	1970-01-01 01:00:00.000000000 +0100
@@ -1,196 +0,0 @@
-8
-
-dir
-8551
-svn://svn.linuxfromscratch.org/LFS/trunk/BOOK/chapter07
-svn://svn.linuxfromscratch.org/LFS
-
-
-
-2008-05-23T01:45:45.142565Z
-8545
-bryan
-
-
-svn:special svn:externals svn:needs-lock
-
-
-
-
-
-
-
-
-
-
-
-4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
-
-hosts.xml
-file
-
-
-
-
-2008-07-14T23:49:41.000000Z
-f45fd1a56ec57232e44ed3830369c091
-2007-03-21T18:42:58.810750Z
-7970
-manuel
-
-profile.xml
-file
-
-
-
-
-2008-07-14T23:49:41.000000Z
-2c2dfe9fa79360156fb8e6a7d377513d
-2007-09-21T17:55:13.696345Z
-8394
-manuel
-
-introduction.xml
-file
-
-
-
-
-2008-07-14T23:49:41.000000Z
-2d4bdacd58813e60667e0ee233ac008c
-2007-07-31T23:56:56.646937Z
-8266
-dnicholson
-
-console.xml
-file
-
-
-
-
-2008-07-14T23:49:41.000000Z
-e620f847b046987441020a3ebdb4bdec
-2008-02-27T00:11:42.369273Z
-8493
-ken
-
-udev.xml
-file
-
-
-
-
-2008-07-14T23:49:41.000000Z
-abf638ae8cd918769b91028b0317c8c5
-2008-05-23T01:45:45.142565Z
-8545
-bryan
-
-inputrc.xml
-file
-
-
-
-
-2008-07-14T23:49:41.000000Z
-c28447f0fc91d37f8f8d9416db90bcb7
-2007-04-05T19:03:40.182185Z
-8015
-manuel
-
-usage.xml
-file
-
-
-
-
-2008-07-14T23:49:41.000000Z
-5ce08110aef6e8fa285192b4043df4eb
-2007-03-21T18:42:58.810750Z
-7970
-manuel
-
-setclock.xml
-file
-
-
-
-
-2008-07-14T23:49:41.000000Z
-af1d0d8885e46e6768769991682d019e
-2007-03-21T18:42:58.810750Z
-7970
-manuel
-
-network.xml
-file
-
-
-
-
-2008-07-14T23:49:41.000000Z
-29c38c8b295bacc93c6fcccab6d65b61
-2008-05-23T01:45:45.142565Z
-8545
-bryan
-
-symlinks.xml
-file
-
-
-
-
-2008-07-14T23:49:41.000000Z
-aa501f3555bc4cc4f90a897b898be6a1
-2008-05-23T01:45:45.142565Z
-8545
-bryan
-
-bootscripts.xml
-file
-
-
-
-
-2008-07-14T23:49:41.000000Z
-bb5792e35cc6d71efa9236af0a7253f4
-2007-09-18T21:11:00.127323Z
-8389
-manuel
-
-chapter07.xml
-file
-
-
-
-
-2008-07-14T23:49:41.000000Z
-8dbb927eb6cee42706de3b220235ad27
-2007-03-21T18:42:58.810750Z
-7970
-manuel
-
-hostname.xml
-file
-
-
-
-
-2008-07-14T23:49:41.000000Z
-65d11577d9bad96047dfd2456cd4eb0f
-2007-03-21T18:42:58.810750Z
-7970
-manuel
-
-sysklogd.xml
-file
-
-
-
-
-2008-07-14T23:49:41.000000Z
-120bd9e1fa07bd9884fcd8d6a36263fb
-2007-03-21T18:42:58.810750Z
-7970
-manuel
-
diff -Naur BOOK/chapter07/.svn/format BOOKfr/chapter07/.svn/format
--- BOOK/chapter07/.svn/format	2008-07-15 00:49:40.000000000 +0100
+++ BOOKfr/chapter07/.svn/format	1970-01-01 01:00:00.000000000 +0100
@@ -1 +0,0 @@
-8
diff -Naur BOOK/chapter07/.svn/text-base/bootscripts.xml.svn-base BOOKfr/chapter07/.svn/text-base/bootscripts.xml.svn-base
--- BOOK/chapter07/.svn/text-base/bootscripts.xml.svn-base	2008-07-15 00:49:41.000000000 +0100
+++ BOOKfr/chapter07/.svn/text-base/bootscripts.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,338 +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-scripts-bootscripts" role="wrap">
-  <?dbhtml filename="bootscripts.html"?>
-
-  <sect1info condition="script">
-    <productname>lfs-bootscripts</productname>
-    <productnumber>&lfs-bootscripts-version;</productnumber>
-    <address>&lfs-bootscripts-url;</address>
-  </sect1info>
-
-  <title>LFS-Bootscripts-&lfs-bootscripts-version;</title>
-
-  <indexterm zone="ch-scripts-bootscripts">
-    <primary sortas="a-Bootscripts">Bootscripts</primary>
-  </indexterm>
-
-  <sect2 role="package">
-    <title/>
-
-    <para>The LFS-Bootscripts package contains a set of scripts to start/stop the
-    LFS system at bootup/shutdown.</para>
-
-    <segmentedlist>
-      <segtitle>&buildtime;</segtitle>
-      <segtitle>&diskspace;</segtitle>
-
-      <seglistitem>
-        <seg>&lfs-bootscripts-ch7-sbu;</seg>
-        <seg>&lfs-bootscripts-ch7-du;</seg>
-      </seglistitem>
-    </segmentedlist>
-
-  </sect2>
-
-  <sect2 role="installation">
-    <title>Installation of LFS-Bootscripts</title>
-
-    <para>Install the package:</para>
-
-<screen><userinput remap="install">make install</userinput></screen>
-
-  </sect2>
-
-  <sect2 id="contents-bootscripts" role="content">
-    <title>Contents of LFS-Bootscripts</title>
-
-    <segmentedlist>
-      <segtitle>Installed scripts</segtitle>
-
-      <seglistitem>
-        <seg>checkfs, cleanfs, console, consolelog, functions, halt, ifdown,
-        ifup, localnet, modules, mountfs, mountkernfs, network, rc, reboot,
-        sendsignals, setclock, static, swap, sysctl, sysklogd, template,
-        udev, and udev_retry</seg>
-      </seglistitem>
-    </segmentedlist>
-
-    <variablelist>
-      <bridgehead renderas="sect3">Short Descriptions</bridgehead>
-      <?dbfo list-presentation="list"?>
-      <?dbhtml list-presentation="table"?>
-
-      <varlistentry id="checkfs-bootscripts">
-        <term><command>checkfs</command></term>
-        <listitem>
-          <para>Checks the integrity of the file systems before they are mounted
-          (with the exception of journal and network based file systems)</para>
-          <indexterm zone="ch-scripts-bootscripts checkfs-bootscripts">
-            <primary sortas="d-checkfs">checkfs</primary>
-          </indexterm>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry id="cleanfs-bootscripts">
-        <term><command>cleanfs</command></term>
-        <listitem>
-          <para>Removes files that should not be preserved between reboots, such
-          as those in <filename class="directory">/var/run/</filename> and
-          <filename class="directory">/var/lock/</filename>; it re-creates
-          <filename>/var/run/utmp</filename> and removes the possibly present
-          <filename>/etc/nologin</filename>, <filename>/fastboot</filename>, and
-          <filename>/forcefsck</filename> files</para>
-          <indexterm zone="ch-scripts-bootscripts cleanfs-bootscripts">
-            <primary sortas="d-cleanfs">cleanfs</primary>
-          </indexterm>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry id="console-bootscripts">
-        <term><command>console</command></term>
-        <listitem>
-          <para>Loads the correct keymap table for the desired keyboard layout;
-          it also sets the screen font</para>
-          <indexterm zone="ch-scripts-bootscripts console-bootscripts">
-            <primary sortas="d-console">console</primary>
-          </indexterm>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry id="consolelog-bootscripts">
-        <term><command>consolelog</command></term>
-        <listitem>
-          <para>Sets the kernel log level to control messages reaching the
-          console.</para>
-          <indexterm zone="ch-scripts-bootscripts consolelog-bootscripts">
-            <primary sortas="d-consolelog">consolelog</primary>
-          </indexterm>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry id="functions-bootscripts">
-        <term><command>functions</command></term>
-        <listitem>
-          <para>Contains common functions, such as error and status checking,
-          that are used by several bootscripts</para>
-          <indexterm zone="ch-scripts-bootscripts functions-bootscripts">
-            <primary sortas="d-functions">functions</primary>
-          </indexterm>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry id="halt-bootscripts">
-        <term><command>halt</command></term>
-        <listitem>
-          <para>Halts the system</para>
-          <indexterm zone="ch-scripts-bootscripts halt-bootscripts">
-            <primary sortas="d-halt">halt</primary>
-          </indexterm>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry id="ifdown-bootscripts">
-        <term><command>ifdown</command></term>
-        <listitem>
-          <para>Assists the network script with stopping network devices</para>
-          <indexterm zone="ch-scripts-bootscripts ifdown-bootscripts">
-            <primary sortas="d-ifdown">ifdown</primary>
-          </indexterm>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry id="ifup-bootscripts">
-        <term><command>ifup</command></term>
-        <listitem>
-          <para>Assists the network script with starting network devices</para>
-          <indexterm zone="ch-scripts-bootscripts ifup-bootscripts">
-            <primary sortas="d-ifup">ifup</primary>
-          </indexterm>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry id="localnet-bootscripts">
-        <term><command>localnet</command></term>
-        <listitem>
-          <para>Sets up the system's hostname and local loopback device</para>
-          <indexterm zone="ch-scripts-bootscripts localnet-bootscripts">
-            <primary sortas="d-localnet">localnet</primary>
-          </indexterm>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry id="modules-bootscripts">
-        <term><command>modules</command></term>
-        <listitem>
-          <para>Loads kernel modules listed in
-          <filename>/etc/sysconfig/modules</filename>, using arguments
-          that are also given there</para>
-          <indexterm zone="ch-scripts-bootscripts modules-bootscripts">
-            <primary sortas="d-modules">modules</primary>
-          </indexterm>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry id="mountfs-bootscripts">
-        <term><command>mountfs</command></term>
-        <listitem>
-          <para>Mounts all file systems, except ones that are marked
-          <emphasis>noauto</emphasis> or are network based</para>
-          <indexterm zone="ch-scripts-bootscripts mountfs-bootscripts">
-            <primary sortas="d-mountfs">mountfs</primary>
-          </indexterm>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry id="mountkernfs-bootscripts">
-        <term><command>mountkernfs</command></term>
-        <listitem>
-          <para>Mounts virtual kernel file systems, such as <systemitem
-          class="filesystem">proc</systemitem></para>
-          <indexterm zone="ch-scripts-bootscripts mountkernfs-bootscripts">
-            <primary sortas="d-mountkernfs">mountkernfs</primary>
-          </indexterm>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry id="network-bootscripts">
-        <term><command>network</command></term>
-        <listitem>
-          <para>Sets up network interfaces, such as network cards, and sets up
-          the default gateway (where applicable)</para>
-          <indexterm zone="ch-scripts-bootscripts network-bootscripts">
-            <primary sortas="d-network">network</primary>
-          </indexterm>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry id="rc-bootscripts">
-        <term><command>rc</command></term>
-        <listitem>
-          <para>The master run-level control script; it is responsible for
-          running all the other bootscripts one-by-one, in a sequence determined
-          by the name of the symbolic links being processed</para>
-          <indexterm zone="ch-scripts-bootscripts rc-bootscripts">
-            <primary sortas="d-rc">rc</primary>
-          </indexterm>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry id="reboot-bootscripts">
-        <term><command>reboot</command></term>
-        <listitem>
-          <para>Reboots the system</para>
-          <indexterm zone="ch-scripts-bootscripts reboot-bootscripts">
-            <primary sortas="d-reboot">reboot</primary>
-          </indexterm>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry id="sendsignals-bootscripts">
-        <term><command>sendsignals</command></term>
-        <listitem>
-          <para>Makes sure every process is terminated before the system reboots
-          or halts</para>
-          <indexterm zone="ch-scripts-bootscripts sendsignals-bootscripts">
-            <primary sortas="d-sendsignals">sendsignals</primary>
-          </indexterm>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry id="setclock-bootscripts">
-        <term><command>setclock</command></term>
-        <listitem>
-          <para>Resets the kernel clock to local time in case the hardware clock
-          is not set to UTC time</para>
-          <indexterm zone="ch-scripts-bootscripts setclock-bootscripts">
-            <primary sortas="d-setclock">setclock</primary>
-          </indexterm>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry id="static-bootscripts">
-        <term><command>static</command></term>
-        <listitem>
-          <para>Provides the functionality needed to assign a static Internet
-          Protocol (IP) address to a network interface</para>
-          <indexterm zone="ch-scripts-bootscripts static-bootscripts">
-            <primary sortas="d-static">static</primary>
-          </indexterm>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry id="swap-bootscripts">
-        <term><command>swap</command></term>
-        <listitem>
-          <para>Enables and disables swap files and partitions</para>
-          <indexterm zone="ch-scripts-bootscripts swap-bootscripts">
-            <primary sortas="d-swap">swap</primary>
-          </indexterm>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry id="sysctl-bootscripts">
-        <term><command>sysctl</command></term>
-        <listitem>
-          <para>Loads system configuration values from
-          <filename>/etc/sysctl.conf</filename>, if that file exists,
-          into the running kernel</para>
-          <indexterm zone="ch-scripts-bootscripts sysctl-bootscripts">
-            <primary sortas="d-sysctl">sysctl</primary>
-          </indexterm>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry id="sysklogd-bootscripts">
-        <term><command>sysklogd</command></term>
-        <listitem>
-          <para>Starts and stops the system and kernel log daemons</para>
-          <indexterm zone="ch-scripts-bootscripts sysklogd-bootscripts">
-            <primary sortas="d-sysklogd">sysklogd</primary>
-          </indexterm>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry id="template-bootscripts">
-        <term><command>template</command></term>
-        <listitem>
-          <para>A template to create custom bootscripts for other
-          daemons</para>
-          <indexterm zone="ch-scripts-bootscripts template-bootscripts">
-            <primary sortas="d-template">template</primary>
-          </indexterm>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry id="udev-bootscripts">
-        <term><command>udev</command></term>
-        <listitem>
-          <para>Prepares the <filename class="directory">/dev</filename>
-          directory and starts Udev</para>
-          <indexterm zone="ch-scripts-bootscripts udev-bootscripts">
-            <primary sortas="d-udev">udev</primary>
-          </indexterm>
-        </listitem>
-      </varlistentry>
-
-      <varlistentry id="udev-retry-bootscripts">
-        <term><command>udev_retry</command></term>
-        <listitem>
-          <para>Retries failed udev uevents, and copies generated rules
-          files from <filename class="directory">/dev/.udev</filename> to
-          <filename class="directory">/etc/udev/rules.d</filename> if required</para>
-          <indexterm zone="ch-scripts-bootscripts udev-retry-bootscripts">
-            <primary sortas="d-udev-retry">udev_retry</primary>
-          </indexterm>
-        </listitem>
-      </varlistentry>
-
-    </variablelist>
-
-  </sect2>
-
-</sect1>
diff -Naur BOOK/chapter07/.svn/text-base/chapter07.xml.svn-base BOOKfr/chapter07/.svn/text-base/chapter07.xml.svn-base
--- BOOK/chapter07/.svn/text-base/chapter07.xml.svn-base	2008-07-15 00:49:41.000000000 +0100
+++ BOOKfr/chapter07/.svn/text-base/chapter07.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,28 +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-bootscripts" xreflabel="Chapter 7">
-  <?dbhtml dir="chapter07"?>
-  <?dbhtml filename="chapter07.html"?>
-
-  <title>Setting Up System Bootscripts</title>
-
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="introduction.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="bootscripts.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="usage.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="udev.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="setclock.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="console.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="sysklogd.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="inputrc.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="profile.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="hostname.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="hosts.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="symlinks.xml"/>
-  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="network.xml"/>
-
-</chapter>
diff -Naur BOOK/chapter07/.svn/text-base/console.xml.svn-base BOOKfr/chapter07/.svn/text-base/console.xml.svn-base
--- BOOK/chapter07/.svn/text-base/console.xml.svn-base	2008-07-15 00:49:41.000000000 +0100
+++ BOOKfr/chapter07/.svn/text-base/console.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,236 +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-scripts-console">
-  <?dbhtml filename="console.html"?>
-
-  <title>Configuring the Linux Console</title>
-
-  <indexterm zone="ch-scripts-console">
-    <primary sortas="d-console">console</primary>
-    <secondary>configuring</secondary>
-  </indexterm>
-
-  <indexterm zone="ch-scripts-console">
-    <primary sortas="d-consolelog">consolelog</primary>
-    <secondary>configuring</secondary>
-  </indexterm>
-
-  <para>This section discusses how to configure the <command>console</command>
-  and <command>consolelog</command> bootscripts that set up the keyboard map,
-  console font and console kernel log level. If non-ASCII characters (e.g.,
-  the copyright sign, the British pound sign and Euro symbol) will not be used
-  and the keyboard is a U.S. one, much of this section can be skipped. Without
-  the configuration file, the <command>console</command> bootscript will do
-  nothing.</para>
-
-  <para>The <command>console</command>  and <command>consolelog</command>
-  script reads the <filename>/etc/sysconfig/console</filename> file for
-  configuration information.
-  Decide which keymap and screen font will be used. Various language-specific
-  HOWTOs can also help with this, see <ulink
-  url="http://www.tldp.org/HOWTO/HOWTO-INDEX/other-lang.html"/>. If still in
-  doubt, look in the <filename class="directory">/lib/kbd</filename>
-  directory for valid keymaps and screen fonts. Read
-  <filename>loadkeys(1)</filename> and <filename>setfont(8)</filename> manual
-  pages to determine the correct arguments for these programs.</para>
-
-  <para>The <filename>/etc/sysconfig/console</filename> file should contain lines
-  of the form: VARIABLE="value". The following variables are recognized:</para>
-
-  <variablelist>
-
-    <varlistentry>
-      <term>LOGLEVEL</term>
-      <listitem>
-        <para>This variable specifies the log level for kernel messages sent
-        to the console as set by <command>dmesg</command>. Valid levels are
-        from "1" (no messages) to "8". The default level is "7".</para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term>KEYMAP</term>
-      <listitem>
-        <para>This variable specifies the arguments for the
-        <command>loadkeys</command> program, typically, the name of keymap
-        to load, e.g., <quote>es</quote>. If this variable is not set, the
-	bootscript will not run the <command>loadkeys</command> program,
-	and the default kernel keymap will be used.</para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term>KEYMAP_CORRECTIONS</term>
-      <listitem>
-        <para>This (rarely used) variable
-        specifies the arguments for the second call to the
-        <command>loadkeys</command> program. This is useful if the stock keymap
-        is not completely satisfactory and a small adjustment has to be made. E.g.,
-        to include the Euro sign into a keymap that normally doesn't have it,
-        set this variable to <quote>euro2</quote>.</para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term>FONT</term>
-      <listitem>
-        <para>This variable specifies the arguments for the
-        <command>setfont</command> program. Typically, this includes the font
-        name, <quote>-m</quote>, and the name of the application character
-	map to load. E.g., in order to load the <quote>lat1-16</quote> font
-	together with the <quote>8859-1</quote> application character map
-	(as it is appropriate in the USA), <!-- because of the copyright sign -->
-	set this variable to <quote>lat1-16 -m 8859-1</quote>.
-        If this variable is not set, the bootscript will not run the
-        <command>setfont</command> program, and the default VGA font will be
-        used together with the default application character map.</para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term>UNICODE</term>
-      <listitem>
-        <para>Set this variable to <quote>1</quote>, <quote>yes</quote> or
-	<quote>true</quote> in order to put the
-        console into UTF-8 mode. This is useful in UTF-8 based locales and
-        harmful otherwise.</para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term>LEGACY_CHARSET</term>
-      <listitem>
-        <para>For many keyboard layouts, there is no stock Unicode keymap in
-        the Kbd package. The <command>console</command> bootscript will
-        convert an available keymap to UTF-8 on the fly if this variable is
-	set to the encoding of the available non-UTF-8 keymap.</para>
-      </listitem>
-    </varlistentry>
-
-  </variablelist>
-
-  <para>Some examples:</para>
-
-  <itemizedlist>
-
-    <listitem>
-      <para>For a non-Unicode setup, only the KEYMAP and FONT variables are
-      generally needed. E.g., for a Polish setup, one would use:</para>
-
-<screen role="nodump"><userinput>cat &gt; /etc/sysconfig/console &lt;&lt; "EOF"
-<literal># Begin /etc/sysconfig/console
-
-KEYMAP="pl2"
-FONT="lat2a-16 -m 8859-2"
-
-# End /etc/sysconfig/console</literal>
-EOF</userinput></screen>
-    </listitem>
-
-    <listitem>
-      <para>As mentioned above, it is sometimes necessary to adjust a
-      stock keymap slightly. The following example adds the Euro symbol to the
-      German keymap:</para>
-
-<screen role="nodump"><userinput>cat &gt; /etc/sysconfig/console &lt;&lt; "EOF"
-<literal># Begin /etc/sysconfig/console
-
-KEYMAP="de-latin1"
-KEYMAP_CORRECTIONS="euro2"
-FONT="lat0-16 -m 8859-15"
-
-# End /etc/sysconfig/console</literal>
-EOF</userinput></screen>
-    </listitem>
-
-    <listitem>
-      <para>The following is a Unicode-enabled example for Bulgarian, where a
-      stock UTF-8 keymap exists:</para>
-
-<screen role="nodump"><userinput>cat &gt; /etc/sysconfig/console &lt;&lt; "EOF"
-<literal># Begin /etc/sysconfig/console
-
-UNICODE="1"
-KEYMAP="bg_bds-utf8"
-FONT="LatArCyrHeb-16"
-
-# End /etc/sysconfig/console</literal>
-EOF</userinput></screen>
-    </listitem>
-
-    <listitem>
-      <para>Due to the use of a 512-glyph LatArCyrHeb-16 font in the previous
-      example, bright colors are no longer available on the Linux console unless
-      a framebuffer is used. If one wants to have bright colors without
-      framebuffer and can live without characters not belonging to his language,
-      it is still possible to use a language-specific 256-glyph font, as
-      illustrated below:</para>
-
-<screen role="nodump"><userinput>cat &gt; /etc/sysconfig/console &lt;&lt; "EOF"
-<literal># Begin /etc/sysconfig/console
-
-UNICODE="1"
-KEYMAP="bg_bds-utf8"
-FONT="cyr-sun16"
-
-# End /etc/sysconfig/console</literal>
-EOF</userinput></screen>
-    </listitem>
-
-    <listitem>
-      <para>There is no pre-made UTF-8 Russian keymap, therefore it has to be
-      produced by converting the existing KOI8-R keymap as illustrated
-      below:</para>
-
-<screen role="nodump"><userinput>cat &gt; /etc/sysconfig/console &lt;&lt; "EOF"
-<literal># Begin /etc/sysconfig/console
-
-UNICODE="1"
-KEYMAP="ru-ms"
-LEGACY_CHARSET="koi8-r"
-FONT="LatArCyrHeb-16"
-
-# End /etc/sysconfig/console</literal>
-EOF</userinput></screen>
-    </listitem>
-
-    <listitem>
-      <para>Some keymaps have dead keys (i.e., keys that don't produce a
-      character by themselves, but put an accent on the character produced
-      by the next key) or define composition rules (such as: <quote>press
-      Ctrl+. A E to get &AElig;</quote> in the default keymap).
-      Linux-&linux-version; in UTF-8 keyboard mode assumes that accented
-      characters produced via dead keys or composing are in the Latin-1 range
-      of Unicode, and it is impossible to change this assumption. Thus,
-      accented characters needed for, e.g., the Czech language, can't be typed
-      on Linux console in UTF-8 mode (but files containing these characters can
-      be displayed correctly). The solution is either to avoid the use of
-      UTF-8, or to install the X window system that doesn't have this
-      limitation in its input handling.</para>
-    </listitem>
-
-    <listitem>
-      <para>For Chinese, Japanese, Korean and some other languages, the Linux
-      console cannot be configured to display the needed characters. Users
-      who need such languages should install the X Window System, fonts that
-      cover the necessary character ranges, and the proper input method (e.g.,
-      SCIM, it supports a wide variety of languages).</para>
-    </listitem>
-
-  </itemizedlist>
-
-  <!-- Added because folks keep posting their console file with X questions
-  to blfs-support list -->
-  <note>
-    <para>The <filename>/etc/sysconfig/console</filename> file only controls the    Linux text console localization. It has nothing to do with setting the
-    proper keyboard layout and terminal fonts in the X Window System, with ssh
-    sessions or with a serial console. In such situations, limitations mentioned
-    in the last two list items above do not apply.</para>
-  </note>
-
-</sect1>
diff -Naur BOOK/chapter07/.svn/text-base/hostname.xml.svn-base BOOKfr/chapter07/.svn/text-base/hostname.xml.svn-base
--- BOOK/chapter07/.svn/text-base/hostname.xml.svn-base	2008-07-15 00:49:41.000000000 +0100
+++ BOOKfr/chapter07/.svn/text-base/hostname.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,32 +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-scripts-hostname">
-  <?dbhtml filename="hostname.html"?>
-
-  <title>Configuring the localnet Script</title>
-
-  <indexterm zone="ch-scripts-hostname">
-    <primary sortas="d-localnet">localnet</primary>
-    <secondary>configuring</secondary>
-  </indexterm>
-
-  <para>Part of the job of the <command>localnet</command> script is setting the
-  system's hostname. This needs to be configured in the
-  <filename>/etc/sysconfig/network</filename> file.</para>
-
-  <para>Create the <filename>/etc/sysconfig/network</filename> file and enter a
-  hostname by running:</para>
-
-<screen><userinput>echo "HOSTNAME=<replaceable>&lt;lfs&gt;</replaceable>" &gt; /etc/sysconfig/network</userinput></screen>
-
-  <para><replaceable>&lt;lfs&gt;</replaceable> needs to be replaced with the name given
-  to the computer. Do not enter the Fully Qualified Domain Name (FQDN) here. That
-  information will be put in the <filename>/etc/hosts</filename> file in the next
-  section.</para>
-
-</sect1>
diff -Naur BOOK/chapter07/.svn/text-base/hosts.xml.svn-base BOOKfr/chapter07/.svn/text-base/hosts.xml.svn-base
--- BOOK/chapter07/.svn/text-base/hosts.xml.svn-base	2008-07-15 00:49:41.000000000 +0100
+++ BOOKfr/chapter07/.svn/text-base/hosts.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,80 +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-scripts-hosts">
-  <?dbhtml filename="hosts.html"?>
-
-  <title>Customizing the /etc/hosts File</title>
-
-  <indexterm zone="ch-scripts-hosts">
-    <primary sortas="e-/etc/hosts">/etc/hosts</primary>
-  </indexterm>
-
-  <indexterm zone="ch-scripts-hosts">
-    <primary sortas="d-localnet">localnet</primary>
-  <secondary>/etc/hosts</secondary></indexterm>
-
-  <indexterm zone="ch-scripts-hosts">
-    <primary sortas="d-network">network</primary>
-  <secondary>/etc/hosts</secondary></indexterm>
-
-  <para>If a network card is to be configured, decide on the IP address,
-  fully-qualified domain name (FQDN), and possible aliases for use in the
-  <filename>/etc/hosts</filename> file. The syntax is:</para>
-
-<screen><literal>IP_address myhost.example.org aliases</literal></screen>
-
-  <para>Unless the computer is to be visible to the Internet (i.e.,
-  there is a registered domain and a valid block of assigned IP
-  addresses&mdash;most users do not have this), make sure that the IP
-  address is in the private network IP address range. Valid ranges
-  are:</para>
-
-<screen><literal>Private Network Address Range      Normal Prefix
-10.0.0.1 - 10.255.255.254           8
-172.x.0.1 - 172.x.255.254           16
-192.168.y.1 - 192.168.y.254         24</literal></screen>
-
-  <para>x can be any number in the range 16-31. y can be any number in
-  the range 0-255.</para>
-
-  <para>A valid private IP address could be 192.168.1.1. A valid FQDN for this
-  IP could be lfs.example.org.</para>
-
-  <para>Even if not using a network card, a valid FQDN is still required.
-  This is necessary for certain programs to operate correctly.</para>
-
-  <para>Create the  <filename>/etc/hosts</filename> file by running:</para>
-
-<screen><userinput>cat &gt; /etc/hosts &lt;&lt; "EOF"
-<literal># Begin /etc/hosts (network card version)
-
-127.0.0.1 localhost
-<replaceable>&lt;192.168.1.1&gt;</replaceable> <replaceable>&lt;HOSTNAME.example.org&gt;</replaceable> <replaceable>[alias1] [alias2 ...]</replaceable>
-
-# End /etc/hosts (network card version)</literal>
-EOF</userinput></screen>
-
-  <para>The <replaceable>&lt;192.168.1.1&gt;</replaceable> and
-  <replaceable>&lt;HOSTNAME.example.org&gt;</replaceable>
-  values need to be changed for specific users or requirements (if
-  assigned an IP address by a network/system administrator and the
-  machine will be connected to an existing network). The optional alias
-  name(s) can be omitted.</para>
-
-  <para>If a network card is not going to be configured, create the
-  <filename>/etc/hosts</filename> file by running:</para>
-
-<screen role="nodump"><userinput>cat &gt; /etc/hosts &lt;&lt; "EOF"
-<literal># Begin /etc/hosts (no network card version)
-
-127.0.0.1 <replaceable>&lt;HOSTNAME.example.org&gt;</replaceable> <replaceable>&lt;HOSTNAME&gt;</replaceable> localhost
-
-# End /etc/hosts (no network card version)</literal>
-EOF</userinput></screen>
-
-</sect1>
diff -Naur BOOK/chapter07/.svn/text-base/inputrc.xml.svn-base BOOKfr/chapter07/.svn/text-base/inputrc.xml.svn-base
--- BOOK/chapter07/.svn/text-base/inputrc.xml.svn-base	2008-07-15 00:49:41.000000000 +0100
+++ BOOKfr/chapter07/.svn/text-base/inputrc.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,80 +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-scripts-inputrc">
-  <?dbhtml filename="inputrc.html"?>
-
-  <title>Creating the /etc/inputrc File</title>
-
-  <indexterm zone="ch-scripts-inputrc">
-    <primary sortas="e-/etc/inputrc">/etc/inputrc</primary>
-  </indexterm>
-
-  <para>The <filename>inputrc</filename> file handles keyboard mapping for
-  specific situations. This file is the startup file used by Readline &mdash; the
-  input-related library &mdash; used by Bash and most other shells.</para>
-
-  <para>Most people do not need user-specific keyboard mappings so the command
-  below creates a global <filename>/etc/inputrc</filename> used by everyone who
-  logs in. If you later decide you need to override the defaults on a per-user
-  basis, you can create a <filename>.inputrc</filename> file in the user's home
-  directory with the modified mappings.</para>
-
-  <para>For more information on how to edit the <filename>inputrc</filename>
-  file, see <command>info bash</command> under the <emphasis>Readline Init
-  File</emphasis> section. <command>info readline</command> is also a good
-  source of information.</para>
-
-  <para>Below is a generic global <filename>inputrc</filename> along with comments
-  to explain what the various options do. Note that comments cannot be on the same
-  line as commands. Create the file using the following command:</para>
-
-<screen><userinput>cat &gt; /etc/inputrc &lt;&lt; "EOF"
-<literal># Begin /etc/inputrc
-# Modified by Chris Lynn &lt;roryo@roryo.dynup.net&gt;
-
-# Allow the command prompt to wrap to the next line
-set horizontal-scroll-mode Off
-
-# Enable 8bit input
-set meta-flag On
-set input-meta On
-
-# Turns off 8th bit stripping
-set convert-meta Off
-
-# Keep the 8th bit for display
-set output-meta On
-
-# none, visible or audible
-set bell-style none
-
-# All of the following map the escape sequence of the value
-# contained in the 1st argument to the readline specific functions
-"\eOd": backward-word
-"\eOc": forward-word
-
-# for linux console
-"\e[1~": beginning-of-line
-"\e[4~": end-of-line
-"\e[5~": beginning-of-history
-"\e[6~": end-of-history
-"\e[3~": delete-char
-"\e[2~": quoted-insert
-
-# for xterm
-"\eOH": beginning-of-line
-"\eOF": end-of-line
-
-# for Konsole
-"\e[H": beginning-of-line
-"\e[F": end-of-line
-
-# End /etc/inputrc</literal>
-EOF</userinput></screen>
-
-</sect1>
diff -Naur BOOK/chapter07/.svn/text-base/introduction.xml.svn-base BOOKfr/chapter07/.svn/text-base/introduction.xml.svn-base
--- BOOK/chapter07/.svn/text-base/introduction.xml.svn-base	2008-07-15 00:49:41.000000000 +0100
+++ BOOKfr/chapter07/.svn/text-base/introduction.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,27 +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-scripts-introduction">
-  <?dbhtml filename="introduction.html"?>
-
-  <title>Introduction</title>
-
-  <para>This chapter details how to install and configure the LFS-Bootscripts
-  package. Most of these scripts will work without modification, but a few require
-  additional configuration files because they deal with hardware-dependent
-  information.</para>
-
-  <para>System-V style init scripts are employed in this book because they are
-  widely used. For additional options, a hint detailing the BSD style init setup
-  is available at <ulink url="&hints-root;bsd-init.txt"/>.
-  Searching the LFS mailing lists for <quote>depinit</quote> will also offer
-  additional choices.</para>
-
-  <para>If using an alternative style of init scripts, skip this chapter
-  and move on to <xref linkend="chapter-bootable"/>.</para>
-
-</sect1>
diff -Naur BOOK/chapter07/.svn/text-base/network.xml.svn-base BOOKfr/chapter07/.svn/text-base/network.xml.svn-base
--- BOOK/chapter07/.svn/text-base/network.xml.svn-base	2008-07-15 00:49:41.000000000 +0100
+++ BOOKfr/chapter07/.svn/text-base/network.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,201 +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-scripts-network">
-  <?dbhtml filename="network.html"?>
-
-  <title>Configuring the network Script</title>
-
-  <indexterm zone="ch-scripts-network">
-    <primary sortas="d-network">network</primary>
-  <secondary>configuring</secondary></indexterm>
-
-  <para>This section only applies if a network card is to be
-  configured.</para>
-
-  <para>If a network card will not be used, there is likely no need to
-  create any configuration files relating to network cards. If that is
-  the case, remove the <filename class="symlink">network</filename>
-  symlinks from all run-level directories (<filename
-  class="directory">/etc/rc.d/rc*.d</filename>).</para>
-
-  <sect2>
-    <title>Creating stable names for network interfaces</title>
-
-    <para>With Udev and modular network drivers, the network interface numbering
-    is not persistent across reboots by default, because the drivers are loaded
-    in parallel and, thus, in random order. For example, on a computer having
-    two network cards made by Intel and Realtek, the network card manufactured
-    by Intel may become <filename class="devicefile">eth0</filename> and the
-    Realtek card becomes  <filename class="devicefile">eth1</filename>. In some
-    cases, after a reboot the cards get renumbered the other way around. To
-    avoid this, Udev comes with a script and some rules to assign stable names
-    to network cards based on their MAC address.</para>
-
-    <para>Pre-generate the rules to ensure the same names get assigned to the
-    same devices at every boot, including the first:</para>
-
-<screen><userinput>for NIC in /sys/class/net/* ; do
-    INTERFACE=${NIC##*/} udevadm test --action=add --subsystem=net $NIC
-done</userinput></screen>
-
-    <para>Now, inspect the <filename>/etc/udev/rules.d/70-persistent-net.rules</filename>
-    file, to find out which name was assigned to which network device:</para>
-
-<screen><userinput>cat /etc/udev/rules.d/70-persistent-net.rules</userinput></screen>
-
-    <para>The file begins with a comment block followed by two lines for each
-    NIC. The first line for each NIC is a commented description showing its
-    hardware IDs (e.g. its PCI vendor and device IDs, if it's a PCI card),
-    along with its driver in parentheses, if the driver can be found. Neither
-    the hardware ID nor the driver is used to determine which name to give an
-    interface; this information is only for reference. The second line is the
-    Udev rule that matches this NIC and actually assigns it a name.</para>
-
-    <para>All Udev rules are made up of several keys, separated by commas and
-    optional whitespace. This rule's keys and an explanation of each of them
-    are as follows:</para>
-
-    <itemizedlist>
-      <listitem>
-        <para><literal>SUBSYSTEM=="net"</literal> - This tells Udev to ignore
-        devices that are not network cards.</para>
-      </listitem>
-      <listitem>
-        <para><literal>ACTION=="add"</literal> - This tells Udev to ignore this
-        rule for a uevent that isn't an add ("remove" and "change" uevents also
-        happen, but don't need to rename network interfaces).</para>
-      </listitem>
-      <listitem>
-        <para><literal>DRIVERS=="?*"</literal> - This exists so that Udev will
-        ignore VLAN or bridge sub-interfaces (because these sub-interfaces do
-        not have drivers). These sub-interfaces are skipped because the name
-        that would be assigned would collide with their parent devices.</para>
-      </listitem>
-      <listitem>
-        <para><literal>ATTR{address}</literal> - The value of this key is the
-        NIC's MAC address.</para>
-      </listitem>
-      <listitem>
-        <para><literal>ATTR{type}=="1"</literal> - This ensures the rule only
-        matches the primary interface in the case of certain wireless drivers,
-        which create multiple virtual interfaces. The secondary interfaces are
-        skipped for the same reason that VLAN and bridge sub-interfaces are
-        skipped: there would be a name collision otherwise.</para>
-      </listitem>
-      <listitem>
-        <para><literal>KERNEL=="eth*"</literal> - This key was added to the
-        Udev rule generator to handle machines that have multiple network
-        interfaces, all with the same MAC address (the PS3 is one such
-        machine).  If the independent interfaces have different basenames,
-        this key will allow Udev to tell them apart.  This is generally not
-        necessary for most Linux From Scratch users, but does not hurt.</para>
-      </listitem>
-      <listitem>
-        <para><literal>NAME</literal> - The value of this key is the name that
-        Udev will assign to this interface.</para>
-      </listitem>
-    </itemizedlist>
-
-    <para>The value of <literal>NAME</literal> is the important part. Make sure
-    you know which name has been assigned to each of your network cards before
-    proceeding, and be sure to use that <literal>NAME</literal> value when
-    creating your configuration files below.</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 and directories in the <filename
-    class="directory">/etc/sysconfig/network-devices</filename> hierarchy.
-    This directory should contain a sub-directory for each interface to be
-    configured, such as <filename>ifconfig.xyz</filename>, where
-    <quote>xyz</quote> is a network interface name. Inside this directory
-    would be files defining the attributes to this interface, such as its IP
-    address(es), subnet masks, and so forth.</para>
-
-    <para>The following command creates a sample <filename>ipv4</filename>
-    file for the <emphasis>eth0</emphasis> device:</para>
-
-<screen><userinput>cd /etc/sysconfig/network-devices
-mkdir -v ifconfig.eth0
-cat &gt; ifconfig.eth0/ipv4 &lt;&lt; "EOF"
-<literal>ONBOOT=yes
-SERVICE=ipv4-static
-IP=192.168.1.1
-GATEWAY=192.168.1.2
-PREFIX=24
-BROADCAST=192.168.1.255</literal>
-EOF</userinput></screen>
-
-    <para>The values of these variables must be changed in every file to match
-    the proper setup. If the <envar>ONBOOT</envar> variable is set to
-    <quote>yes</quote> the network script will bring up the Network Interface
-    Card (NIC) during booting of the system. If set to anything but
-    <quote>yes</quote> the NIC will be ignored by the network script and not
-    be brought up.</para>
-
-    <para>The <envar>SERVICE</envar> variable defines the method used for
-    obtaining the IP address. The LFS-Bootscripts package has a modular IP
-    assignment format, and creating additional files in the <filename
-    class="directory">/etc/sysconfig/network-devices/services</filename>
-    directory allows other IP assignment methods. This is commonly used for
-    Dynamic Host Configuration Protocol (DHCP), which is addressed in the
-    BLFS book.</para>
-
-    <para>The <envar>GATEWAY</envar> variable should contain the default
-    gateway IP address, if one is present. If not, then comment out the
-    variable entirely.</para>
-
-    <para>The <envar>PREFIX</envar> variable needs to contain the number of
-    bits used in the subnet. Each octet in an IP address is 8 bits. If the
-    subnet's netmask is 255.255.255.0, then it is using the first three octets
-    (24 bits) to specify the network number. If the netmask is 255.255.255.240,
-    it would be using the first 28 bits.  Prefixes longer than 24 bits are
-    commonly used by DSL and cable-based Internet Service Providers (ISPs).
-    In this example (PREFIX=24), the netmask is 255.255.255.0. Adjust the
-    <envar>PREFIX</envar> variable according to your specific subnet.</para>
-
-  </sect2>
-
-  <sect2 id="resolv.conf">
-    <title>Creating the /etc/resolv.conf File</title>
-
-    <indexterm zone="resolv.conf">
-      <primary sortas="e-/etc/resolv.conf">/etc/resolv.conf</primary>
-    </indexterm>
-
-    <para>If the system is going to be connected to the Internet, it will
-    need some means of Domain Name Service (DNS) name resolution to
-    resolve Internet domain names to IP addresses, and vice versa. This is
-    best achieved by placing the IP address of the DNS server, available
-    from the ISP or network administrator, into
-    <filename>/etc/resolv.conf</filename>. Create the file by running the
-    following:</para>
-
-<screen><userinput>cat &gt; /etc/resolv.conf &lt;&lt; "EOF"
-<literal># Begin /etc/resolv.conf
-
-domain <replaceable>&lt;Your Domain Name&gt;</replaceable>
-nameserver <replaceable>&lt;IP address of your primary nameserver&gt;</replaceable>
-nameserver <replaceable>&lt;IP address of your secondary nameserver&gt;</replaceable>
-
-# End /etc/resolv.conf</literal>
-EOF</userinput></screen>
-
-    <para>Replace <replaceable>&lt;IP address of the nameserver&gt;</replaceable>
-    with the IP address of the DNS most appropriate for the setup. There will
-    often be more than one entry (requirements demand secondary servers for
-    fallback capability). If you only need or want one DNS server, remove the
-    second <emphasis>nameserver</emphasis> line from the file. The IP address
-    may also be a router on the local network.</para>
-
-  </sect2>
-
-</sect1>
diff -Naur BOOK/chapter07/.svn/text-base/profile.xml.svn-base BOOKfr/chapter07/.svn/text-base/profile.xml.svn-base
--- BOOK/chapter07/.svn/text-base/profile.xml.svn-base	2008-07-15 00:49:41.000000000 +0100
+++ BOOKfr/chapter07/.svn/text-base/profile.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,164 +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-scripts-profile">
-  <?dbhtml filename="profile.html"?>
-
-  <title>The Bash Shell Startup Files</title>
-
-  <indexterm zone="ch-scripts-profile">
-    <primary sortas="e-/etc/profile">/etc/profile</primary>
-  </indexterm>
-
-  <para>The shell program <command>/bin/bash</command> (hereafter referred to
-  as <quote>the shell</quote>) uses a collection of startup files to help
-  create an environment to run in. Each file has a specific use and may affect
-  login and interactive environments differently. The files in the <filename
-  class="directory">/etc</filename> directory provide global settings. If an
-  equivalent file exists in the home directory, it may override the global
-  settings.</para>
-
-  <para>An interactive login shell is started after a successful login, using
-  <command>/bin/login</command>, by reading the <filename>/etc/passwd</filename>
-  file. An interactive non-login shell is started at the command-line (e.g.,
-  <prompt>[prompt]$</prompt><command>/bin/bash</command>). A non-interactive
-  shell is usually present when a shell script is running. It is non-interactive
-  because it is processing a script and not waiting for user input between
-  commands.</para>
-
-  <para>For more information, see <command>info bash</command> under the
-  <emphasis>Bash Startup Files and Interactive Shells</emphasis> section.</para>
-
-  <para>The files <filename>/etc/profile</filename> and
-  <filename>~/.bash_profile</filename> are read when the shell is
-  invoked as an interactive login shell.</para>
-
-  <para>The base <filename>/etc/profile</filename> below sets some
-  environment variables necessary for native language support. Setting
-  them properly results in:</para>
-
-  <itemizedlist>
-    <listitem>
-      <para>The output of programs translated into the native language</para>
-    </listitem>
-    <listitem>
-      <para>Correct classification of characters into letters, digits and other
-      classes. This is necessary for <command>bash</command> to properly accept
-      non-ASCII characters in command lines in non-English locales</para>
-    </listitem>
-    <listitem>
-      <para>The correct alphabetical sorting order for the country</para>
-    </listitem>
-    <listitem>
-      <para>Appropriate default paper size</para>
-    </listitem>
-    <listitem>
-      <para>Correct formatting of monetary, time, and date values</para>
-    </listitem>
-  </itemizedlist>
-
-  <para>Replace <replaceable>&lt;ll&gt;</replaceable> below with the two-letter code
-  for the desired language (e.g., <quote>en</quote>) and
-  <replaceable>&lt;CC&gt;</replaceable> with the two-letter code for the appropriate
-  country (e.g., <quote>GB</quote>). <replaceable>&lt;charmap&gt;</replaceable> should
-  be replaced with the canonical charmap for your chosen locale. Optional
-  modifiers such as <quote>@euro</quote> may also be present.</para>
-
-  <para>The list of all locales supported by Glibc can be obtained by running
-  the following command:</para>
-
-<screen role="nodump"><userinput>locale -a</userinput></screen>
-
-  <para>Charmaps can have a number of aliases, e.g., <quote>ISO-8859-1</quote>
-  is also referred to as <quote>iso8859-1</quote> and <quote>iso88591</quote>.
-  Some applications cannot handle the various synonyms correctly (e.g., require
-  that <quote>UTF-8</quote> is written as <quote>UTF-8</quote>, not
-  <quote>utf8</quote>), so it is safest in most
-  cases to choose the canonical name for a particular locale. To determine
-  the canonical name, run the following command, where <replaceable>&lt;locale
-  name&gt;</replaceable> is the output given by <command>locale -a</command> for
-  your preferred locale (<quote>en_GB.iso88591</quote> in our example).</para>
-
-<screen role="nodump"><userinput>LC_ALL=<replaceable>&lt;locale name&gt;</replaceable> locale charmap</userinput></screen>
-
-  <para>For the <quote>en_GB.iso88591</quote> locale, the above command
-  will print:</para>
-
-<screen><computeroutput>ISO-8859-1</computeroutput></screen>
-
-  <para>This results in a final locale setting of <quote>en_GB.ISO-8859-1</quote>.
-  It is important that the locale found using the heuristic above is tested prior
-  to it being added to the Bash startup files:</para>
-
-<screen role="nodump"><userinput>LC_ALL=&lt;locale name&gt; locale language
-LC_ALL=&lt;locale name&gt; locale charmap
-LC_ALL=&lt;locale name&gt; locale int_curr_symbol
-LC_ALL=&lt;locale name&gt; locale int_prefix</userinput></screen>
-
-  <para>The above commands should print the language name, the character
-  encoding used by the locale, the local currency, and the prefix to dial
-  before the telephone number in order to get into the country. If any of the
-  commands above fail with a message similar to the one shown below, this means
-  that your locale was either not installed in Chapter 6 or is not supported by
-  the default installation of Glibc.</para>
-
-<screen><computeroutput>locale: Cannot set LC_* to default locale: No such file or directory</computeroutput></screen>
-
-  <para>If this happens, you should either install the desired locale using the
-  <command>localedef</command> command, or consider choosing a different locale.
-  Further instructions assume that there are no such error messages from
-  Glibc.</para>
-
-  <!-- FIXME: the xlib example will became obsolete real soon -->
-  <para>Some packages beyond LFS may also lack support for your chosen locale. One
-  example is the X library (part of the X Window System), which outputs the
-  following error message if the locale does not exactly match one of the character
-  map names in its internal files:</para>
-
-<screen><computeroutput>Warning: locale not supported by Xlib, locale set to C</computeroutput></screen>
-
-  <para>In several cases Xlib expects that the character map will be listed in
-  uppercase notation with canonical dashes. For instance, "ISO-8859-1" rather
-  than "iso88591". It is also  possible to find an appropriate specification by
-  removing the charmap part of the locale specification.  This can be checked
-  by running the <command>locale charmap</command> command in both locales.
-  For example, one would have to change "de_DE.ISO-8859-15@euro" to
-  "de_DE@euro" in order to get this locale recognized by Xlib.</para>
-
-  <para>Other packages can also function incorrectly (but may not necessarily
-  display any error messages) if the locale name does not meet their expectations.
-  In those cases, investigating how other Linux distributions support your locale
-  might provide some useful information.</para>
-
-  <para>Once the proper locale settings have been determined, create the
-  <filename>/etc/profile</filename> file:</para>
-
-<screen><userinput>cat &gt; /etc/profile &lt;&lt; "EOF"
-<literal># Begin /etc/profile
-
-export LANG=<replaceable>&lt;ll&gt;_&lt;CC&gt;.&lt;charmap&gt;&lt;@modifiers&gt;</replaceable>
-
-# End /etc/profile</literal>
-EOF</userinput></screen>
-
-  <para>The <quote>C</quote> (default) and <quote>en_US</quote> (the recommended
-  one for United States English users) locales are different. <quote>C</quote>
-  uses the US-ASCII 7-bit character set, and treats bytes with the high bit set
-  as invalid characters. That's why, e.g., the <command>ls</command> command
-  substitutes them with question marks in that locale. Also, an attempt to send
-  mail with such characters from Mutt or Pine results in non-RFC-conforming
-  messages being sent (the charset in the outgoing mail is indicated as <quote>unknown
-  8-bit</quote>). So you can use the <quote>C</quote> locale only if you are sure that
-  you will never need 8-bit characters.</para>
-
-  <para>UTF-8 based locales are not supported well by many programs. E.g., the
-  <command>watch</command> program displays only ASCII characters in UTF-8
-  locales and has no such restriction in traditional 8-bit locales like en_US.
-  Work is in progress to document and, if possible, fix such problems, see
-  <ulink url="&blfs-root;view/svn/introduction/locale-issues.html"/>.</para>
-
-</sect1>
diff -Naur BOOK/chapter07/.svn/text-base/setclock.xml.svn-base BOOKfr/chapter07/.svn/text-base/setclock.xml.svn-base
--- BOOK/chapter07/.svn/text-base/setclock.xml.svn-base	2008-07-15 00:49:41.000000000 +0100
+++ BOOKfr/chapter07/.svn/text-base/setclock.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,56 +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-scripts-setclock">
-  <?dbhtml filename="setclock.html"?>
-
-  <title>Configuring the setclock Script</title>
-
-  <indexterm zone="ch-scripts-setclock">
-    <primary sortas="d-setclock">setclock</primary>
-  <secondary>configuring</secondary></indexterm>
-
-  <para>The <command>setclock</command> script reads the time from the hardware
-  clock, also known as the BIOS or the Complementary Metal Oxide Semiconductor
-  (CMOS) clock. If the hardware clock is set to UTC, this script will convert the
-  hardware clock's time to the local time using the
-  <filename>/etc/localtime</filename> file (which tells the
-  <command>hwclock</command> program which timezone the user is in). There is no
-  way to detect whether or not the hardware clock is set to UTC, so this
-  needs to be configured manually.</para>
-
-  <para>If you cannot remember whether or not the hardware clock is set to UTC,
-  find out by running the <userinput>hwclock --localtime --show</userinput>
-  command. This will display what the current time is according to the hardware
-  clock. If this time matches whatever your watch says, then the hardware clock is
-  set to local time. If the output from <command>hwclock</command> is not local
-  time, chances are it is set to UTC time. Verify this by adding or subtracting
-  the proper amount of hours for the timezone to the time shown by
-  <command>hwclock</command>. For example, if you are currently in the MST
-  timezone, which is also known as GMT -0700, add seven hours to the local
-  time.</para>
-
-  <para>Change the value of the <envar>UTC</envar> variable below
-  to a value of <parameter>0</parameter> (zero) if the hardware clock
-  is <emphasis>not</emphasis> set to UTC time.</para>
-
-  <para>Create a new file <filename>/etc/sysconfig/clock</filename> by running
-  the following:</para>
-
-<screen><userinput>cat &gt; /etc/sysconfig/clock &lt;&lt; "EOF"
-<literal># Begin /etc/sysconfig/clock
-
-UTC=1
-
-# End /etc/sysconfig/clock</literal>
-EOF</userinput></screen>
-
-  <para>A good hint explaining how to deal with time on LFS is available
-  at <ulink url="&hints-root;time.txt"/>. It explains issues such as
-  time zones, UTC, and the <envar>TZ</envar> environment variable.</para>
-
-</sect1>
diff -Naur BOOK/chapter07/.svn/text-base/symlinks.xml.svn-base BOOKfr/chapter07/.svn/text-base/symlinks.xml.svn-base
--- BOOK/chapter07/.svn/text-base/symlinks.xml.svn-base	2008-07-15 00:49:41.000000000 +0100
+++ BOOKfr/chapter07/.svn/text-base/symlinks.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,153 +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-scripts-symlinks">
-  <?dbhtml filename="symlinks.html"?>
-
-  <title>Creating Custom Symlinks to Devices</title>
-
-  <sect2>
-
-    <title>CD-ROM symlinks</title>
-
-    <para>Some software that you may want to install later (e.g., various
-    media players) expect the <filename class="symlink">/dev/cdrom</filename>
-    and <filename class="symlink">/dev/dvd</filename> symlinks to exist, and
-    to point to a CD-ROM or DVD-ROM device. Also, it may be convenient to put
-    references to those symlinks into <filename>/etc/fstab</filename>. Udev
-    comes with a script that will generate rules files to create these symlinks
-    for you, depending on the capabilities of each device, but you need to
-    decide which of two modes of operation you wish to have the script use.</para>
-
-    <para>First, the script can operate in <quote>by-path</quote> mode (used by
-    default for USB and FireWire devices), where the rules it creates depend on
-    the physical path to the CD or DVD device. Second, it can operate in
-    <quote>by-id</quote> mode (default for IDE and SCSI devices), where the
-    rules it creates depend on identification strings stored in the CD or DVD
-    device itself. The path is determined by Udev's <command>path_id</command>
-    script, and the identification strings are read from the hardware by its
-    <command>ata_id</command> or <command>scsi_id</command> programs, depending
-    on which type of device you have.</para>
-
-    <para>There are advantages to each approach; the correct approach to use
-    will depend on what kinds of device changes may happen. If you expect the
-    physical path to the device (that is, the ports and/or slots that it plugs
-    into) to change, for example because you plan on moving the drive to a
-    different IDE port or a different USB connector, then you should use the
-    <quote>by-id</quote> mode. On the other hand, if you expect the device's
-    identification to change, for example because it may die, and you would
-    replace it with a different device with the same capabilities and which
-    is plugged into the same connectors, then you should use the
-    <quote>by-path</quote> mode.</para>
-
-    <para>If either type of change is possible with your drive, then choose a
-    mode based on the type of change you expect to happen more often.</para>
-
-<!-- If you use by-id mode, the symlinks will survive even the transition
-     to libata for IDE drives, but that is not for the book. -->
-
-    <important><para>External devices (for example, a USB-connected CD drive)
-    should not use by-path persistence, because each time the device is plugged
-    into a new external port, its physical path will change. All
-    externally-connected devices will have this problem if you write Udev rules
-    to recognize them by their physical path; the problem is not limited to CD
-    and DVD drives.</para></important>
-
-    <para>If you wish to see the values that the Udev scripts will use, then
-    for the appropriate CD-ROM device, find the corresponding directory under
-    <filename class="directory">/sys</filename> (e.g., this can be
-    <filename class="directory">/sys/block/hdd</filename>) and
-    run a command similar to the following:</para>
-
-<screen role="nodump"><userinput>udevadm test /sys/block/hdd</userinput></screen>
-
-    <para>Look at the lines containing the output of various *_id programs.
-    The <quote>by-id</quote> mode will use the ID_SERIAL value if it exists and
-    is not empty, otherwise it will use a combination of ID_MODEL and
-    ID_REVISION. The <quote>by-path</quote> mode will use the ID_PATH value.</para>
-
-    <para>If the default mode is not suitable for your situation, then the
-    following modification can be made to the
-    <filename>/etc/udev/rules.d/75-cd-aliases-generator.rules</filename> file,
-    as follows (where <replaceable>mode</replaceable> is one of
-    <quote>by-id</quote> or <quote>by-path</quote>):</para>
-
-<screen role="nodump"><userinput>sed -i -e 's/write_cd_rules/&amp; <replaceable>mode</replaceable>/' \
-    /etc/udev/rules.d/75-cd-aliases-generator.rules</userinput></screen>
-
-    <para>Note that it is not necessary to create the rules files or symlinks
-    at this time, because you have bind-mounted the host's
-    <filename class="directory">/dev</filename> directory into the LFS system,
-    and we assume the symlinks exist on the host. The rules and symlinks will
-    be created the first time you boot your LFS system.</para>
-
-    <para>However, if you have multiple CD-ROM devices, then the symlinks
-    generated at that time may point to different devices than they point to on
-    your host, because devices are not discovered in a predictable order. The
-    assignments created when you first boot the LFS system will be stable, so
-    this is only an issue if you need the symlinks on both systems to point to
-    the same device. If you need that, then inspect (and possibly edit) the
-    generated <filename>/etc/udev/rules.d/70-persistent-cd.rules</filename>
-    file after booting, to make sure the assigned symlinks match what you need.</para>
-
-  </sect2>
-
-  <sect2>
-
-    <title>Dealing with duplicate devices</title>
-
-    <para>As explained in <xref linkend="ch-scripts-udev"/>, the order in
-    which devices with the same function appear in
-    <filename class="directory">/dev</filename> is essentially random.
-    E.g., if you have a USB web camera and a TV tuner, sometimes
-    <filename>/dev/video0</filename> refers to the camera and
-    <filename>/dev/video1</filename> refers to the tuner, and sometimes
-    after a reboot the order changes to the opposite one.
-    For all classes of hardware except sound cards and network cards, this is
-    fixable by creating udev rules for custom persistent symlinks.
-    The case of network cards is covered separately in
-    <xref linkend="ch-scripts-network"/>, and sound card configuration can
-    be found in <ulink url="&blfs-root;">BLFS</ulink>.</para>
-
-    <para>For each of your devices that is likely to have this problem
-    (even if the problem doesn't exist in your current Linux distribution),
-    find the corresponding directory under
-    <filename class="directory">/sys/class</filename> or
-    <filename class="directory">/sys/block</filename>.
-    For video devices, this may be
-    <filename
-    class="directory">/sys/class/video4linux/video<replaceable>X</replaceable></filename>.
-    Figure out the attributes that identify the device uniquely (usually,
-    vendor and product IDs and/or serial numbers work):</para>
-
-<screen role="nodump"><userinput>udevadm info -a -p /sys/class/video4linux/video0</userinput></screen>
-
-    <para>Then write rules that create the symlinks, e.g.:</para>
-
-<screen role="nodump"><userinput>cat &gt; /etc/udev/rules.d/83-duplicate_devs.rules &lt;&lt; "EOF"
-<literal>
-# Persistent symlinks for webcam and tuner
-KERNEL=="video*", ATTRS{idProduct}=="1910", ATTRS{idVendor}=="0d81", \
-    SYMLINK+="webcam"
-KERNEL=="video*", ATTRS{device}=="0x036f", ATTRS{vendor}=="0x109e", \
-    SYMLINK+="tvtuner"
-</literal>
-EOF</userinput></screen>
-
-    <para>The result is that <filename>/dev/video0</filename> and
-    <filename>/dev/video1</filename> devices still refer randomly to the tuner
-    and the web camera (and thus should never be used directly), but there are
-    symlinks <filename>/dev/tvtuner</filename> and
-    <filename>/dev/webcam</filename> that always point to the correct
-    device.</para>
-
-    <para>More information on writing Udev rules can be found in
-    <filename>/usr/share/doc/udev-&udev-version;/index.html</filename>.</para>
-
- </sect2>
-
-</sect1>
diff -Naur BOOK/chapter07/.svn/text-base/sysklogd.xml.svn-base BOOKfr/chapter07/.svn/text-base/sysklogd.xml.svn-base
--- BOOK/chapter07/.svn/text-base/sysklogd.xml.svn-base	2008-07-15 00:49:41.000000000 +0100
+++ BOOKfr/chapter07/.svn/text-base/sysklogd.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,26 +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-scripts-sysklogd">
-  <?dbhtml filename="sysklogd.html"?>
-
-  <title>Configuring the sysklogd Script</title>
-
-  <indexterm zone="ch-scripts-sysklogd">
-    <primary sortas="d-sysklogd">sysklogd</primary>
-    <secondary>configuring</secondary>
-  </indexterm>
-
-  <para>The <filename>sysklogd</filename> script invokes the
-  <command>syslogd</command> program with the <parameter>-m 0</parameter> option.
-  This option turns off the periodic timestamp mark that
-  <command>syslogd</command> writes to the log files every 20 minutes by default.
-  If you want to turn on this periodic timestamp mark, edit the
-  <filename>sysklogd</filename> script and make the changes accordingly. See
-  <userinput>man syslogd</userinput> for more information.</para>
-
-</sect1>
diff -Naur BOOK/chapter07/.svn/text-base/udev.xml.svn-base BOOKfr/chapter07/.svn/text-base/udev.xml.svn-base
--- BOOK/chapter07/.svn/text-base/udev.xml.svn-base	2008-07-15 00:49:41.000000000 +0100
+++ BOOKfr/chapter07/.svn/text-base/udev.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,354 +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-scripts-udev">
-  <?dbhtml filename="udev.html"?>
-
-  <title>Device and Module Handling on an LFS System</title>
-
-  <indexterm zone="ch-scripts-udev">
-    <primary sortas="a-Udev">Udev</primary>
-    <secondary>usage</secondary>
-  </indexterm>
-
-  <para>In <xref linkend="chapter-building-system"/>, we installed the Udev
-  package. Before we go into the details regarding how this works,
-  a brief history of previous methods of handling devices is in
-  order.</para>
-
-  <para>Linux systems in general traditionally use a static device creation
-  method, whereby a great many device nodes are created under <filename
-  class="directory">/dev</filename> (sometimes literally thousands of nodes),
-  regardless of whether the corresponding hardware devices actually exist. This
-  is typically done via a <command>MAKEDEV</command> script, which contains a
-  number of calls to the <command>mknod</command> program with the relevant
-  major and minor device numbers for every possible device that might exist in
-  the world.</para>
-
-  <para>Using the Udev method, only those devices which are detected by the
-  kernel get device nodes created for them. Because these device nodes will be
-  created each time the system boots, they will be stored on a <systemitem
-  class="filesystem">tmpfs</systemitem> file system (a virtual file system that
-  resides entirely in system memory). Device nodes do not require much space, so
-  the memory that is used is negligible.</para>
-
-  <sect2>
-    <title>History</title>
-
-    <para>In February 2000, a new filesystem called <systemitem
-    class="filesystem">devfs</systemitem> was merged into the 2.3.46 kernel
-    and was made available during the 2.4 series of stable kernels. Although
-    it was present in the kernel source itself, this method of creating devices
-    dynamically never received overwhelming support from the core kernel
-    developers.</para>
-
-    <para>The main problem with the approach adopted by <systemitem
-    class="filesystem">devfs</systemitem> was the way it handled device
-    detection, creation, and naming. The latter issue, that of device node
-    naming, was perhaps the most critical. It is generally accepted that if
-    device names are allowed to be configurable, then the device naming policy
-    should be up to a system administrator, not imposed on them by any
-    particular developer(s). The <systemitem
-    class="filesystem">devfs</systemitem> file system also suffers from race
-    conditions that are inherent in its design and cannot be fixed without a
-    substantial revision to the kernel. It was marked as deprecated for a long
-    period &ndash; due to a lack of maintenance &ndash; and was finally removed
-    from the kernel in June, 2006.</para>
-
-    <para>With the development of the unstable 2.5 kernel tree, later released
-    as the 2.6 series of stable kernels, a new virtual filesystem called
-    <systemitem class="filesystem">sysfs</systemitem> came to be. The job of
-    <systemitem class="filesystem">sysfs</systemitem> is to export a view of
-    the system's hardware configuration to userspace processes. With this
-    userspace-visible representation, the possibility of seeing a userspace
-    replacement for <systemitem class="filesystem">devfs</systemitem> became
-    much more realistic.</para>
-
-  </sect2>
-
-  <sect2>
-    <title>Udev Implementation</title>
-
-    <sect3>
-      <title>Sysfs</title>
-
-      <para>The <systemitem class="filesystem">sysfs</systemitem> filesystem was
-      mentioned briefly above. One may wonder how <systemitem
-      class="filesystem">sysfs</systemitem> knows about the devices present on
-      a system and what device numbers should be used for them. Drivers that
-      have been compiled into the kernel directly register their objects with
-      <systemitem class="filesystem">sysfs</systemitem> as they are detected by
-      the kernel. For drivers compiled as modules, this registration will happen
-      when the module is loaded. Once the <systemitem
-      class="filesystem">sysfs</systemitem> filesystem is mounted (on <filename
-      class="directory">/sys</filename>), data which the built-in drivers
-      registered with <systemitem class="filesystem">sysfs</systemitem> are
-      available to userspace processes and to <command>udevd</command> for device
-      node creation.</para>
-
-    </sect3>
-
-    <sect3>
-      <title>Udev Bootscript</title>
-
-      <para>The <command>S10udev</command> initscript takes care of creating
-      device nodes when Linux is booted. The script unsets the uevent handler
-      from the default of <command>/sbin/hotplug</command>.  This is done
-      because the kernel no longer needs to call out to an external binary.
-      Instead <command>udevd</command> will listen on a netlink socket for
-      uevents that the kernel raises. Next, the bootscript copies any static
-      device nodes that exist in <filename
-      class="directory">/lib/udev/devices</filename> to <filename
-      class="directory">/dev</filename>. This is necessary because some devices,
-      directories, and symlinks are needed before the dynamic device handling
-      processes are available during the early stages of booting a system, or
-      are required by <command>udevd</command> itself.  Creating static device
-      nodes in <filename class="directory">/lib/udev/devices</filename> also
-      provides an easy workaround for devices that are not supported by the
-      dynamic device handling infrastructure. The bootscript then starts the
-      Udev daemon, <command>udevd</command>, which will act on any uevents it
-      receives. Finally, the bootscript forces the kernel to replay uevents for
-      any devices that have already been registered and then waits for
-      <command>udevd</command> to handle them.</para>
-
-    </sect3>
-
-    <sect3>
-      <title>Device Node Creation</title>
-
-      <para>To obtain the right major and minor number for a device, Udev relies
-      on the information provided by <systemitem
-      class="filesystem">sysfs</systemitem> in <filename
-      class="directory">/sys</filename>.  For example,
-      <filename>/sys/class/tty/vcs/dev</filename> contains the string
-      <quote>7:0</quote>. This string is used by <command>udevd</command>
-      to create a device node with major number <emphasis>7</emphasis> and minor
-      <emphasis>0</emphasis>. The names and permissions of the nodes created
-      under the <filename class="directory">/dev</filename> directory are
-      determined by rules specified in the files within the <filename
-      class="directory">/etc/udev/rules.d/</filename> directory. These are
-      numbered in a similar fashion to the LFS-Bootscripts package. If
-      <command>udevd</command> can't find a rule for the device it is creating,
-      it will default permissions to <emphasis>660</emphasis> and ownership to
-      <emphasis>root:root</emphasis>. Documentation on the syntax of the Udev
-      rules configuration files are available in
-      <filename>/usr/share/doc/udev-&udev-version;/index.html</filename></para>
-
-    </sect3>
-
-    <sect3>
-      <title>Module Loading</title>
-
-      <para>Device drivers compiled as modules may have aliases built into them.
-      Aliases are visible in the output of the <command>modinfo</command>
-      program and are usually related to the bus-specific identifiers of devices
-      supported by a module. For example, the <emphasis>snd-fm801</emphasis>
-      driver supports PCI devices with vendor ID 0x1319 and device ID 0x0801,
-      and has an alias of <quote>pci:v00001319d00000801sv*sd*bc04sc01i*</quote>.
-      For most devices, the bus driver exports the alias of the driver that
-      would handle the device via <systemitem
-      class="filesystem">sysfs</systemitem>. E.g., the
-      <filename>/sys/bus/pci/devices/0000:00:0d.0/modalias</filename> file
-      might contain the string
-      <quote>pci:v00001319d00000801sv00001319sd00001319bc04sc01i00</quote>.
-      The default rules provided with Udev will cause <command>udevd</command>
-      to call out to <command>/sbin/modprobe</command> with the contents of the
-      <envar>MODALIAS</envar> uevent environment variable (which should be the
-      same as the contents of the <filename>modalias</filename> file in sysfs),
-      thus loading all modules whose aliases match this string after wildcard
-      expansion.</para>
-
-      <para>In this example, this means that, in addition to
-      <emphasis>snd-fm801</emphasis>, the obsolete (and unwanted)
-      <emphasis>forte</emphasis> driver will be loaded if it is
-      available. See below for ways in which the loading of unwanted drivers can
-      be prevented.</para>
-
-      <para>The kernel itself is also able to load modules for network
-      protocols, filesystems and NLS support on demand.</para>
-
-    </sect3>
-
-    <sect3>
-      <title>Handling Hotpluggable/Dynamic Devices</title>
-
-      <para>When you plug in a device, such as a Universal Serial Bus (USB) MP3
-      player, the kernel recognizes that the device is now connected and
-      generates a uevent. This uevent is then handled by
-      <command>udevd</command> as described above.</para>
-
-    </sect3>
-
-  </sect2>
-
-  <sect2>
-    <title>Problems with Loading Modules and Creating Devices</title>
-
-    <para>There are a few possible problems when it comes to automatically
-    creating device nodes.</para>
-
-    <sect3>
-      <title>A kernel module is not loaded automatically</title>
-
-      <para>Udev will only load a module if it has a bus-specific alias and the
-      bus driver properly exports the necessary aliases to <systemitem
-      class="filesystem">sysfs</systemitem>. In other cases, one should
-      arrange module loading by other means. With Linux-&linux-version;, Udev is
-      known to load properly-written drivers for INPUT, IDE, PCI, USB, SCSI,
-      SERIO and FireWire devices.</para>
-
-      <para>To determine if the device driver you require has the necessary
-      support for Udev, run <command>modinfo</command> with the module name as
-      the argument.  Now try locating the device directory under
-      <filename class="directory">/sys/bus</filename> and check whether there is
-      a <filename>modalias</filename> file there.</para>
-
-      <para>If the <filename>modalias</filename> file exists in <systemitem
-      class="filesystem">sysfs</systemitem>, the driver supports the device and
-      can talk to it directly, but doesn't have the alias, it is a bug in the
-      driver. Load the driver without the help from Udev and expect the issue
-      to be fixed later.</para>
-
-      <para>If there is no <filename>modalias</filename> file in the relevant
-      directory under <filename class="directory">/sys/bus</filename>, this
-      means that the kernel developers have not yet added modalias support to
-      this bus type. With Linux-&linux-version;, this is the case with ISA
-      busses. Expect this issue to be fixed in later kernel versions.</para>
-
-      <para>Udev is not intended to load <quote>wrapper</quote> drivers such as
-      <emphasis>snd-pcm-oss</emphasis> and non-hardware drivers such as
-      <emphasis>loop</emphasis> at all.</para>
-
-    </sect3>
-
-    <sect3>
-      <title>A kernel module is not loaded automatically, and Udev is not
-      intended to load it</title>
-
-      <para>If the <quote>wrapper</quote> module only enhances the functionality
-      provided by some other module (e.g., <emphasis>snd-pcm-oss</emphasis>
-      enhances the functionality of <emphasis>snd-pcm</emphasis> by making the
-      sound cards available to OSS applications), configure
-      <command>modprobe</command> to load the wrapper after Udev loads the
-      wrapped module. To do this, add an <quote>install</quote> line in
-      <filename>/etc/modprobe.conf</filename>. For example:</para>
-
-<screen role="nodump"><literal>install snd-pcm /sbin/modprobe -i snd-pcm ; \
-    /sbin/modprobe snd-pcm-oss ; true</literal></screen>
-
-      <para>If the module in question is not a wrapper and is useful by itself,
-      configure the <command>S05modules</command> bootscript to load this
-      module on system boot. To do this, add the module name to the
-      <filename>/etc/sysconfig/modules</filename> file on a separate line.
-      This works for wrapper modules too, but is suboptimal in that case.</para>
-
-    </sect3>
-
-    <sect3>
-      <title>Udev loads some unwanted module</title>
-
-      <para>Either don't build the module, or blacklist it in
-      <filename>/etc/modprobe.conf</filename> file as done with the
-      <emphasis>forte</emphasis> module in the example below:</para>
-
-<screen role="nodump"><literal>blacklist forte</literal></screen>
-
-      <para>Blacklisted modules can still be loaded manually with the
-      explicit <command>modprobe</command> command.</para>
-
-    </sect3>
-
-    <sect3>
-      <title>Udev creates a device incorrectly, or makes a wrong symlink</title>
-
-      <para>This usually happens if a rule unexpectedly matches a device. For
-      example, a poorly-writen rule can match both a SCSI disk (as desired)
-      and the corresponding SCSI generic device (incorrectly) by vendor.
-      Find the offending rule and make it more specific, with the help of the
-      <command>udevadm info</command> command.</para>
-
-    </sect3>
-
-    <sect3>
-      <title>Udev rule works unreliably</title>
-
-      <para>This may be another manifestation of the previous problem. If not,
-      and your rule uses <systemitem class="filesystem">sysfs</systemitem>
-      attributes, it may be a kernel timing issue, to be fixed in later kernels.
-      For now, you can work around it by creating a rule that waits for the used
-      <systemitem class="filesystem">sysfs</systemitem> attribute and appending
-      it to the <filename>/etc/udev/rules.d/10-wait_for_sysfs.rules</filename>
-      file (create this file if it does not exist). Please notify the LFS
-      Development list if you do so and it helps.</para>
-
-    </sect3>
-
-    <sect3>
-      <title>Udev does not create a device</title>
-
-      <para>Further text assumes that the driver is built statically into the
-      kernel or already loaded as a module, and that you have already checked
-      that Udev doesn't create a misnamed device.</para>
-
-      <para>Udev has no information needed to create a device node if a kernel
-      driver does not export its data to <systemitem
-      class="filesystem">sysfs</systemitem>.
-      This is most common with third party drivers from outside the kernel
-      tree. Create a static device node in
-      <filename>/lib/udev/devices</filename> with the appropriate major/minor
-      numbers (see the file <filename>devices.txt</filename> inside the kernel
-      documentation or the documentation provided by the third party driver
-      vendor). The static device node will be copied to
-      <filename class="directory">/dev</filename> by the
-      <command>S10udev</command> bootscript.</para>
-
-    </sect3>
-
-    <sect3>
-      <title>Device naming order changes randomly after rebooting</title>
-
-      <para>This is due to the fact that Udev, by design, handles uevents and
-      loads modules in parallel, and thus in an unpredictable order. This will
-      never be <quote>fixed</quote>. You should not rely upon the kernel device
-      names being stable. Instead, create your own rules that make symlinks with
-      stable names based on some stable attributes of the device, such as a
-      serial number or the output of various *_id utilities installed by Udev.
-      See <xref linkend="ch-scripts-symlinks"/> and
-      <xref linkend="ch-scripts-network"/> for examples.</para>
-
-    </sect3>
-
-  </sect2>
-
-  <sect2>
-    <title>Useful Reading</title>
-
-    <para>Additional helpful documentation is available at the following
-    sites:</para>
-
-    <itemizedlist>
-
-      <listitem>
-        <para>A Userspace Implementation of <systemitem class="filesystem">devfs</systemitem>
-        <ulink url="http://www.kroah.com/linux/talks/ols_2003_udev_paper/Reprint-Kroah-Hartman-OLS2003.pdf"/></para>
-      </listitem>
-
-      <listitem>
-        <para>udev FAQ
-        <ulink url="http://www.kernel.org/pub/linux/utils/kernel/hotplug/udev-FAQ"/></para>
-      </listitem>
-
-      <listitem>
-        <para>The <systemitem class="filesystem">sysfs</systemitem> Filesystem
-        <ulink url="http://www.kernel.org/pub/linux/kernel/people/mochel/doc/papers/ols-2005/mochel.pdf"/></para>
-      </listitem>
-
-    </itemizedlist>
-
-  </sect2>
-
-</sect1>
diff -Naur BOOK/chapter07/.svn/text-base/usage.xml.svn-base BOOKfr/chapter07/.svn/text-base/usage.xml.svn-base
--- BOOK/chapter07/.svn/text-base/usage.xml.svn-base	2008-07-15 00:49:41.000000000 +0100
+++ BOOKfr/chapter07/.svn/text-base/usage.xml.svn-base	1970-01-01 01:00:00.000000000 +0100
@@ -1,129 +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-scripts-usage">
-  <?dbhtml filename="usage.html"?>
-
-  <title>How Do These Bootscripts Work?</title>
-
-  <indexterm zone="ch-scripts-usage">
-    <primary sortas="a-Bootscripts">Bootscripts</primary>
-    <secondary>usage</secondary>
-  </indexterm>
-
-  <para>Linux uses a special booting facility named SysVinit that is based on a
-  concept of <emphasis>run-levels</emphasis>. It can be quite different from one
-  system to another, so it cannot be assumed that because things worked in one
-  particular Linux distribution, they should work the same in LFS too. LFS has its
-  own way of doing things, but it respects generally accepted standards.</para>
-
-  <para>SysVinit (which will be referred to as <quote>init</quote> from now on)
-  works using a run-levels scheme. There are seven (numbered 0 to 6) run-levels
-  (actually, there are more run-levels, but they are for special cases and are
-  generally not used. See <filename>init(8)</filename> for more details), and
-  each one of those corresponds to the actions the computer is supposed to
-  perform when it starts up. The default run-level is 3. Here are the
-  descriptions of the different run-levels as they are 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 <command>xdm</command> or KDE's <command>kdm</command>)
-6: reboot the computer</literallayout>
-
-  <para>The command used to change run-levels is <command>init
-  <replaceable>&lt;runlevel&gt;</replaceable></command>, where
-  <replaceable>&lt;runlevel&gt;</replaceable> is the target run-level. For example, to
-  reboot the computer, a user could issue the <command>init 6</command> command,
-  which is an alias for the <command>reboot</command> command. Likewise,
-  <command>init 0</command> is an alias for the <command>halt</command>
-  command.</para>
-
-  <para>There are a number of directories under <filename
-  class="directory">/etc/rc.d</filename> that look like <filename
-  class="directory">rc?.d</filename> (where ? is the number of the run-level) and
-  <filename class="directory">rcsysinit.d</filename>, all containing a number of
-  symbolic links. Some begin with a <emphasis>K</emphasis>, the others begin with
-  an <emphasis>S</emphasis>, and all of them have two 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&mdash;the lower the number the earlier it gets executed. When
-  <command>init</command> switches to another run-level, the appropriate services
-  are either started or stopped, depending on the runlevel chosen.</para>
-
-  <para>The real scripts are in <filename
-  class="directory">/etc/rc.d/init.d</filename>. They do the actual work, and
-  the symlinks all point to them. Killing links and starting links point to
-  the same script in <filename class="directory">/etc/rc.d/init.d</filename>.
-  This is because the scripts can be called with different parameters like
-  <parameter>start</parameter>, <parameter>stop</parameter>,
-  <parameter>restart</parameter>, <parameter>reload</parameter>, and
-  <parameter>status</parameter>. When a K link is encountered, the appropriate
-  script is run with the <parameter>stop</parameter> argument. When an S link
-  is encountered, the appropriate script is run with the
-  <parameter>start</parameter> argument.</para>
-
-  <para>There is one exception to this explanation. Links that start
-  with an <emphasis>S</emphasis> in the <filename
-  class="directory">rc0.d</filename> and <filename
-  class="directory">rc6.d</filename> directories will not cause anything
-  to be started. They will be called with the parameter
-  <parameter>stop</parameter> to stop something. The logic behind this
-  is that when a user is going to reboot or halt the system, nothing
-  needs to be started.  The system only needs to be stopped.</para>
-
-  <para>These are descriptions of what the arguments make the scripts
-  do:</para>
-
-  <variablelist>
-
-    <varlistentry>
-      <term><parameter>start</parameter></term>
-      <listitem>
-        <para>The service is started.</para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><parameter>stop</parameter></term>
-      <listitem>
-        <para>The service is stopped.</para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><parameter>restart</parameter></term>
-      <listitem>
-        <para>The service is stopped and then started again.</para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><parameter>reload</parameter></term>
-      <listitem>
-        <para>The configuration of the service is updated.
-        This is used after the configuration file of a service was modified, when
-        the service does not need to be restarted.</para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term><parameter>status</parameter></term>
-      <listitem>
-        <para>Tells if the service is running and with which PIDs.</para>
-      </listitem>
-    </varlistentry>
-
-  </variablelist>
-
-  <para>Feel free to modify the way the boot process works (after all,
-  it is your own LFS system). The files given here are an example of how
-  it can be done.</para>
-
-</sect1>
diff -Naur BOOK/chapter07/CVS/Entries BOOKfr/chapter07/CVS/Entries
--- BOOK/chapter07/CVS/Entries	1970-01-01 01:00:00.000000000 +0100
+++ BOOKfr/chapter07/CVS/Entries	2008-07-14 19:36:08.000000000 +0100
@@ -0,0 +1,16 @@
+/loadkeys.xml/1.11/Tue Jun 24 17:07:44 2008//
+/bootscripts.xml/1.7/Tue Jul  1 22:56:35 2008//
+/console.xml/1.7/Tue Jul  1 23:39:21 2008//
+/hosts.xml/1.17/Tue Jul  1 22:58:59 2008//
+/introduction.xml/1.12/Tue Jul  1 22:50:43 2008//
+/network.xml/1.16/Wed Jul  2 00:36:30 2008//
+/profile.xml/1.6/Tue Jul  1 23:31:47 2008//
+/setclock.xml/1.14/Tue Jul  1 23:34:09 2008//
+/symlinks.xml/1.2/Wed Jul  2 01:11:13 2008//
+/sysklogd.xml/1.10/Tue Jul  1 23:40:55 2008//
+/udev.xml/1.5/Wed Jul  2 00:57:04 2008//
+/usage.xml/1.19/Tue Jul  1 23:02:37 2008//
+/chapter07.xml/1.10/Tue Jul  1 22:47:52 2008//
+/hostname.xml/1.8/Sun Jun 22 19:37:07 2008//
+/inputrc.xml/1.4/Tue Jul  1 23:03:47 2008//
+D
diff -Naur BOOK/chapter07/CVS/Repository BOOKfr/chapter07/CVS/Repository
--- BOOK/chapter07/CVS/Repository	1970-01-01 01:00:00.000000000 +0100
+++ BOOKfr/chapter07/CVS/Repository	2008-07-14 18:47:59.000000000 +0100
@@ -0,0 +1 @@
+lfs/chapter07
diff -Naur BOOK/chapter07/CVS/Root BOOKfr/chapter07/CVS/Root
--- BOOK/chapter07/CVS/Root	1970-01-01 01:00:00.000000000 +0100
+++ BOOKfr/chapter07/CVS/Root	2008-07-14 18:47:59.000000000 +0100
@@ -0,0 +1 @@
+:ext:texou@traduc.org:/var/lib/cvs/lfs
diff -Naur BOOK/chapter07/bootscripts.xml BOOKfr/chapter07/bootscripts.xml
--- BOOK/chapter07/bootscripts.xml	2008-07-15 00:49:41.000000000 +0100
+++ BOOKfr/chapter07/bootscripts.xml	2008-07-01 23:56:35.000000000 +0100
@@ -15,7 +15,6 @@
   </sect1info>
 
   <title>LFS-Bootscripts-&lfs-bootscripts-version;</title>
-
   <indexterm zone="ch-scripts-bootscripts">
     <primary sortas="a-Bootscripts">Bootscripts</primary>
   </indexterm>
@@ -23,8 +22,9 @@
   <sect2 role="package">
     <title/>
 
-    <para>The LFS-Bootscripts package contains a set of scripts to start/stop the
-    LFS system at bootup/shutdown.</para>
+    <para>Le paquet LFS-Bootscripts contient un ensemble de scripts de
+    démarrage pour démarrer/arrêter le système LFS lors de l'amorçage ou
+    de l'arrêt.</para>
 
     <segmentedlist>
       <segtitle>&buildtime;</segtitle>
@@ -39,38 +39,38 @@
   </sect2>
 
   <sect2 role="installation">
-    <title>Installation of LFS-Bootscripts</title>
+    <title>Installation de LFS-Bootscripts</title>
 
-    <para>Install the package:</para>
+    <para>Installez le paquet&nbsp;:</para>
 
 <screen><userinput remap="install">make install</userinput></screen>
 
   </sect2>
 
   <sect2 id="contents-bootscripts" role="content">
-    <title>Contents of LFS-Bootscripts</title>
+    <title>Contenu de LFS-Bootscripts</title>
 
     <segmentedlist>
-      <segtitle>Installed scripts</segtitle>
+      <segtitle>Scripts installés</segtitle>
 
       <seglistitem>
         <seg>checkfs, cleanfs, console, consolelog, functions, halt, ifdown,
         ifup, localnet, modules, mountfs, mountkernfs, network, rc, reboot,
         sendsignals, setclock, static, swap, sysctl, sysklogd, template,
-        udev, and udev_retry</seg>
+        udev et udev_retry</seg>
       </seglistitem>
     </segmentedlist>
 
     <variablelist>
-      <bridgehead renderas="sect3">Short Descriptions</bridgehead>
+      <bridgehead renderas="sect3">Descriptions courtes</bridgehead>
       <?dbfo list-presentation="list"?>
       <?dbhtml list-presentation="table"?>
 
       <varlistentry id="checkfs-bootscripts">
         <term><command>checkfs</command></term>
         <listitem>
-          <para>Checks the integrity of the file systems before they are mounted
-          (with the exception of journal and network based file systems)</para>
+          <para>Vérifie l'intégrité des systèmes de fichiers avant de les monter (avec
+          l'exception des systèmes de fichiers journalisés ou réseau)</para>
           <indexterm zone="ch-scripts-bootscripts checkfs-bootscripts">
             <primary sortas="d-checkfs">checkfs</primary>
           </indexterm>
@@ -80,12 +80,12 @@
       <varlistentry id="cleanfs-bootscripts">
         <term><command>cleanfs</command></term>
         <listitem>
-          <para>Removes files that should not be preserved between reboots, such
-          as those in <filename class="directory">/var/run/</filename> and
-          <filename class="directory">/var/lock/</filename>; it re-creates
-          <filename>/var/run/utmp</filename> and removes the possibly present
-          <filename>/etc/nologin</filename>, <filename>/fastboot</filename>, and
-          <filename>/forcefsck</filename> files</para>
+          <para>Supprime les fichiers qui ne devraient pas être conservés après un
+          redémarrage, tels que ceux compris dans <filename class="directory">/var/run/</filename>
+          et <filename class="directory">/var/lock/</filename>&nbsp;; il re-crée
+          <filename>/var/run/utmp</filename> et supprime les fichiers
+          <filename>/etc/nologin</filename>, <filename>/fastboot</filename> et
+          <filename>/forcefsck</filename></para>
           <indexterm zone="ch-scripts-bootscripts cleanfs-bootscripts">
             <primary sortas="d-cleanfs">cleanfs</primary>
           </indexterm>
@@ -95,8 +95,8 @@
       <varlistentry id="console-bootscripts">
         <term><command>console</command></term>
         <listitem>
-          <para>Loads the correct keymap table for the desired keyboard layout;
-          it also sets the screen font</para>
+          <para>Charge la bonne table de correspondance du clavier&nbsp;; il
+          initialise aussi la police de l'écran</para>
           <indexterm zone="ch-scripts-bootscripts console-bootscripts">
             <primary sortas="d-console">console</primary>
           </indexterm>
@@ -106,8 +106,8 @@
       <varlistentry id="consolelog-bootscripts">
         <term><command>consolelog</command></term>
         <listitem>
-          <para>Sets the kernel log level to control messages reaching the
-          console.</para>
+          <para>Paramètre le niveau de traçage du noyau pour contrôler 
+          les messages arrivant sur la console.</para>
           <indexterm zone="ch-scripts-bootscripts consolelog-bootscripts">
             <primary sortas="d-consolelog">consolelog</primary>
           </indexterm>
@@ -117,8 +117,8 @@
       <varlistentry id="functions-bootscripts">
         <term><command>functions</command></term>
         <listitem>
-          <para>Contains common functions, such as error and status checking,
-          that are used by several bootscripts</para>
+          <para>Contient des fonctions communes, telles que la vérification d'erreurs et
+          de statuts, utilisées par les différents scripts de démarrage</para>
           <indexterm zone="ch-scripts-bootscripts functions-bootscripts">
             <primary sortas="d-functions">functions</primary>
           </indexterm>
@@ -128,7 +128,7 @@
       <varlistentry id="halt-bootscripts">
         <term><command>halt</command></term>
         <listitem>
-          <para>Halts the system</para>
+          <para>Arrête le système
           <indexterm zone="ch-scripts-bootscripts halt-bootscripts">
             <primary sortas="d-halt">halt</primary>
           </indexterm>
@@ -138,7 +138,7 @@
       <varlistentry id="ifdown-bootscripts">
         <term><command>ifdown</command></term>
         <listitem>
-          <para>Assists the network script with stopping network devices</para>
+          <para>Assiste le script network pour l'arrêt des périphériques réseaux<
           <indexterm zone="ch-scripts-bootscripts ifdown-bootscripts">
             <primary sortas="d-ifdown">ifdown</primary>
           </indexterm>
@@ -148,7 +148,7 @@
       <varlistentry id="ifup-bootscripts">
         <term><command>ifup</command></term>
         <listitem>
-          <para>Assists the network script with starting network devices</para>
+          <para>Assiste le script network pour le démarrage des périphériques réseaux</para>
           <indexterm zone="ch-scripts-bootscripts ifup-bootscripts">
             <primary sortas="d-ifup">ifup</primary>
           </indexterm>
@@ -158,7 +158,8 @@
       <varlistentry id="localnet-bootscripts">
         <term><command>localnet</command></term>
         <listitem>
-          <para>Sets up the system's hostname and local loopback device</para>
+          <para>Configure le nom d'hôte du système et le périphérique de boucle
+          locale</para>
           <indexterm zone="ch-scripts-bootscripts localnet-bootscripts">
             <primary sortas="d-localnet">localnet</primary>
           </indexterm>
@@ -168,9 +169,9 @@
       <varlistentry id="modules-bootscripts">
         <term><command>modules</command></term>
         <listitem>
-          <para>Loads kernel modules listed in
-          <filename>/etc/sysconfig/modules</filename>, using arguments
-          that are also given there</para>
+          <para>Charge les modules du noyau listés dans
+          <filename>/etc/sysconfig/modules</filename>, en utilisant les arguments
+          qui y sont donnés</para>
           <indexterm zone="ch-scripts-bootscripts modules-bootscripts">
             <primary sortas="d-modules">modules</primary>
           </indexterm>
@@ -180,8 +181,8 @@
       <varlistentry id="mountfs-bootscripts">
         <term><command>mountfs</command></term>
         <listitem>
-          <para>Mounts all file systems, except ones that are marked
-          <emphasis>noauto</emphasis> or are network based</para>
+          <para>Monte tous les systèmes de fichiers, sauf ceux marqués
+          <emphasis>noauto</emphasis> ou les systèmes réseaux</para>
           <indexterm zone="ch-scripts-bootscripts mountfs-bootscripts">
             <primary sortas="d-mountfs">mountfs</primary>
           </indexterm>
@@ -191,8 +192,9 @@
       <varlistentry id="mountkernfs-bootscripts">
         <term><command>mountkernfs</command></term>
         <listitem>
-          <para>Mounts virtual kernel file systems, such as <systemitem
-          class="filesystem">proc</systemitem></para>
+          <para>Monte les systèmes de fichiers virtuels fournies par le noyau,
+          tels que
+          <systemitem class="filesystem">proc</systemitem></para>
           <indexterm zone="ch-scripts-bootscripts mountkernfs-bootscripts">
             <primary sortas="d-mountkernfs">mountkernfs</primary>
           </indexterm>
@@ -202,8 +204,8 @@
       <varlistentry id="network-bootscripts">
         <term><command>network</command></term>
         <listitem>
-          <para>Sets up network interfaces, such as network cards, and sets up
-          the default gateway (where applicable)</para>
+          <para>Configure les interfaces réseaux, telles que les cartes réseaux, et
+          configure la passerelle par défaut (lorsque c'est applicable)</para>
           <indexterm zone="ch-scripts-bootscripts network-bootscripts">
             <primary sortas="d-network">network</primary>
           </indexterm>
@@ -213,9 +215,9 @@
       <varlistentry id="rc-bootscripts">
         <term><command>rc</command></term>
         <listitem>
-          <para>The master run-level control script; it is responsible for
-          running all the other bootscripts one-by-one, in a sequence determined
-          by the name of the symbolic links being processed</para>
+          <para>Script de contrôle du niveau d'exécution maître&nbsp;; il est
+          responsable du lancement des autres scripts un par un dans une séquence
+          déterminée par le nom des liens symboliques en cours de traitement</para>
           <indexterm zone="ch-scripts-bootscripts rc-bootscripts">
             <primary sortas="d-rc">rc</primary>
           </indexterm>
@@ -225,7 +227,7 @@
       <varlistentry id="reboot-bootscripts">
         <term><command>reboot</command></term>
         <listitem>
-          <para>Reboots the system</para>
+          <para>Redémarre le système</para>
           <indexterm zone="ch-scripts-bootscripts reboot-bootscripts">
             <primary sortas="d-reboot">reboot</primary>
           </indexterm>
@@ -235,8 +237,8 @@
       <varlistentry id="sendsignals-bootscripts">
         <term><command>sendsignals</command></term>
         <listitem>
-          <para>Makes sure every process is terminated before the system reboots
-          or halts</para>
+          <para>S'assure que chaque processus est terminé avant que le système redémarre
+          ou s'arrête</para>
           <indexterm zone="ch-scripts-bootscripts sendsignals-bootscripts">
             <primary sortas="d-sendsignals">sendsignals</primary>
           </indexterm>
@@ -246,8 +248,8 @@
       <varlistentry id="setclock-bootscripts">
         <term><command>setclock</command></term>
         <listitem>
-          <para>Resets the kernel clock to local time in case the hardware clock
-          is not set to UTC time</para>
+          <para>Réinitialise l'horloge noyau avec l'heure locale au cas où l'horloge
+          matérielle n'est pas en temps UTC</para>
           <indexterm zone="ch-scripts-bootscripts setclock-bootscripts">
             <primary sortas="d-setclock">setclock</primary>
           </indexterm>
@@ -257,8 +259,8 @@
       <varlistentry id="static-bootscripts">
         <term><command>static</command></term>
         <listitem>
-          <para>Provides the functionality needed to assign a static Internet
-          Protocol (IP) address to a network interface</para>
+          <para>Fournit les fonctionnalités nécessaires à l'affectation d'une adresse
+          statique IP (Internet Protocol) vers une interface réseau</para>
           <indexterm zone="ch-scripts-bootscripts static-bootscripts">
             <primary sortas="d-static">static</primary>
           </indexterm>
@@ -268,7 +270,7 @@
       <varlistentry id="swap-bootscripts">
         <term><command>swap</command></term>
         <listitem>
-          <para>Enables and disables swap files and partitions</para>
+          <para>Active et désactive les fichiers swap et les partitions</para>
           <indexterm zone="ch-scripts-bootscripts swap-bootscripts">
             <primary sortas="d-swap">swap</primary>
           </indexterm>
@@ -278,9 +280,9 @@
       <varlistentry id="sysctl-bootscripts">
         <term><command>sysctl</command></term>
         <listitem>
-          <para>Loads system configuration values from
-          <filename>/etc/sysctl.conf</filename>, if that file exists,
-          into the running kernel</para>
+          <para>Charge les valeurs de configuration du système à partir de
+          <filename>/etc/sysctl.conf</filename>, si ce fichier existe, dans le
+          noyau en cours d'exécution</para>
           <indexterm zone="ch-scripts-bootscripts sysctl-bootscripts">
             <primary sortas="d-sysctl">sysctl</primary>
           </indexterm>
@@ -290,7 +292,7 @@
       <varlistentry id="sysklogd-bootscripts">
         <term><command>sysklogd</command></term>
         <listitem>
-          <para>Starts and stops the system and kernel log daemons</para>
+          <para>Lance et arrête les démons des journaux système et noyau</para>
           <indexterm zone="ch-scripts-bootscripts sysklogd-bootscripts">
             <primary sortas="d-sysklogd">sysklogd</primary>
           </indexterm>
@@ -300,8 +302,8 @@
       <varlistentry id="template-bootscripts">
         <term><command>template</command></term>
         <listitem>
-          <para>A template to create custom bootscripts for other
-          daemons</para>
+          <para>Un modèle pour créer des scripts de démarrage personnalisés pour d'autres
+          démons</para>
           <indexterm zone="ch-scripts-bootscripts template-bootscripts">
             <primary sortas="d-template">template</primary>
           </indexterm>
@@ -311,8 +313,8 @@
       <varlistentry id="udev-bootscripts">
         <term><command>udev</command></term>
         <listitem>
-          <para>Prepares the <filename class="directory">/dev</filename>
-          directory and starts Udev</para>
+          <para>Prépare le répertoire <filename class="directory">/dev</filename>
+          et lance Udev</para>
           <indexterm zone="ch-scripts-bootscripts udev-bootscripts">
             <primary sortas="d-udev">udev</primary>
           </indexterm>
@@ -322,9 +324,10 @@
       <varlistentry id="udev-retry-bootscripts">
         <term><command>udev_retry</command></term>
         <listitem>
-          <para>Retries failed udev uevents, and copies generated rules
-          files from <filename class="directory">/dev/.udev</filename> to
-          <filename class="directory">/etc/udev/rules.d</filename> if required</para>
+          <para>Réessaie les uevents udev échoués, et copie les fichiers de 
+          règles générés de 
+          <filename class="directory">/dev/.udev</filename> vers
+          <filename class="directory">/etc/udev/rules.d</filename> si nécessaire</para>
           <indexterm zone="ch-scripts-bootscripts udev-retry-bootscripts">
             <primary sortas="d-udev-retry">udev_retry</primary>
           </indexterm>
diff -Naur BOOK/chapter07/chapter07.xml BOOKfr/chapter07/chapter07.xml
--- BOOK/chapter07/chapter07.xml	2008-07-15 00:49:41.000000000 +0100
+++ BOOKfr/chapter07/chapter07.xml	2008-07-01 23:47:52.000000000 +0100
@@ -9,7 +9,7 @@
   <?dbhtml dir="chapter07"?>
   <?dbhtml filename="chapter07.html"?>
 
-  <title>Setting Up System Bootscripts</title>
+  <title>Initialiser les scripts de démarrage du système</title>
 
   <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="introduction.xml"/>
   <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="bootscripts.xml"/>
diff -Naur BOOK/chapter07/console.xml BOOKfr/chapter07/console.xml
--- BOOK/chapter07/console.xml	2008-07-15 00:49:41.000000000 +0100
+++ BOOKfr/chapter07/console.xml	2008-07-02 00:39:21.000000000 +0100
@@ -8,119 +8,129 @@
 <sect1 id="ch-scripts-console">
   <?dbhtml filename="console.html"?>
 
-  <title>Configuring the Linux Console</title>
+  <title>Configurer la console Linux</title>
 
   <indexterm zone="ch-scripts-console">
     <primary sortas="d-console">console</primary>
-    <secondary>configuring</secondary>
+    <secondary>configuration</secondary>
   </indexterm>
 
   <indexterm zone="ch-scripts-console">
     <primary sortas="d-consolelog">consolelog</primary>
-    <secondary>configuring</secondary>
+    <secondary>configuration</secondary>
   </indexterm>
 
-  <para>This section discusses how to configure the <command>console</command>
-  and <command>consolelog</command> bootscripts that set up the keyboard map,
-  console font and console kernel log level. If non-ASCII characters (e.g.,
-  the copyright sign, the British pound sign and Euro symbol) will not be used
-  and the keyboard is a U.S. one, much of this section can be skipped. Without
-  the configuration file, the <command>console</command> bootscript will do
-  nothing.</para>
-
-  <para>The <command>console</command>  and <command>consolelog</command>
-  script reads the <filename>/etc/sysconfig/console</filename> file for
-  configuration information.
-  Decide which keymap and screen font will be used. Various language-specific
-  HOWTOs can also help with this, see <ulink
-  url="http://www.tldp.org/HOWTO/HOWTO-INDEX/other-lang.html"/>. If still in
-  doubt, look in the <filename class="directory">/lib/kbd</filename>
-  directory for valid keymaps and screen fonts. Read
-  <filename>loadkeys(1)</filename> and <filename>setfont(8)</filename> manual
-  pages to determine the correct arguments for these programs.</para>
-
-  <para>The <filename>/etc/sysconfig/console</filename> file should contain lines
-  of the form: VARIABLE="value". The following variables are recognized:</para>
+  <para>Cette section discute de la configuration du script de démarrage
+  <command>console</command>, initialisant le plan de codage du clavier
+  et la police de la console. Si des caractères non ASCII (par exemple,
+  la livre anglaise et le caractère Euro) ne seront pas utilisés et que
+  le clavier est un clavier US, passez cette section. Sans le fichier de
+  configuration, le script de démarrage <command>console</command> ne
+  fera rien.</para>
+
+  <para>Les scripts <command>console</command>  et
+  <command>consolelog</command> lisent le fichier
+  <filename>/etc/sysconfig/console</filename> pour des informations de
+  configuration. Il décide du plan de codage et de la police de la
+  console à utiliser. Différents guides pratiques spécifiques aux
+  langues peuvent aussi être d'une grande aide (voir
+
+  <ulink url="http://www.tldp.org/HOWTO/HOWTO-INDEX/other-lang.html"/>.
+  Si vous avez toujours des doutes, jetez un &oelig;il dans le
+  répertoire
+
+  <filename class="directory">/lib/kbd</filename> pour des plans de
+  codage valides et des polices pour écran. Lisez les pages man de
+  <filename>loadkeys(1)</filename> et de <filename>setfont(8)</filename>
+  pour déterminer les bons arguments pour ces programmes.</para>
+
+  <para>Le fichier <filename>/etc/sysconfig/console</filename> devrait
+  contenir des lignes sous la forme&nbsp;: VARIABLE="valeur". Les
+  variables suivantes sont reconnues&nbsp;:</para>
 
   <variablelist>
 
     <varlistentry>
       <term>LOGLEVEL</term>
       <listitem>
-        <para>This variable specifies the log level for kernel messages sent
-        to the console as set by <command>dmesg</command>. Valid levels are
-        from "1" (no messages) to "8". The default level is "7".</para>
+        <para>Cette variable spécifie le niveau de traçage pour les messages du 
+        noyau envoyés à la console, selon le paramétrage par 
+        <command>dmesg</command>. Les niveaux valides sont de « 1 » (aucun 
+        message) à « 8 ». Le niveau par défaut est « 7 ».</para>
       </listitem>
     </varlistentry>
 
     <varlistentry>
       <term>KEYMAP</term>
       <listitem>
-        <para>This variable specifies the arguments for the
-        <command>loadkeys</command> program, typically, the name of keymap
-        to load, e.g., <quote>es</quote>. If this variable is not set, the
-	bootscript will not run the <command>loadkeys</command> program,
-	and the default kernel keymap will be used.</para>
+        <para>Cette variable spécifie les arguments du programme
+        <command>loadkeys</command>, en général le nom du plan de codage à
+        charger, comme <quote>es</quote>. Si cette variable n'est pas réglée,
+        le script de démarrage ne lancera pas le programme <command>loadkeys</command>,
+	et le plan de codage du noyau par défaut sera utilisé.</para>
       </listitem>
     </varlistentry>
 
     <varlistentry>
       <term>KEYMAP_CORRECTIONS</term>
       <listitem>
-        <para>This (rarely used) variable
-        specifies the arguments for the second call to the
-        <command>loadkeys</command> program. This is useful if the stock keymap
-        is not completely satisfactory and a small adjustment has to be made. E.g.,
-        to include the Euro sign into a keymap that normally doesn't have it,
-        set this variable to <quote>euro2</quote>.</para>
-      </listitem>
-    </varlistentry>
-
-    <varlistentry>
-      <term>FONT</term>
-      <listitem>
-        <para>This variable specifies the arguments for the
-        <command>setfont</command> program. Typically, this includes the font
-        name, <quote>-m</quote>, and the name of the application character
-	map to load. E.g., in order to load the <quote>lat1-16</quote> font
-	together with the <quote>8859-1</quote> application character map
-	(as it is appropriate in the USA), <!-- because of the copyright sign -->
-	set this variable to <quote>lat1-16 -m 8859-1</quote>.
-        If this variable is not set, the bootscript will not run the
-        <command>setfont</command> program, and the default VGA font will be
-        used together with the default application character map.</para>
+        <para>Cette variable (rarement utilisée) spécifie les arguments du
+        second appel au programme <command>loadkeys</command>. C'est
+        utile si le plan de codage stocké n'est pas totalement satisfaisant
+        et que vous devez faire un petit ajustement. Par exemple, pour inclure le
+					signe Euro dans un plan de codage qui ne l'a normalement pas, réglez
+					cette variable à <quote>euro2</quote>.</para>
+				</listitem>
+			</varlistentry>
+
+			<varlistentry>
+				<term>FONT</term>
+				<listitem>
+					<para>Cette variable spécifie les arguments du programme
+					<command>setfont</command>. En principe, ceci inclut le nom de la police,
+					<quote>-m</quote> et le nom du plan de caractères de l'application
+        à charger. Par exemple, pour charger la police <quote>lat1-16</quote>
+        avec le plan de caractère de l'application <quote>8859-1</quote>, (comme
+        il convient aux Etats-Unis),  <!-- because of the copyright sign -->
+	réglez cette variable à <quote>lat1-16 -m 8859-1</quote>.
+        Si cette variable n'est pas réglée, le script de démarrage ne lancera
+        pas le programme <command>setfont</command>, et la police VGA par 
+        défaut sera utilisée avec le plan de caractère de l'application par
+        défaut.</para>
       </listitem>
     </varlistentry>
 
     <varlistentry>
       <term>UNICODE</term>
       <listitem>
-        <para>Set this variable to <quote>1</quote>, <quote>yes</quote> or
-	<quote>true</quote> in order to put the
-        console into UTF-8 mode. This is useful in UTF-8 based locales and
-        harmful otherwise.</para>
+        <para>Règle cette variable à <quote>1</quote>, <quote>yes</quote> ou
+	<quote>true</quote> afin de mettre la console en mode UTF-8. Ceci
+        est utile dans les locales basées sur UTF-8 et sinon difficiles.</para>
       </listitem>
     </varlistentry>
 
     <varlistentry>
       <term>LEGACY_CHARSET</term>
       <listitem>
-        <para>For many keyboard layouts, there is no stock Unicode keymap in
-        the Kbd package. The <command>console</command> bootscript will
-        convert an available keymap to UTF-8 on the fly if this variable is
-	set to the encoding of the available non-UTF-8 keymap.</para>
+        <para>Pour beaucoup de types de clavier, il n'y a pas de plan de codage 
+        pour le stock Unicode dans le paquet Kbd. Le script de démarrage
+
+        <command>console</command> convertira un plan de codage disponible en
+        UTF-8 au vol si cette variable est réglée à l'encodage du plan de codage
+	non UTF-8 disponible.</para>
       </listitem>
     </varlistentry>
 
   </variablelist>
 
-  <para>Some examples:</para>
+  <para>Quelques exemples&nbsp;:</para>
 
   <itemizedlist>
 
     <listitem>
-      <para>For a non-Unicode setup, only the KEYMAP and FONT variables are
-      generally needed. E.g., for a Polish setup, one would use:</para>
+      <para>Pour une initialisation non Unicode, en général seules les
+      variables KEYMAP et FONT sont nécessaires. Par exemple, pour 
+      l'initialisation en polonais, on utiliserait&nbsp;:</para>
 
 <screen role="nodump"><userinput>cat &gt; /etc/sysconfig/console &lt;&lt; "EOF"
 <literal># Begin /etc/sysconfig/console
@@ -133,9 +143,9 @@
     </listitem>
 
     <listitem>
-      <para>As mentioned above, it is sometimes necessary to adjust a
-      stock keymap slightly. The following example adds the Euro symbol to the
-      German keymap:</para>
+      <para>Comme mentioné ci-dessus, il est parfois nécessaire d'ajuster 
+      légèrement un plan de codage stocké. L'exemple suivant ajoute le symbole
+      Euro au plan de codage allemand&nbsp;:</para>
 
 <screen role="nodump"><userinput>cat &gt; /etc/sysconfig/console &lt;&lt; "EOF"
 <literal># Begin /etc/sysconfig/console
@@ -149,8 +159,8 @@
     </listitem>
 
     <listitem>
-      <para>The following is a Unicode-enabled example for Bulgarian, where a
-      stock UTF-8 keymap exists:</para>
+      <para>Ce qui suit est un exemple avec l'Unicode activé pour le bulgare, où
+      un plan de codage UTF-8 stocké existe&nbsp;:</para>
 
 <screen role="nodump"><userinput>cat &gt; /etc/sysconfig/console &lt;&lt; "EOF"
 <literal># Begin /etc/sysconfig/console
@@ -164,12 +174,13 @@
     </listitem>
 
     <listitem>
-      <para>Due to the use of a 512-glyph LatArCyrHeb-16 font in the previous
-      example, bright colors are no longer available on the Linux console unless
-      a framebuffer is used. If one wants to have bright colors without
-      framebuffer and can live without characters not belonging to his language,
-      it is still possible to use a language-specific 256-glyph font, as
-      illustrated below:</para>
+      <para>Du fait de l'utilisation d'une police 512-glyph LatArCyrHeb-16 dans
+      l'exemple précédent, les couleurs brillantes ne sont plus disponibles 
+      sur la console Linux à moins qu'un framebuffer soit utilisé. Si vous
+      voulez avoir les couleurs brillantes sans framebuffer et que vous pouvez
+     vivre sans caractère n'appartenant pas à votre langue, il est encore 
+      possible d'utiliser une police 256-glyph spécifique à votre langue, 
+      comme illustré ci-dessous&nbsp;:</para>
 
 <screen role="nodump"><userinput>cat &gt; /etc/sysconfig/console &lt;&lt; "EOF"
 <literal># Begin /etc/sysconfig/console
@@ -183,9 +194,9 @@
     </listitem>
 
     <listitem>
-      <para>There is no pre-made UTF-8 Russian keymap, therefore it has to be
-      produced by converting the existing KOI8-R keymap as illustrated
-      below:</para>
+      <para>Il n'y a pas de plan de codage russe pour UTF-8 préfabriqué,
+      donc il faut le produire en convertissant le plan de codage existant
+      KOI8-R comme illustré ci-dessous&nbsl;:</para>
 
 <screen role="nodump"><userinput>cat &gt; /etc/sysconfig/console &lt;&lt; "EOF"
 <literal># Begin /etc/sysconfig/console
@@ -200,26 +211,28 @@
     </listitem>
 
     <listitem>
-      <para>Some keymaps have dead keys (i.e., keys that don't produce a
-      character by themselves, but put an accent on the character produced
-      by the next key) or define composition rules (such as: <quote>press
-      Ctrl+. A E to get &AElig;</quote> in the default keymap).
-      Linux-&linux-version; in UTF-8 keyboard mode assumes that accented
-      characters produced via dead keys or composing are in the Latin-1 range
-      of Unicode, and it is impossible to change this assumption. Thus,
-      accented characters needed for, e.g., the Czech language, can't be typed
-      on Linux console in UTF-8 mode (but files containing these characters can
-      be displayed correctly). The solution is either to avoid the use of
-      UTF-8, or to install the X window system that doesn't have this
-      limitation in its input handling.</para>
+      <para>Certains plans de codage ont des touches mortes (par exemple,
+      les touches qui ne produisent pas un caractère en elles-mêmes, mais mettent
+       un accent sur le caractère produit par la touche suivante) ou définissent
+      des règles de comportement (comme&nbsp;: <quote>Appuyez sur Ctrl+. A E pour
+      obtenir &AElig;</quote> dans le plan de codage par défaut).
+      Linux-&linux-version; dans le mode clavier UTF-8 assume que les caractères
+      accentués produit par des touches mortes ou de composition sont dans
+      la série Latin-1 de Unicode, et il est impossible de changer cette
+      suposition). Donc, les caractères accentués nécessaires, comme le Tchèque,
+      ne peuvent être tapés sur la console Linux en mode UTF-8 (mais des fichiers
+      contenant ces caractères peuvent être affichés correctement). La solution
+      est soit d'éviter d'utiliser UTF-8, soit d'installer le X window system
+      qui n'a pas cette limitation dans sa gestion de l'entrée.</para>
     </listitem>
 
     <listitem>
-      <para>For Chinese, Japanese, Korean and some other languages, the Linux
-      console cannot be configured to display the needed characters. Users
-      who need such languages should install the X Window System, fonts that
-      cover the necessary character ranges, and the proper input method (e.g.,
-      SCIM, it supports a wide variety of languages).</para>
+      <para>Pour le Chinois, le Japonais, le Coréen et certaines autres langues,
+      la console Linux ne peut pas être configurée pour afficher les caractères
+      nécessaires. Les utilisateurs qui ont besoin de telles langues devraient
+      installer le X Window System, dont les polices couvrent la plage de 
+      caractères nécessaire et qui a la bonne méthode d'entrée (par exemlle
+      SCIM supporte une large variété de langues).</para>
     </listitem>
 
   </itemizedlist>
@@ -227,10 +240,12 @@
   <!-- Added because folks keep posting their console file with X questions
   to blfs-support list -->
   <note>
-    <para>The <filename>/etc/sysconfig/console</filename> file only controls the    Linux text console localization. It has nothing to do with setting the
-    proper keyboard layout and terminal fonts in the X Window System, with ssh
-    sessions or with a serial console. In such situations, limitations mentioned
-    in the last two list items above do not apply.</para>
+    <para>Le fichier <filename>/etc/sysconfig/console</filename> ne contrôle
+     que la localisation de la console Linux en texte. Cela n'a rien à voir
+     avec le bon paramétrage du type de clavier et des polices du terminal dans
+    le X Window System, avec les sessions ssh ou une console en série. Dans de
+    telles situations, les limitations mentionnées dans les deux derniers points
+    de la liste ci-dessus ne s'appliquent pas.</para>
   </note>
 
 </sect1>
diff -Naur BOOK/chapter07/hostname.xml BOOKfr/chapter07/hostname.xml
--- BOOK/chapter07/hostname.xml	2008-07-15 00:49:41.000000000 +0100
+++ BOOKfr/chapter07/hostname.xml	2008-06-22 20:37:07.000000000 +0100
@@ -8,25 +8,26 @@
 <sect1 id="ch-scripts-hostname">
   <?dbhtml filename="hostname.html"?>
 
-  <title>Configuring the localnet Script</title>
+  <title>Configurer le script localnet</title>
 
   <indexterm zone="ch-scripts-hostname">
     <primary sortas="d-localnet">localnet</primary>
-    <secondary>configuring</secondary>
+    <secondary>configuration</secondary>
   </indexterm>
 
-  <para>Part of the job of the <command>localnet</command> script is setting the
-  system's hostname. This needs to be configured in the
-  <filename>/etc/sysconfig/network</filename> file.</para>
+  <para>Une partie du boulot du script <command>localnet</command>
+   est de configurer le nom du système. Ce nom doit être indiqué dans le fichier
+   <filename>/etc/sysconfig/network</filename>.</para>
 
-  <para>Create the <filename>/etc/sysconfig/network</filename> file and enter a
-  hostname by running:</para>
+  <para>Créez le fichier <filename>/etc/sysconfig/network</filename> et
+  entrez le nom du système en lançant&nbsp;:</para>
 
 <screen><userinput>echo "HOSTNAME=<replaceable>&lt;lfs&gt;</replaceable>" &gt; /etc/sysconfig/network</userinput></screen>
 
-  <para><replaceable>&lt;lfs&gt;</replaceable> needs to be replaced with the name given
-  to the computer. Do not enter the Fully Qualified Domain Name (FQDN) here. That
-  information will be put in the <filename>/etc/hosts</filename> file in the next
-  section.</para>
+  <para><replaceable>&lt;lfs&gt;</replaceable> doit être remplacé par le
+  nom de l'ordinateur. Ne saisissez pas le FQDN (Fully Qualified Domain
+  Name, nom de domaine pleinement qualifié) ici. Cette information sera
+  rentrée dans le fichier <filename>/etc/hosts</filename> dans la
+  prochaine section.</para>
 
 </sect1>
diff -Naur BOOK/chapter07/hosts.xml BOOKfr/chapter07/hosts.xml
--- BOOK/chapter07/hosts.xml	2008-07-15 00:49:41.000000000 +0100
+++ BOOKfr/chapter07/hosts.xml	2008-07-01 23:58:59.000000000 +0100
@@ -8,7 +8,7 @@
 <sect1 id="ch-scripts-hosts">
   <?dbhtml filename="hosts.html"?>
 
-  <title>Customizing the /etc/hosts File</title>
+  <title>Personnaliser le fichier /etc/hosts</title>
 
   <indexterm zone="ch-scripts-hosts">
     <primary sortas="e-/etc/hosts">/etc/hosts</primary>
@@ -22,33 +22,42 @@
     <primary sortas="d-network">network</primary>
   <secondary>/etc/hosts</secondary></indexterm>
 
-  <para>If a network card is to be configured, decide on the IP address,
-  fully-qualified domain name (FQDN), and possible aliases for use in the
-  <filename>/etc/hosts</filename> file. The syntax is:</para>
+  <para>Si une carte réseau doit être configurée, choisissez l'adresse
+  IP, le nom de domaine pleinement qualifié et les alias possibles à
+  déclarer
+
+  dans le fichier <filename>/etc/hosts</filename>. La syntaxe
+  est&nbsp;:</para>
 
 <screen><literal>IP_address myhost.example.org aliases</literal></screen>
 
-  <para>Unless the computer is to be visible to the Internet (i.e.,
-  there is a registered domain and a valid block of assigned IP
-  addresses&mdash;most users do not have this), make sure that the IP
-  address is in the private network IP address range. Valid ranges
-  are:</para>
+  <para>À moins que votre ordinateur ne doit être visible à partir
+  d'Internet (c'est-à-dire que vous avez enregistré un domaine et un
+  bloc valide d'adresses IP qui vous est affecté, la plupart des
+  utilisateurs n'ont pas ceci), vous devez vous assurer que l'adresse IP
+  se trouve dans la plage d'adresses réservée aux réseaux privés. Les
+  plages valides sont&nbsp;:</para>
 
 <screen><literal>Private Network Address Range      Normal Prefix
 10.0.0.1 - 10.255.255.254           8
 172.x.0.1 - 172.x.255.254           16
 192.168.y.1 - 192.168.y.254         24</literal></screen>
 
-  <para>x can be any number in the range 16-31. y can be any number in
-  the range 0-255.</para>
+  <para>x peut être un nombre compris entre 16 et 31. y peut être un nombre
+  comprii entre 0 et 255.</para>
+
+  <para>Une adresse IP valide pourrait être 192.168.1.1. Un nom de
+  domaine
 
-  <para>A valid private IP address could be 192.168.1.1. A valid FQDN for this
-  IP could be lfs.example.org.</para>
+  pleinement qualifié pour cette adresse IP pourrait être
+  lfs.example.org.</para>
 
-  <para>Even if not using a network card, a valid FQDN is still required.
-  This is necessary for certain programs to operate correctly.</para>
+  <para>Même si vous ne possédez pas de carte réseau, un nom de domaine
+  pleinement qualifié est toujours requis. Certains programmes en ont
+  besoin pour fonctionner correctement.</para>
 
-  <para>Create the  <filename>/etc/hosts</filename> file by running:</para>
+  <para>Créez le fichier <filename>/etc/hosts</filename> en
+  lançant&nbsp;:</para>
 
 <screen><userinput>cat &gt; /etc/hosts &lt;&lt; "EOF"
 <literal># Begin /etc/hosts (network card version)
@@ -59,15 +68,25 @@
 # End /etc/hosts (network card version)</literal>
 EOF</userinput></screen>
 
-  <para>The <replaceable>&lt;192.168.1.1&gt;</replaceable> and
-  <replaceable>&lt;HOSTNAME.example.org&gt;</replaceable>
-  values need to be changed for specific users or requirements (if
-  assigned an IP address by a network/system administrator and the
-  machine will be connected to an existing network). The optional alias
-  name(s) can be omitted.</para>
+  <para>Les valeurs <replaceable>&lt;192.168.1.1&gt;</replaceable> et
+  <replaceable>&lt;HOSTNAME.example.org&gt;</replaceable> 
+
+  # Fin de /etc/hosts (version avec carte réseau)
+
+  <userinput>EOF</userinput></screen>
+
+  
+
+  <para>Les valeurs <replaceable>[192.168.1.1]</replaceable> et
+  <replaceable>[&lt;nom d'hôte&gt;.exemple.org]</replaceable> doivent
+  être remplacées suivant les contraintes/besoins des utilisateurs (si
+  la machine se voit affectée une adresse IP par un administrateur
+  réseau/système et que cette machine est connectée à un réseau
+  existant). Vous pouvez ne pas mettre le(s) nom(s) d'alias
+  optionnel(s).</para>
 
-  <para>If a network card is not going to be configured, create the
-  <filename>/etc/hosts</filename> file by running:</para>
+  <para>Si vous n'avez pas de carte réseau, créez le fichier
+  <filename>/etc/hosts</filename> en lançant la commande&nbsp;:</para>
 
 <screen role="nodump"><userinput>cat &gt; /etc/hosts &lt;&lt; "EOF"
 <literal># Begin /etc/hosts (no network card version)
diff -Naur BOOK/chapter07/inputrc.xml BOOKfr/chapter07/inputrc.xml
--- BOOK/chapter07/inputrc.xml	2008-07-15 00:49:41.000000000 +0100
+++ BOOKfr/chapter07/inputrc.xml	2008-07-02 00:03:47.000000000 +0100
@@ -8,30 +8,38 @@
 <sect1 id="ch-scripts-inputrc">
   <?dbhtml filename="inputrc.html"?>
 
-  <title>Creating the /etc/inputrc File</title>
+  <title>Créer le fichier /etc/inputrc</title>
 
   <indexterm zone="ch-scripts-inputrc">
     <primary sortas="e-/etc/inputrc">/etc/inputrc</primary>
   </indexterm>
 
-  <para>The <filename>inputrc</filename> file handles keyboard mapping for
-  specific situations. This file is the startup file used by Readline &mdash; the
-  input-related library &mdash; used by Bash and most other shells.</para>
-
-  <para>Most people do not need user-specific keyboard mappings so the command
-  below creates a global <filename>/etc/inputrc</filename> used by everyone who
-  logs in. If you later decide you need to override the defaults on a per-user
-  basis, you can create a <filename>.inputrc</filename> file in the user's home
-  directory with the modified mappings.</para>
-
-  <para>For more information on how to edit the <filename>inputrc</filename>
-  file, see <command>info bash</command> under the <emphasis>Readline Init
-  File</emphasis> section. <command>info readline</command> is also a good
-  source of information.</para>
-
-  <para>Below is a generic global <filename>inputrc</filename> along with comments
-  to explain what the various options do. Note that comments cannot be on the same
-  line as commands. Create the file using the following command:</para>
+  <para>Le fichier <filename>inputrc</filename> gère les fichiers de
+  correspondance du clavier pour les situations spécifiques. Ce fichier
+  est le fichier de démarrage utilisé par Readline &mdash; la
+  bibliothèque relative aux entrées &mdash; utilisée par Bash et la
+  plupart des autres shells.</para>
+
+  <para>La plupart des personnes n'ont pas besoin de fichiers de
+  correspondance spécifiques, donc la commande ci-dessous crée un
+  fichier <filename>/etc/inputrc</filename> global utilisé par tous ceux
+  qui se connectent. Si vous décidez plus tard que vous avez besoin de
+  surcharger les valeurs par défaut utilisateur par utilisateur, vous
+  pouvez créer un fichier <filename>.inputrc</filename> dans le
+  répertoire personnel de l'utilisateur avec les correspondances
+  modifiées.</para>
+
+  <para>Pour plus d'informations sur l'édition du fichier
+  <filename>inputrc</filename>, voir <command>info bash</command>
+  sous la section <emphasis>Fichier d'initialisation Readline</emphasis>
+  (ou <emphasis>Readline Init File</emphasis>). <command>info
+  readline</command> est aussi une bonne source d'informations.</para>
+
+  <para>Ci-dessous se trouve un fichier <filename>inputrc</filename>
+  générique avec des commentaires expliquant l'utilité des différentes
+  options. Notez que les commentaires ne peuvent pas être sur la même
+  ligne que les commandes. Créez le fichier en utilisant la commande
+  suivante&nbsp;:</para>
 
 <screen><userinput>cat &gt; /etc/inputrc &lt;&lt; "EOF"
 <literal># Begin /etc/inputrc
diff -Naur BOOK/chapter07/introduction.xml BOOKfr/chapter07/introduction.xml
--- BOOK/chapter07/introduction.xml	2008-07-15 00:49:41.000000000 +0100
+++ BOOKfr/chapter07/introduction.xml	2008-07-01 23:50:43.000000000 +0100
@@ -10,18 +10,22 @@
 
   <title>Introduction</title>
 
-  <para>This chapter details how to install and configure the LFS-Bootscripts
-  package. Most of these scripts will work without modification, but a few require
-  additional configuration files because they deal with hardware-dependent
-  information.</para>
+  <para>Ce chapitre montre comment installer et configurer les scripts
+  de démarrag LFS. La plupart de ces scripts fonctionne sans
+  modification mais quelques-uns nécessitent des fichiers de
+  configuration supplémentaires car ils utilisent des informations
+  dépendant du matériel.</para>
 
-  <para>System-V style init scripts are employed in this book because they are
-  widely used. For additional options, a hint detailing the BSD style init setup
-  is available at <ulink url="&hints-root;bsd-init.txt"/>.
-  Searching the LFS mailing lists for <quote>depinit</quote> will also offer
-  additional choices.</para>
+  <para>Les scripts de démarrage compatibles System-V sont utilisés dans
+  ce livre simplement parce qu'ils sont largement utilisés. Pour
+  d'autres options, une astuce détaillant les scripts compatibles BSD
+  est disponible sur
+  <ulink url="&hints-root;bsd-init.txt"/>.
+  Une recherche de <quote>depinit</quote> sur les listes de diffusion LFS
+  offrira des choix supplémentaires.
 
-  <para>If using an alternative style of init scripts, skip this chapter
-  and move on to <xref linkend="chapter-bootable"/>.</para>
+  <para>Si vous utilisez un autre style de scripts de démarrage, passez
+  ce chapitre et allez directement sur le
+  <xref linkend="chapter-bootable"/>.</para>
 
 </sect1>
diff -Naur BOOK/chapter07/loadkeys.xml BOOKfr/chapter07/loadkeys.xml
--- BOOK/chapter07/loadkeys.xml	1970-01-01 01:00:00.000000000 +0100
+++ BOOKfr/chapter07/loadkeys.xml	2008-06-24 18:07:44.000000000 +0100
@@ -0,0 +1,30 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
+"http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
+  <!ENTITY % general-entities SYSTEM "../general.ent">
+  %general-entities;
+]>
+<sect1 id="ch-scripts-loadkeys">
+<title>Besoin du script loadkeys</title>
+<?dbhtml filename="loadkeys.html"?>
+
+<indexterm zone="ch-scripts-loadkeys">
+<primary sortas="d-loadkeys">loadkeys</primary>
+<secondary>configuration</secondary></indexterm>
+
+<para>Si vous pensez compiler le plan de codage directement dans le noyau lors
+du <xref linkend="chapter-bootable"/> (voir <xref linkend="ch-system-kbd"/>),
+alors vous n'avez réellement pas besoin de lancer ce script car le noyau
+initialisera le plan de codage pour vous. Si vous le souhaitez, vous pouvez 
+toujours exécuter le script, cela ne fera aucun mal. Le conserver peut aussi
+être intéressant au cas où vous utilisez un grand nombre de noyaux différents
+et que vous n'êtes pas sûr que le plan de codage soit dans chacun d'entre
+eux.</para>
+
+<para>Si vous décidez que vous n'en avez pas besoin ou que vous ne voulez
+pas utiliser le script loadkeys, supprimez le lien symbolique
+<filename class="symlink">/etc/rc.d/rcsysinit.d/S70loadkeys</filename>.
+</para>
+
+</sect1>
+
diff -Naur BOOK/chapter07/network.xml BOOKfr/chapter07/network.xml
--- BOOK/chapter07/network.xml	2008-07-15 00:49:41.000000000 +0100
+++ BOOKfr/chapter07/network.xml	2008-07-02 01:36:30.000000000 +0100
@@ -8,120 +8,140 @@
 <sect1 id="ch-scripts-network">
   <?dbhtml filename="network.html"?>
 
-  <title>Configuring the network Script</title>
+  <title>Configurer le script network</title>
 
   <indexterm zone="ch-scripts-network">
     <primary sortas="d-network">network</primary>
-  <secondary>configuring</secondary></indexterm>
+  <secondary>configuration</secondary></indexterm>
 
-  <para>This section only applies if a network card is to be
-  configured.</para>
+  <para>Cette section s'applique seulement si une carte réseau doit être
+  configurée.</para>
 
-  <para>If a network card will not be used, there is likely no need to
-  create any configuration files relating to network cards. If that is
-  the case, remove the <filename class="symlink">network</filename>
-  symlinks from all run-level directories (<filename
-  class="directory">/etc/rc.d/rc*.d</filename>).</para>
+  <para>Si une carte réseau ne sera pas utilisée, il n'y a aucun besoin
+  de créer des fichiers de configuration relatifs aux cartes réseau. Si
+  c'est le cas, supprimez les liens symboliques
 
-  <sect2>
-    <title>Creating stable names for network interfaces</title>
+  <filename class="symlink">network</filename> de tous les répertoires
+  des niveaux d'exécution
+
+  (<filename class="directory">/etc/rc.d/rc*.d</filename>).</para>
 
-    <para>With Udev and modular network drivers, the network interface numbering
-    is not persistent across reboots by default, because the drivers are loaded
-    in parallel and, thus, in random order. For example, on a computer having
-    two network cards made by Intel and Realtek, the network card manufactured
-    by Intel may become <filename class="devicefile">eth0</filename> and the
-    Realtek card becomes  <filename class="devicefile">eth1</filename>. In some
-    cases, after a reboot the cards get renumbered the other way around. To
-    avoid this, Udev comes with a script and some rules to assign stable names
-    to network cards based on their MAC address.</para>
+  <sect2>
+    <title>Création de noms stable pour les interfaces réseau</title>
 
-    <para>Pre-generate the rules to ensure the same names get assigned to the
-    same devices at every boot, including the first:</para>
+    <para>Avec Udev, la numérotation ddes pilotes réseau en module
+    n'est pas constante au fur et à mesure des redémarrages par défaut,
+    car les pilotes sont chargés en parallèle, et du coup, dans un ordre
+    aléatoire. Par exemple, sur un ordinateur ayant deux cartes réseau
+    fabriquées par Intel et Realtek, la carte réseau produite par Intel
+    peut devenir <filename class="devicefile">eth0</filename> et celle
+    de Realtek devient <filename class="devicefile">eth1</filename>.
+    Dans certains cas, après un redémarrage, les cartes sont
+    renumérotées d'une autre façon. Pour éviter cela, Udev est fourni
+    avec un script et des règles pour affecter des noms stables aux
+    cartes réseau basés sur leur adresse MAC.</para>
+
+    <para>Pré-générez les règles pour vous assurer que les mêmes noms
+    seront affectés aux mêmes périphériques à chaque démarrage, y
+    compris le premier&nbsp;:</para>
 
 <screen><userinput>for NIC in /sys/class/net/* ; do
     INTERFACE=${NIC##*/} udevadm test --action=add --subsystem=net $NIC
 done</userinput></screen>
 
-    <para>Now, inspect the <filename>/etc/udev/rules.d/70-persistent-net.rules</filename>
-    file, to find out which name was assigned to which network device:</para>
+
+    <para>Maintenant, examinez le fichier 
+    <filename>/etc/udev/rules.d/70-persistent-net.rules</filename>, pour
+    trouver quel nom a été donné à quel périphérique
+    réseau&nbsp;:</para>
 
 <screen><userinput>cat /etc/udev/rules.d/70-persistent-net.rules</userinput></screen>
 
-    <para>The file begins with a comment block followed by two lines for each
-    NIC. The first line for each NIC is a commented description showing its
-    hardware IDs (e.g. its PCI vendor and device IDs, if it's a PCI card),
-    along with its driver in parentheses, if the driver can be found. Neither
-    the hardware ID nor the driver is used to determine which name to give an
-    interface; this information is only for reference. The second line is the
-    Udev rule that matches this NIC and actually assigns it a name.</para>
-
-    <para>All Udev rules are made up of several keys, separated by commas and
-    optional whitespace. This rule's keys and an explanation of each of them
-    are as follows:</para>
+    <para>Le fichier commence par un bloc de commentaire suivi de deux
+    lignes pour chaque NIC. La première ligne de chaque NIC est une
+    description commentée montrant ses IDs matériels (comme ses IDs de
+    fabricant PCI et de périphérique, si c'est une carte PCI), puis avec
+    ses pilotes entre parenthèses, si le pilote peut être trouvé. Ni
+    l'ID du périphérique ni le pilote ne sont utilisés pour déterminer
+    quel nom donner à une interface. Ces informations ne sont
+    qu'en tant que référence. La deuxième ligne est la règle Udev
+    correspondant à ce NIC et qui lui affecte au final un nom..</para>
+
+    <para>Toutes les règles Udev sont constituées de plusieurs mots,
+    séparés par une virgule ou optionnellement un espace. Ces clés de
+    règle ainsi qu'une explication de chacune d'entre elles sont les
+    suivantes&nbsp;:</para>
 
     <itemizedlist>
       <listitem>
-        <para><literal>SUBSYSTEM=="net"</literal> - This tells Udev to ignore
-        devices that are not network cards.</para>
+        <para><literal>SUBSYSTEM=="net"</literal> - Ceci dit à Udev d'ignorer
+        les périphériques qui ne sont pas des cartes réseau.</para>
       </listitem>
       <listitem>
-        <para><literal>ACTION=="add"</literal> - This tells Udev to ignore this
-        rule for a uevent that isn't an add ("remove" and "change" uevents also
-        happen, but don't need to rename network interfaces).</para>
-      </listitem>
+        <para><literal>ACTION=="add"</literal> - Ceci dit à Udev d'ignorer cette
+        règle pour un uevent qui n'est pas un ajout (les uevents "retrait" et
+        "changement" se produisent aussi mais ils n'ont pas besoin de renommer
+        les interfaces réseau).</para>
+ 
       <listitem>
-        <para><literal>DRIVERS=="?*"</literal> - This exists so that Udev will
-        ignore VLAN or bridge sub-interfaces (because these sub-interfaces do
-        not have drivers). These sub-interfaces are skipped because the name
-        that would be assigned would collide with their parent devices.</para>
+        <para><literal>DRIVERS=="?*"</literal> - Ceci existe afin qu'Udev ignore
+        les VLAN ou les sous-interfaces bridge (car les sous-interfaces 
+        n'ont pas de pilotes). Ces sous-interfaces sont sautées car le nom
+        qui pourrait leur être affecté entrerait en conflit avec leur périphériques
+        parents.</para>
       </listitem>
       <listitem>
-        <para><literal>ATTR{address}</literal> - The value of this key is the
-        NIC's MAC address.</para>
+        <para><literal>ATTRS{type}=="1"</literal> - La valeur de cette
+
+        clé est l'adresse MAC du NIC.</para>
       </listitem>
       <listitem>
-        <para><literal>ATTR{type}=="1"</literal> - This ensures the rule only
-        matches the primary interface in the case of certain wireless drivers,
-        which create multiple virtual interfaces. The secondary interfaces are
-        skipped for the same reason that VLAN and bridge sub-interfaces are
-        skipped: there would be a name collision otherwise.</para>
+        <para><literal>ATTR{type}=="1"</literal> - Ceci assure que la règle ne
+        correspond qu'à l'interface primaire dans le cas de certains pilotes
+      sans fil, qui créent plusieurs interfaces virtuelles. Les interfaces
+        secondaires sont sautées pour la même raison que le sont les VLAN et lei
+        sous-interfaces bridge&nbsp;: il y aurait en ce cas un conflit de noms.</para>
       </listitem>
       <listitem>
-        <para><literal>KERNEL=="eth*"</literal> - This key was added to the
-        Udev rule generator to handle machines that have multiple network
-        interfaces, all with the same MAC address (the PS3 is one such
-        machine).  If the independent interfaces have different basenames,
-        this key will allow Udev to tell them apart.  This is generally not
-        necessary for most Linux From Scratch users, but does not hurt.</para>
+        <para><literal>KERNEL=="eth*"</literal> - Cette clé a été ajoutée au
+       générateur de règles d'Udev ´pour gérer les machines ayant plusieurs
+       interfaces réseau, toutes ayant la même adresse MAC (la machine PS3 en 
+       fait partie). Si les interfaces indépendantes ont des noms de base
+       différents, cette clé permettra à Udev de leur parler en apartée. Ce
+       n'est normalement pas nécessaire pour la plupart des utilisateurs de
+       Lin1x From Scratch, mais ça ne fait pas de mal.</para>
       </listitem>
       <listitem>
-        <para><literal>NAME</literal> - The value of this key is the name that
-        Udev will assign to this interface.</para>
+        <para><literal>NAME</literal> - La valeur de cette clé est le nom qu'Udev
+        affectera à l'interface.</para>
       </listitem>
     </itemizedlist>
 
-    <para>The value of <literal>NAME</literal> is the important part. Make sure
-    you know which name has been assigned to each of your network cards before
-    proceeding, and be sure to use that <literal>NAME</literal> value when
-    creating your configuration files below.</para>
+    <para>La valeur de <literal>NAME</literal> est la partie importante.
+    Assurez-vous de connaître quel nom a été affecté à chacune de vos
+    cartes réseau avant de continuer, et aisurez-vous d'utiliser cette
+    valeur <literal>NAME</literal> lorsque vous créerez les fichiers de
+    configuration ci-dessous.</para>
 
   </sect2>
 
   <sect2>
-    <title>Creating Network Interface Configuration Files</title>
+    <title>Créer des fichiers de configuration des interfaces réseau</title>
 
-    <para>Which interfaces are brought up and down by the network script
-    depends on the files and directories in the <filename
-    class="directory">/etc/sysconfig/network-devices</filename> hierarchy.
-    This directory should contain a sub-directory for each interface to be
-    configured, such as <filename>ifconfig.xyz</filename>, where
-    <quote>xyz</quote> is a network interface name. Inside this directory
-    would be files defining the attributes to this interface, such as its IP
-    address(es), subnet masks, and so forth.</para>
-
-    <para>The following command creates a sample <filename>ipv4</filename>
-    file for the <emphasis>eth0</emphasis> device:</para>
+    <para>Les interfaces activées et désactivées par le script network
+    dépendent des fichiers et des répertoires compris dans la hiérarchie
+    <filename
+    class="directory">/etc/sysconfig/network-devices</filename>. Ce
+    répertoire doit contenir un sous-répertoire pour chaque interface à
+    configurer, comme <filename>ifconfig.xyz</filename>, où
+    <quote>xyz</quote> est le nom de l'interface réseau. Dans ce
+    répertoire se trouvent des fichiers définissant les attributs de
+    cette interface, comme le(s) adresse(s) IP, masque de sous-réseau et
+    ainsi de suite.</para>
+
+    <para>La commande suivante crée un fichier <filename>ipv4</filename>
+    d'exemple pour le périphérique 
+    <emphasis>eth0</emphasis>&nbsp;:</para>
 
 <screen><userinput>cd /etc/sysconfig/network-devices
 mkdir -v ifconfig.eth0
@@ -134,67 +154,77 @@
 BROADCAST=192.168.1.255</literal>
 EOF</userinput></screen>
 
-    <para>The values of these variables must be changed in every file to match
-    the proper setup. If the <envar>ONBOOT</envar> variable is set to
-    <quote>yes</quote> the network script will bring up the Network Interface
-    Card (NIC) during booting of the system. If set to anything but
-    <quote>yes</quote> the NIC will be ignored by the network script and not
-    be brought up.</para>
-
-    <para>The <envar>SERVICE</envar> variable defines the method used for
-    obtaining the IP address. The LFS-Bootscripts package has a modular IP
-    assignment format, and creating additional files in the <filename
+    <para>Les valeurs de ces variables doivent être modifiées dans
+    chaque fichier pour correspondre à la bonne configuration. Si la
+    variable <envar>ONBOOT</envar> est configurée à <quote>yes</quote>,
+    le script network configurera la carte réseau
+    (<foreignphrase>Network Interface Card</foreignphrase>, NIC) pendant
+    le démarrage du système. S'il est configuré avec toute autre valeur
+    que <quote>yes</quote>, l'interface réseau sera ignorée par le
+    script network et non montée.</para>
+
+    <para>La variable <envar>SERVICE</envar> définit la méthode utilisée
+    pour obteni une adresse IP. Les scripts de démarrage LFS ont un
+    format d'affectation IP modulaire. Créer les fichier supplémentaires
+    dans le répertoire
+
+    <filename
     class="directory">/etc/sysconfig/network-devices/services</filename>
-    directory allows other IP assignment methods. This is commonly used for
-    Dynamic Host Configuration Protocol (DHCP), which is addressed in the
-    BLFS book.</para>
-
-    <para>The <envar>GATEWAY</envar> variable should contain the default
-    gateway IP address, if one is present. If not, then comment out the
-    variable entirely.</para>
-
-    <para>The <envar>PREFIX</envar> variable needs to contain the number of
-    bits used in the subnet. Each octet in an IP address is 8 bits. If the
-    subnet's netmask is 255.255.255.0, then it is using the first three octets
-    (24 bits) to specify the network number. If the netmask is 255.255.255.240,
-    it would be using the first 28 bits.  Prefixes longer than 24 bits are
-    commonly used by DSL and cable-based Internet Service Providers (ISPs).
-    In this example (PREFIX=24), the netmask is 255.255.255.0. Adjust the
-    <envar>PREFIX</envar> variable according to your specific subnet.</para>
+    autorise d'autres méthodes d'affectation. Ceci est habituellement
+    utilisé pour le DHCP (<foreignphrase>Dynamic Host Configuration
+    Protocol</foreignphrase>, NdT&nbsp;:protocole de configuration de
+    l'hôte dynamique), qui est adressé dans le livre BLFS.
+
+    <para>La variable <envar>GATEWAY</envar> devrait contenir l'adresse
+    IP par défaut de la passerelle, si elle existe. Sinon, mettez
+    entièrement en commentaire la variable.</para>
+
+    <para>La variable <envar>PREFIX</envar> a besoin de contenir le
+    nombre de bits utilisé dans le sous-réseau. Chaque octet dans une
+    adresse IP est sur huit bits. Si le masque réseau du sous-réseau est
+    255.255.255.0, alors il est en train d'utiliser les trois premiers
+    octets (24 bits) pour spécifier le numéro réseau. Si le
+    masque réseau est 255.255.255.240, il utiliserait les 128 premiers
+    bits. Les préfixes plus longs que 24 bits sont habituellement
+    utilisés par les fournisseurs d'accès à Internet ADSL et câble. Dans
+    cet exemple (PREFIX=24), le masque réseau est 255.255.255.0. Ajustez
+    la variable <envar>PREFIX</envar> en concordance avec votre
+    sous-réseau spécifique.</para>
 
   </sect2>
 
   <sect2 id="resolv.conf">
-    <title>Creating the /etc/resolv.conf File</title>
+    <title>Créer le fichier /etc/resolv.conf</title>
 
     <indexterm zone="resolv.conf">
       <primary sortas="e-/etc/resolv.conf">/etc/resolv.conf</primary>
     </indexterm>
 
-    <para>If the system is going to be connected to the Internet, it will
-    need some means of Domain Name Service (DNS) name resolution to
-    resolve Internet domain names to IP addresses, and vice versa. This is
-    best achieved by placing the IP address of the DNS server, available
-    from the ISP or network administrator, into
-    <filename>/etc/resolv.conf</filename>. Create the file by running the
-    following:</para>
+    <para>Si le système a besoin d'être connecté à Internet, il aura
+    besoin de la résolution de noms proposée par le DNS (Domain Name
+    Service) pour résoudre les noms de domaines Internet, et vice-versa.
+    Ceci se fait en plaçant les adresses IP du serveur DNS, disponibles
+    auprès du FAI ou de l'administrateur système, dans
+    <filename>/etc/resolv.conf</filename>. Créez le fichier en lançant
+    ce qui suit&nbsp;:</para>
 
 <screen><userinput>cat &gt; /etc/resolv.conf &lt;&lt; "EOF"
 <literal># Begin /etc/resolv.conf
 
-domain <replaceable>&lt;Your Domain Name&gt;</replaceable>
-nameserver <replaceable>&lt;IP address of your primary nameserver&gt;</replaceable>
-nameserver <replaceable>&lt;IP address of your secondary nameserver&gt;</replaceable>
+domain <replaceable>&lt;Votre nom de domaine&gt;</replaceable>
+nameserver <replaceable>&lt;Adresse IP du DNS primaire&gt;</replaceable>
+nameserver <replaceable>&lt;Adresse IP du DNS secodaire&gt;</replaceable>
 
 # End /etc/resolv.conf</literal>
 EOF</userinput></screen>
 
-    <para>Replace <replaceable>&lt;IP address of the nameserver&gt;</replaceable>
-    with the IP address of the DNS most appropriate for the setup. There will
-    often be more than one entry (requirements demand secondary servers for
-    fallback capability). If you only need or want one DNS server, remove the
-    second <emphasis>nameserver</emphasis> line from the file. The IP address
-    may also be a router on the local network.</para>
+    <para>Remplacez <replaceable>&lt;adresse IP du DNS&gt;</replaceable> avec l'adresse
+    IP du DNS le plus approprié pour la configuration. Il y aura souvent plus d'une
+    entrée (les conseils recommandent des serveurs DNS disposant de capacité de
+    prise en charge. Si vous avez seulement besoin ou si vous voulez uniquement le
+    serveur DNS, supprimez la seconde ligne <emphasis>serveur de noms</emphasis> à
+    partir du fichier. L'adresse IP pourrait aussi être un routeur sur le réseau
+    local.</para>
 
   </sect2>
 
diff -Naur BOOK/chapter07/profile.xml BOOKfr/chapter07/profile.xml
--- BOOK/chapter07/profile.xml	2008-07-15 00:49:41.000000000 +0100
+++ BOOKfr/chapter07/profile.xml	2008-07-02 00:31:47.000000000 +0100
@@ -8,134 +8,154 @@
 <sect1 id="ch-scripts-profile">
   <?dbhtml filename="profile.html"?>
 
-  <title>The Bash Shell Startup Files</title>
+  <title>Fichiers de démarrage du shell Bash</title>
 
   <indexterm zone="ch-scripts-profile">
     <primary sortas="e-/etc/profile">/etc/profile</primary>
   </indexterm>
 
-  <para>The shell program <command>/bin/bash</command> (hereafter referred to
-  as <quote>the shell</quote>) uses a collection of startup files to help
-  create an environment to run in. Each file has a specific use and may affect
-  login and interactive environments differently. The files in the <filename
-  class="directory">/etc</filename> directory provide global settings. If an
-  equivalent file exists in the home directory, it may override the global
-  settings.</para>
-
-  <para>An interactive login shell is started after a successful login, using
-  <command>/bin/login</command>, by reading the <filename>/etc/passwd</filename>
-  file. An interactive non-login shell is started at the command-line (e.g.,
-  <prompt>[prompt]$</prompt><command>/bin/bash</command>). A non-interactive
-  shell is usually present when a shell script is running. It is non-interactive
-  because it is processing a script and not waiting for user input between
-  commands.</para>
-
-  <para>For more information, see <command>info bash</command> under the
-  <emphasis>Bash Startup Files and Interactive Shells</emphasis> section.</para>
-
-  <para>The files <filename>/etc/profile</filename> and
-  <filename>~/.bash_profile</filename> are read when the shell is
-  invoked as an interactive login shell.</para>
-
-  <para>The base <filename>/etc/profile</filename> below sets some
-  environment variables necessary for native language support. Setting
-  them properly results in:</para>
+  <para>Le programme shell <command>/bin/bash</command> (dénommé
+  ci-après <quote>le shell</quote>) utilise une collection de fichiers
+  de démarrage pour aider à la création d'un environnement d'exécution.
+  Chaque fichier a une utilisation spécifique et pourrait avoir des
+  effets différents sur les environnements de connexion et interactif.
+  Les fichiers du répertoire <filename class="directory">/etc</filename>
+  fournissent un paramétrage global. Si un fichier équivalent existe
+  dans le répertoire personnel, il pourrait surcharger les paramétrages
+  globaux.</para>
+
+  <para>Un shell interactif de connexion est lancé après une connexion
+  réussie, en utilisant <command>/bin/login</command>, par la lecture du
+  fichier <filename>/etc/passwd</filename>. Un shell interactif sans
+  connexion est lancé en ligne de commande (c'est-à-dire
+  <prompt>[prompt]$</prompt><command>/bin/bash</command>). Un shell non
+  interactif est habituellement présent quand un script shell est en
+  cours d'exécution. Il est non interactif parce qu'il traite un script
+  et n'attend pas une saisie de l'utilisateur entre les
+  commandes.</para>
+
+  <para>Pour plus d'informations, voir <command>info bash</command> sous
+  la section <emphasis>Bash Startup Files and Interactive
+  Shells</emphasis> (Fichiers de démarrage de Áash et shells
+  interactifs).</para>
+
+  <para>Les fichiers <filename>/etc/profile</filename> et
+  <filename>~/.bash_profile</filename> sont lus quand le shell est
+  appelé en tant que shell interactif de connexion.</para>
+
+  <para>Le fichier <filename>/etc/profile</filename> de base ci-dessous
+	configure quelques variables d'environnement nécessaire au support des langues
+  natives. Les configurer proprement résulte en ce qui
+  suit&nbsp;:</para>
 
   <itemizedlist>
     <listitem>
-      <para>The output of programs translated into the native language</para>
+      <para>La sortie des programmes traduite dans la langue
+      natif</para>
     </listitem>
     <listitem>
-      <para>Correct classification of characters into letters, digits and other
-      classes. This is necessary for <command>bash</command> to properly accept
-      non-ASCII characters in command lines in non-English locales</para>
+      <para>La correction de la classification des caractères en lettres,
+      chiffres et autres classes. Ceci est nécessaire pour que <command>bash</command>
+      accepte proprement les caractères non ASCII dans les lignes de commandes pour
+      les locales autres qu'anglais</para>
     </listitem>
     <listitem>
-      <para>The correct alphabetical sorting order for the country</para>
+      <para>L'ordre de tri alphabétique correct pour le pays</para>
     </listitem>
     <listitem>
-      <para>Appropriate default paper size</para>
+      <para>La taille de papier par défaut appropriée</para>
     </listitem>
     <listitem>
-      <para>Correct formatting of monetary, time, and date values</para>
+      <para>Le bon formatage des valeurs monétaires, de l'heure et des
+      dates</para>
     </listitem>
   </itemizedlist>
 
-  <para>Replace <replaceable>&lt;ll&gt;</replaceable> below with the two-letter code
-  for the desired language (e.g., <quote>en</quote>) and
-  <replaceable>&lt;CC&gt;</replaceable> with the two-letter code for the appropriate
-  country (e.g., <quote>GB</quote>). <replaceable>&lt;charmap&gt;</replaceable> should
-  be replaced with the canonical charmap for your chosen locale. Optional
-  modifiers such as <quote>@euro</quote> may also be present.</para>
+  <para>Remplacez <replaceable>&lt;ll&gt;</replaceable> ci-dessous
+  avec le code à deux lettres de la langue désirée (par exemple,
+  <quote>en</quote>) et <replaceable>&lt;CC&gt;</replaceable> avec le code à 
+	deux lettres du pays approprié (par exemple, <quote>GB</quote>).
+  <replaceable>&lt;charmap&gt;</replaceable> devra être remplacé avec le
+  jeu de caractères canonique de la locale choisie. Des modificateurs optionnels
+  comme <quote>@euro</quote> peuvent aussi être présents.</para>
 
-  <para>The list of all locales supported by Glibc can be obtained by running
-  the following command:</para>
+  <para>La liste de toutes les locales supportées par Glibc peut être
+  obtenue en exécutant la commande suivante&nbsp;:</para>
 
 <screen role="nodump"><userinput>locale -a</userinput></screen>
 
-  <para>Charmaps can have a number of aliases, e.g., <quote>ISO-8859-1</quote>
-  is also referred to as <quote>iso8859-1</quote> and <quote>iso88591</quote>.
-  Some applications cannot handle the various synonyms correctly (e.g., require
-  that <quote>UTF-8</quote> is written as <quote>UTF-8</quote>, not
-  <quote>utf8</quote>), so it is safest in most
-  cases to choose the canonical name for a particular locale. To determine
-  the canonical name, run the following command, where <replaceable>&lt;locale
-  name&gt;</replaceable> is the output given by <command>locale -a</command> for
-  your preferred locale (<quote>en_GB.iso88591</quote> in our example).</para>
+  <para>Les locales peuvent avoir plusieurs synonymes. Par exemple,
 
-<screen role="nodump"><userinput>LC_ALL=<replaceable>&lt;locale name&gt;</replaceable> locale charmap</userinput></screen>
+  <quote>ISO-8859-1</quote> est aussi appelée <quote>iso8859-1</quote> et
 
-  <para>For the <quote>en_GB.iso88591</quote> locale, the above command
-  will print:</para>
+  <quote>iso88591</quote>. Quelques applications ne peuvent pas gérer les
+
+  différents synonymes correctement (elles nécessitent par exemple l'écriture de
+  <quote>UTF-8</quote> sous la forme <quote>UTF-8</quote>, non
+  <quote>utf8</quote>), donc il est plus sûr de choisir le nom
+  canonique pour une locale particulière. Pour déterminer le nom canonique,
+  lancez la commande suivante, où <replaceable>&lt;nom locale&gt;</replaceable> 
+   est l'affichage donnée par <command>locale
+  -a</command> pour votre locale préférée (<quote>en_GB.iso88591</quote> dans
+  notre exemple).</para>
+
+<screen role="nodump"><userinput>LC_ALL=<replaceable>&lt;nom_de_la_locale&gt;</replaceable> locale charmap</userinput></screen>
+
+  <para>Pour la locale <quote>en_GB.iso88591</quote>, la commande
+  ci-dessus affichera&nbsp;:</para>
 
 <screen><computeroutput>ISO-8859-1</computeroutput></screen>
 
-  <para>This results in a final locale setting of <quote>en_GB.ISO-8859-1</quote>.
-  It is important that the locale found using the heuristic above is tested prior
-  to it being added to the Bash startup files:</para>
+  <para>Ceci résulte en un paramétrage final de locale avec
+  <quote>en_GB.ISO-8859-1</quote>. Il est important que la locale
+  trouvée utilisant l'heuristique ci-dessus soit testée avant d'être
+  ajoutée aux fichiers de démarrage de Bash&nbsp;:</para>
 
 <screen role="nodump"><userinput>LC_ALL=&lt;locale name&gt; locale language
 LC_ALL=&lt;locale name&gt; locale charmap
 LC_ALL=&lt;locale name&gt; locale int_curr_symbol
 LC_ALL=&lt;locale name&gt; locale int_prefix</userinput></screen>
 
-  <para>The above commands should print the language name, the character
-  encoding used by the locale, the local currency, and the prefix to dial
-  before the telephone number in order to get into the country. If any of the
-  commands above fail with a message similar to the one shown below, this means
-  that your locale was either not installed in Chapter 6 or is not supported by
-  the default installation of Glibc.</para>
+  <para>Les commandes ci-dessus devraient afficher les noms du pays et
+  de la langue, le codage des caractères utilisé par la locale, la
+  monnaie et le préfixe à composer avant de saisir le numéro de
+  téléphone. Si une des commandes ci-dessus échoue avec un message
+  similaire à un de ceux montrés ci-dessous, cela signifie que votre
+  locale n'a pas été installée dans le chapitre 6 ou qu'elle n'est pas
+  supportée par l'installation par défaut de Glibc.</para>
 
 <screen><computeroutput>locale: Cannot set LC_* to default locale: No such file or directory</computeroutput></screen>
 
-  <para>If this happens, you should either install the desired locale using the
-  <command>localedef</command> command, or consider choosing a different locale.
-  Further instructions assume that there are no such error messages from
-  Glibc.</para>
+  <para>Si cela arrive, vous pouvez soit installer la locale désirée en
+  utilisant la commande <command>localedef</command> soit considérer
+  l'utilisation d'une locale différente. Les instructions suivantes
+  supposent qu'il n'y a pas eu de tels messages de Glibc.</para>
 
   <!-- FIXME: the xlib example will became obsolete real soon -->
-  <para>Some packages beyond LFS may also lack support for your chosen locale. One
-  example is the X library (part of the X Window System), which outputs the
-  following error message if the locale does not exactly match one of the character
-  map names in its internal files:</para>
+  <para>Certains paquets en dehors de LFS pourraient aussi ne pas avoir
+  de support pour la locale que vous avez choisi. Un exemple est la
+  bibliothèque X (qui fait partie du système X Window), qui affiche le
+  message d'erreur suivant&nbsp;:</para>
 
 <screen><computeroutput>Warning: locale not supported by Xlib, locale set to C</computeroutput></screen>
 
-  <para>In several cases Xlib expects that the character map will be listed in
-  uppercase notation with canonical dashes. For instance, "ISO-8859-1" rather
-  than "iso88591". It is also  possible to find an appropriate specification by
-  removing the charmap part of the locale specification.  This can be checked
-  by running the <command>locale charmap</command> command in both locales.
-  For example, one would have to change "de_DE.ISO-8859-15@euro" to
-  "de_DE@euro" in order to get this locale recognized by Xlib.</para>
-
-  <para>Other packages can also function incorrectly (but may not necessarily
-  display any error messages) if the locale name does not meet their expectations.
-  In those cases, investigating how other Linux distributions support your locale
-  might provide some useful information.</para>
+  <para>Dans certains cas Xlib s'attend à ce que le plan de caractère
+  soit listé en majuscule avec des tirets canoniques. Par
+  exemple, "ISO-8859-1" plutôt que "iso88591". Il est aussi possible de
+  trouver la spécification adéquate en supprimant la sartie charmap de
+  la spécification de la locale. Vous pouvez le vérifier en lançant la
+  commande <command>locale charmap</command> dans les deux locales. Par
+  exemple, vous pourriez vouloir remplacer "de_DE.ISO-8859-15@euro" par
+  "de_DE@euro" afin que cette locale soit reconnue par Xlib.</para>
+
+  <para>D'autres paquets peuvent aussi mal fonctionner (mais pourraient
+  ne pas nécessairement afficher de messages d'erreurs) si le nom de la
+  locale ne correspond pas à leur attente. Dans de tels cas, vous pouvez
+  obtenir des informations utile en cherchant comment les autres
+  distributions Linux supportent votre locale.</para>
 
-  <para>Once the proper locale settings have been determined, create the
-  <filename>/etc/profile</filename> file:</para>
+  <para>Une fois que les bons paramètres de locale ont été déterminés,
+  créez le fichier <filename>/etc/profile</filename>&nbsp;:</para>
 
 <screen><userinput>cat &gt; /etc/profile &lt;&lt; "EOF"
 <literal># Begin /etc/profile
@@ -145,20 +165,26 @@
 # End /etc/profile</literal>
 EOF</userinput></screen>
 
-  <para>The <quote>C</quote> (default) and <quote>en_US</quote> (the recommended
-  one for United States English users) locales are different. <quote>C</quote>
-  uses the US-ASCII 7-bit character set, and treats bytes with the high bit set
-  as invalid characters. That's why, e.g., the <command>ls</command> command
-  substitutes them with question marks in that locale. Also, an attempt to send
-  mail with such characters from Mutt or Pine results in non-RFC-conforming
-  messages being sent (the charset in the outgoing mail is indicated as <quote>unknown
-  8-bit</quote>). So you can use the <quote>C</quote> locale only if you are sure that
-  you will never need 8-bit characters.</para>
-
-  <para>UTF-8 based locales are not supported well by many programs. E.g., the
-  <command>watch</command> program displays only ASCII characters in UTF-8
-  locales and has no such restriction in traditional 8-bit locales like en_US.
-  Work is in progress to document and, if possible, fix such problems, see
-  <ulink url="&blfs-root;view/svn/introduction/locale-issues.html"/>.</para>
+  <para>Les locales <quote>C</quote> (par défaut) et
+  <quote>en_US</quote> (celle recommandée pour les utilisateurs de
+  langue anglaise vivant aux États-Unis) sont différentes.
+  <quote>C</quote> utilise le codage US-ASCII 7-bit et traite les bytes
+  avec un paramètre de bit haut comme des caractères invalides.
+  C'est pourquoi, par exemple, la commande <command>ls</command> les
+  remplace par des points d'interrogation dans cette locale. De même, un
+  essai d'envoyer un mail avec de tels caractères depuis Mutt ou Pine
+  donne l'envoi de messages en version non compatible avec RFC (le codage du mail
+  sortant est indiqué comme <quote>unknown 8-bit</quote> (8-bit
+  inconnu)). Donc, vous ne pouvez utiliser la locale <quote>C</quote>
+  que si vous êtes sûr de ne jamais avoir besoin de caractères
+  8-bit.</para>
+
+  <para>Les locales basées sur UTF-8 ne sont pas bien supportées par
+  beaucoup de programmes. Par exemple, le programme
+  <command>watch</command> n'affiche que les caractères ASCII dans les
+  locales UTF-8 et n'a pas de telles restrictions dans les locales 8-bit
+  traditionnelles comme en_US. Le travail progresse pour documenter et,
+  si possible, réparer de tels problèmes, voir <ulink 
+  url="&blfs-root;view/svn/introduction/locale-issues.html"/>.</para>
 
 </sect1>
diff -Naur BOOK/chapter07/setclock.xml BOOKfr/chapter07/setclock.xml
--- BOOK/chapter07/setclock.xml	2008-07-15 00:49:41.000000000 +0100
+++ BOOKfr/chapter07/setclock.xml	2008-07-02 00:34:09.000000000 +0100
@@ -8,38 +8,47 @@
 <sect1 id="ch-scripts-setclock">
   <?dbhtml filename="setclock.html"?>
 
-  <title>Configuring the setclock Script</title>
+  <title>Configurer le script setclock</title>
 
   <indexterm zone="ch-scripts-setclock">
     <primary sortas="d-setclock">setclock</primary>
-  <secondary>configuring</secondary></indexterm>
+  <secondary>configuration</secondary></indexterm>
 
-  <para>The <command>setclock</command> script reads the time from the hardware
-  clock, also known as the BIOS or the Complementary Metal Oxide Semiconductor
-  (CMOS) clock. If the hardware clock is set to UTC, this script will convert the
-  hardware clock's time to the local time using the
-  <filename>/etc/localtime</filename> file (which tells the
-  <command>hwclock</command> program which timezone the user is in). There is no
-  way to detect whether or not the hardware clock is set to UTC, so this
-  needs to be configured manually.</para>
-
-  <para>If you cannot remember whether or not the hardware clock is set to UTC,
-  find out by running the <userinput>hwclock --localtime --show</userinput>
-  command. This will display what the current time is according to the hardware
-  clock. If this time matches whatever your watch says, then the hardware clock is
-  set to local time. If the output from <command>hwclock</command> is not local
-  time, chances are it is set to UTC time. Verify this by adding or subtracting
-  the proper amount of hours for the timezone to the time shown by
-  <command>hwclock</command>. For example, if you are currently in the MST
-  timezone, which is also known as GMT -0700, add seven hours to the local
-  time.</para>
-
-  <para>Change the value of the <envar>UTC</envar> variable below
-  to a value of <parameter>0</parameter> (zero) if the hardware clock
-  is <emphasis>not</emphasis> set to UTC time.</para>
-
-  <para>Create a new file <filename>/etc/sysconfig/clock</filename> by running
-  the following:</para>
+  <para>Le script <command>setclock</command> lit le temps sur l'horloge
+  matérielle, aussi connu sous le nom d'horloge BIOS or CMOS
+  (Complementary Metal Oxide Semiconductor). Si l'horloge matérielle est
+  configurée en UTC, le script convertira le temps de l'horloge
+  matérielle en temps local en utilisant le fichier
+
+  <filename>/etc/localtime</filename> (indiquant au programme
+  <command>hwclock</command> le fuseau horaire où se situe
+  l'utilisateur). Il n'existe pas de moyens de détecter si l'horloge
+  matérielle est configurée en UTC, donc elle doit être configurée
+  manuellement.</para>
+
+  <para>Si vous ne vous rappeler pas si l'horloge matérielle est configurée en
+  UTC, découvrez-le en exécutant 
+
+  <userinput>hwclock --localtime --show</userinput>. Ceci affichera
+  l'heure courante suivant l'horloge matérielle. Si l'heure
+  correspond à ce qui vous dit votre montre, alors l'horloge matérielle est
+  configurée sur l'heure locale. Si la sortie de <command>hwclock</command> n'est pas
+  l'heure locale, il y a des chances qu'elle soit configurée en UTC. Vérifiez
+  ceci en ajoutant ou en soustrayant le bon nombre d'heures pour votre fuseau 
+
+  horaire à l'heure affichée par <command>hwclock</command>. Par exemple, si 
+  vous êtes actuellement sur le fuseau horaire MST, aussi connu en tant que GMT
+  -0700, ajoutez sept heures à l'heure locale.</para>
+
+  <para>Modifiez la valeur de la variable <envar>UTC</envar> ci-dessous
+  par une valeur <parameter>0</parameter> (zéro) si l'horloge matérielle
+  n'est <emphasis>pas</emphasis> si l'horloge matérielle n'est
+
+  <emphasis>pas</emphasis> configurée en temps UTC.</para>
+
+  <para>Créez un nouveau fichier
+  <filename>/etc/sysconfig/clock</filename> en lançant ce qui
+  suit&nbsp;:</para>
 
 <screen><userinput>cat &gt; /etc/sysconfig/clock &lt;&lt; "EOF"
 <literal># Begin /etc/sysconfig/clock
@@ -49,8 +58,11 @@
 # End /etc/sysconfig/clock</literal>
 EOF</userinput></screen>
 
-  <para>A good hint explaining how to deal with time on LFS is available
-  at <ulink url="&hints-root;time.txt"/>. It explains issues such as
-  time zones, UTC, and the <envar>TZ</envar> environment variable.</para>
+  <para> Une bonne astuce expliquant comment gérer l'horloge sur LFS est
+  disponible sur
+
+  <ulink url="&hints-root;time.txt"/>. Il explique certains concepts
+  comme les fuseaux horaires, UTC et la variable d'environnement
+  <envar>TZ</envar>.</para>
 
 </sect1>
diff -Naur BOOK/chapter07/symlinks.xml BOOKfr/chapter07/symlinks.xml
--- BOOK/chapter07/symlinks.xml	2008-07-15 00:49:41.000000000 +0100
+++ BOOKfr/chapter07/symlinks.xml	2008-07-02 02:11:13.000000000 +0100
@@ -8,125 +8,153 @@
 <sect1 id="ch-scripts-symlinks">
   <?dbhtml filename="symlinks.html"?>
 
-  <title>Creating Custom Symlinks to Devices</title>
+  <title>Création de liens symboliques personnalisés vers les
+  périphériques</title>
 
   <sect2>
 
-    <title>CD-ROM symlinks</title>
+    <title>Liens symboliques pour le CD-ROM</title>
 
-    <para>Some software that you may want to install later (e.g., various
-    media players) expect the <filename class="symlink">/dev/cdrom</filename>
-    and <filename class="symlink">/dev/dvd</filename> symlinks to exist, and
-    to point to a CD-ROM or DVD-ROM device. Also, it may be convenient to put
-    references to those symlinks into <filename>/etc/fstab</filename>. Udev
-    comes with a script that will generate rules files to create these symlinks
-    for you, depending on the capabilities of each device, but you need to
-    decide which of two modes of operation you wish to have the script use.</para>
-
-    <para>First, the script can operate in <quote>by-path</quote> mode (used by
-    default for USB and FireWire devices), where the rules it creates depend on
-    the physical path to the CD or DVD device. Second, it can operate in
-    <quote>by-id</quote> mode (default for IDE and SCSI devices), where the
-    rules it creates depend on identification strings stored in the CD or DVD
-    device itself. The path is determined by Udev's <command>path_id</command>
-    script, and the identification strings are read from the hardware by its
-    <command>ata_id</command> or <command>scsi_id</command> programs, depending
-    on which type of device you have.</para>
-
-    <para>There are advantages to each approach; the correct approach to use
-    will depend on what kinds of device changes may happen. If you expect the
-    physical path to the device (that is, the ports and/or slots that it plugs
-    into) to change, for example because you plan on moving the drive to a
-    different IDE port or a different USB connector, then you should use the
-    <quote>by-id</quote> mode. On the other hand, if you expect the device's
-    identification to change, for example because it may die, and you would
-    replace it with a different device with the same capabilities and which
-    is plugged into the same connectors, then you should use the
-    <quote>by-path</quote> mode.</para>
-
-    <para>If either type of change is possible with your drive, then choose a
-    mode based on the type of change you expect to happen more often.</para>
+    <para>Certains logiciels que vous pourriez vouloir installer plus
+    tard (comme divers lecteurs multimédias) s'attendent à ce que les
+    liens symboliques <filename class="symlink">/dev/cdrom</filename> et
+    <filename class="symlink">/dev/dvd</filename> existent et pointent
+    vers le lecteur CD-ROM ou DVD-ROM. De plus, il peut être pratique de
+    mettre des références à ces liens symboliques dans
+    <filename>/etc/fstab</filename>. Udev est fourni avec un script qui
+    générera des fichiers de règle pour créer ces liens symboliques pour
+    vous, selon les possibilités de chaque périphérique, mais vous devez
+    décider lequel des deux modes opératoires vous souhaitez que le script
+    utilise.</para>
+
+    <para>Tout d'abord, le script peut opérer en mode
+    <quote>selon-le-chemin</quote> (utilisé par défaut pour les
+    périphériques USB et FireWire), où les règles qu'il crée dépendent
+    du chemin physique vers le lecteur CD ou DVD. Ensuite, il peut
+    opérer en mode <quote>selon-l-id</quote> (par défaut pour les
+    périphériques IDE et SCSI), où les règles qu'il crée dépendent des
+    chaînes d'identification contenues dans le lecteur CD ou DVD
+    lui-même. Le chemin est déterminé par le script
+    <command>path_id</command> d'Udev, et les chaînes d'identification
+    sont lues à partir du matériel par ses programmes
+    <command>ata_id</command> ou <command>scsi_id</command>, selon le
+    type de périphérique que vous avez.</para>
+
+    <para>Il y a des avantages dans chaque approche&nbsp;; la bonne
+    approche à utiliser dépendra des types de changement de périphérique
+    qui peuvent se produire. Si vous vous attendez à ce que Le chemin
+    physique vers le périphérique (c'est-à-dire, les ports et/ou les
+    slots par lesquels ils sont branchés) change, par exemple parce que
+    vous envisagez de déplacer le lecteur sur un port IDE différent ou
+    un connecteur USB différent, alors vous devriez utiliser le mode
+    <quote>par-l-id</quote>. D'un autre côté, si vous vous attezdez à ce
+    que l'identification du périphérique change, par exemple parce qu'il
+    peut mourir et que vous le remplaceriez par un périphérique différent
+    avec les mêmes possibilités et qui serait monté sur les mêmes
+    connecteurs, vous devriez utiliser le mode
+    <quote>par-chemin</quote>.</para>
+
+    <para>Si d'autres types de changement sont possibles avec votre
+    lecteur, choisissez un mode basé sur le type de changement que vous
+    pensez avoir plus fréquemment.</para>
 
 <!-- If you use by-id mode, the symlinks will survive even the transition
      to libata for IDE drives, but that is not for the book. -->
 
-    <important><para>External devices (for example, a USB-connected CD drive)
-    should not use by-path persistence, because each time the device is plugged
-    into a new external port, its physical path will change. All
-    externally-connected devices will have this problem if you write Udev rules
-    to recognize them by their physical path; the problem is not limited to CD
-    and DVD drives.</para></important>
-
-    <para>If you wish to see the values that the Udev scripts will use, then
-    for the appropriate CD-ROM device, find the corresponding directory under
-    <filename class="directory">/sys</filename> (e.g., this can be
-    <filename class="directory">/sys/block/hdd</filename>) and
-    run a command similar to the following:</para>
-
-<screen role="nodump"><userinput>udevadm test /sys/block/hdd</userinput></screen>
-
-    <para>Look at the lines containing the output of various *_id programs.
-    The <quote>by-id</quote> mode will use the ID_SERIAL value if it exists and
-    is not empty, otherwise it will use a combination of ID_MODEL and
-    ID_REVISION. The <quote>by-path</quote> mode will use the ID_PATH value.</para>
-
-    <para>If the default mode is not suitable for your situation, then the
-    following modification can be made to the
-    <filename>/etc/udev/rules.d/75-cd-aliases-generator.rules</filename> file,
-    as follows (where <replaceable>mode</replaceable> is one of
-    <quote>by-id</quote> or <quote>by-path</quote>):</para>
+    <important><para>Les périphériques externes (par exemple un lecteur
+    CD connecté en USB) ne devraient pas utiliser la méthode by-path,
+    car chaque fois que le périphérique est monté sur un nouveau port,
+    son chemin physique changera. Tous les périphériques connectés en
+    externe auront ce problème si vous écrivez des règles Udev pour les
+    reconnaître par leur chemin physique&nbsp;, le problème ne concerne
+    pas que les lecteurs CD et DVD.</para></important>
+
+    <para>Si vous souhaitez voir les valeurs que les scripts Udev
+    utiliseront, et pour le périphérique CD-ROM approprié, trouvez le
+    répertoire correspondant sous
+
+    <filename class="directory">/sys</filename> (cela peut être par
+    exemple <filename class="directory">/sys/block/hdd</filename>) et
+    lancez une commande ressemblant à ce qui suit&nbsp;:</para>
+
+<screen role="nodump"><userinput>udevadmtest/sys/block/hdd</userinput></screen>
+
+    <para>Regardez les lignes contenant la sortie des divers programmes
+    *_id. Le mode <quote>par-l-id</quote> utilisera la valeur ID_SERIAL
+    si elle existe et qu'elle n'est pas vide, sinon il utilisera une combinaison
+    de ID_MODEL et de ID_REVISION. Le mode <quote>by-path</quote> utilisera la
+    valeur de ID_PATH.</para>
+
+    <para>Si le mode par défaut ne convient pas à votre situation, vous
+    pouvez faire la modification suivante du fichier
+    <filename>/etc/udev/rules.d/75-cd-aliases-generator.rules</filename>,
+    comme suit, (où <replaceable>mode</replaceable> est soit 
+
+    <quote>par-l-id</quote> soit <quote>par-chemin</quote>)&nbsp;:</para>
 
 <screen role="nodump"><userinput>sed -i -e 's/write_cd_rules/&amp; <replaceable>mode</replaceable>/' \
     /etc/udev/rules.d/75-cd-aliases-generator.rules</userinput></screen>
 
-    <para>Note that it is not necessary to create the rules files or symlinks
-    at this time, because you have bind-mounted the host's
-    <filename class="directory">/dev</filename> directory into the LFS system,
-    and we assume the symlinks exist on the host. The rules and symlinks will
-    be created the first time you boot your LFS system.</para>
-
-    <para>However, if you have multiple CD-ROM devices, then the symlinks
-    generated at that time may point to different devices than they point to on
-    your host, because devices are not discovered in a predictable order. The
-    assignments created when you first boot the LFS system will be stable, so
-    this is only an issue if you need the symlinks on both systems to point to
-    the same device. If you need that, then inspect (and possibly edit) the
-    generated <filename>/etc/udev/rules.d/70-persistent-cd.rules</filename>
-    file after booting, to make sure the assigned symlinks match what you need.</para>
+    <para>Notez qu'il n'est pas nécessaire de créer les fichiers de règle ou les
+     liens symboliques à ce moment puisque vous avez monté en bind le répertoire
+    <filename class="directory">/dev</filename> du système hôte dans le système
+    LFS, et nous assumons que les liens symboliques existent sur l'hôte. Les
+    règles et les liens symboliques seront créés la première fois que vous 
+    démarrerez votre système LFS.</para>
+
+    <para>Cependant, si vous avez plusieurs lecteurs CD-ROM, les liens
+    symboliques générés à ce moment peuvent pointer vers des
+    périphériques différents de ceux vers lesquels ils pointent sur
+    votre hôte, car les périphériques ne sont pas découverts dans un
+    ordre prévisible. Les affectations créées quand vous démarrerez pour
+    la première fois le système LFS seront stables, donc cela n'est un
+    problème que si vous avez besoin que les liens symboliques sur les
+    deux systèmes poinjent vers le même périphérique. Si tel est le cas,
+    inspectez (et éditez peut-être) le fichier
+    <filename>/etc/udev/rules.d/70-persistent-cd.rules</filename> généré
+    après le démarrage pour vous assurer que les liens symboliques
+    affectés correspondent à ce dont vous avez besoin.</para>
 
   </sect2>
 
   <sect2>
 
-    <title>Dealing with duplicate devices</title>
+    <title>Gestion des périphériques doubles</title>
+
+    <para>Comme expliqué dans <xref linkend="ch-scripts-udev"/>, l'ordre
+    dans lequel les périphériques ayant la même fonction apparaissent
+    dans <filename class="directory">/dev</filename> est essentiellement
+    aléatoire. Par exemple si vous avez une webcam en USB et un tunner
+    TV, parfois <filename>/dev/video0</filename> renvoie à la webcam, et
+    <filename>/dev/video1</filename> renvoie au tuner, et parfois après
+    un redémarrage l'ordre s'inverse. Pour toutes les classes
+    de matériel sauf les cartes son et les cartes réseau, ceci peut se
+    corriger en créant des règles udev pour des liens symboliques
+    constants personnalisés. Le cas des cartes réseau est couvert de
+    façon séparé dans <xref linkend="ch-scripts-network"/>, et vous
+    pouvez trouver la configuration des cartes son dans
+
+    <ulink url="&blfs-root;">BLFS</ulink>.</para>
+
+    <para>Pour chacun des périphériques susceptibles d'avoir ce problème
+    (même si le problème n'apparaît pas dans votre distribution Linux
+    actuelle), trouvez le répertoire correspondant sous
+
+    <filename class="directory">/sys/class</filename> ou
+
+    <filename class="directory">/sys/block</filename>. Pour les
+    périphériques vidéo, cela peut être 
 
-    <para>As explained in <xref linkend="ch-scripts-udev"/>, the order in
-    which devices with the same function appear in
-    <filename class="directory">/dev</filename> is essentially random.
-    E.g., if you have a USB web camera and a TV tuner, sometimes
-    <filename>/dev/video0</filename> refers to the camera and
-    <filename>/dev/video1</filename> refers to the tuner, and sometimes
-    after a reboot the order changes to the opposite one.
-    For all classes of hardware except sound cards and network cards, this is
-    fixable by creating udev rules for custom persistent symlinks.
-    The case of network cards is covered separately in
-    <xref linkend="ch-scripts-network"/>, and sound card configuration can
-    be found in <ulink url="&blfs-root;">BLFS</ulink>.</para>
-
-    <para>For each of your devices that is likely to have this problem
-    (even if the problem doesn't exist in your current Linux distribution),
-    find the corresponding directory under
-    <filename class="directory">/sys/class</filename> or
-    <filename class="directory">/sys/block</filename>.
-    For video devices, this may be
     <filename
     class="directory">/sys/class/video4linux/video<replaceable>X</replaceable></filename>.
-    Figure out the attributes that identify the device uniquely (usually,
-    vendor and product IDs and/or serial numbers work):</para>
+    Calculez les attributs qui identifient de façon unique un
+    périphérique (normalement basé sur l'ID du fabricant et du produit
+    et/ou les numéros de sïrie)&nbsp;:</para>
 
 <screen role="nodump"><userinput>udevadm info -a -p /sys/class/video4linux/video0</userinput></screen>
 
-    <para>Then write rules that create the symlinks, e.g.:</para>
+      <para>Puis, écrivez des règles qui créent les liens symboliques,
+      comme&nbsp;:</para>
 
 <screen role="nodump"><userinput>cat &gt; /etc/udev/rules.d/83-duplicate_devs.rules &lt;&lt; "EOF"
 <literal>
@@ -138,14 +166,16 @@
 </literal>
 EOF</userinput></screen>
 
-    <para>The result is that <filename>/dev/video0</filename> and
-    <filename>/dev/video1</filename> devices still refer randomly to the tuner
-    and the web camera (and thus should never be used directly), but there are
-    symlinks <filename>/dev/tvtuner</filename> and
-    <filename>/dev/webcam</filename> that always point to the correct
-    device.</para>
+    <para>Il en résulte que les périphériques
+    <filename>/dev/video0</filename> et <filename>/dev/video1</filename>
+    renvoient encore de manière aléatoire au tuner et à la webcam (et
+    donc ne devrait jamais être utilisé directement), mais il y a des
+    liens smboliques <filename>/dev/tvtuner</filename> et
+    <filename>/dev/webcam</filename> qui pointent toujours vers le bon
+    périphérique.</para>
 
-    <para>More information on writing Udev rules can be found in
+    <para>Vous pouvez trouver plus d'informations sur l'écriture de
+    règles Udev dans
     <filename>/usr/share/doc/udev-&udev-version;/index.html</filename>.</para>
 
  </sect2>
diff -Naur BOOK/chapter07/sysklogd.xml BOOKfr/chapter07/sysklogd.xml
--- BOOK/chapter07/sysklogd.xml	2008-07-15 00:49:41.000000000 +0100
+++ BOOKfr/chapter07/sysklogd.xml	2008-07-02 00:40:55.000000000 +0100
@@ -8,19 +8,21 @@
 <sect1 id="ch-scripts-sysklogd">
   <?dbhtml filename="sysklogd.html"?>
 
-  <title>Configuring the sysklogd Script</title>
+  <title>Configurer le script sysklogd</title>
 
   <indexterm zone="ch-scripts-sysklogd">
     <primary sortas="d-sysklogd">sysklogd</primary>
-    <secondary>configuring</secondary>
+    <secondary>configuration</secondary>
   </indexterm>
 
-  <para>The <filename>sysklogd</filename> script invokes the
-  <command>syslogd</command> program with the <parameter>-m 0</parameter> option.
-  This option turns off the periodic timestamp mark that
-  <command>syslogd</command> writes to the log files every 20 minutes by default.
-  If you want to turn on this periodic timestamp mark, edit the
-  <filename>sysklogd</filename> script and make the changes accordingly. See
-  <userinput>man syslogd</userinput> for more information.</para>
+  <para>Le script <filename>sysklogd</filename> invoque le
+  programme <command>syslogd</command> avec l'option
+
+  <parameter>-m 0</parameter>. Cette option désactive la marque
+  périodique que <command>syslogd</command> ajoute. Si vous voulez l'activer,
+  éditez le script <filename>sysklogd</filename> et faites les
+  changements adéquats. Voir la page de manuel
+
+  <userinput>man syslogd</userinput> pour plus d'informations.</para>
 
 </sect1>
diff -Naur BOOK/chapter07/udev.xml BOOKfr/chapter07/udev.xml
--- BOOK/chapter07/udev.xml	2008-07-15 00:49:41.000000000 +0100
+++ BOOKfr/chapter07/udev.xml	2008-07-02 01:57:04.000000000 +0100
@@ -8,343 +8,414 @@
 <sect1 id="ch-scripts-udev">
   <?dbhtml filename="udev.html"?>
 
-  <title>Device and Module Handling on an LFS System</title>
+  <title>Gestion des périphériques et modules sur un système LFS</title>
 
   <indexterm zone="ch-scripts-udev">
     <primary sortas="a-Udev">Udev</primary>
-    <secondary>usage</secondary>
+    <secondary>utilisation</secondary>
   </indexterm>
 
-  <para>In <xref linkend="chapter-building-system"/>, we installed the Udev
-  package. Before we go into the details regarding how this works,
-  a brief history of previous methods of handling devices is in
-  order.</para>
-
-  <para>Linux systems in general traditionally use a static device creation
-  method, whereby a great many device nodes are created under <filename
-  class="directory">/dev</filename> (sometimes literally thousands of nodes),
-  regardless of whether the corresponding hardware devices actually exist. This
-  is typically done via a <command>MAKEDEV</command> script, which contains a
-  number of calls to the <command>mknod</command> program with the relevant
-  major and minor device numbers for every possible device that might exist in
-  the world.</para>
-
-  <para>Using the Udev method, only those devices which are detected by the
-  kernel get device nodes created for them. Because these device nodes will be
-  created each time the system boots, they will be stored on a <systemitem
-  class="filesystem">tmpfs</systemitem> file system (a virtual file system that
-  resides entirely in system memory). Device nodes do not require much space, so
-  the memory that is used is negligible.</para>
+  <para>Dans <xref linkend="chapter-building-system"/>, nous avons
+  installé le paquet Udev. Avant d'aller dans les détails concernant son
+  fonctionnement, un bref historique des méthodes précédentes de gestion
+  des périphériques est nécessaire.</para>
+
+  <para>Les systèmes Linux en général utilisent traditionnellement une
+  méthode de création de périphériques statiques avec laquelle un grand
+  nombre de n&oelig;uds périphériques est créé sous
+
+  <filename class="directory">/dev</filename> (quelque fois des milliers
+  de n&oelig;uds), quel le matériel correspondant existe ou pas. Ceci se
+  fait typiquement avec un script <command>MAKEDEV</command>, qui
+  contient des appels au programme <command>mknod</command> avec les
+  numéros de périphériques majeurs et mineurs pour chaque périphérique
+  possible qui pourrait exister dans le monde.</para>
+
+  <para>En utilisant la méthode udev, seuls les périphériques détectés
+  par le noyau obtiennent des n&oelig;uds périphériques créés pour eux.
+  Comme ces n&oelig;uds périphériques seront créés à chaque lancement du
+  système, ils seront stockés dans un 
+
+  <systemitem class="filesystem">tmpfs</systemitem> (un système de
+  fichiers qui réside entièrement en mémoire). Les n&oelig;uds
+  périphériques ne requièrent pas beaucoup d'espace disque, donc la
+  mémoire utilisée est négligeable.</para>
 
   <sect2>
-    <title>History</title>
+    <title>Historique</title>
 
-    <para>In February 2000, a new filesystem called <systemitem
-    class="filesystem">devfs</systemitem> was merged into the 2.3.46 kernel
-    and was made available during the 2.4 series of stable kernels. Although
-    it was present in the kernel source itself, this method of creating devices
-    dynamically never received overwhelming support from the core kernel
-    developers.</para>
-
-    <para>The main problem with the approach adopted by <systemitem
-    class="filesystem">devfs</systemitem> was the way it handled device
-    detection, creation, and naming. The latter issue, that of device node
-    naming, was perhaps the most critical. It is generally accepted that if
-    device names are allowed to be configurable, then the device naming policy
-    should be up to a system administrator, not imposed on them by any
-    particular developer(s). The <systemitem
-    class="filesystem">devfs</systemitem> file system also suffers from race
-    conditions that are inherent in its design and cannot be fixed without a
-    substantial revision to the kernel. It was marked as deprecated for a long
-    period &ndash; due to a lack of maintenance &ndash; and was finally removed
-    from the kernel in June, 2006.</para>
-
-    <para>With the development of the unstable 2.5 kernel tree, later released
-    as the 2.6 series of stable kernels, a new virtual filesystem called
-    <systemitem class="filesystem">sysfs</systemitem> came to be. The job of
-    <systemitem class="filesystem">sysfs</systemitem> is to export a view of
-    the system's hardware configuration to userspace processes. With this
-    userspace-visible representation, the possibility of seeing a userspace
-    replacement for <systemitem class="filesystem">devfs</systemitem> became
-    much more realistic.</para>
+    <para>En février 2000, un nouveau système de fichiers appelé
+    <systemitem class="filesystem">devfs</systemitem> a été intégré au
+    noyau 2.3.46 et rendu disponible pour la série 2.4 des noyaux
+    stables. Bien qu'il soit présent dans le source du noyau, cette
+    méthode de création dynamique de périphérique n'a jamais reçu un
+    support inconditionnel des développeurs du noyau.</para>
+
+    <para>Le principal problème de l'approche adopté par 
+
+    <systemitem class="filesystem">devfs</systemitem> était la façon dont il gérait la
+
+    détection, la création et le nommage des périphériques. Ce dernier problème, le
+
+    nommage des périphériques, était peut-être le plus critique. Il est
+
+    généralement accepté que s'il est possible de configurer les noms des
+
+    périphériques, alors la politique de nommage des périphériques revient à
+
+    l'administrateur du système, et du coup n'est pas imposée par un ou
+    des développeur(s) en particulier. Le système de fichiers
+
+    <systemitem class="filesystem">devfs</systemitem> souffre aussi de 
+    conditions particulières inhérentes à son concept et ne peut pas
+    être  corrigé sans une revue importante du noyau. Il a aussi été
+    marqué comme obsolète pendant une longue période &mdash; à cause
+    d'un manque de  maintenance &mdash; et a finalement été supprimé du
+    noyau en juin 2006.</para>
+
+    <para>Avec le développement du noyau instable 2.5, sorti ensuite en
+    tant que la série 2.6 des noyaux stables, un nouveau système de
+    fichiers virtuel appelé 
+
+    <systemitem class="filesystem">sysfs</systemitem> est arrivé. Le
+    d'exporter une vue de la configuration matérielle du système pour
+    les processus en espace utilisateur. Avec cette représentation
+    visible de l'espace utilisateur, la possibilité de voir un
+    remplacement de l'espace utilisateur pour  
+
+    <systemitem class="filesystem">devfs</systemitem> est devenu
+    beaucoup plus réaliste.</para>
 
   </sect2>
 
   <sect2>
-    <title>Udev Implementation</title>
+    <title>Implémentation d'Udev</title>
 
     <sect3>
       <title>Sysfs</title>
 
-      <para>The <systemitem class="filesystem">sysfs</systemitem> filesystem was
-      mentioned briefly above. One may wonder how <systemitem
-      class="filesystem">sysfs</systemitem> knows about the devices present on
-      a system and what device numbers should be used for them. Drivers that
-      have been compiled into the kernel directly register their objects with
-      <systemitem class="filesystem">sysfs</systemitem> as they are detected by
-      the kernel. For drivers compiled as modules, this registration will happen
-      when the module is loaded. Once the <systemitem
-      class="filesystem">sysfs</systemitem> filesystem is mounted (on <filename
-      class="directory">/sys</filename>), data which the built-in drivers
-      registered with <systemitem class="filesystem">sysfs</systemitem> are
-      available to userspace processes and to <command>udevd</command> for device
-      node creation.</para>
-
-    </sect3>
-
-    <sect3>
-      <title>Udev Bootscript</title>
-
-      <para>The <command>S10udev</command> initscript takes care of creating
-      device nodes when Linux is booted. The script unsets the uevent handler
-      from the default of <command>/sbin/hotplug</command>.  This is done
-      because the kernel no longer needs to call out to an external binary.
-      Instead <command>udevd</command> will listen on a netlink socket for
-      uevents that the kernel raises. Next, the bootscript copies any static
-      device nodes that exist in <filename
-      class="directory">/lib/udev/devices</filename> to <filename
-      class="directory">/dev</filename>. This is necessary because some devices,
-      directories, and symlinks are needed before the dynamic device handling
-      processes are available during the early stages of booting a system, or
-      are required by <command>udevd</command> itself.  Creating static device
-      nodes in <filename class="directory">/lib/udev/devices</filename> also
-      provides an easy workaround for devices that are not supported by the
-      dynamic device handling infrastructure. The bootscript then starts the
-      Udev daemon, <command>udevd</command>, which will act on any uevents it
-      receives. Finally, the bootscript forces the kernel to replay uevents for
-      any devices that have already been registered and then waits for
-      <command>udevd</command> to handle them.</para>
-
-    </sect3>
-
-    <sect3>
-      <title>Device Node Creation</title>
-
-      <para>To obtain the right major and minor number for a device, Udev relies
-      on the information provided by <systemitem
-      class="filesystem">sysfs</systemitem> in <filename
-      class="directory">/sys</filename>.  For example,
-      <filename>/sys/class/tty/vcs/dev</filename> contains the string
-      <quote>7:0</quote>. This string is used by <command>udevd</command>
-      to create a device node with major number <emphasis>7</emphasis> and minor
-      <emphasis>0</emphasis>. The names and permissions of the nodes created
-      under the <filename class="directory">/dev</filename> directory are
-      determined by rules specified in the files within the <filename
-      class="directory">/etc/udev/rules.d/</filename> directory. These are
-      numbered in a similar fashion to the LFS-Bootscripts package. If
-      <command>udevd</command> can't find a rule for the device it is creating,
-      it will default permissions to <emphasis>660</emphasis> and ownership to
-      <emphasis>root:root</emphasis>. Documentation on the syntax of the Udev
-      rules configuration files are available in
-      <filename>/usr/share/doc/udev-&udev-version;/index.html</filename></para>
-
-    </sect3>
-
-    <sect3>
-      <title>Module Loading</title>
-
-      <para>Device drivers compiled as modules may have aliases built into them.
-      Aliases are visible in the output of the <command>modinfo</command>
-      program and are usually related to the bus-specific identifiers of devices
-      supported by a module. For example, the <emphasis>snd-fm801</emphasis>
-      driver supports PCI devices with vendor ID 0x1319 and device ID 0x0801,
-      and has an alias of <quote>pci:v00001319d00000801sv*sd*bc04sc01i*</quote>.
-      For most devices, the bus driver exports the alias of the driver that
-      would handle the device via <systemitem
-      class="filesystem">sysfs</systemitem>. E.g., the
-      <filename>/sys/bus/pci/devices/0000:00:0d.0/modalias</filename> file
-      might contain the string
+      <para>Le système de fichier
+
+      <systemitem class="filesystem">sysfs</systemitem>. On pourrait se
+      demander comment <systemitem class="filesystem">sysfs</systemitem>
+      connaît les périphériques présents sur un système et quels numéros
+      de périphériques devraient être utilisés. Les pilotes qui ont été
+      compilés directement dans le noyau enregistrent leur objet avec
+      <systemitem class="filesystem">sysfs</systemitem> quand ils sont
+      détectés par le noyau. Pour les pilotes compilés en tant que
+      modules, cet enregistrement surviendra quand le module sera
+      chargé. Une fois que le système de fichier
+
+      <systemitem class="filesystem">sysfs</systemitem> est monté (sur
+      <filename class="directory">/sys</filename>), les données
+      enregistrées par les pilotes internes avec
+
+      <systemitem class="filesystem">sysfs</systemitem> sont disponibles
+      pour les processus en espace utilisateur ainsi qu'à
+      <command>udev</command> pour la création des n&oelig;uds
+      périphériques.</para>
+
+    </sect3>
+
+    <sect3>
+      <title>Scripts de démarrage d'Udev</title>
+
+      <para>Le script de démarrage <command>S10udev</command> fait
+      attention à créer les n&oelig;uds périphériques au lancement de
+      Linux. Le script supprime la gestion des uevents de 
+      <command>/sbin/hotplug</command> par défaut. On fait cela car le
+      noyau n'a plus besoin de faire appel à un binaire externe. À la
+      place, <command>udevd</command> écoutera sur un socket netlink les
+      uevents que le noyau fait apparaître. Puis, le script de démarrage
+      copie les n&oelig;uds des périphériques statiques qui existent
+      dans <filename class="directory">/lib/udev/devices</filename> vers
+      <filename class="directory">/dev</filename>. Cela est nécessaire
+      car certains périphériques, répertoires et liens symboliques sont
+      requis avant que les processus de gestion du périphérique
+      dynamique ne soient disponibles pendant les premières étapes du
+      démarrage d'un système, ou car  <command>udevd</command> lui-même
+      les exige. La création des n&oelig;uds vers un périphérique
+      statique dans
+
+      <filename class="directory">/lib/udev/devices</filename> fournit
+      aussi un environnement de travail facile pour les périphériques
+      qui ne sont pas supportés par l'infrastructure de gestion des
+      périphériques en dynamique. Ensuite le script de démarrage lance
+      le démon Udev, <command>udevd</command>, qui agira sur tous les
+      uevents qu'il reçoit. Enfin, le script de démarrage oblige le
+      noyau à répéter des uevents pour chaque périphérique qui a été
+      déjà enregistré puis attend que <command>udevd</command> les
+      gère.</para>
+
+    </sect3>
+
+    <sect3>
+      <title>Création de n&oelig;uds de périphérique</title>
+
+      <para>Pour obtenir le bon nombre majeur ou mineur d'un périphérique,
+      Udev s'appuie sur les informations fournies par 
+      <systemitem class="filesystem">sysfs</systemitem> dans
+      <filename class="directory">/sys</filename>. Par exemple,
+      <filename>/sys/class/tty/vcs/dev</filename> contient la chaîne
+      <quote>7:0</quote>. Cette chaîne est utilisée par <command>udevd</command>
+      pour créer un n&oelig;ud de périphérique avec un nombre majeur
+      <emphasis>7</emphasis> et et un nombre mineur <emphasis>0</emphasis>. Les noms
+      et les droits des n&oelig;uds sous le répertoire 
+      <filename class="directory">/dev</filename> sont déterminés par des
+      règles spécifiés dans des fichiers à l'intérieur du répertoire
+		<filename class="directory">/etc/udev/rules.d/</filename>. Celles-ci
+      sont numérotées d'une façon similaire au paquet LFS-Bootscripts. Si
+      <command>udevd</command> ne peut trouver une règle pour le périphérique
+     qu'il est en train de créer, il attribuera par défaut des droits 
+     <emphasis>660</emphasis> et la propriété à <emphasis>root:root</emphasis>.
+     La documentation sur la syntaxe des fichiers de configuration des
+     règles Udev est disponible dans <filename>/usr/share/doc/udev-&udev-version;/index.html</filename></para>
+
+    </sect3>
+
+    <sect3>
+      <title>Chargement d'un module</title>
+
+      <para>Il se peut que les pilotes des périphériques compilés en
+      module aient des aliases compilés en eux. Les aliases sont
+      visibles dans la sortie du programme <command>modinfo</command> et
+      sont souvent liés aux identifiants spécifiques au bus des
+      périphériques supportés par un module. Par exemple, le pilote
+      <emphasis>snd-fm801</emphasis> supporte les périphériques PCI
+      ayant l'ID fabricant 0x1319 et l'ID de périphérique 0x0801, et il
+      a un alias qui est 
+      <quote>pci:v00001319d00000801sv*sd*bc04sc01i*</quote>. Pour la
+      plupart des périphériques, le pilote du bus définit l'alias du
+      pilote qui gérerait le périphérique via  <systemitem
+      class="filesystem">sysfs</systemitem>. Par exemple, le fichier
+      <filename>/sys/bus/pci/devices/0000:00:0d.0/modalias</filename>
+      pourrait contenir la chaîne 
       <quote>pci:v00001319d00000801sv00001319sd00001319bc04sc01i00</quote>.
-      The default rules provided with Udev will cause <command>udevd</command>
-      to call out to <command>/sbin/modprobe</command> with the contents of the
-      <envar>MODALIAS</envar> uevent environment variable (which should be the
-      same as the contents of the <filename>modalias</filename> file in sysfs),
-      thus loading all modules whose aliases match this string after wildcard
-      expansion.</para>
+      Il résultera des règles par défaut fournies avec Udev que
+      <command>udevd</command> fera appel à 
+      <command>/sbin/modprobe</command> avec le contenu de la variable
+      d'environnement de l'uevent <envar>MODALIAS</envar>  qui devrait
+      être la même que le contenu du fichier
+      <filename>modalias</filename> dans sysfs), donc le chargement de
+      après les expansions génériques.</para>
 
-      <para>In this example, this means that, in addition to
-      <emphasis>snd-fm801</emphasis>, the obsolete (and unwanted)
-      <emphasis>forte</emphasis> driver will be loaded if it is
-      available. See below for ways in which the loading of unwanted drivers can
-      be prevented.</para>
+      <para>Dans cet exemple, cela signifie que, outre <emphasis>snd-fm801</emphasis>,
+     le pilote <emphasis>forte</emphasis> obsolète (dont on ne veut pas 
+     sera chargé s'il est disponible. Voir ci-dessous les moyens d'empêcher
+      le chargement des modules indésirables.</para>
 
-      <para>The kernel itself is also able to load modules for network
-      protocols, filesystems and NLS support on demand.</para>
+      <para>Le noyau lui-même est aussi capable de charger des modules
+      de protocole réseau, de support pour des systèmes de fichiers et
+      des NLS sur demande.</para>
 
     </sect3>
 
     <sect3>
-      <title>Handling Hotpluggable/Dynamic Devices</title>
+      <title>Gestion des périphériques dynamiques/montables à chaud</title>
 
-      <para>When you plug in a device, such as a Universal Serial Bus (USB) MP3
-      player, the kernel recognizes that the device is now connected and
-      generates a uevent. This uevent is then handled by
-      <command>udevd</command> as described above.</para>
+      <para>Quand vous connectez un périphérique, comme un lecteur MP3
+      USB (<foreignphrase>Universal Serial Bus</foreignphrase>), le
+      noyau reconnaît que le périphérique est maintenant connecté et
+      génère un uevent. Cet uevent est alors géré par
+      <command>udevd</command> comme décrit ci-dessus.</para>
 
     </sect3>
 
   </sect2>
 
   <sect2>
-    <title>Problems with Loading Modules and Creating Devices</title>
+    <title>Problèmes avec le chargement des modules et la création des périphériques</title>
 
-    <para>There are a few possible problems when it comes to automatically
-    creating device nodes.</para>
+    <para>Il existe quelques problèmes connus pour la création
+    automatique des n&oelig;uds périphériques&nbsp;:</para>
 
     <sect3>
-      <title>A kernel module is not loaded automatically</title>
-
-      <para>Udev will only load a module if it has a bus-specific alias and the
-      bus driver properly exports the necessary aliases to <systemitem
-      class="filesystem">sysfs</systemitem>. In other cases, one should
-      arrange module loading by other means. With Linux-&linux-version;, Udev is
-      known to load properly-written drivers for INPUT, IDE, PCI, USB, SCSI,
-      SERIO and FireWire devices.</para>
-
-      <para>To determine if the device driver you require has the necessary
-      support for Udev, run <command>modinfo</command> with the module name as
-      the argument.  Now try locating the device directory under
-      <filename class="directory">/sys/bus</filename> and check whether there is
-      a <filename>modalias</filename> file there.</para>
+      <title>Un module du noyau n'est pas chargé automatiquement</title>
 
-      <para>If the <filename>modalias</filename> file exists in <systemitem
-      class="filesystem">sysfs</systemitem>, the driver supports the device and
-      can talk to it directly, but doesn't have the alias, it is a bug in the
-      driver. Load the driver without the help from Udev and expect the issue
-      to be fixed later.</para>
-
-      <para>If there is no <filename>modalias</filename> file in the relevant
-      directory under <filename class="directory">/sys/bus</filename>, this
-      means that the kernel developers have not yet added modalias support to
-      this bus type. With Linux-&linux-version;, this is the case with ISA
-      busses. Expect this issue to be fixed in later kernel versions.</para>
-
-      <para>Udev is not intended to load <quote>wrapper</quote> drivers such as
-      <emphasis>snd-pcm-oss</emphasis> and non-hardware drivers such as
-      <emphasis>loop</emphasis> at all.</para>
+      <para>Udev ne chargera un module que s'il a un alias spécifique au
+      bus et si le pilote du bus envoie correctement les alias
+      nécessaires vers <systemitem class="filesystem">sysfs</systemitem>.
+      Sinon, il faut organiser le chargement de modules par d'autres
+      sens. Avec Linux-&linux-version;, Udev est connu pour charger les
+      pilotes correctement écrits pour les périphériques INPUT, IDE,
+      PCI, USB, SCSI, SERIO et FireWire.</para>
+
+      <para>Pour déterminer si le pilote du périphérique dont vous avez
+      besoin a le support nécessaire pour Udev, lancez
+      <command>modinfo</command> avec le nom du module comme argument.
+      Maintenant, essayez de localiser le répertoire du périphérique
+      sous <filename class="directory">/sys/bus</filename> et vérifiez
+      s'il y a un fichier <filename>modalias</filename> là-bas.</para>
+
+      <para>Si le fichier <filename>modalias</filename> existe dans
+      <systemitem class="filesystem">sysfs</systemitem>, si le pilote
+      supporte le périphérique et s'il peut lui parler directement, mais
+      s'il n'a pas d'alias, c'est un bogue dans le pilote. Chargez le
+      pilote sans l'aide d'Udev et attendez que le problème soit corrigé
+      plus tard.</para>
+
+      <para>S'il n'y a pas de fichier <filename>modalias</filename> dans
+      le bon répertoire sous
+
+      <filename class="directory">/sys/bus</filename>, cela signifie que
+      les développeurs du noyau n'ont pas encore ajouté de support
+      modalias à ce type de bus. Avec Linux-&linux-version;, c'est le
+      cas pour les bus ISA. Attendez que ce problème soit réparé dans
+      les versions ultérieures du noyau.</para>
+
+      <para>Udev n'a pas du tout pour but de charger des pilotes
+      <quote>emballés</quote> comme <emphasis>snd-pcm-oss</emphasis> et
+      des pilotes non matériels comme <emphasis>loop</emphasis>.</para>
 
     </sect3>
 
     <sect3>
-      <title>A kernel module is not loaded automatically, and Udev is not
-      intended to load it</title>
-
-      <para>If the <quote>wrapper</quote> module only enhances the functionality
-      provided by some other module (e.g., <emphasis>snd-pcm-oss</emphasis>
-      enhances the functionality of <emphasis>snd-pcm</emphasis> by making the
-      sound cards available to OSS applications), configure
-      <command>modprobe</command> to load the wrapper after Udev loads the
-      wrapped module. To do this, add an <quote>install</quote> line in
-      <filename>/etc/modprobe.conf</filename>. For example:</para>
+      <title>Un module du noyau n'est pas chargé automatiquement et 
+      Udev n'est pas prévu pour le charger</title>
+
+      <para>Si le module <quote>emballé</quote> n'améliore que la
+      fonctionnalité fournie par un autre module (comme
+      <emphasis>snd-pcm-oss</emphasis> améliore la fonctionnalité de
+      <emphasis>snd-pcm</emphasis> en rendant les cartes son disponibles
+      pour les applications OSS), configurez la commande
+      <command>modprobe</command> pour charger le wrapper après qu'Udev a
+      chargé le module emballé. Pour cela, ajoutez une ligne
+      <quote>install</quote> dans
+      <filename>/etc/modprobe.conf</filename>. Par exemple&nbsp;:</para>
 
 <screen role="nodump"><literal>install snd-pcm /sbin/modprobe -i snd-pcm ; \
     /sbin/modprobe snd-pcm-oss ; true</literal></screen>
 
-      <para>If the module in question is not a wrapper and is useful by itself,
-      configure the <command>S05modules</command> bootscript to load this
-      module on system boot. To do this, add the module name to the
-      <filename>/etc/sysconfig/modules</filename> file on a separate line.
-      This works for wrapper modules too, but is suboptimal in that case.</para>
+      <para>Si le module en question n'est pas un emballage et s'avère
+      utile en tant que tel, configurez le script de démarrage
+      <command>S05modules</command> pour charger ce module sur le
+      système de démarrage. Pour cela, ajoutez le nom du module au
+      fichier <filename>/etc/sysconfig/modules</filename> sur une ligne
+      séparée. Cela fonctionne aussi pour les modules emballage, mais ce
+      n'est pas optimal dans ce cas.</para>
 
     </sect3>
 
     <sect3>
-      <title>Udev loads some unwanted module</title>
+      <title>Udev charge un module indésirable</title>
 
-      <para>Either don't build the module, or blacklist it in
-      <filename>/etc/modprobe.conf</filename> file as done with the
-      <emphasis>forte</emphasis> module in the example below:</para>
+      <para>Ne compilez pas le module, ou mettez-le en liste noire dans
+      le fichier <filename>/etc/modprobe.conf</filename> comme cela est
+      fait avec le module <emphasis>forte</emphasis> dans l'exemple
+      ci-dessous&nbsp;:</para>
 
 <screen role="nodump"><literal>blacklist forte</literal></screen>
 
-      <para>Blacklisted modules can still be loaded manually with the
-      explicit <command>modprobe</command> command.</para>
+      <para>Les modules en liste noire peuvent toujours être chargés
+      manuellement avec la commande explicite 
+      <command>modprobe</command>.</para>
 
     </sect3>
 
     <sect3>
-      <title>Udev creates a device incorrectly, or makes a wrong symlink</title>
+      <title>Udev crée mal un périphérique, ou crée un mauvais lien
+      symbolique</title>
 
-      <para>This usually happens if a rule unexpectedly matches a device. For
-      example, a poorly-writen rule can match both a SCSI disk (as desired)
-      and the corresponding SCSI generic device (incorrectly) by vendor.
-      Find the offending rule and make it more specific, with the help of the
-      <command>udevadm info</command> command.</para>
+      <para>Cela se produit normalement si une règle correspond à un
+      périphérique de façon imprévue. Par exemple, une règle écrite de
+      avec des lacunes peut correspondre à un disque SCSI (comme désiré)
+      et au périphérique générique SCSI correspondant (de façon
+      incorrecte) par le fabricant. Trouvez la règle défectueuse et
+      rendez-la plus précise, à l'aide de la commande
+      <command>udevadm info</command></para>
 
     </sect3>
 
     <sect3>
-      <title>Udev rule works unreliably</title>
+      <title>Une règle Udev fonctionne de manière non fiable</title>
 
-      <para>This may be another manifestation of the previous problem. If not,
-      and your rule uses <systemitem class="filesystem">sysfs</systemitem>
-      attributes, it may be a kernel timing issue, to be fixed in later kernels.
-      For now, you can work around it by creating a rule that waits for the used
-      <systemitem class="filesystem">sysfs</systemitem> attribute and appending
-      it to the <filename>/etc/udev/rules.d/10-wait_for_sysfs.rules</filename>
-      file (create this file if it does not exist). Please notify the LFS
-      Development list if you do so and it helps.</para>
+      <para>Cela peut être une autre manifestation du problème
+      précédent. Sinon, et si votre règle utilise les attributs de 
+      <systemitem class="filesystem">sysfs</systemitem>, il se peut que
+      ce soit un problème de timing du noyau, sur le point d'être
+      corrigé dans les noyaux ultérieurs. Pour le moment, vous pouvez
+      contourner en créant une règle qui attend l'attribut
+
+      <systemitem class="filesystem">sysfs</systemitem> utilisé et en la
+      mettant dans le fichier
+      <filename>/etc/udev/rules.d/10-wait_for_sysfs.rules</filename>
+      (créez ce fichier s'il n'existe pas). Merci d'informer la liste de
+      développement de LFS si vous faites ainsi et que cela vous
+      aide.</para>
 
     </sect3>
 
     <sect3>
-      <title>Udev does not create a device</title>
+      <title>Udev ne crée pas de périphérique</title>
 
-      <para>Further text assumes that the driver is built statically into the
-      kernel or already loaded as a module, and that you have already checked
-      that Udev doesn't create a misnamed device.</para>
+      <para>Le texte ci-après assume que le pilote est compilé de
+      manière statique dans le noyau ou qu'il est déjà chargé comme
+      module, et que vous avez déjà vérifié qu'Udev ne crée pas de
+      périphérique mal nommé.</para>
 
-      <para>Udev has no information needed to create a device node if a kernel
-      driver does not export its data to <systemitem
-      class="filesystem">sysfs</systemitem>.
-      This is most common with third party drivers from outside the kernel
-      tree. Create a static device node in
-      <filename>/lib/udev/devices</filename> with the appropriate major/minor
-      numbers (see the file <filename>devices.txt</filename> inside the kernel
-      documentation or the documentation provided by the third party driver
-      vendor). The static device node will be copied to
-      <filename class="directory">/dev</filename> by the
-      <command>S10udev</command> bootscript.</para>
+      <para>Udev n'a pas besoin d'information pour créer un n&oelig;ud
+      périphérique si le pilote du noyau n'envoie pas ses données vers 
+      <systemitem class="filesystem">sysfs</systemitem>. C'est ce qu'il
+      y a de plus courant avec les pilotes de tierces parties à
+      l'extérieur de l'arborescence du noyau. Créez un rieur de
+      l'arborescence du noyau. Créez un n&oelig;ud de périphérique
+      statique dans <filename>/lib/udev/devices</filename> avec les
+      numéros majeurs/mineurs appropriés (voir le fichier
+      <filename>devices.txt</filename> dans la documentation du noyau ou
+      la documentation fournie par le fabricant du pilote tierce
+      partie). Le n&oelig;ud du périphérique statique sera copié vers 
+      <filename class="directory">/dev</filename> par le script de
+      démarrage <command>S10udev</command>.</para>
 
     </sect3>
 
     <sect3>
-      <title>Device naming order changes randomly after rebooting</title>
+      <title>Le nommage des périphériques change de manière aléatoire après
+      le redémarrage</title>
+
+      <para>Cela est dû au fait que Udev, par nature, gère les uevents
+      et charge les modules en parallèle, donc dans un ordre
+      imprévisible. Cela ne sera jamais <quote>corrigé</quote>. Vous ne
+      devriez pas espérer que les noms des périphériques du noyau sont 
+      stables. Créez plutôt vos propres règles qui rendent les liens
+      symboliques stables basés sur des attributs stables du
+      périphérique, comme une série de nombre ou la sortie de divers
+      utilitaires *_id installés par Udev. Voir
+
+      <xref linkend="ch-scripts-symlinks"/> et
 
-      <para>This is due to the fact that Udev, by design, handles uevents and
-      loads modules in parallel, and thus in an unpredictable order. This will
-      never be <quote>fixed</quote>. You should not rely upon the kernel device
-      names being stable. Instead, create your own rules that make symlinks with
-      stable names based on some stable attributes of the device, such as a
-      serial number or the output of various *_id utilities installed by Udev.
-      See <xref linkend="ch-scripts-symlinks"/> and
-      <xref linkend="ch-scripts-network"/> for examples.</para>
+      <xref linkend="ch-scripts-network"/> pour des exemples.</para>
 
     </sect3>
 
   </sect2>
 
   <sect2>
-    <title>Useful Reading</title>
+    <title>Lecture utile</title>
 
-    <para>Additional helpful documentation is available at the following
-    sites:</para>
+    <para>Des documentations supplémentaires sont disponibles sur les
+    sites suivants&nbsp;:</para>
 
     <itemizedlist>
 
       <listitem>
         <para>A Userspace Implementation of <systemitem class="filesystem">devfs</systemitem>
-        <ulink url="http://www.kroah.com/linux/talks/ols_2003_udev_paper/Reprint-Kroah-Hartman-OLS2003.pdf"/></para>
+        <ulink url="http://www.kroah.com/linux/talks/ols_2003_udev_paper/Reprint-Kroah-Hartman-OLS2003.pdf"/>
+        (NdT&nbsp;: Une implémentation en espace utilisateur de devfs)</para>
       </listitem>
 
       <listitem>
-        <para>udev FAQ
+        <para>FAQ udev
         <ulink url="http://www.kernel.org/pub/linux/utils/kernel/hotplug/udev-FAQ"/></para>
       </listitem>
 
       <listitem>
         <para>The <systemitem class="filesystem">sysfs</systemitem> Filesystem
-        <ulink url="http://www.kernel.org/pub/linux/kernel/people/mochel/doc/papers/ols-2005/mochel.pdf"/></para>
+        <ulink url="http://www.kernel.org/pub/linux/kernel/people/mochel/doc/papers/ols-2005/mochel.pdf"/>
+
+        (NdT&nbsp;: Le système de fichier
+
+        <systemitem class="filesystem">sysfs</systemitem>)</para>
       </listitem>
 
     </itemizedlist>
diff -Naur BOOK/chapter07/usage.xml BOOKfr/chapter07/usage.xml
--- BOOK/chapter07/usage.xml	2008-07-15 00:49:41.000000000 +0100
+++ BOOKfr/chapter07/usage.xml	2008-07-02 00:02:37.000000000 +0100
@@ -8,122 +8,154 @@
 <sect1 id="ch-scripts-usage">
   <?dbhtml filename="usage.html"?>
 
-  <title>How Do These Bootscripts Work?</title>
+  <title>Comment fonctionnent ces scripts de démarrage&nbsp;?</title>
 
   <indexterm zone="ch-scripts-usage">
     <primary sortas="a-Bootscripts">Bootscripts</primary>
-    <secondary>usage</secondary>
+    <secondary>utilisation</secondary>
   </indexterm>
 
-  <para>Linux uses a special booting facility named SysVinit that is based on a
-  concept of <emphasis>run-levels</emphasis>. It can be quite different from one
-  system to another, so it cannot be assumed that because things worked in one
-  particular Linux distribution, they should work the same in LFS too. LFS has its
-  own way of doing things, but it respects generally accepted standards.</para>
-
-  <para>SysVinit (which will be referred to as <quote>init</quote> from now on)
-  works using a run-levels scheme. There are seven (numbered 0 to 6) run-levels
-  (actually, there are more run-levels, but they are for special cases and are
-  generally not used. See <filename>init(8)</filename> for more details), and
-  each one of those corresponds to the actions the computer is supposed to
-  perform when it starts up. The default run-level is 3. Here are the
-  descriptions of the different run-levels as they are 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 <command>xdm</command> or KDE's <command>kdm</command>)
-6: reboot the computer</literallayout>
-
-  <para>The command used to change run-levels is <command>init
-  <replaceable>&lt;runlevel&gt;</replaceable></command>, where
-  <replaceable>&lt;runlevel&gt;</replaceable> is the target run-level. For example, to
-  reboot the computer, a user could issue the <command>init 6</command> command,
-  which is an alias for the <command>reboot</command> command. Likewise,
-  <command>init 0</command> is an alias for the <command>halt</command>
-  command.</para>
-
-  <para>There are a number of directories under <filename
-  class="directory">/etc/rc.d</filename> that look like <filename
-  class="directory">rc?.d</filename> (where ? is the number of the run-level) and
-  <filename class="directory">rcsysinit.d</filename>, all containing a number of
-  symbolic links. Some begin with a <emphasis>K</emphasis>, the others begin with
-  an <emphasis>S</emphasis>, and all of them have two 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&mdash;the lower the number the earlier it gets executed. When
-  <command>init</command> switches to another run-level, the appropriate services
-  are either started or stopped, depending on the runlevel chosen.</para>
-
-  <para>The real scripts are in <filename
-  class="directory">/etc/rc.d/init.d</filename>. They do the actual work, and
-  the symlinks all point to them. Killing links and starting links point to
-  the same script in <filename class="directory">/etc/rc.d/init.d</filename>.
-  This is because the scripts can be called with different parameters like
-  <parameter>start</parameter>, <parameter>stop</parameter>,
-  <parameter>restart</parameter>, <parameter>reload</parameter>, and
-  <parameter>status</parameter>. When a K link is encountered, the appropriate
-  script is run with the <parameter>stop</parameter> argument. When an S link
-  is encountered, the appropriate script is run with the
-  <parameter>start</parameter> argument.</para>
-
-  <para>There is one exception to this explanation. Links that start
-  with an <emphasis>S</emphasis> in the <filename
-  class="directory">rc0.d</filename> and <filename
-  class="directory">rc6.d</filename> directories will not cause anything
-  to be started. They will be called with the parameter
-  <parameter>stop</parameter> to stop something. The logic behind this
-  is that when a user is going to reboot or halt the system, nothing
-  needs to be started.  The system only needs to be stopped.</para>
+  <para>Linux utilise un service de démarrage spécial nommé SysVinit qui
+  est basé sur un concept de <emphasis>niveaux d'exécution</emphasis>.
+  Cela peut être bien différent d'un système à un autre, du coup, il ne
+  peut pas être supposé que, parce que cela fonctionne dans une
+  distribution Linux particulière, cela fonctionnera de la même façon
+  dans LFS. LFS a sa propre façon de le faire mais il respecte
+  généralement les standards établis.</para>
+
+  <para>SysVinit (qui sera nommé par la suite <quote>init</quote>)
+  fonctionne en utilisant un schéma de niveaux d'exécution. Ils sont au
+  nombre de sept (numéroté de 0 à 6). En fait, il en existe plus mais
+  ils sont pour des cas spéciaux et ne sont généralement pas utilisés.
+  Voir <filename>init(8)</filename> pour plus de détails. Chacun d'entre
+  eux correspond à des actions que l'ordinateur est supposé effectuer
+  lorsqu'il démarre. Le niveau d'exécution par défaut est 3. Voici les
+  descriptions sur l'implémentation des différents niveaux
+  d'exécution&nbsp;:</para>
+
+<literallayout>
+
+0: arrête l'ordinateur
+
+1: mode simple utilisateur
+
+2: mode multi-utilisateur sans réseau 
+
+3: mode multi-utilisateur avec réseau
+
+4: réservé pour la personnalisation, sinon identique à 3
+
+5: identique à 4, il est habituellement utilisé pour la connexion GUI
+(comme <command>xdm</command> de X ou <command>kdm</command> de KDE) 
+
+6: redémarre l'ordinateur</literallayout>
+
+  <para>La commande utilisée pour modifier le niveau d'exécution est
+  <command>init
+  <replaceable>&lt;[niveau_exécution]&gt;</replaceable></command>, où
+  <replaceable>&lt;[niveau_exécution]&gt;</replaceable> est le niveau
+  d'exécution cible.
+
+  Par exemple, pour redémarrer l'ordinateur, un utilisateur pourrait
+  lancer la commande <command>init 6</command> qui est un alias de la
+  commande <command>reboot</command>. De même, <command>init 0</command>
+  est un alias pour la commande <command>halt</command>.</para>
+
+  <para>Il existe un certain nombre de répertoires sous
+
+  <filename class="directory">/etc/rc.d</filename> qui ressemble à
+  <filename class="directory">rc?.d</filename> (où ? est le numéro du
+  niveau d'exécution) et 
+
+  <filename class="directory">rcsysinit.d</filename>, tous contenant un
+  certain nombre de liens symboliques. Certains commencent avec un
+  <emphasis>K</emphasis>, les autres avec un <emphasis>S</emphasis>, et
+  tous ont deux nombres après la lettre initiale. Le K signifie l'arrêt
+  (kill) d'un service et le S son lancement (start). Les nombres
+  déterminent l'ordre dans lequel les scripts sont exécutés, de 00 à
+  99&mdash;plus ce nombre est petit, plus tôt le script correspondant
+  sera exécuté. Quand <command>init</command> bascule sur un autre
+  niveau d'exécution, les services appropriés sont soit lancé soit tués,
+  suivant le niveau d'exécution choisi.</para>
+
+  <para>Les vrais scripts sont dans
+
+  <filename class="directory">/etc/rc.d/init.d</filename>. Ils font le
+  vrai boulot et les liens symboliques pointent tous vers eux. Les liens
+  d'arrêt et de lancement pointent vers le même script dans 
+
+  <filename class="directory">/etc/rc.d/init.d</filename>. Ceci est dû
+  au fait que les scripts peuvent être appelés avec différents
+  paramètres comme <parameter>start</parameter>,
+  <parameter>stop</parameter>, <parameter>restart</parameter>,
+  <parameter>reload</parameter> et <parameter>status</parameter>. Quand
+  un lien K est rencontré, le script approprié est lancé avec l'argument
+  <parameter>stop</parameter>. Quand un lien S est rencontré, le script
+  approprié est lancé avec l'argument
+  <parameter>start</parameter>.</para>
+
+  <para>Il existe une exception à cette explication. Les liens
+  commençant avec un <emphasis>S</emphasis> dans les répertoires
+  <filename class="directory">rc0.d</filename> et
+
+  <filename class="directory">rc6.d</filename> ne lanceront aucun
+  service. Ils seront
+
+  appelés avec l'argument <parameter>stop</parameter> pour arrêter
+  quelque chose.
+
+  La logique derrière ceci est que, quand un utilisateur va redémarrer
+  ou arrêter le système, rien ne doit être lancé. Le système a seulement
+  besoin d'être stoppé.<</para>
 
-  <para>These are descriptions of what the arguments make the scripts
-  do:</para>
+  <para>Voici des descriptions de ce que font les arguments des
+
+  scripts&nbsp;:</para>
 
   <variablelist>
 
     <varlistentry>
       <term><parameter>start</parameter></term>
       <listitem>
-        <para>The service is started.</para>
+        <para>Le service est lancé.</para>
       </listitem>
     </varlistentry>
 
     <varlistentry>
       <term><parameter>stop</parameter></term>
       <listitem>
-        <para>The service is stopped.</para>
+        <para>Le service est stoppé.</para>
       </listitem>
     </varlistentry>
 
     <varlistentry>
       <term><parameter>restart</parameter></term>
       <listitem>
-        <para>The service is stopped and then started again.</para>
+        <para>Le service est stoppé puis de nouveau lancé.</para>
       </listitem>
     </varlistentry>
 
     <varlistentry>
       <term><parameter>reload</parameter></term>
       <listitem>
-        <para>The configuration of the service is updated.
-        This is used after the configuration file of a service was modified, when
-        the service does not need to be restarted.</para>
+        <para>La configuration du service est mise à jour. Ceci est utilisé
+        après que le fichier de configuration d'un service a été modifié, quand le
+        service n'a pas besoin d'être redémarré.</para>
       </listitem>
     </varlistentry>
 
     <varlistentry>
       <term><parameter>status</parameter></term>
       <listitem>
-        <para>Tells if the service is running and with which PIDs.</para>
+        <para>Indique si le service est en cours d'exécution ainsi que les
+        PID associés.</para>
       </listitem>
     </varlistentry>
 
   </variablelist>
 
-  <para>Feel free to modify the way the boot process works (after all,
-  it is your own LFS system). The files given here are an example of how
-  it can be done.</para>
+  <para>Vous êtes libre de modifier la façon dont le processus de
+  démarrage fonctionne (après tout, c'est votre système LFS). Les
+  fichiers donnés ici sont un exemple d'une façon de faire.</para>
 
 </sect1>
