Subversion Repositories svn LFS-FR

Compare Revisions

Ignore whitespace Rev 6577 → Rev 6578

/trunk/clfs/maj
1,253 → 1,3
diff -ru /home/jp/a/BOOK/bootable/x86/kernel.xml BOOK/bootable/x86/kernel.xml
--- /home/jp/a/BOOK/bootable/x86/kernel.xml 2014-05-11 16:24:52.618516679 +0200
+++ BOOK/bootable/x86/kernel.xml 2014-10-03 20:44:43.900339261 +0200
@@ -8,7 +8,7 @@
<sect1 id="ch-bootable-kernel" role="wrap">
<?dbhtml filename="kernel.html"?>
- <title>Linux-&linux-version;</title>
+ <title>Linux-&linux-version2;</title>
<indexterm zone="ch-bootable-kernel">
<primary sortas="a-Linux">Linux</primary>
@@ -27,6 +27,10 @@
file in the kernel source tree for alternative methods to the way this
book configures the kernel.</para>
+ <para os="p1">Apply the latest Linux sublevel patch:</para>
+
+<screen os="p2"><userinput>xzcat ../&linux-sublevel-patch; | patch -Np1 -i -</userinput></screen>
+
<para os="b">Prepare for compilation by running the following command:</para>
<screen os="c"><userinput>make mrproper</userinput></screen>
@@ -36,11 +40,54 @@
kernel compilation. Do not rely on the source tree being clean after
un-tarring.</para>
+ <note os="kc"><para>A good starting place for setting up the kernel
+ configuration is to run <command>make defconfig</command>. This will set the base configuration to a good state that takes your current system
+ architecture into account.</para>
+
+ <para>Be sure to configure the following options as
+ shown, or the system might not work correctly or boot at all.
+ Refer to <filename>/usr/share/doc/systemd-&systemd-version;/README</filename>:</para>
+
+ <screen role="nodump">General setup ---&gt;
+ [*] open by fhandle syscalls (CONFIG_FHANDLE)
+ [ ] Auditing support (CONFIG_AUDIT)
+ [*] Control Group support (CONFIG_CGROUPS)
+Processor type and features ---&gt;
+ [*] Enable seccomp to safely compute untrusted bytecode (CONFIG_SECCOMP)
+Networking support ---&gt;
+ Networking options ---&gt;
+ &lt;*&gt; The IPv6 protocol (CONFIG_IPV6)
+Device Drivers ---&gt;
+ Generic Driver Options ---&gt;
+ () path to uevent helper (CONFIG_UEVENT_HELPER_PATH)
+ [*] Maintain a devtmpfs filesystem to mount at /dev (CONFIG_DEVTMPFS)
+ [ ] Fallback user-helper invocation for firmware loading (CONFIG_FW_LOADER_USER_HELPER)
+File systems ---&gt;
+ [*] Inotify support for userspace (CONFIG_FSNOTIFY)
+ &lt;*&gt; Kernel automounter version 4 support (also supports v3) (CONFIG_AUTOFS4_FS)
+ Pseudo filesystems ---&gt;
+ [*] Tmpfs POSIX Access Control Lists (CONFIG_TMPFS_POSIX_ACL)
+ [*] Tmpfs extended attributes (CONFIG_TMPFS_XATTR)
+Firmware Drivers ---&gt;
+ EFI (Extensible Firmware Interface) Support ---&gt;
+ &lt;*&gt; EFI Variable Support via sysfs (CONFIG_EFI_VARS)
+-*- Enable the block layer ---&gt; (CONFIG_BLOCK)
+ Partition Types ---&gt;
+ [*] Advanced partition selection (CONFIG_PARTITION_ADVANCED)
+ [*] EFI GUID Partition support (CONFIG_EFI_PARTITION)
+Kernel Hacking ---&gt;
+ [*] Collect scheduler debugging info (CONFIG_SCHED_DEBUG)
+ [*] Collect scheduler statistics (CONFIG_SCHEDSTATS)</screen></note>
+
+ <note os="kd"><para>While "The IPv6 Protocol" is not strictly required, it
+ is highly recommended by the Systemd developers. "EFI Variable support" and
+ "EFI GUID Partition support" are for UEFI systems. "Collect scheduler
+ debugging info" and "Collect scheduler statistics" is for systemd-bootchart.
+ </para></note>
+
<para os="h">Configure the kernel via a menu-driven interface.
- Please note that the udev bootscript requires "rtc", "tmpfs" and "devtmpfs" to be
- enabled and built into the kernel, not as modules. CBLFS has
- some information regarding particular kernel configuration requirements of
- packages outside of CLFS at <ulink
+ CBLFS has some information regarding particular kernel configuration
+ requirements of packages outside of CLFS at <ulink
url="&cblfs-root;"/>:</para>
<screen os="i"><userinput>make menuconfig</userinput></screen>
@@ -60,29 +107,14 @@
<screen os="n"><userinput>make</userinput></screen>
- <para os="o">If using kernel modules, an
- <filename>/etc/modprobe.conf</filename> file may be needed.
+ <para os="o">If using kernel modules, a configuration file in
+ <filename class="directory">/etc/modprobe.d</filename> file may be needed.
Information pertaining to modules and kernel configuration is
located in the kernel documentation in the <filename
class="directory">Documentation</filename> directory of the kernel
- sources tree. Also, <filename>modprobe.conf(5)</filename> may
+ sources tree. Also, <filename>modprobe.d(5)</filename> may
be of interest.</para>
- <para os="p">Be very careful when reading other documentation relating to
- kernel modules because it usually applies to 2.4.x kernels only. As
- far as we know, kernel configuration issues specific to Hotplug and
- Eudev are not documented. The problem is that Eudev will create a device
- node only if Hotplug or a user-written script inserts the corresponding
- module into the kernel, and not all modules are detectable by Hotplug.
- Note that statements like the one below in the
- <filename>/etc/modprobe.conf</filename> file do not work with Eudev:</para>
-
-<screen os="q"><literal>alias char-major-XXX some-module</literal></screen>
-
- <para os="r">Because of the complications with Eudev and modules,
- we strongly recommend starting with a completely non-modular kernel
- configuration, especially if this is the first time using Eudev.</para>
-
<para os="s">Install the modules, if the kernel configuration uses
them:</para>
@@ -99,21 +131,21 @@
<para os="v">Issue the following command to install the kernel:</para>
-<screen><userinput>cp -v arch/i386/boot/bzImage /boot/vmlinuz-clfs-&linux-version;</userinput></screen>
+<screen><userinput>cp -v arch/i386/boot/bzImage /boot/vmlinuz-clfs-&linux-version2;</userinput></screen>
<para os="w"><filename>System.map</filename> is a symbol file for the kernel.
It maps the function entry points of every function in the kernel API,
as well as the addresses of the kernel data structures for the running
kernel. Issue the following command to install the map file:</para>
-<screen os="w1"><userinput>cp -v System.map /boot/System.map-&linux-version;</userinput></screen>
+<screen os="w1"><userinput>cp -v System.map /boot/System.map-&linux-version2;</userinput></screen>
<para os="x">The kernel configuration file <filename>.config</filename>
produced by the <command>make menuconfig</command> step above contains
all the configuration selections for the kernel that was just compiled.
It is a good idea to keep this file for future reference:</para>
-<screen os="x1"><userinput>cp -v .config /boot/config-&linux-version;</userinput></screen>
+<screen os="x1"><userinput>cp -v .config /boot/config-&linux-version2;</userinput></screen>
<para os="y">It is important to note that the files in the kernel source
directory are not owned by <systemitem class="username">root</systemitem>.
diff -ru /home/jp/a/BOOK/bootable/x86_64/kernel.xml BOOK/bootable/x86_64/kernel.xml
--- /home/jp/a/BOOK/bootable/x86_64/kernel.xml 2014-05-11 16:24:52.614516679 +0200
+++ BOOK/bootable/x86_64/kernel.xml 2014-10-03 20:44:43.900339261 +0200
@@ -8,7 +8,7 @@
<sect1 id="ch-bootable-kernel" role="wrap">
<?dbhtml filename="kernel.html"?>
- <title>Linux-&linux-version;</title>
+ <title>Linux-&linux-version2;</title>
<indexterm zone="ch-bootable-kernel">
<primary sortas="a-Linux">Linux</primary>
@@ -27,6 +27,14 @@
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
href="../x86/kernel.xml"
+ xpointer="xpointer(//*[@os='p1'])"/>
+
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
+ href="../x86/kernel.xml"
+ xpointer="xpointer(//*[@os='p2'])"/>
+
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
+ href="../x86/kernel.xml"
xpointer="xpointer(//*[@os='b'])"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
@@ -39,6 +47,14 @@
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
href="../x86/kernel.xml"
+ xpointer="xpointer(//*[@os='kc'])"/>
+
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
+ href="../x86/kernel.xml"
+ xpointer="xpointer(//*[@os='kd'])"/>
+
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
+ href="../x86/kernel.xml"
xpointer="xpointer(//*[@os='h'])"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
@@ -67,24 +83,12 @@
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
href="../x86/kernel.xml"
- xpointer="xpointer(//*[@os='p'])"/>
-
- <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
- href="../x86/kernel.xml"
- xpointer="xpointer(//*[@os='q'])"/>
-
- <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
- href="../x86/kernel.xml"
- xpointer="xpointer(//*[@os='r'])"/>
-
- <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
- href="../x86/kernel.xml"
xpointer="xpointer(//*[@os='s'])"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
href="../x86/kernel.xml"
xpointer="xpointer(//*[@os='t'])"/>
-
+
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
href="../x86/kernel.xml"
xpointer="xpointer(//*[@os='s2'])"/>
@@ -101,7 +105,7 @@
href="../x86/kernel.xml"
xpointer="xpointer(//*[@os='v'])"/>
-<screen><userinput>cp -v arch/x86_64/boot/bzImage /boot/vmlinuz-clfs-&linux-version;</userinput></screen>
+<screen><userinput>cp -v arch/x86_64/boot/bzImage /boot/vmlinuz-clfs-&linux-version2;</userinput></screen>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
href="../x86/kernel.xml"
diff -ru /home/jp/a/BOOK/bootable/x86_64-64-chapter.xml BOOK/bootable/x86_64-64-chapter.xml
--- /home/jp/a/BOOK/bootable/x86_64-64-chapter.xml 2014-05-11 16:24:52.618516679 +0200
+++ BOOK/bootable/x86_64-64-chapter.xml 2014-10-03 20:44:43.900339261 +0200
@@ -12,7 +12,6 @@
<title>Making the CLFS System Bootable</title>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="common/introduction.xml"/>
- <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="common/fstab.xml"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="x86_64/kernel.xml"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="x86/grub.xml"/>
diff -ru /home/jp/a/BOOK/bootable/x86_64-chapter.xml BOOK/bootable/x86_64-chapter.xml
--- /home/jp/a/BOOK/bootable/x86_64-chapter.xml 2014-05-11 16:24:52.614516679 +0200
+++ BOOK/bootable/x86_64-chapter.xml 2014-10-03 20:44:43.900339261 +0200
@@ -12,7 +12,6 @@
<title>Making the CLFS System Bootable</title>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="common/introduction.xml"/>
- <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="common/fstab.xml"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="x86_64/kernel.xml"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="x86/grub.xml"/>
diff -ru /home/jp/a/BOOK/bootable/x86-chapter.xml BOOK/bootable/x86-chapter.xml
--- /home/jp/a/BOOK/bootable/x86-chapter.xml 2014-05-11 16:24:52.618516679 +0200
+++ BOOK/bootable/x86-chapter.xml 2014-10-03 20:44:43.900339261 +0200
@@ -12,7 +12,6 @@
<title>Making the CLFS System Bootable</title>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="common/introduction.xml"/>
- <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="common/fstab.xml"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="x86/kernel.xml"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="x86/grub.xml"/>
diff -ru /home/jp/a/BOOK/chroot/64/createfiles.xml BOOK/chroot/64/createfiles.xml
--- /home/jp/a/BOOK/chroot/64/createfiles.xml 2014-05-11 16:24:52.622516679 +0200
+++ BOOK/chroot/64/createfiles.xml 2014-10-03 20:44:43.900339261 +0200
/trunk/clfs/bootable/x86_64-chapter.xml
12,7 → 12,6
<title>Rendre le système CLFS démarrable</title>
 
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="common/introduction.xml"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="common/fstab.xml"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="x86_64/kernel.xml"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="x86/grub.xml"/>
 
/trunk/clfs/bootable/x86/kernel.xml
8,7 → 8,7
<sect1 id="ch-bootable-kernel" role="wrap">
<?dbhtml filename="kernel.html"?>
 
<title>Linux-&linux-version;</title>
<title>Linux-&linux-version2;</title>
 
<indexterm zone="ch-bootable-kernel">
<primary sortas="a-Linux">Linux</primary>
27,6 → 27,10
dans l'arborescence des sources du noyau pour des méthodes alternatives de
à celle utilisée par le livre pour configurer le noyau.</para>
 
<para os="p1">Appliquez le dernier correctif de sous-niveau de Linux&nbsp;:</para>
 
<screen os="p2"><userinput>xzcat ../&linux-sublevel-patch; | patch -Np1 -i -</userinput></screen>
 
<para os="b">Préparez la compilation en lançant la commande suivante&nbsp;:</para>
 
<screen os="c"><userinput>make mrproper</userinput></screen>
36,9 → 40,53
compilation du noyau. Ne pensez pas que l'arborescence des sources est propre après
la décompression.</para>
 
<para os="h">Configurez le noyau avec une interface en menus. Merci de
noter que le script de démarrage d'Eudev exige que "rtc", "tmpfs" et "devtmpfs"
soient activés et construits en dur dans le noyau et non en modules. CBLFS
<note os="kc"><para>Un bon début pour paramétrer la
configuration du noyau est de lancer <command>make defconfig</command>. Cela
règlera la configuration de base correctement en prenant en compte votre
architecture système.</para>
 
<para>Assurez-vous de configurer les options suivantes comme indiqué, sans
quoi le système pourrait ne pas marcher correctement, voire pas du tout.
Reportez-vous à <filename>/usr/share/doc/systemd-&systemd-version;/README</filename>&nbsp;:</para>
 
<screen role="nodump">General setup ---&gt;
[*] open by fhandle syscalls (CONFIG_FHANDLE)
[ ] Auditing support (CONFIG_AUDIT)
[*] Control Group support (CONFIG_CGROUPS)
Processor type and features ---&gt;
[*] Enable seccomp to safely compute untrusted bytecode (CONFIG_SECCOMP)
Networking support ---&gt;
Networking options ---&gt;
&lt;*&gt; The IPv6 protocol (CONFIG_IPV6)
Device Drivers ---&gt;
Generic Driver Options ---&gt;
() path to uevent helper (CONFIG_UEVENT_HELPER_PATH)
[*] Maintain a devtmpfs filesystem to mount at /dev (CONFIG_DEVTMPFS)
[ ] Fallback user-helper invocation for firmware loading (CONFIG_FW_LOADER_USER_HELPER)
File systems ---&gt;
[*] Inotify support for userspace (CONFIG_FSNOTIFY)
&lt;*&gt; Kernel automounter version 4 support (also supports v3) (CONFIG_AUTOFS4_FS)
Pseudo filesystems ---&gt;
[*] Tmpfs POSIX Access Control Lists (CONFIG_TMPFS_POSIX_ACL)
[*] Tmpfs extended attributes (CONFIG_TMPFS_XATTR)
Firmware Drivers ---&gt;
EFI (Extensible Firmware Interface) Support ---&gt;
&lt;*&gt; EFI Variable Support via sysfs (CONFIG_EFI_VARS)
-*- Enable the block layer ---&gt; (CONFIG_BLOCK)
Partition Types ---&gt;
[*] Advanced partition selection (CONFIG_PARTITION_ADVANCED)
[*] EFI GUID Partition support (CONFIG_EFI_PARTITION)
Kernel Hacking ---&gt;
[*] Collect scheduler debugging info (CONFIG_SCHED_DEBUG)
[*] Collect scheduler statistics (CONFIG_SCHEDSTATS)</screen></note>
 
<note os="kd"><para>Si "The IPv6 Protocol" n'est pas absolument nécessaire,
il est fortement recommandé par les développeurs de Systemd. "EFI Variable support"
et "EFI GUID Partition support" sont pour les systèmes UEFI. "Collect scheduler
debugging info" et "Collect scheduler statistics" sont pour le démarrage
avec systemd.</para></note>
 
<para os="h">Configurez le noyau avec une interface en menus. CBLFS
contient des informations sur les exigences de configuration particulières des paquets hors CLFS, sur <ulink
url="&cblfs-root;"/>:</para>
 
59,32 → 107,16
 
<screen os="n"><userinput>make</userinput></screen>
 
<para os="o">If using kernel modules, an
<filename>/etc/modprobe.conf</filename> file may be needed.
Information pertaining to modules and kernel configuration is
located in the kernel documentation in the <filename
class="directory">Documentation</filename> directory of the kernel
sources tree. Also, <filename>modprobe.conf(5)</filename> may
be of interest.</para>
<para os="o">Si vous utilisez les modules du noyau, il se peut que vous
ayez besoin d'un fichier de configuration <filename>/etc/modprobe.d</filename>.
Les informations sur les modules et la configuration du noyau se trouvent
dans la documentation du noyau, dans le répertoire <filename
class="directory">Documentation</filename> de l'arborescence des
sources du noyau. En outre, <filename>modprobe.d(5)</filename> peut être
intéressant.</para>
 
<para os="p">Be very careful when reading other documentation relating to
kernel modules because it usually applies to 2.4.x kernels only. As
far as we know, kernel configuration issues specific to Hotplug and
Eudev are not documented. The problem is that Udev will create a device
node only if Hotplug or a user-written script inserts the corresponding
module into the kernel, and not all modules are detectable by Hotplug.
Note that statements like the one below in the
<filename>/etc/modprobe.conf</filename> file do not work with Eudev:</para>
<para os="s">Installez les modules, si la configuration du noyau en utilise&nbsp;:</para>
 
<screen os="q"><literal>alias char-major-XXX some-module</literal></screen>
 
<para os="r">Because of the complications with Eudev and modules,
we strongly recommend starting with a completely non-modular kernel
configuration, especially if this is the first time using Eudev.</para>
 
<para os="s">Install the modules, if the kernel configuration uses
them:</para>
 
<screen os="t"><userinput>make modules_install</userinput></screen>
 
<para os="s2">Installez le firmware si la configuration du noyau en utilise
92,20 → 124,20
 
<screen os="t2"><userinput>make firmware_install</userinput></screen>
 
<para os="u">After kernel compilation is complete, additional steps are
required to complete the installation. Some files need to be copied to
the <filename class="directory">/boot</filename> directory.</para>
<para os="u">Après que la compilation est finie, des étapes supplémentaires
sont nécessaire pour achever l'installation. Il faut copier certains fichiers
dans le répertoire <filename class="directory">/tools/boot</filename>.</para>
 
<para os="v">Issue the following command to install the kernel:</para>
<para os="v">Lancez la commande suivante pour installer le noyau&nbsp;:</para>
 
<screen><userinput>cp -v arch/i386/boot/bzImage /boot/vmlinuz-clfs-&linux-version;</userinput></screen>
<screen><userinput>cp -v arch/i386/boot/bzImage /boot/vmlinuz-clfs-&linux-version2;</userinput></screen>
 
<para os="w"><filename>System.map</filename> is a symbol file for the kernel.
It maps the function entry points of every function in the kernel API,
as well as the addresses of the kernel data structures for the running
kernel. Issue the following command to install the map file:</para>
<para os="w"><filename>System.map</filename> est un fichier de symbole
pour le noyau. Il pose les points d'entrée des fonctions de l'API du noyau
et les adresses des structures de données du noyau pour la version du
noyau. Lancez la commande suivante pour installer le fichier de plan&nbsp;:</para>
 
<screen os="w1"><userinput>cp -v System.map /boot/System.map-&linux-version;</userinput></screen>
<screen os="w1"><userinput>cp -v System.map /boot/System.map-&linux-version2;</userinput></screen>
 
<para os="x">The kernel configuration file <filename>.config</filename>
produced by the <command>make menuconfig</command> step above contains
112,46 → 144,47
all the configuration selections for the kernel that was just compiled.
It is a good idea to keep this file for future reference:</para>
 
<screen os="x1"><userinput>cp -v .config /boot/config-&linux-version;</userinput></screen>
<screen os="x1"><userinput>cp -v .config /boot/config-&linux-version2;</userinput></screen>
 
<para os="y">It is important to note that the files in the kernel source
directory are not owned by <systemitem class="username">root</systemitem>.
Whenever a package is unpacked as user <systemitem
class="username">root</systemitem> (like we do inside the final-system
build environment), the files have the user and group IDs of whatever
they were on the packager's computer. This is usually not a problem
for any other package to be installed because the source tree is
removed after the installation. However, the Linux source tree is
often retained for a long time. Because of this, there is a chance
that whatever user ID the packager used will be assigned to somebody
on the machine. That person would then have write access to the kernel
source.</para>
<para os="y">Il est important de remarquer que les fichiers du répertoire des
sources du noyau n'appartiennent pas à <systemitem class="username">root</systemitem>.
A chaque fois qu'un paquet est déballé par l'utilisateur <systemitem
class="username">root</systemitem> (comme on le fait dans l'environnement
de construction du système final), les fichiers prennent l'ID de l'utilisateur
et du groupe tant qu'ils seront sur l'ordinateur de l'empaqueteur. Ce
n'est pas un problème en général pour installer d'autres paquets car
l'arborescence des sources est supprimée après l'installation. Cependant,
l'arborescence des sources de Linux est longtemps conservée. C'est pourquoi
il y a des chances qu'un ID utilisateur utilisé par l'empaqueteur soit
affecté à quelqu'un sur la machine. Cette personne aurait alors un accès en
écriture aux sources du noyau.</para>
 
<para os="y1">If the kernel source tree is going to retained, run
<command>chown -R 0:0</command> on the <filename
class="directory">linux-&linux-version;</filename> directory to
ensure all files are owned by user <systemitem
<para os="y1">Si vous allez garder l'arborescence des sources du noyau,
lancez <command>chown -R 0:0</command> dans le répertoire <filename
class="directory">linux-&linux-version;</filename> pour garantir que tous
les fichiers appartiennent à l'utilisateur <systemitem
class="username">root</systemitem>.</para>
 
<warning os="z">
<para>Some kernel documentation recommends creating a symlink from
<filename class="symlink">/usr/src/linux</filename> pointing to the
kernel source directory. This is specific to kernels prior to the
2.6 series and <emphasis>must not</emphasis> be created on a CLFS
system as it can cause problems for packages you may wish to build
once your base CLFS system is complete.</para>
<para>Certaines documentations du noyau recommandent de créer un lien
symbolique de
<filename class="symlink">/usr/src/linux</filename> vers le répertoire des
sources du noyau. Il est spécifique aux noyaux antérieurs à la série 2.6
et <emphasis>vous ne devez pas</emphasis> le créer sur un système CLFS
car cela peut poser des problèmes aux paquets souhaitant se construire
une fois que votre système CLFS de base est terminé.</para>
 
<para>Also, the headers in the system's <filename
class="directory">include</filename> directory should
<emphasis>always</emphasis> be the ones against which Glibc was
compiled and should <emphasis>never</emphasis> be replaced by headers
from a different kernel version.</para>
<para>De plus, le répertoire <filename
class="directory">include</filename> du système devrait
<emphasis>toujours</emphasis> être celui contre lequel Glibc a été
compilé et <emphasis>jamais</emphasis> remplacé pao les en-têtes d'une
version différente du noyau.</para>
</warning>
 
</sect2>
 
<sect2 id="contents-kernel" role="content">
<title>Contents of Linux</title>
<title>Contenu de Linux</title>
 
<segmentedlist>
<segtitle>Fichiers installés</segtitle>
172,7 → 205,7
<varlistentry id="config">
<term><filename>config-[linux-version]</filename></term>
<listitem>
<para>Contains all the configuration selections for the kernel</para>
<para>Contient tous les choix de configuration du noyau</para>
<indexterm zone="ch-bootable-kernel config">
<primary sortas="e-/boot/config">/boot/config-[linux-version]</primary>
</indexterm>
182,13 → 215,13
<varlistentry id="clfskernel">
<term><filename>clfskernel-[linux-version]</filename></term>
<listitem>
<para>The engine of the Linux system. When turning on the
computer, the kernel is the first part of the operating system
that gets loaded. It detects and initializes all components of
the computer's hardware, then makes these components available
as a tree of files to the software and turns a single CPU into
a multitasking machine capable of running scores of programs
seemingly at the same time.</para>
<para>Moteur du système Linux. Quand vous allumez l'ordinateur, le
noyau est la première partie du système d'exploitation chargée.
Il détecte et initialise tous les composants matériels de l'ordinateur,
ce qui rend disponibles les composants sous forme d'arborescence de
fichiers au niveau logiciel et passe un processeur en
machine multitâches capable de lancer des scores de programmes
qui se ressemblent et en même temps.</para>
<indexterm zone="ch-bootable-kernel clfskernel">
<primary sortas="b-clfskernel">clfskernel-[linux-version]</primary>
</indexterm>
198,9 → 231,8
<varlistentry id="System.map">
<term><filename>System.map-[linux-version]</filename></term>
<listitem>
<para>A list of addresses and symbols; it maps the entry points
and addresses of all the functions and data structures in the
kernel</para>
<para>Une liste des adresses et des symboles&nbsp;; il pose les points
d'entrée et les adresses des structures de données du noyau</para>
<indexterm zone="ch-bootable-kernel System.map">
<primary sortas="e-/boot/System.map">/boot/System.map-[linux-version]</primary>
</indexterm>
/trunk/clfs/bootable/x86_64/kernel.xml
8,7 → 8,7
<sect1 id="ch-bootable-kernel" role="wrap">
<?dbhtml filename="kernel.html"?>
 
<title>Linux-&linux-version;</title>
<title>Linux-&linux-version2;</title>
 
<indexterm zone="ch-bootable-kernel">
<primary sortas="a-Linux">Linux</primary>
27,6 → 27,14
 
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
href="../x86/kernel.xml"
xpointer="xpointer(//*[@os='p1'])"/>
 
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
href="../x86/kernel.xml"
xpointer="xpointer(//*[@os='p2'])"/>
 
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
href="../x86/kernel.xml"
xpointer="xpointer(//*[@os='b'])"/>
 
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
39,6 → 47,14
 
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
href="../x86/kernel.xml"
xpointer="xpointer(//*[@os='kc'])"/>
 
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
href="../x86/kernel.xml"
xpointer="xpointer(//*[@os='kd'])"/>
 
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
href="../x86/kernel.xml"
xpointer="xpointer(//*[@os='h'])"/>
 
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
67,18 → 83,6
 
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
href="../x86/kernel.xml"
xpointer="xpointer(//*[@os='p'])"/>
 
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
href="../x86/kernel.xml"
xpointer="xpointer(//*[@os='q'])"/>
 
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
href="../x86/kernel.xml"
xpointer="xpointer(//*[@os='r'])"/>
 
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
href="../x86/kernel.xml"
xpointer="xpointer(//*[@os='s'])"/>
 
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
101,7 → 105,7
href="../x86/kernel.xml"
xpointer="xpointer(//*[@os='v'])"/>
 
<screen><userinput>cp -v arch/x86_64/boot/bzImage /boot/vmlinuz-clfs-&linux-version;</userinput></screen>
<screen><userinput>cp -v arch/x86_64/boot/bzImage /boot/vmlinuz-clfs-&linux-version2;</userinput></screen>
 
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
href="../x86/kernel.xml"
/trunk/clfs/bootable/x86-chapter.xml
12,7 → 12,6
<title>Rendre le système CLFS démarrable</title>
 
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="common/introduction.xml"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="common/fstab.xml"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="x86/kernel.xml"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="x86/grub.xml"/>
 
/trunk/clfs/bootable/x86_64-64-chapter.xml
12,7 → 12,6
<title>Rendre le système CLFS démarrable</title>
 
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="common/introduction.xml"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="common/fstab.xml"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="x86_64/kernel.xml"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="x86/grub.xml"/>