Subversion Repositories svn LFS-FR

Rev

Rev 7255 | Rev 7276 | Go to most recent revision | Blame | Compare with Previous | Last modification | View Log | RSS feed

msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2017-03-30 21:21+0000\n"
"PO-Revision-Date: 2017-05-20 13:25+0000\n"
"Last-Translator: roptat <roptat@lepiller.eu>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"Language: fr\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
"X-Generator: Pootle 2.8\n"
"X-POOTLE-MTIME: 1495286752.748794\n"

#. type: Content of: <h1>
#: complete.html:2
msgid "Frequently Asked Questions"
msgstr "Foire Aux Questions"

#. type: Content of: <p>
#: complete.html:3
msgid ""
"The FAQ is divided in three documents. The <a href=\"/faq/index.html\">"
"General FAQ</a> has links to all questions and answers.  The <a href=\""
"/lfs/faq.html\">LFS FAQ</a> is a selection of LFS-specific FAQ's and the <a "
"href=\"/blfs/faq.html\">BLFS FAQ</a> is a selection of BLFS-specific FAQ's."
msgstr ""
"La FAQ est divisée en trois documents. La <a href=\"/faq/index.html\">FAQ "
"générale</a> propose des liens vers toutes les questions et les réponses. La "
"<a href=\"/lfs/faq.html\">FAQ LFS</a> est une sélection des questions les "
"plus fréquemment posées concernant LFS et la <a href=\"/blfs/faq.html\">FAQ "
"BLFS</a> est une sélection des questions les plus fréquentes et spécifiques "
"à BLFS."

#. type: Content of: <h2>
#: complete.html:7
msgid "General FAQ"
msgstr "FAQ générale"

#. type: Content of: <h3>
#: complete.html:8
msgid "<a href=\"#intro\">General information about these FAQ's</a>"
msgstr "<a href=\"#intro\">Informations générales à propos de ces FAQ</a>"

#. type: Content of: <ul><li>
#: complete.html:10
msgid "<a href=\"#why-faq\">Why this FAQ?</a>"
msgstr "<a href=\"#why-faq\">Pourquoi cette FAQ&nbsp;?</a>"

#. type: Content of: <ul><li>
#: complete.html:11
msgid "<a href=\"#what-is-lfs\">What is LFS?</a>"
msgstr "<a href=\"#what-is-lfs\">Qu'est ce que LFS&nbsp;?</a>"

#. type: Content of: <ul><li>
#: complete.html:12
msgid "<a href=\"#what-is-blfs\">What is BLFS?</a>"
msgstr "<a href=\"#what-is-blfs\">Qu'est ce que BLFS&nbsp;?</a>"

#. type: Content of: <ul><li>
#: complete.html:13
msgid "<a href=\"#contribute\">How can I contribute to this FAQ?</a>"
msgstr ""
"<a href=\"#contribute\">Comment puis-je contribuer à cette FAQ&nbsp;?</a>"

#. type: Content of: <h3>
#: complete.html:15
msgid "<a href=\"#support\">Support guidelines</a>"
msgstr "<a href=\"#support\">Instructions sur l'assistance</a>"

#. type: Content of: <ul><li>
#: complete.html:17
msgid ""
"<a href=\"#newbie\">I'm a newbie to Linux or LFS and I need some help?</a>"
msgstr ""
"<a href=\"#newbie\">Je débute sur Linux ou LFS et j'ai besoin d'aide</a>"

#. type: Content of: <ul><li>
#: complete.html:18
msgid "<a href=\"#getting-help\">Where is the best place to get help?</a>"
msgstr ""
"<a href=\"#getting-help\">Quel est le meilleur endroit pour trouver de "
"l'aide&nbsp;?</a>"

#. type: Content of: <ul><li>
#: complete.html:19
msgid "<a href=\"#which-list\">Which list should I use for what topic?</a>"
msgstr ""
"<a href=\"#which-list\">Quelle liste de diffusion pour quel sujet&nbsp;?</a>"

#. type: Content of: <ul><li>
#: complete.html:20
msgid "<a href=\"#netiquette\">How do I address the LFS community?</a>"
msgstr ""
"<a href=\"#netiquette\">Comment dois-je m'adresser à la communauté "
"LFS&nbsp;?</a>"

#. type: Content of: <h3>
#: complete.html:22
msgid "<a href=\"#frb\">Frequently Reported Bugs</a>"
msgstr "<a href=\"#frb\">Bugs fréquemment remontés</a>"

#. type: Content of: <ul><li>
#: complete.html:24
msgid ""
"<a href=\"#wrong-ln-s-command\">The \"ln -s\" commands in the Book are "
"wrong.</a>"
msgstr ""
"<a href=\"#wrong-ln-s-command\">Les commandes \"ln -s\" du livre sont "
"fausses.</a>"

#. type: Content of: <ul><li>
#: complete.html:25
msgid "<a href=\"#its-hardlink-not-copy\">/bin/foo is a copy of /bin/bar.</a>"
msgstr ""
"<a href=\"#its-hardlink-not-copy\">/bin/foo est une copie de /bin/bar.</a>"

#. type: Content of: <ul><li>
#: complete.html:26
msgid ""
"<a href=\"#why-not-version\">Can I use a version newer than the one in the "
"Book?</a>"
msgstr ""
"<a href=\"#why-not-version\">Puis-je utiliser une version plus récente que "
"celle du livre&nbsp;?</a>"

#. type: Content of: <ul><li>
#: complete.html:27
msgid "<a href=\"#new-version\">There's a new version of package Foo.</a>"
msgstr "<a href=\"#new-version\">Il y a une nouvelle version du paquet Foo.</a>"

#. type: Content of: <ul><li>
#: complete.html:28
msgid "<a href=\"#delete_key_not_work\">The Delete key doesn't work.</a>"
msgstr "<a href=\"#delete_key_not_work\">La touche Del ne fonctionne pas.</a>"

#. type: Content of: <ul><li>
#: complete.html:29
msgid ""
"<a href=\"#shutdown-on-fsck-error\">The system shuts down when fsck errors "
"out!</a>"
msgstr ""
"<a href=\"#shutdown-on-fsck-error\">Le système s'éteint après que fsck soit "
"sorti en erreur&nbsp;!</a>"

#. type: Content of: <ul><li>
#: complete.html:30
msgid ""
"<a href=\"#where-lfs-packages\">Where are the lfs-packages tarballs or wget "
"scripts?</a>"
msgstr ""
"<a href=\"#where-lfs-packages\">Où sont les archives des paquets de lfs ou "
"les scripts wget&nbsp;?</a>"

#. type: Content of: <ul><li>
#: complete.html:31
msgid "<a href=\"#how-to-find\">How do I find a package or command?</a>"
msgstr ""
"<a href=\"#how-to-find\">Comment puis-je trouver un paquet ou une "
"commande&nbsp;?</a>"

#. type: Content of: <ul><li>
#: complete.html:32
msgid "<a href=\"#how-to-upgrade\">How do I upgrade my LFS/BLFS system?</a>"
msgstr ""
"<a href=\"#how-to-upgrade\">Comment faire pour mettre à jour mon système "
"LFS/BLFS&nbsp;?</a>"

#. type: Content of: <h2>
#: complete.html:35
msgid "LFS FAQ:"
msgstr "La FAQ LFS&nbsp;:"

#. type: Content of: <h3>
#: complete.html:36
msgid "<a href=\"/lfs/faq.html#fre\">Frequently Requested Enhancements</a>"
msgstr "<a href=\"/lfs/faq.html#fre\">Améliorations fréquemment demandées</a>"

#. type: Content of: <ul><li>
#: complete.html:38
msgid ""
"<a href=\"/lfs/faq.html#add-grub\">Why not use LILO instead of GRUB?</a>"
msgstr ""
"<a href=\"/lfs/faq.html#add-grub\">Pourquoi ne pas utiliser LILO plutôt que "
"GRUB&nbsp;?</a>"

#. type: Content of: <ul><li>
#: complete.html:39
msgid ""
"<a href=\"/lfs/faq.html#why-not-faq\">Why not include the FAQ in the "
"book?</a>"
msgstr ""
"<a href=\"/lfs/faq.html#why-not-faq\">Pourquoi ne pas inclure la FAQ au "
"livre&nbsp;?</a>"

#. type: Content of: <ul><li>
#: complete.html:40
msgid "<a href=\"/lfs/faq.html#why-vim\">Why is vim in the book?</a>"
msgstr ""
"<a href=\"/lfs/faq.html#why-vim\">Pourquoi est-ce que Vim est dans le "
"livre&nbsp;?</a>"

#. type: Content of: <ul><li>
#: complete.html:41
msgid ""
"<a href=\"/lfs/faq.html#hjl-binutils\">Why is HJL's Binutils not in the "
"book?</a>"
msgstr ""
"<a href=\"/lfs/faq.html#hjl-binutils\">Pourquoi est-ce que la version HJL de "
"Binutils n'est pas dans le livre&nbsp;?</a>"

#. type: Content of: <ul><li>
#: complete.html:42
msgid ""
"<a href=\"/lfs/faq.html#why-not-package-management\">Why isn't some package "
"manager in the book?</a>"
msgstr ""
"<a href=\"/lfs/faq.html#why-not-package-management\">Pourquoi n'y a-t'il pas "
"de gestionnaire de paquets dans le livre&nbsp;?</a>"

#. type: Content of: <ul><li>
#: complete.html:43
msgid ""
"<a href=\"/lfs/faq.html#no-poweroff\">How do I make my machine poweroff when "
"shut down?</a>"
msgstr ""
"<a href=\"/lfs/faq.html#no-poweroff\">Comment provoquer l'arrêt électrique "
"de la machine à la sortie du système&nbsp;?</a>"

#. type: Content of: <h3>
#: complete.html:45
msgid "<a href=\"/lfs/faq.html#resources\">When reading and building LFS</a>"
msgstr ""
"<a href=\"/lfs/faq.html#resources\">Pendant la lecture et la construction de "
"LFS</a>"

#. type: Content of: <ul><li>
#: complete.html:47
msgid ""
"<a href=\"/lfs/faq.html#what-dist\">What distribution should I use to start "
"from?</a>"
msgstr ""
"<a href=\"/lfs/faq.html#what-dist\">Quel distribution dois-je utiliser pour "
"commencer?</a>"

#. type: Content of: <ul><li>
#: complete.html:48
msgid ""
"<a href=\"/lfs/faq.html#kernel-modules\">How do I compile a kernel or set up "
"modules?</a>"
msgstr ""
"<a href=\"/lfs/faq.html#kernel-modules\">Comment compiler le noyau ou "
"configurer un module?</a>"

#. type: Content of: <ul><li>
#: complete.html:49
msgid ""
"<a href=\"/lfs/faq.html#gcc-warnings\">Are compiler warnings from GCC "
"bad?</a>"
msgstr ""
"<a href=\"/lfs/faq.html#gcc-warnings\">Est-ce que c'est mal, les "
"avertissements de compilation de Gcc&nbsp;?</a>"

#. type: Content of: <ul><li>
#: complete.html:50
msgid ""
"<a href=\"/lfs/faq.html#dirty-sources\">Do I need to keep the source after "
"installing?</a>"
msgstr ""
"<a href=\"/lfs/faq.html#dirty-sources\">Dois-je conserver les sources après "
"l'installation&nbsp;?</a>"

#. type: Content of: <ul><li>
#: complete.html:51
msgid ""
"<a href=\"/lfs/faq.html#really-small\">How do I make that really small "
"install the book mentions?</a>"
msgstr ""
"<a href=\"/lfs/faq.html#really-small\">Comment puis-je procéder à cette "
"toute petite installation dont parle le livre&nbsp;?</a>"

#. type: Content of: <ul><li>
#: complete.html:52
msgid ""
"<a href=\"/lfs/faq.html#procs-lfs\">Is there information about building LFS "
"on other processors?</a>"
msgstr ""
"<a href=\"/lfs/faq.html#procs-lfs\">Existe-t'il des informations sur la "
"façon de construire LFS sur d'autres architectures&nbsp;?</a>"

#. type: Content of: <ul><li>
#: complete.html:53
msgid "<a href=\"/lfs/faq.html#cross-compile\">How do I cross compile LFS?</a>"
msgstr ""
"<a href=\"/lfs/faq.html#cross-compile\">Comment faire une compilation "
"croisée avec LFS&nbsp;?</a>"

#. type: Content of: <ul><li>
#: complete.html:54
msgid "<a href=\"/lfs/faq.html#dos-text\">What's a DOS format text file?</a>"
msgstr ""
"<a href=\"/lfs/faq.html#dos-text\">Qu'est qu'un fichier texte au format "
"DOS&nbsp;?</a>"

#. type: Content of: <ul><li>
#: complete.html:55
msgid ""
"<a href=\"/lfs/faq.html#no-ptys\">The system has no more ptys. Ask your "
"system administrator to create more.</a>"
msgstr ""
"<a href=\"/lfs/faq.html#no-ptys\">Le système n'a plus de ptys. Demandez à "
"votre administrateur d'en créer d'autres.</a>"

#. type: Content of: <h3>
#: complete.html:57
msgid "<a href=\"/lfs/faq.html#generrors\">General compilation errors</a>"
msgstr ""
"<a href=\"/lfs/faq.html#generrors\">Erreurs de compilation usuelles.</a>"

#. type: Content of: <ul><li>
#: complete.html:59
msgid ""
"<a href=\"/lfs/faq.html#gnu-patches\">I used a patch from GNU to upgrade. Is "
"that OK?</a>"
msgstr ""
"<a href=\"/lfs/faq.html#gnu-patches\">J'ai utilisé un patch provenant de GNU "
"pour faire des mises à jour. C'est bon&nbsp;?</a>"

#. type: Content of: <ul><li>
#: complete.html:60
msgid ""
"<a href=\"/lfs/faq.html#optimizations\">When using optimization flags ("
"setting CFLAGS)</a>"
msgstr ""
"<a href=\"/lfs/faq.html#optimizations\">Utilisation des paramètres "
"d'optimisation (paramétrage des CFLAGS)</a>"

#. type: Content of: <ul><li>
#: complete.html:61
msgid ""
"<a href=\"/lfs/faq.html#config-hang-size_t\">Why does configure hang at "
"&quot;checking for signed size_t type...&quot;?</a>"
msgstr ""
"<a href=\"/lfs/faq.html#config-hang-size_t\">Pourquoi est-ce que configure "
"se fige sur «&nbsp;checking for signed size_t type...&nbsp;»&nbsp;?</a>"

#. type: Content of: <ul><li>
#: complete.html:62
msgid ""
"<a href=\"/lfs/faq.html#dirty-sources\">I didn't delete the source tree "
"after my last attempt. Do I need to?</a>"
msgstr ""
"<a href=\"/lfs/faq.html#dirty-sources\">Je n'ai pas effacé l'arborescence "
"des sources après mon dernier essai. Faut-il le faire&nbsp;?</a>"

#. type: Content of: <ul><li>
#: complete.html:63
msgid ""
"<a href=\"/lfs/faq.html#perm-denied\">I'm getting `/dev/null: Permission "
"denied'</a>"
msgstr ""
"<a href=\"/lfs/faq.html#perm-denied\">J'obtiens le message «&nbsp;/dev/null: "
"Permission denied&nbsp;»</a>"

#. type: Content of: <ul><li>
#: complete.html:64
msgid ""
"<a href=\"/lfs/faq.html#sig11\">signal 11 (internal error: Segmentation "
"fault)</a>"
msgstr ""
"<a href=\"/lfs/faq.html#sig11\">signal 11 (internal error: Segmentation "
"fault)</a>"

#. type: Content of: <ul><li>
#: complete.html:65
msgid ""
"<a href=\"/lfs/faq.html#any-no-such-file\">No such file or directory</a>"
msgstr ""
"<a href=\"/lfs/faq.html#any-no-such-file\">No such file or directory</a>"

#. type: Content of: <ul><li>
#: complete.html:66
msgid ""
"<a href=\"/lfs/faq.html#configure-no-such-file\">bash: ./configure: No such "
"file or directory</a>"
msgstr ""
"<a href=\"/lfs/faq.html#configure-no-such-file\">bash: ./configure: No such "
"file or directory</a>"

#. type: Content of: <ul><li>
#: complete.html:67
msgid ""
"<a href=\"/lfs/faq.html#bad-interpreter-permission-denied\">./configure: bad "
"interpreter: Permission denied</a>"
msgstr ""
"<a href=\"/lfs/faq.html#bad-interpreter-permission-denied\">./configure: bad "
"interpreter: Permission denied</a>"

#. type: Content of: <ul><li>
#: complete.html:68
msgid ""
"<a href=\"/lfs/faq.html#conf-guess-fail\">configure can't guess my host "
"type.</a>"
msgstr ""
"<a href=\"/lfs/faq.html#conf-guess-fail\">configure n'arrive pas à "
"déterminer le type de mon hôte.</a>"

#. type: Content of: <ul><li>
#: complete.html:69
msgid ""
"<a href=\"/lfs/faq.html#config-not-gnu-c\">checking whether we are using GNU "
"C... no</a>"
msgstr ""
"<a href=\"/lfs/faq.html#config-not-gnu-c\">checking whether we are using GNU "
"C... no</a>"

#. type: Content of: <h3>
#: complete.html:71
msgid "<a href=\"../lfs/faq.html#packerrors\">Package-specific errors</a>"
msgstr ""
"<a href=\"../lfs/faq.html#packerrors\">Erreurs spécifiques à certains "
"paquets</a>"

#. type: Content of: <ul><li>
#: complete.html:73
msgid ""
"<a href=\"/lfs/faq.html#unknown-pseudo-op-hidden\">GCC: Error: Unknown "
"pseudo-op: `.hidden'</a>"
msgstr ""
"<a href=\"/lfs/faq.html#unknown-pseudo-op-hidden\">GCC: Error: Unknown "
"pseudo-op: `.hidden'</a>"

#. type: Content of: <ul><li>
#: complete.html:74
msgid ""
"<a href=\"/lfs/faq.html#no-linuxthreads\">Glibc: &quot;... it is normal to "
"compile GNU libc with the `linuxthreads' add-on...&quot;</a>"
msgstr ""
"<a href=\"/lfs/faq.html#no-linuxthreads\">Glibc: &quot;... it is normal to "
"compile GNU libc with the `linuxthreads' add-on...&quot;</a>"

#. type: Content of: <ul><li>
#: complete.html:75
msgid ""
"<a href=\"/lfs/faq.html#glibc-awk-fail\">Glibc fails and mentions BEGIN and "
"END.</a>"
msgstr ""
"<a href=\"/lfs/faq.html#glibc-awk-fail\">Glibc sort en erreur et évoque "
"BEGIN et END.</a>"

#. type: Content of: <ul><li>
#: complete.html:76
msgid ""
"<a href=\"/lfs/faq.html#glibc-nss\">Glibc compilation errors out due to a "
"missing nss.h header file</a>"
msgstr ""
"<a href=\"/lfs/faq.html#glibc-nss\">La compilation de Glibc sort en erreur à "
"cause de l'absence du fichier d'entête nss.h</a>"

#. type: Content of: <ul><li>
#: complete.html:77
msgid ""
"<a href=\"/lfs/faq.html#cpp-fails-sanity-check\">Ncurses: C++ preprocessor "
"&quot;/lib/cpp&quot; fails sanity check</a>"
msgstr ""
"<a href=\"/lfs/faq.html#cpp-fails-sanity-check\">Ncurses: le préprocesseur "
"C++ \"/lib/cpp\" échoue lors de la vérification de conformité</a>"

#. type: Content of: <h3>
#: complete.html:79
msgid "<a href=\"/lfs/faq.html#confboot\">Configuration and booting issues</a>"
msgstr ""
"<a href=\"/lfs/faq.html#confboot\">Problèmes de configuration et de "
"démarrage</a>"

#. type: Content of: <ul><li>
#: complete.html:81
msgid ""
"<a href=\"/lfs/faq.html#unable-to-mount-root\">Kernel panic: VFS: unable to "
"mount root fs</a>"
msgstr ""
"<a href=\"/lfs/faq.html#unable-to-mount-root\">Kernel panic: VFS: unable to "
"mount root fs</a>"

#. type: Content of: <ul><li>
#: complete.html:82
msgid ""
"<a href=\"/lfs/faq.html#respawning-too-fast\">init: Id &quot;1&quot; "
"respawning too fast: disabled for 5 minutes</a>"
msgstr ""
"<a href=\"/lfs/faq.html#respawning-too-fast\">init: Id &quot;1&quot; "
"respawning too fast: disabled for 5 minutes</a>"

#. type: Content of: <ul><li>
#: complete.html:83
msgid ""
"<a href=\"/lfs/faq.html#net-pf-x\">I'm getting errors about net-pf-?.</a>"
msgstr ""
"<a href=\"/lfs/faq.html#net-pf-x\">J'obtiens des erreurs à propos de net-"
"pf-?.</a>"

#. type: Content of: <ul><li>
#: complete.html:84
msgid ""
"<a href=\"/lfs/faq.html#char-major-10-135\">modprobe: Can't locate module "
"char-major-10-135</a>"
msgstr ""
"<a href=\"/lfs/faq.html#char-major-10-135\">modprobe: Can't locate module "
"char-major-10-135</a>"

#. type: Content of: <ul><li>
#: complete.html:85
msgid ""
"<a href=\"/lfs/faq.html#no-dev-rtc\">modprobe: Can't locate module "
"/dev/rtc</a>"
msgstr ""
"<a href=\"/lfs/faq.html#no-dev-rtc\">modprobe: Can't locate module "
"/dev/rtc</a>"

#. type: Content of: <ul><li>
#: complete.html:86
msgid ""
"<a href=\"/lfs/faq.html#eth0-unknown-interface\">eth0:unknown interface</a>"
msgstr ""
"<a href=\"/lfs/faq.html#eth0-unknown-interface\">eth0: unknown interface</a>"

#. type: Content of: <ul><li>
#: complete.html:87
msgid ""
"<a href=\"/lfs/faq.html#spurious-8259A-interrupt\">spurious 8259A interrupt: "
"IRQ14</a>"
msgstr ""
"<a href=\"/lfs/faq.html#spurious-8259A-interrupt\">spurious 8259A interrupt: "
"IRQ14</a>"

#. type: Content of: <ul><li>
#: complete.html:88
msgid ""
"<a href=\"/lfs/faq.html#less-prints-ad\">Why does less (and therefore man) "
"print &lt;AD&gt; instead of hyphens?</a>"
msgstr ""
"<a href=\"/lfs/faq.html#less-prints-ad\">Pourquoi est-ce que less (et par "
"conséquent man) affiche &lt;AD&gt; au lieu des tirets&nbsp;?</a>"

#. type: Content of: <h2>
#: complete.html:90
msgid "BLFS FAQ:"
msgstr "FAQ de BLFS&nbsp;:"

#. type: Content of: <h3>
#: complete.html:91
msgid "<a href=\"/blfs/faq.html#genblfs\">General BLFS questions</a>"
msgstr ""
"<a href=\"/blfs/faq.html#genblfs\">Questions d'ordre général sur BLFS</a>"

#. type: Content of: <ul><li>
#: complete.html:93
msgid "<a href=\"/blfs/faq.html#bootcd\">How do I make a bootable CD?</a>"
msgstr ""
"<a href=\"/blfs/faq.html#bootcd\">Comment faire un CD de démarrage&nbsp;?</a>"

#. type: Content of: <ul><li>
#: complete.html:94
msgid ""
"<a href=\"/blfs/faq.html#seti\">Where do I join the LFS SETI/Predictor/etc "
"teams?</a>"
msgstr ""
"<a href=\"/blfs/faq.html#seti\">Où puis-je joindre les équipes LFS "
"SETI/Predictor/etc&nbsp;?</a>"

#. type: Content of: <h3>
#: complete.html:96
msgid "<a href=\"/blfs/faq.html#compissues\">Compilation issues</a>"
msgstr "<a href=\"/blfs/faq.html#compissues\">Problèmes de compilation</a>"

#. type: Content of: <ul><li>
#: complete.html:98
msgid ""
"<a href=\"/blfs/faq.html#gtk-2_0\">I'm getting errors building a package "
"that requires GTK+,but I've installed GTK+ 2.x.</a>"
msgstr ""
"<a href=\"/blfs/faq.html#gtk-2_0\">J'obtiens des erreurs quand je construis "
"un paquet qui requiert GTK+, mais j'ai bien installé GTK+ 2.x.</a>"

#. type: Content of: <ul><li>
#: complete.html:99
msgid ""
"<a href=\"/blfs/faq.html#undefined-deflate\">undefined reference to "
"`deflate'</a>"
msgstr ""
"<a href=\"/blfs/faq.html#undefined-deflate\">undefined reference to "
"`deflate'</a>"

#. type: Content of: <ul><li>
#: complete.html:100
msgid ""
"<a href=\"/blfs/faq.html#missing-x-includes\">X11/Xlib.h: No such file or "
"directory</a>"
msgstr ""
"<a href=\"/blfs/faq.html#missing-x-includes\">X11/Xlib.h: No such file or "
"directory</a>"

#. type: Content of: <ul><li>
#: complete.html:101
msgid ""
"<a href=\"/blfs/faq.html#gnome-versions\">Any error while building part of "
"Gnome</a>"
msgstr ""
"<a href=\"/blfs/faq.html#gnome-versions\">Toute erreur survenant lors de la "
"compilation d'un élément de Gnome</a>"

#. type: Content of: <ul><li>
#: complete.html:102
msgid ""
"<a href=\"/blfs/faq.html#xfree-missing-seperator\">XFree86: "
"Makefile.proto:32: *** missing separator</a>"
msgstr ""
"<a href=\"/blfs/faq.html#xfree-missing-seperator\">XFree86: "
"Makefile.proto:32: *** missing separator</a>"

#. type: Content of: <h3>
#: complete.html:104
msgid "<a href=\"/blfs/faq.html#confissues\">Configuration issues</a>"
msgstr "<a href=\"/blfs/faq.html#confissues\">Problème de configuration</a>"

#. type: Content of: <ul><li>
#: complete.html:106
msgid "<a href=\"/blfs/faq.html#how-to-print\">How do I print?</a>"
msgstr "<a href=\"/blfs/faq.html#how-to-print\">Comment imprimer&nbsp;?</a>"

#. type: Content of: <ul><li>
#: complete.html:107
msgid "<a href=\"/blfs/faq.html#konsole-ps1\">How do I set PS1 in Konsole?</a>"
msgstr ""
"<a href=\"/blfs/faq.html#konsole-ps1\">Comment paramétrer PS1 dans "
"Konsole&nbsp;?</a>"

#. type: Content of: <h3>
#: complete.html:111
msgid "General information about these FAQ's"
msgstr "Informations générales à propos de ces FAQ"

#. type: Content of: <dl><dt>
#: complete.html:113
msgid "Why this FAQ?"
msgstr "Pourquoi cette FAQ&nbsp;?"

#. type: Content of: <dl><dd><p>
#: complete.html:115
msgid ""
"The FAQ tries to answer questions before they're asked. This saves the "
"trouble of asking them, and sometimes, the trouble of encountering a problem."
msgstr ""
"La FAQ essaye de répondre aux questions avant qu'elles soient posées. Ça "
"vous évite le souci de poser les questions et parfois, celui de rencontrer "
"le problème."

#. type: Content of: <dl><dd><p>
#: complete.html:118
msgid ""
"This does reduce traffic and improve the signal to noise ratio but that is "
"merely a useful side effect."
msgstr ""
"Cela réduit le trafic et améliore le ratio signal/bruit, même si cela n'est "
"qu'un effet de bord bien utile."

#. type: Content of: <dl><dd><p>
#: complete.html:120
msgid ""
"Since the FAQ isn't the natural place to look for information, items should "
"be added to it only if they can't be added to the appropriate documentation. "
"Sometimes it will be necessary to add a pointer to the information in the "
"documentation."
msgstr ""
"Comme la FAQ n'est pas l'emplacement naturel où chercher l'information, on "
"ne devrait y ajouter que ce qui ne peut pas aller dans la documentation "
"adéquate. Il sera parfois nécessaire d'ajouter à la documentation un "
"pointeur vers cette information."

#. type: Content of: <dl><dt>
#: complete.html:125
msgid "What is LFS?"
msgstr "Qu'est ce que LFS&nbsp;?"

#. type: Content of: <dl><dd><p>
#: complete.html:127
msgid ""
"LFS stands for Linux From Scratch which is a project that aims to teach you "
"about the inner workings of Linux by building a Linux system by downloading, "
"building, and installing the packages yourself."
msgstr ""
"LFS signifie Linux From Scratch et c'est un projet qui a pour but de vous "
"apprendre le fonctionnement interne de Linux en vous faisant construire un "
"système Linux par le téléchargement, la compilation et l'installation des "
"paquets."

#. type: Content of: <dl><dd><p>
#: complete.html:130
msgid "Also check out the <a href=\"/lfs/index.html\">introduction to LFS</a>."
msgstr ""
"Vous pouvez aussi aller lire <a href=\"/lfs/index.html\">l'introduction à "
"LFS</a>."

#. type: Content of: <dl><dt>
#: complete.html:132
msgid "What is BLFS?"
msgstr "Qu'est ce que BLFS&nbsp;?"

#. type: Content of: <dl><dd><p>
#: complete.html:134
msgid ""
"LFS is a very basic system, in massive contrast to traditional "
"distributions. The reason is this: LFS is not intended to create your system "
"as you want it. It's intended to be just enough to allow you to build your "
"system as you want it. It's not an end, it's a beginning. When you're done "
"with LFS, you've just started building your system."
msgstr ""
"LFS est un système très basique, qui contraste beaucoup avec les "
"distributions traditionnelles. La raison est la suivante&nbsp;: LFS n'est "
"pas prévu pour créer un système à votre guise. Il est prévu pour être juste "
"suffisant pour vous permettre de créer un système à votre guise. Ce n'est "
"pas une fin, c'est un commencement. Quand vous en avez terminé avec LFS, "
"vous venez seulement de commencer à bâtir votre système."

#. type: Content of: <dl><dd><p>
#: complete.html:139
msgid ""
"This can be a problem if you're new to Unix systems and want a typical "
"desktop install with X and a web browser but have no idea what packages you "
"need. For this reason, there is Beyond Linux From Scratch, or <a href=\""
"/blfs/index.html\">BLFS</a>."
msgstr ""
"Ça peut être un problème si vous débutez avec les systèmes Unix et voulez "
"une installation bureautique classique avec X et un navigateur internet sans "
"savoir de quels paquets vous avez besoin. C'est pour cela qu'il existe "
"Beyond Linux From Scratch, ou <a href=\"/blfs/index.html\">BLFS</a>."

#. type: Content of: <dl><dt>
#: complete.html:144
msgid "Contributing to this FAQ."
msgstr "Contribuer à cette FAQ."

#. type: Content of: <dl><dd><p>
#: complete.html:146
msgid ""
"Suggestions are more than welcome. The FAQ maintainer can be reached either "
"via direct email or on the <a href=\""
"http://lists.linuxfromscratch.org/listinfo/faq/\">FAQ mailing list</a>."
msgstr ""
"Les suggestions sont plus que bienvenues. Le mainteneur de la FAQ peut être "
"joint par courrier électronique directement ou sur la <a href=\""
"http://lists.linuxfromscratch.org/listinfo/faq/\">Liste de diffusion de la "
"FAQ</a>."

#. type: Content of: <dl><dd><p>
#: complete.html:150
msgid ""
"Useful suggestions include the addition of questions that are actually "
"frequently asked (with well researched answers) and the removal of questions "
"that are obsolete."
msgstr ""
"Les suggestions pertinentes comprennent l'ajout de questions fréquemment "
"posées (avec des réponses fouillées) et la suppression des questions "
"obsolètes."

#. type: Content of: <dl><dd><p>
#: complete.html:153
msgid ""
"If you intend to regularly contribute to this FAQ, you might want to "
"subscribe to the FAQ mailing list. All suggestions, additions (and sometimes "
"removals) of the FAQ's are discussed there. Patches against the FAQ's are "
"also welcome, although regular text-based contributions are accepted as well."
msgstr ""
"Si vous pensez contribuer régulièrement à cette FAQ, vous devriez vous "
"inscrire à la liste de diffusion. Toutes les suggestions, tous les ajouts ("
"et parfois suppressions) y sont débattues. Il est possible d'appliquer des "
"patches à la FAQ, même si les contributions au classique format texte sont "
"également acceptées."

#. type: Content of: <dl><dd><p>
#: complete.html:158
msgid ""
"Everything intended to go in the FAQ without substantial editing must be "
"well thought out, checked, and researched; and written in a style consistent "
"with the existing content."
msgstr ""
"Tout ce qui est censé intégrer la FAQ, sans qu'il s'agisse d'une révision "
"complète, doit être réfléchi, vérifié, approfondi ; et écrit dans un style "
"qui se marie bien avec le contenu actuel."

#. type: Content of: <dl><p>
#: complete.html:163
#: complete.html:341
#: complete.html:455
msgid "<a href=\"#generalfaq\">Back to the top.</a>"
msgstr "<a href=\"#generalfaq\">Haut de page.</a>"

#. type: Content of: <h3>
#: complete.html:164
msgid "Support guidelines"
msgstr "Instructions sur l'assistance"

#. type: Content of: <dl><dt>
#: complete.html:166
msgid "What if I'm a newbie to Linux or LFS?"
msgstr "Et si je débute avec Linux ou LFS&nbsp;?"

#. type: Content of: <dl><dd><p>
#: complete.html:168
msgid ""
"If you've read the <a href=\"/lfs/view/stable/prologue/prerequisites.html\""
">prerequisites</a> and <a href=\"/lfs/view/stable/prologue/audience.html\""
">audience</a> pages you know that the target audience of LFS are "
"intermediate and advanced Linux users. Anybody who has a couple of months "
"experience with Linux and especially the console should be able to "
"successfully assemble an LFS system."
msgstr ""
"Si vous avez lu les pages <a href=\"/lfs/view/stable/prologue/prerequisites."
"html\">prérequis</a> et <a href=\"/lfs/view/stable/prologue/audience.html\""
">public</a>, vous savez que LFS vise les utilisateurs de Linux qui ont un "
"niveau intermédiaire et avancé. Quiconque a quelques mois d'expérience sur "
"Linux et en particulier la console devrait pouvoir monter avec succès son "
"système LFS."

#. type: Content of: <dl><dd><p>
#: complete.html:175
msgid ""
"While LFS seems like a good guide for newbies to Linux, the reality is "
"actually quite different. Experience with the support channels shows that "
"LFS is hard to grasp and a frustrating experience for newbies because they "
"lack understanding of the basic concepts."
msgstr ""
"LFS semble être un bon guide pour débuter sous Linux, cependant la réalité "
"est bien différente. Notre expérience sur les canaux d'assistance montre que "
"LFS est difficile à appréhender, et se révèle être une expérience frustrante "
"pour les débutants parce qu'il leur manque la compréhension des concepts de "
"base."

#. type: Content of: <dl><dd><p>
#: complete.html:179
msgid ""
"Practically, this means that newbies should get some experience before "
"starting with LFS. The <a href=\"/lfs/view/stable/prologue/prerequisites."
"html\">prerequisites page</a> lists the minimal required Linux knowledge, "
"but please also read the <a href=\"/hints/downloads/files/\">&quot;Essential "
"pre-reading for life with LFS&quot;</a> hint."
msgstr ""
"Concrètement, cela signifie que les débutants devraient acquérir de "
"l'expérience avant de commencer avec LFS. La <a href=\""
"/lfs/view/stable/prologue/prerequisites.html\">page des prérequis</a> liste "
"les connaissances minimales à avoir sur Linux, et s'il vous plaît, lisez "
"également l'astuce sur la <a href=\"/hints/downloads/files/\">«&nbsp;Pré-"
"lecture essentielle pour vivre avec une LFS&nbsp;»</a>."

#. type: Content of: <dl><dd><p>
#: complete.html:185
msgid ""
"These documents and this FAQ are your basic Linux survival guide.  You'll "
"have a great time with LFS if you've read them, and may have some difficulty "
"with LFS and the community, but most likely yourself, if you haven't read "
"them."
msgstr ""
"Ces documents et cette FAQ sont votre petit guide de survie sous Linux. Vous "
"allez bien vous amuser avec LFS si vous les avez lu, ce sera beaucoup plus "
"difficile avec LFS et avec la communauté, et plus probablement avec vous-"
"même, si vous ne les avez pas lu."

#. type: Content of: <dl><dt>
#: complete.html:190
msgid "Where is the best place to get help?"
msgstr "Quel est le meilleur endroit où trouver de l'aide&nbsp;?"

#. type: Content of: <dl><dd><p>
#: complete.html:192
msgid "When this FAQ fails to help, there are several places to go."
msgstr ""
"Si vous n'avez pas trouvé de réponse dans cette FAQ, il y a d'autres "
"endroits où aller chercher."

#. type: Content of: <dl><dd><p>
#: complete.html:193
msgid ""
"If you're having a problem with something in the book, it never hurts to go "
"back over the book. It's surprising how easy it is to overlook little things."
msgstr ""
"Si vous rencontrez un problème avec un passage du livre, ça ne peut pas "
"faire de mal de revenir quelques pages en arrière. C'est surprenant avec "
"quelle facilité certaines petites choses peuvent nous échapper."

#. type: Content of: <dl><dd><p>
#: complete.html:196
msgid ""
"If nothing else, reading the appropriate man and info pages will yield "
"useful information on some subject, if not what you were looking for, and "
"ensure that you know enough not to embarrass yourself if you have to ask "
"someone."
msgstr ""
"Enfin, la lecture des pages de man et d'info vous apportera des informations "
"pratiques sur certains sujets, si ce n'est la réponse à ce que vous "
"cherchez. Cela vous assurera également d'en savoir assez pour ne pas vous "
"mettre dans l'embarras si vous devez poser une question à quelqu'un."

#. type: Content of: <dl><dd><p>
#: complete.html:200
msgid ""
"<a href=\"http://www.tldp.org/\">The Linux Documentation Project</a> has the "
"HOW-TOs and a great deal of other documentation. You might find something "
"there."
msgstr ""
"<a href=\"http://www.tldp.org/\">Le Projet de Documentation de Linux</a> "
"propose des tutoriels et une tonne de documentation. Vous devriez y trouver "
"quelque chose."

#. type: Content of: <dl><dd><p>
#: complete.html:203
msgid ""
"The <a href=\"/search.html\">website's search</a> includes the mailing "
"lists. Many questions have been discussed there at least once."
msgstr ""
"La <a href=\"/search.html\">page de recherche</a> du site inclut les listes "
"de diffusion. Beaucoup de questions y ont été débattues au moins une fois."

#. type: Content of: <dl><dd><p>
#: complete.html:205
msgid ""
"For support-type help, IRC is often best. It's faster, and doesn't clog the "
"mailing lists. There's more information about the <a href=\"/support.html#"
"irc\">IRC channels</a> on the <a href=\"/support.html\">support</a> webpage."
msgstr ""
"Pour une aide de type «&nbsp;assistance&nbsp;», IRC est souvent le meilleur. "
"C'est plus rapide et ça n'encombre pas la liste de diffusion. Plus "
"d'informations sur les <a href=\"/support.html#irc\">canaux IRC</a> sur la <"
"a href=\"/support.html\">page de support</a>."

#. type: Content of: <dl><dd><p>
#: complete.html:209
msgid "There are a few IRC channels of interest."
msgstr "Il y a quelques canaux IRC dignes d'intérêt."

#. type: Content of: <dl><dd><ul><li>
#: complete.html:211
msgid ""
"<a href=\"irc://irc.freenode.net/lfs\">#lfs</a> - the LFS community channel."
msgstr ""
"<a href=\"irc://irc.freenode.net/lfs\">#lfs</a> - le canal communautaire de "
"LFS."

#. type: Content of: <dl><dd><ul><li>
#: complete.html:212
msgid ""
"<a href=\"irc://irc.freenode.net/lfs-support\">#lfs-support</a> - Support "
"for LFS and BLFS."
msgstr ""
"<a href=\"irc://irc.freenode.net/lfs-support\">#lfs-support</a> - Support "
"pour LFS et BLFS."

#. type: Content of: <dl><dd><ul><li>
#: complete.html:213
msgid ""
"<a href=\"irc://irc.freenode.net/hlfs\">#hlfs</a> - Support for the HLFS "
"book."
msgstr ""
"<a href=\"irc://irc.freenode.net/hlfs\">#hlfs</a> - Support pour le livre "
"HLFS."

#. type: Content of: <dl><dd><p>
#: complete.html:215
msgid ""
"If you are asking a support question, you are more likely to attract "
"competent and friendly help in <a href=\"irc://irc.freenode.net/lfs-support\""
">#lfs-support</a>."
msgstr ""
"Si vous formulez une requête d'assistance, vous aurez plus de chances "
"d'obtenir une aide amicale et compétente sur <a href=\"irc://irc.freenode.net"
"/lfs-support\">#lfs-support</a>."

#. type: Content of: <dl><dd><p>
#: complete.html:218
msgid ""
"As a last resort, there are the mailing lists. People will get frustrated "
"with you if you use the wrong one or cross post. Mailing list information is "
"on the <a href=\"/support.html#mailinglists\">support webpage</a> and tells "
"which list to use."
msgstr ""
"En dernier recours, on trouve les listes de diffusion. Les gens risquent de "
"vous en vouloir si vous utilisez la mauvaise liste ou si vous postez sur "
"plusieurs listes à la fois. Les informations sur les listes de diffusions se "
"trouvent sur la <a href=\"/support.html#mailinglists\">page assistance</a> "
"et indiquent quelle liste utiliser."

#. type: Content of: <dl><dd><p>
#: complete.html:222
msgid ""
"Please remember to provide enough information when you post to the mailing "
"lists. In <a href=\"/lfs/view/stable/chapter01/askforhelp.html\">chapter 1 "
"of LFS</a> you find a good method for posting. Additionally, someone has "
"written <a href=\"/hints/downloads/files/errors.txt\">a hint</a> which "
"details the error reporting procedure."
msgstr ""
"Souvenez-vous de fournir suffisamment d'informations quand vous postez sur "
"la liste de diffusion. Au <a href=\"/lfs/view/stable/chapter01/askforhelp."
"html\">chapitre 1 de LFS</a> vous trouverez des instructions pour utiliser "
"ces listes. De plus, quelqu'un a écrit <a href=\""
"/hints/downloads/files/errors.txt\">une astuce</a> qui détaille la procédure "
"de remontée d'erreurs."

#. type: Content of: <dl><dt>
#: complete.html:229
msgid "Which list should I use for what topic?"
msgstr "Quelle liste de diffusion pour quel sujet&nbsp;?"

#. type: Content of: <dl><dd><p>
#: complete.html:231
msgid ""
"Information about all the public mailing lists is available on the <a href=\""
"/mail.html\">mailing list</a> page.  Here are some general guidelines about "
"which list to use:"
msgstr ""
"Des informations sur toutes les listes de diffusion publiques sont "
"disponibles sur la page des <a href=\"/mail.html\">listes de diffusion</a>. "
"Voici quelques instructions pour déterminer quelle liste utiliser&nbsp;:"

#. type: Content of: <dl><dd><ul><li>
#: complete.html:235
msgid ""
"Send <em>support</em> questions for the stable released books to <a href=\""
"http://lists.linuxfromscratch.org/listinfo/lfs-support/\">lfs-support</a>.  "
"For anything which doesn't belong in LFS, use <a href=\""
"http://lists.linuxfromscratch.org/listinfo/blfs-support/\">blfs-support</a>"
".  Bug reports are gladly accepted; you can <a href=\""
"http://wiki.linuxfromscratch.org/\">create a ticket</a> for the appropriate "
"project or report to the <a href=\"http://lists.linuxfromscratch.org/listinfo"
"/lfs-dev/\">lfs-dev</a> mailing list."
msgstr ""
"Envoyez vos requêtes d'<em>assistance</em> sur les livres des versions "
"stables sur <a href=\"http://lists.linuxfromscratch.org/listinfo/lfs-support"
"/\">lfs-support</a>. Pour tout ce qui ne concerne pas LFS, utilisez <a href="
"\"http://lists.linuxfromscratch.org/listinfo/blfs-support/\">blfs-support</a>"
". Les rapports de bogues sont les bienvenus&nbsp;; vous pouvez <a href=\""
"http://wiki.linuxfromscratch.org/\">créer un ticket</a> pour le projet "
"adéquat ou envoyer un rapport sur la liste de diffusion <a href=\""
"http://lists.linuxfromscratch.org/listinfo/lfs-dev/\">lfs-dev</a>."

#. type: Content of: <dl><dd><ul><li>
#: complete.html:244
msgid ""
"If you are not having trouble following the <em>LFS</em> Book itself, do "
"<em>not</em> email <a href=\"http://lists.linuxfromscratch.org/listinfo/lfs-"
"support/\"><em>lfs</em>-support</a>."
msgstr ""
"Si vous n'avez aucune difficulté à suivre le Livre <em>LFS</em> lui-même, "
"n'envoyez <em>pas</em> de courriel à <a href=\""
"http://lists.linuxfromscratch.org/listinfo/lfs-support/\""
"><em>lfs</em>-support</a>."

#. type: Content of: <dl><dd><ul><li>
#: complete.html:247
msgid ""
"Unless you are <em>suggesting an improvement</em> to the LFS Book itself, do "
"not email <a href=\"http://lists.linuxfromscratch.org/listinfo/lfs-dev"
"/\">lfs-dev</a>."
msgstr ""
"A moins que vous ne <em>suggériez une amélioration</em> au livre LFS lui-"
"même, n'envoyez pas de courriel à <a href=\""
"http://lists.linuxfromscratch.org/listinfo/lfs-dev/\">lfs-dev</a>."

#. type: Content of: <dl><dd><ul><li>
#: complete.html:250
msgid ""
"Only suggestions concerning the BLFS Book are acceptable on <a href=\""
"http://lists.linuxfromscratch.org/listinfo/blfs-dev/\">blfs-dev</a>."
msgstr ""
"Seules les suggestions sur le Livre BLFS sont acceptées sur <a href=\""
"http://lists.linuxfromscratch.org/listinfo/blfs-dev/\">blfs-dev</a>."

#. type: Content of: <dl><dd><ul><li>
#: complete.html:252
msgid ""
"Things are a little different with <a href=\""
"http://lists.linuxfromscratch.org/listinfo/blfs-support/\">blfs-support</a>"
".  Everything that doesn't fit one of the preceding lists fits there except "
"for the price of beer and GNU versus BSD flame wars."
msgstr ""
"Les choses sont un peu différentes avec <a href=\""
"http://lists.linuxfromscratch.org/listinfo/blfs-support/\">blfs-support</a>. "
"Tout ce qui ne rentre pas dans une des listes précédentes rentre ici sauf si "
"cela concerne le prix de la bière et les guerres GNU contre BSD."

#. type: Content of: <dl><dd><ul><li>
#: complete.html:256
msgid ""
"The price of beer, GNU versus BSD, and Microsoft versus Linux flame wars are "
"restricted to <a href=\"http://lists.linuxfromscratch.org/listinfo/lfs-chat"
"/\">lfs-chat</a>.  These days, hardware discussion should go there as well."
msgstr ""
"Le prix de la bière, les guerres GNU contre BSD ou Microsoft contre Linux "
"sont limitées à <a href=\"http://lists.linuxfromscratch.org/listinfo/lfs-chat"
"/\">lfs-chat</a>. Aujourd'hui, c'est là également que les discussions sur la "
"matériel devraient se dérouler."

#. type: Content of: <dl><dd><p>
#: complete.html:261
msgid ""
"Of special note is that if you mention XFree86, KDE or GNOME you may be sure "
"that your post does not belong on <a href=\""
"http://lists.linuxfromscratch.org/listinfo/lfs-dev/\">lfs-dev</a> or <a href="
"\"http://lists.linuxfromscratch.org/listinfo/lfs-support/\">lfs-support</a>."
msgstr ""
"Notez que si vous évoquez XFree86, KDE ou GNOME, vous pouvez être sûr que "
"votre message n'est pas fait pour <a href=\""
"http://lists.linuxfromscratch.org/listinfo/lfs-dev/\">lfs-dev</a> ou <a href="
"\"http://lists.linuxfromscratch.org/listinfo/lfs-support/\">lfs-support</a>."

#. type: Content of: <dl><dt>
#: complete.html:267
msgid "What about netiquette?"
msgstr "Et la netiquette&nbsp;?"

#. type: Content of: <dl><dd><p>
#: complete.html:269
msgid ""
"Here are some practical points of etiquette. They include only those items "
"that will draw mention if missed. Those who've been around project mailing "
"lists awhile will find the first few obvious. There are less obvious items "
"toward the end."
msgstr ""
"Voici quelques informations pratiques sur l'étiquette. Elles incluent "
"seulement celles qui seront signalées si vous les avez omises. Ceux qui ont "
"l'habitude des listes de diffusion de projets trouveront que les premières "
"infos sont évidentes. Vers la fin, elles le sont un peu moins."

#. type: Content of: <dl><dd><p>
#: complete.html:273
msgid ""
"The reasons for these points are omitted for brevity, but rest assured, "
"these guidelines are more than just an individual's personal preference."
msgstr ""
"Les justifications de ces règles ne sont pas mentionnées mais soyez assurés "
"que ces instructions sont bien plus que les préférences personnelles d'un "
"individu."

#. type: Content of: <dl><dd><p>
#: complete.html:276
msgid ""
"While the text refers to \"the lists\" exclusively, it doesn't intend to "
"ignore the news groups that mirror the mailing lists."
msgstr ""
"Même si le texte mentionne exclusivement «&nbsp;les listes&nbsp;», le but "
"n'est pas d'ignorer les newsgroups miroirs des listes de diffusion."

#. type: Content of: <dl><dd><p>
#: complete.html:278
msgid ""
"With that out of the way, here are a couple manners oriented items followed "
"by more \"mechanical\" stuff:"
msgstr ""
"Ceci étant fait, voici quelques infos sur les comportements à adopter suivis "
"de choses plus «&nbsp;mécaniques&nbsp;»&nbsp;:"

#. type: Content of: <dl><dd><p>
#: complete.html:280
msgid ""
"Please remember that it is rude to post questions that are answered in "
"commonly available documentation such as the LFS and BLFS Books, this FAQ, "
"the LFS Hints, the appropriate man pages, the list archives, and Google "
"searches. As long as you can demonstrate that you've made an effort to find "
"the answer and you're not offended by a pointer to documentation, no "
"reasonable person will object to your question."
msgstr ""
"Souvenez-vous qu'il est incorrect de poser des questions dont les réponses "
"figurent dans la documentation couramment accessible comme les livres LFS ou "
"BLFS, cette FAQ, les astuces LFS, les pages de man correspondantes, les "
"archives des listes et les recherches Google. Tant que vous pouvez montrer "
"que vous avez fourni un effort pour trouver une réponse et que vous ne vous "
"sentez pas offensé par un pointeur vers la documentation, aucune personne "
"raisonnable n'opposera d'objection à votre question."

#. type: Content of: <dl><dd><p>
#: complete.html:286
msgid ""
"Most of the bothersome flame wars start when a newbie posts an obvious "
"question, is then criticized (even in a kindly manner), and becomes publicly "
"offended. Please try to avoid this situation. \"Wordlessly\" pointing to the "
"exact spot in the documentation is sufficient. If you feel you must "
"criticize, please do it via private email, not on the lists. The same "
"applies to anything else that may become heated."
msgstr ""
"La plupart des conflits embarrassants débutent lorsqu'un débutant pose une "
"question dont la réponse est évidente, se fait alors critiquer (même "
"gentiment) et se trouve publiquement offensé. Essayez, s'il vous plait, "
"d'éviter cette situation. Le fait de diriger, sans autre explication, vers "
"la réponse exacte dans la documentation est suffisant. Si vous ressentez le "
"besoin de critiquer, faites le en privé, pas sur les listes. Le raisonnement "
"est le même pour tout ce qui pourrait \"s'enflammer\"."

#. type: Content of: <dl><dd><p>
#: complete.html:292
msgid ""
"The lists have an international membership so slang of all sorts and idioms "
"are likely to be misunderstood. (Witness the recent discussion of \""
"bootstrapping\".) Any mention of profanity, politics, war, or religion (even "
"in signatures) is likely to upset someone somewhere in the world so please "
"avoid them as well. Finally, it is considered polite to post in English "
"since many more people on the lists know it than any other language."
msgstr ""
"Les membres des listes viennent du monde entier, donc l'argot et les "
"expressions idiomatiques risquent d'être mal comprises (comme en témoigne la "
"discussion récente sur le démarrage). Les propos injurieux, relatifs à la "
"politique, à la guerre, à la religion (même dans les signatures) risquent de "
"contrarier quelqu'un quelque part dans le monde, alors évitez les, s'il vous "
"plait. Enfin, on considère qu'il est plus poli de rédiger en anglais car "
"c'est une langue que la plupart des gens connaissent avant tout autre."

#. type: Content of: <dl><dd><p>
#: complete.html:299
msgid "Now for the more \"mechanical\" stuff."
msgstr "Passons maintenant aux choses plus «&nbsp;mécaniques&nbsp;»."

#. type: Content of: <dl><dd><ul><li>
#: complete.html:301
msgid ""
"<strong>Do not post in HTML.</strong> If you use Yahoo, Hotmail, or Outlook "
"and haven't turned HTML off, then it is on. If you're using another mail "
"client, please do check before posting. If you don't know how to turn HTML "
"off, see <a href=\"nomime.html\">nomime.html</a>.  <strong>All posts which "
"contain HTML tags will be sent to /dev/null and never reach the list</strong>"
". Unfortunately, Spamassassin's HTML filter is very strict and will block "
"all posts with HTML or XML-like tags, keep this in mind when posting XML "
"snippets to a list. A commonly used trick is to replace the triangle "
"brackets &lt; &gt; with angel brackets []."
msgstr ""
"<strong>Ne postez pas en HTML</strong>. Si vous utilisez Yahoo, Hotmail, ou "
"Outlook et n'avez pas désactivé le HTML, c'est qu'il est activé. Si vous "
"utilisez un autre client de messagerie, vérifiez avant de poster. Si vous ne "
"savez pas comment désactiver le HTML, allez lire <a href=\"nomime.html\""
">nomime.html</a>. <strong>Tous les courriers contenant du HTML seront "
"redirigés vers /dev/null et n'atteindront jamais la liste</strong>. "
"Malheureusement, le filtre HTML de Spamassassin est très strict et bloquera "
"tous les courriers avec du HTML ou des balises de type XML. Gardez bien cela "
"en tête si vous postez des extraits de XML sur une liste. Un contournement "
"largement utilisé consiste à remplacer les signes supérieur &lt; et "
"inférieur &gt; par des crochets []."

#. type: Content of: <dl><dd><ul><li>
#: complete.html:311
msgid ""
"<strong>Wrap text at 72 characters.</strong> If you do not wish to do this "
"by hand, set your mail client to do it automatically when sending."
msgstr ""
"<strong>Coupez les lignes à 72 caractères</strong>. Si vous ne voulez pas le "
"faire à la main, configurez votre client de messagerie pour qu'il le fasse "
"automatiquement à l'envoi des messages."

#. type: Content of: <dl><dd><ul><li>
#: complete.html:314
msgid ""
"<strong>Reply <em>below</em> quoted text.</strong> Outlook makes this "
"difficult. There is a <a href=\"http://home.in.tum.de/%7Ejain/software"
"/outlook-quotefix/\">plug-in to fix Outlook</a>, and <a href=\""
"http://home.in.tum.de/%7Ejain/software/oe-quotefix/\">one for Outlook "
"Express</a>."
msgstr ""
"<strong>Répondez <em>sous</em> les citations</strong>. Ce n'est pas facile "
"avec Outlook. Il existe un <a href=\"http://home.in.tum.de/%7Ejain/software"
"/outlook-quotefix/\">greffon pour corriger Outlook</a>, et <a href=\""
"http://home.in.tum.de/%7Ejain/software/oe-quotefix/\">un pour Outlook "
"Express</a>."

#. type: Content of: <dl><dd><ul><li>
#: complete.html:320
msgid "<strong>Limit signatures to four lines.</strong>"
msgstr "<strong>Limitez vos signatures à quatre lignes.</strong>"

#. type: Content of: <dl><dd><ul><li>
#: complete.html:321
msgid ""
"<strong>Trim quoted text,</strong> especially signatures. But <strong>do not "
"trim so that it is confusing to read your reply</strong> without consulting "
"the original."
msgstr ""
"<strong>Élaguez les citations</strong>, surtout les signatures. Mais <strong>"
"n'élaguez pas au point de rendre votre message difficile à "
"comprendre</strong> sans consulter le message original."

#. type: Content of: <dl><dd><ul><li>
#: complete.html:324
msgid ""
"<strong>Do not click reply unless you're actually replying to a "
"post.</strong> Use new, or compose, or whatever your mail client calls it, "
"to ask a new question or start a new thread. Reply sets more than just the "
"subject line and will cause your post to appear in the wrong place unless "
"you're actually answering."
msgstr ""
"<strong>Ne cliquez pas sur \"Répondre\" à moins que vous ne soyez vraiment "
"en train de répondre à un message</strong>. Utilisez les boutons \"Nouveau\" "
"ou \"Écrire\" ou quel que soit le nom que votre logiciel de messagerie lui "
"donne, pour poser une nouvelle question ou commencer un nouveau fil de "
"discussion. Le bouton \"Répondre\" ne fait pas que remplir le champs \""
"Sujet\", il enverra votre message à un mauvais endroit sauf si votre message "
"est effectivement une réponse."

#. type: Content of: <dl><dd><p>
#: complete.html:330
msgid ""
"The following isn't major, but is useful to know. On the LFS lists, people "
"usually clear the CC field and just mail the list with replies.  This is "
"probably not a good idea but is existing practice due to a political "
"situation which is unlikely to change."
msgstr ""
"Ce qui suit n'est pas de la plus grande importance, mais ça peut être utile "
"de le savoir. Sur les listes LFS, les gens effacent généralement le champs "
"CC et envoient leurs réponses à la liste. Ce n'est sans doute pas une bonne "
"idée mais cette pratique existe. Elle est due à une situation politique qui "
"n'est pas près de changer."

#. type: Content of: <dl><dd><p>
#: complete.html:334
msgid ""
"<a href=\"http://www.ietf.org/rfc/rfc1855.txt\">RFC 1855</a> &quot;provides "
"a minimum set of guidelines for Network Etiquette (Netiquette) and functions "
"as a minimum set of guidelines for individuals, both users and administrators"
msgstr ""
"La <a href=\"http://www.ietf.org/rfc/rfc1855.txt\">RFC 1855</a> «&nbsp;"
"fournit un jeu d'instructions minimal concernant l'Étiquette sur la Toile ("
"la Netiquette) et fonctionne comme un jeu d'instructions minimal à "
"destination des individus, qu'ils soient utilisateurs ou "
"administrateurs&nbsp;»."

#. type: Content of: <dl><h3>
#: complete.html:342
msgid "Frequently Reported Bugs"
msgstr "Bogues fréquemment remontés"

#. type: Content of: <dl><dl><dt>
#: complete.html:344
msgid "The &quot;ln -s&quot; commands in the Book are wrong."
msgstr "Dans le livre, les commandes «&nbsp;ln -s&nbsp;» sont incorrectes."

#. type: Content of: <dl><dl><dd><p>
#: complete.html:346
msgid ""
"No, the &quot;ln -s&quot; commands in the Book are correct. A symlink is "
"just a special file containing the given filename. So that filename is "
"relative to the link, not the working directory when the link is created.  "
"Try it and see. More information in <code>man ln</code>."
msgstr ""
"Non, les commandes «&nbsp;ln -s&nbsp;» du livre sont correctes. Un lien "
"symbolique est juste un fichier spécial qui contient le nom de fichier "
"donné. Le nom de fichier est donc relatif au lien, pas au répertoire courant "
"au moment de la création du lien. Essayez pour voir. Plus d'informations "
"avec <code>man ln</code>."

#. type: Content of: <dl><dl><dt>
#: complete.html:351
msgid "/bin/foo is a copy of /bin/bar."
msgstr "/bin/foo est une copie de /bin/bar."

#. type: Content of: <dl><dl><dd><p>
#: complete.html:353
msgid ""
"Try &quot;ls -i /bin/foo /bin/bar&quot;. Are the inode numbers the same? If "
"so, they're not copies, they're hard linked."
msgstr ""
"Essayez \"ls -i /bin/foo /bin/bar\". Les numéros d'inodes sont-ils les "
"mêmes&nbsp;? Si oui, ce ne sont pas des copies, ce sont des liens matériels."

#. type: Content of: <dl><dl><dd><p>
#: complete.html:355
msgid ""
"For more information explaining the difference between hard and soft links, "
"please take a look at the Q &amp; A article on Linux Gazette at <a href=\""
"http://linuxgazette.net/105/pitcher.html\""
">http://linuxgazette.net/105/pitcher.html</a>."
msgstr ""
"Pour plus d'explications sur les différences entre liens symboliques et "
"liens matériels, consultez la page de Questions/Réponses sur Linux Gazette à "
"cette adresse&nbsp;: <a href=\"http://linuxgazette.net/105/pitcher.html\""
">http://linuxgazette.net/105/pitcher.html</a>."

#. type: Content of: <dl><dl><dt>
#: complete.html:360
msgid "Can I use a version newer than the one in the Book?"
msgstr "Puis-je utiliser une version plus récente que celle du livre&nbsp;?"

#. type: Content of: <dl><dl><dd><p>
#: complete.html:362
msgid ""
"If this is your first time building LFS, using a version not in the book or "
"varying from the book in any way is not a good idea. The IRC channel "
"regulars have a saying, &quot;FBBG&quot;, meaning &quot;Follow Book, Book "
"Good.&quot; They and the people on the lists have helped many an unhappy "
"newbie who deviated from the book during that first build."
msgstr ""
"Si c'est la première fois que vous construisez LFS, ce n'est pas une bonne "
"idée d'utiliser une version qui n'est pas dans le livre, ou qui en diffère. "
"Les utilisateurs réguliers des canaux IRC ont un proverbe, \"FBBG\" (\""
"Follow Book, Book Good\"), soit \"Suivez livre, livre bon\". Ils ont, avec "
"les utilisateurs des listes, souvent aidé des débutants mécontents ayant "
"dévié du livre pour leur première construction."

#. type: Content of: <dl><dl><dd><p>
#: complete.html:367
msgid ""
"Once you've built a system &quot;by the book&quot;, you have a stable "
"knowledge base from which to experiment to your heart's content (or pain, as "
"is often the case.)"
msgstr ""
"Une fois que vous avez bâti un système «&nbsp;au plus près du livre&nbsp;», "
"vous avez une base de connaissance solide à partir de laquelle vous allez "
"pouvoir vous lancer à cœur joie (ou endolori le plus souvent) dans diverses "
"expériences."

#. type: Content of: <dl><dl><dt>
#: complete.html:371
msgid "There's a new version of package Foo."
msgstr "Il y a une nouvelle version du paquet Foo."

#. type: Content of: <dl><dl><dd><p>
#: complete.html:373
msgid ""
"If the new version is more than a day old, it is likely that someone has "
"tested the release and reported it on the mailing lists. Please search the "
"archives before posting questions about whether it works."
msgstr ""
"Si cette nouvelle version a plus d'un jour, il est probable que quelqu'un "
"l'ait déjà testé et mentionné dans les listes de diffusion. Cherchez dans "
"les archives avant de poster une question pour savoir si ce paquet "
"fonctionne."

#. type: Content of: <dl><dl><dd><p>
#: complete.html:376
msgid ""
"If you'd like to report the new release, follow these steps to avoid making "
"a duplicate report."
msgstr ""
"Si vous voulez annoncer la sortie d'une nouvelle version, suivez ces étapes "
"pour éviter de faire une annonce en double."

#. type: Content of: <dl><dl><dd><ul><li>
#: complete.html:378
msgid ""
"Check for open <a href=\"http://wiki.linuxfromscratch.org/lfs/\">LFS "
"tickets</a> or <a href=\"http://wiki.linuxfromscratch.org/blfs/\">BLFS "
"tickets</a> to see if the release has been posted there."
msgstr ""
"Vérifiez s'il y a un <a href=\"http://wiki.linuxfromscratch.org/lfs/\">"
"ticket LFS</a> ou un <a href=\"http://wiki.linuxfromscratch.org/blfs/\">"
"ticket BLFS</a> ouvert pour voir si elle y a été postée."

#. type: Content of: <dl><dl><dd><ul><li>
#: complete.html:382
msgid ""
"If the release is not in an open ticket, report it to lfs-book (or blfs-book "
"for packages in BLFS). And if you like, test it and report any problems or "
"changes in compilation instructions, too."
msgstr ""
"S'il n'y a pas de ticket ouvert concernant cette sortie, annoncez-la sur la "
"liste lfs-book (ou sur blfs-book si le paquet concerne BLFS). Et si vous "
"voulez, testez-le et rapportez tout problème ou changement dans les "
"instructions de compilation."

#. type: Content of: <dl><dl><dt>
#: complete.html:387
msgid "The Delete key doesn't work."
msgstr "La touche Suppr. ne fonctionne pas."

#. type: Content of: <dl><dl><dd><p>
#: complete.html:389
msgid ""
"Please read the LFS <a href=\"/lfs/view/stable/chapter07/inputrc.html\">"
"inputrc page</a>."
msgstr ""
"Lisez la page <a href=\"/lfs/view/stable/chapter07/inputrc.html\">inputrc</a>"
" du livre LFS."

#. type: Content of: <dl><dl><dt>
#: complete.html:391
msgid "The system shuts down when fsck errors out!"
msgstr "Le système s'éteint quand fsck sort en erreur&nbsp;!"

#. type: Content of: <dl><dl><dd><p>
#: complete.html:393
msgid ""
"Unix systems normally run sulogin if the normal bootup fsck run errors out "
"so that root can log in and fix it. Because sulogin will accept any password "
"if /etc/passwd is corrupt, the LFS developers decided this was a security "
"risk. Therefore, the LFS bootscripts shut the machine down if fsck errors, "
"and it must be booted with the \"init=/bin/bash\" kernel parameter to get a "
"root shell. Whether this is wise is beyond the scope of the FAQ, but if it "
"doesn't work for you you'll want to change that boot script before it's too "
"late."
msgstr ""
"Les système Unix lancent normalement sulogin quand le fsck d'un démarrage "
"normal sort en erreur, afin que root puisse se connecter et résoudre le "
"problème. Comme sulogin va accepter n'importe quel mot de passe si /etc/"
"passwd est corrompu, les développeurs de LFS ont estimé que cela "
"représentait un risque pour la sécurité. Les scripts de démarrage de LFS "
"éteignent donc la machine en cas d'erreur de fsck, et elle doit être "
"démarrée avec le paramètre de noyau \"init=/bin/bash\" afin d'obtenir un "
"shell root. Savoir si cela est sage ne rentre pas dans le périmètre de cette "
"FAQ, mais si cela ne vous convient pas, changez les scripts de démarrage "
"avant qu'il ne soit trop tard."

#. type: Content of: <dl><dl><dt>
#: complete.html:402
msgid "Where are the lfs-packages tarballs or wget scripts?"
msgstr "Où sont les archives des paquets LFS ou les scripts wget&nbsp;?"

#. type: Content of: <dl><dl><dd><p>
#: complete.html:404
msgid ""
"Package tarballs are available at <a href=\""
"http://anduin.linuxfromscratch.org/sources/LFS/lfs-packages/\">the LFS file "
"repository</a>. There is also a wget-list linked in the book, near the "
"bottom of the <a href=\"/lfs/view/stable/chapter03/introduction.html\">"
"Packages and Patches Introduction page</a>."
msgstr ""
"Les archives des paquets sont disponibles sur <a href=\""
"http://anduin.linuxfromscratch.org/sources/LFS/lfs-packages/\">le dépôt de "
"fichiers de LFS</a>. Il y a aussi un lien vers wget-list dans le livre, vers "
"la fin de la page d'<a href=\"/lfs/view/stable/chapter03/introduction.html\""
">Introduction</a> aux paquets et correctifs."

#. type: Content of: <dl><dl><dt>
#: complete.html:411
msgid "How do I find a package or command?"
msgstr "Comment puis-je trouver un paquet ou une commande&nbsp;?"

#. type: Content of: <dl><dl><dd><p>
#: complete.html:413
msgid ""
"Please refer to the <a href=\"/lfs/download.html\">download LFS</a> webpage."
msgstr ""
"Consultez la page <a href=\"/lfs/download.html\">téléchargement de LFS</a>."

#. type: Content of: <dl><dl><dt>
#: complete.html:415
msgid "How do I upgrade my LFS/BLFS system?"
msgstr "Comment puis-je mettre à jour mon système LFS/BLFS&nbsp;?"

#. type: Content of: <dl><dl><dd><p>
#: complete.html:417
msgid ""
"You probably know this already, but LFS is not a distro in the traditional "
"sense. Its primary goal is: <a href=\"/lfs/index.html\">teaching people how "
"a Linux system works internally</a>."
msgstr ""
"Vous le savez probablement déjà mais LFS n'est pas un distribution au sens "
"traditionnel du terme. Son but premier est&nbsp;: <a href=\"/lfs/index.html\""
">enseigner aux gens comment un système Linux fonctionne en interne</a>."

#. type: Content of: <dl><dl><dd><p>
#: complete.html:420
msgid ""
"While this means you have great control over your system (&quot;Your distro. "
"Your rules.&quot;), it also has the drawback of having to take care of "
"updating it yourself."
msgstr ""
"Bien que cela signifie que vous aillez un grand contrôle sur votre système ("
"\"Votre distro. Vos règles.\"), Il a aussi l'inconvénient d'avoir à prendre "
"soin de la mise à jour vous-même."

# je ne comprend pas le sens de burned....je ne pense pas que c'est brulé ;o)
#. type: Content of: <dl><dl><dd><p>
#: complete.html:423
msgid ""
"If you've built an LFS system and have extended it to become your primary "
"system, the best thing to do is to decide on an upgrade policy. Do you want "
"to keep the latest version of every package? Then be careful, because you're "
"going to be burned. I recommend slight conservatism when upgrading to keep a "
"healthy system. A general rule of thumb which works for most people is: only "
"upgrade packages if they have security fixes.  Subscribe to lfs-security and "
"LWN to keep yourself informed about security fixes. Another rule of thumb is:"
" don't upgrade the toolchain (gcc, glibc and binutils) unless you're going "
"to rebuild your entire system. These packages form the heart of your LFS "
"system, destroying them means destroying the ability to compile packages or "
"even run binaries."
msgstr ""
"Si vous avez construit un système LFS et l'avez complété pour qu'il devienne "
"votre système principal, la meilleure chose à faire est de décider d'une "
"stratégie de mise à niveau. Vous voulez conserver la dernière version de "
"chaque paquet&nbsp;? Alors faites attention, parce que vous allez vous "
"brûler. Je recommande d'être légèrement conservateur lors de la mise à "
"niveau pour maintenir un système sain. Une règle générale qui fonctionne "
"pour la plupart des gens est&nbsp;: mettre à jour seulement les paquets "
"s'ils ont des correctifs de sécurité. Inscrivez-vous à lfs-security et LWN "
"pour vous tenir au courant des correctifs de sécurité. Une autre règle "
"est&nbsp;: ne pas mettre à jour la chaîne d'outils (gcc, glibc et binutils) "
"à moins de reconstruire votre système entièrement. Ces paquets constituent "
"le cœur de votre système LFS, les détruire signifie détruire la capacité de "
"compiler des paquets ou même exécuter des fichiers binaires."

# bleeding-edge ???
#. type: Content of: <dl><dl><dd><p>
#: complete.html:434
msgid ""
"Remember that updating packages is at your own risk. LFS takes great care to "
"present a stable mix of packages which are compatible all the way up to BLFS "
"so you can compile OpenOffice.Org and Java (which are real dinosaurs to "
"compile). This means that your LFS system may get slightly outdated but "
"ensures compatibility and stability. You can compare this to Debian's stable "
"and testing releases, although LFS stable is generally bleeding-edge "
"compared to other distro's."
msgstr ""
"Rappelez vous que la mise à jour des paquets se fait à vos risques et "
"périls. LFS fait très attention à présenter un ensemble stable de paquets "
"qui sont compatibles pour aller au bout de BLFS et que vous puissiez "
"compiler OpenOffice.Org et Java (qui sont de vrais mastodontes à compiler). "
"Cela signifie que votre système LFS peut être un peu dépassé mais assurer la "
"compatibilité et la stabilité. Vous pouvez comparer cela aux versions Stable "
"et testing de Debian, bien que la version LFS stable soit généralement très "
"récente comparée aux autres distributions."

#. type: Content of: <dl><dl><dd><p>
#: complete.html:441
msgid ""
"In general it is safe to upgrade single packages; they'll just overwrite the "
"old contents. Package managers take care of uninstalling old versions, and "
"it's really convenient to have some sort of package management system in "
"place. Have a look at the hints; there are several, ranging from RPM to DEB "
"to TGZ (Slackware) to Checkinstall to package users."
msgstr ""
"En général il est possible de mettre à jour des paquets seuls&nbsp;; ils "
"réécriront simplement le vieux contenu. Les gestionnaires de paquets "
"prennent soin de désinstaller les anciennes versions, et c'est clairement "
"pratique d'avoir une sorte de gestion de paquet en place. Regardez les "
"astuces&nbsp;; il y en a plusieurs, de RPM à DEB en passant par TGZ "
"(Slackware), Checkinstall et les utilisateurs paquets."

#. type: Content of: <dl><dl><dd><p>
#: complete.html:447
msgid ""
"A final comment: what package instructions should you use when updating a "
"package? In general, you can use the standard LFS instructions, although you "
"shouldn't blindly assume they will apply to all packages. To keep yourself "
"informed about upgrades and new package instructions, subscribe to lfs-dev. "
"Keep in mind that this is not a support list but a development list."
msgstr ""
"Un dernier commentaire : Quelles instructions devez vous utiliser pour la "
"mise à jour d'un paquet ? En général, vous pouvez utiliser les instructions "
"standards de LFS, bien que vous ne devez pas aveuglement penser qu'elles "
"s'appliqueront pour tous les paquets. Pour rester informé des mises à jour "
"et des nouvelles instructions, inscrivez vous à lfs-dev. Gardez en tête que "
"ce n'est pas une liste de support mais une liste de développement."

# a travailler..... pour une trad de expired
#. type: Content of: <dl><h3>
#: complete.html:456
msgid "Old and expired FAQ's"
msgstr "FAQ anciennes et périmées"

#. type: Content of: <dl><dl><dt>
#: complete.html:458
msgid ""
"<a href=\"#version-not-in-book\">I'm using a version not in the book. Is "
"that a problem?</a>"
msgstr ""
"<a href=\"#version-not-in-book\">J'ai utilisé une version qui n'est pas dans "
"le livre. Est-ce un problème ?</a>"

#. type: Content of: <dl><dl><dd><p>
#: complete.html:461
msgid ""
"There's already a <a href=\"#why-not-version\">FAQ entry</a> which describes "
"this. Since hardly anyone refers to this entry it's now obsolete."
msgstr ""
"Il y a déjà une <a href=\"#why-not-version\">entrée dans la FAQ</a> qui "
"décrit cela. Comme presque personne ne se réfère à cette entrée, elle est "
"maintenant obsolète. "

#. type: Content of: <dl><dl><dt>
#: complete.html:465
msgid "<a href=\"#wheres-which\">Where's which?</a>"
msgstr "<a href=\"#wheres-which\">Où est-ce?</a>"

#. type: Content of: <dl><dl><dd><p>
#: complete.html:467
msgid ""
"Obsolete on account of the <a href=\"/blfs/view/stable/general/which.html\""
">BLFS</a> book."
msgstr ""
"Obsolète à cause du livre <a href=\"/blfs/view/stable/general/which.html\""
">BLFS</a>."

#. type: Content of: <dl><dl><dt>
#: complete.html:470
msgid "<a href=\"#portmap\">Where's portmap?</a>"
msgstr "<a href=\"#portmap\">Où est portmap?</a>"

#. type: Content of: <dl><dl><dd><p>
#: complete.html:472
msgid ""
"Obsolete on account of the <a href=\"/blfs/view/stable/basicnet/rpcbind."
"html\">BLFS</a> book."
msgstr ""
"Obsolète à cause du livre <a href=\"/blfs/view/stable/basicnet/rpcbind.html\""
">BLFS</a>."

#. type: Content of: <dl><dl><dt>
#: complete.html:475
msgid "<a href=\"#lfs-logos\">Where can I get LFS Logos?</a>"
msgstr "<a href=\"#lfs-logos\">Où puis-je avoir des Logos LFS?</a>"

#. type: Content of: <dl><dl><dd><p>
#: complete.html:477
msgid ""
"Obsolete on account of the <a href=\"/blfs/artwork/\">BLFS artwork</a> "
"webpage."
msgstr ""
"Obsolète à cause de la page Web <a href=\"/blfs/artwork/\">BLFS artwork</a>."

#. type: Content of: <dl><dl><dt>
#: complete.html:479
msgid ""
"<a href=\"#optimized-glibc-fail\">My optimized build of glibc is failing in "
"spinlock.c</a>"
msgstr ""
"<a href=\"#optimized-glibc-fail\">Ma construction optimisée de glibc échoue "
"dans spinlock.c</a>"

#. type: Content of: <dl><dl><dd><p>
#: complete.html:482
msgid ""
"Let's not encourage people to optimize glibc. Besides, the <a href=\""
"/lfs/faq.html#optimizations\">when using optimization flags (setting "
"CFLAGS)</a> entry should take care of this question."
msgstr ""
"Nous n'incitons pas les gens à optimiser la glibc. De plus, <a href=\""
"/lfs/faq.html#optimizations\">lorsque vous utilisez des indicateurs "
"d'optimisation (paramètres CFLAGS)</a>, il faudrait faire attention à cette "
"question."

#. type: Content of: <dl><h3>
#: complete.html:487
msgid "Thanks"
msgstr "Merci"

#. type: Content of: <dl><p>
#: complete.html:488
msgid ""
"This FAQ is dedicated to all the hard-working people on the support lists "
"who keep me busy with this FAQ ;-)."
msgstr ""
"Cette FAQ est dédiée à tous les gens durs à la tâche sur les listes de "
"support qui me tiennent occupés avec cette FAQ ;-)."

#. type: Content of: <dl><p>
#: complete.html:490
msgid "Thanks go to..."
msgstr "Merci à..."

#. type: Content of: <dl><ul><li>
#: complete.html:492
msgid "Seth W. Klein for creating and maintaining this FAQ before me."
msgstr ""
"Seth W. Klein pour la création et la maintenance de cette FAQ avant moi."

#. type: Content of: <dl><ul><li>
#: complete.html:493
msgid ""
"All the guys (and all of the few girls as well, wish there were more of you) "
"on the lists, from whose answers so many of these answers come."
msgstr ""
"Tous les gars (et toutes les quelques filles aussi, j'aimerai qu'il y en ai "
"plus) des listes, de qui les réponses, beaucoup des réponses viennnent."

#. type: Content of: <dl><ul><li>
#: complete.html:496
msgid ""
"Especially those of you who sort out a question, its symptoms, and its "
"answer and mail the lot to me. Your IDs are immortalized in the commit logs ("
"though only for the span of a digital forever, but hey, I try :-)"
msgstr ""
"En particuliers ceux d'entre vous qui comprennent la question, ses symptômes "
"et ses réponses et qui m'envoient le tout. Votre ID est immortalisée pour "
"toujours dans le journal des modifications (enfin seulement pour la durée "
"d'un toujours numérique, mais bon, au moins j'essaye :-))"

#. type: Content of: <dl><ul><li>
#: complete.html:500
msgid ""
"Tushar Teredesai, Chris Lingard, Jeremy Utley, The Cheeze and countless "
"other people who regularly post FAQ links to the support lists."
msgstr ""
"Tushar Teredesai, Chris Lingard, Jeremy Utley, The Cheeze et les "
"innombrables autres personnes qui régulièrement poste des liens de FAQ sur "
"les listes d'aide."

#. type: Content of: <dl><ul><li>
#: complete.html:503
msgid "The BLFS editors whose book produces so delightfully few FAQs."
msgstr ""
"Les éditeurs de BLFS dont le livre produit si délicieusement quelques FAQ."

#. type: Content of: <dl><h1>
#: complete.html:508
msgid "BLFS Frequently Asked Questions"
msgstr "Foire aux questions de BLFS"

#. type: Content of: <p>
#: faq-en.html:3
msgid ""
"The FAQ is divided in three documents. The <a href=\"/faq/index.html\">"
"General FAQ</a> has links to all questions and answers. The <a href=\""
"/lfs/faq.html\">LFS FAQ</a> is a selection of LFS-specific FAQ's and the <a "
"href=\"/blfs/faq.html\">BLFS FAQ</a> is a selection of BLFS-specific FAQ's."
msgstr ""
"La FAQ est divisée en trois documents. La <a href=\"/faq/index.html\">FAQ "
"générale</a> propose des liens vers toutes les questions et les réponses. La "
"<a href=\"/lfs/faq.html\">FAQ LFS</a> est une sélection des questions les "
"plus fréquemment posées concernant LFS et la <a href=\"/blfs/faq.html\">FAQ "
"BLFS</a> est une sélection des questions les plus fréquemment posées "
"spécifiques à BLFS."

#. type: Content of: <dl><h3>
#: complete.html:513
msgid "<a href=\"#genblfs\">General BLFS questions</a>"
msgstr "<a href=\"#genblfs\">Questions générales sur BLFS</a>"

#. type: Content of: <dl><ul><li>
#: complete.html:515
msgid "<a href=\"#bootcd\">How do I make a bootable CD?</a>"
msgstr "<a href=\"#bootcd\">Comment faire un CD bootable?</a>"

#. type: Content of: <dl><ul><li>
#: complete.html:516
msgid "<a href=\"#seti\">Where do I join the LFS SETI/Predictor/etc team?</a>"
msgstr ""
"<a href=\"#seti\">Où puis-je joindre l'équipe LFS "
"SETI/Predictor/etc&nbsp;?</a>"

#. type: Content of: <dl><h3>
#: complete.html:518
msgid "<a href=\"#compissues\">Compilation issues</a>"
msgstr "<a href=\"#compissues\">Problèmes de compilation</a>"

#. type: Content of: <dl><ul><li>
#: complete.html:520
msgid ""
"<a href=\"#gtk-2_0\">I'm getting errors building a package that requires GTK+"
",but I've installed GTK+ 2.x.</a>"
msgstr ""
"<a href=\"#gtk-2_0\">Je rencontre une erreur en construisant un paquet "
"demandant GTK+, mais j'ai installé GTK+ 2.x</a>"

#. type: Content of: <dl><ul><li>
#: complete.html:521
msgid "<a href=\"#undefined-deflate\">undefined reference to `deflate'</a>"
msgstr "<a href=\"#undefined-deflate\">référence indéfini à \"deflate\"</a>"

#. type: Content of: <dl><ul><li>
#: complete.html:522
msgid ""
"<a href=\"#missing-x-includes\">X11/Xlib.h: No such file or directory</a>"
msgstr ""
"<a href=\"#missing-x-includes\">X11/Xlib.h&nbsp;: No such file or "
"directory</a>"

#. type: Content of: <dl><ul><li>
#: complete.html:523
msgid "<a href=\"#gnome-versions\">Any error while building part of Gnome</a>"
msgstr ""
"<a href=\"#gnome-versions\">Toute erreur lors de la construction d'une "
"partie de Gnome</a>"

#. type: Content of: <dl><ul><li>
#: complete.html:524
msgid ""
"<a href=\"#xfree-missing-seperator\">XFree86: Makefile.proto:32: *** missing "
"separator</a>"
msgstr ""
"<a href=\"#xfree-missing-seperator\">XFree86: Makefile.proto:32: *** missing "
"separator</a>"

#. type: Content of: <dl><h3>
#: complete.html:526
msgid "<a href=\"#confissues\">Configuration issues</a>"
msgstr "<a href=\"#confissues\">Problèmes de configuration</a>"

#. type: Content of: <dl><ul><li>
#: complete.html:528
msgid "<a href=\"#how-to-print\">How do I print?</a>"
msgstr "<a href=\"#how-to-print\">Comment faire pour imprimer?</a>"

#. type: Content of: <dl><ul><li>
#: complete.html:529
msgid "<a href=\"#konsole-ps1\">How do I set PS1 in Konsole?</a>"
msgstr ""
"<a href=\"#konsole-ps1\">Comment puis-je initialiser PS1 dans Konsole?</a>"

#. type: Content of: <dl><h3>
#: complete.html:533
msgid "General BLFS questions"
msgstr "Questions générales de BLFS"

#. type: Content of: <dl><dl><dt>
#: complete.html:535
msgid "How do I make a bootable CD?"
msgstr "Comment faire un CD bootable?"

#. type: Content of: <dl><dl><dd><p>
#: complete.html:537
msgid ""
"The <a href=\"/livecd/index.html\">LFS LiveCD</a> Project has already done "
"the dirty work! The project has a <a href=\"/livecd/documentation.html\">"
"documentation page</a>. Information about how to obtain the project's "
"makefiles, scripts and configurations are available on the <a href=\""
"/livecd/download.html\">download page</a>."
msgstr ""
"Le projet <a href=\"/livecd/index.html\">LFS LiveCD</a> à déjà fait le plus "
"gros du travail! Le projet a une <a href=\"/livecd/documentation.html\">page "
"de documentation</a>. Des informations sur comment faire pour obtenir les "
"makefiles du projet, les scripts et les configurations sont disponibles sur "
"la <a href=\"/livecd/download.html\">page téléchargement</a>."

#. type: Content of: <dl><dl><dd><p>
#: complete.html:538
msgid ""
"If that doesn't interest you, there are several <a href=\""
"/hints/downloads/files/\">hints</a> related to boot CD's."
msgstr ""
"Si cela ne vous intéresse pas, il y a plusieurs <a href=\""
"/hints/downloads/files/\">astuces</a> relatives aux CD bootables. "

#. type: Content of: <dl><dl><dt>
#: complete.html:540
msgid "Where do I join the LFS SETI/Predictor/etc team?"
msgstr "Où puis-je joindre l'équipe LFS SETI/Predictor/etc&nbsp;?"

#. type: Content of: <dl><dl><dd><p>
#: complete.html:542
msgid ""
"Einstein@Home: <a href=\""
"http://einstein.phys.uwm.edu/create_account_form.php?teamid=3584\">Join Team "
"LFS</a>"
msgstr ""
"Einstein@Home: <a href=\""
"http://einstein.phys.uwm.edu/create_account_form.php?teamid=3584\">Joindre "
"l'équipe LFS</a>"

#. type: Content of: <dl><dl><dd><p>
#: complete.html:543
msgid ""
"LHC@Home: <a href=\""
"http://lhcathomeclassic.cern.ch/sixtrack/team_display.php?teamid=4461\">Team "
"LFS Page</a>"
msgstr ""
"LHC@Home: <a href=\""
"http://lhcathomeclassic.cern.ch/sixtrack/team_display.php?teamid=4461\">Page "
"de l'équipe LFS</a>"

#. type: Content of: <dl><p>
#: complete.html:546
#: complete.html:603
msgid "<a href=\"#blfsfaq\">Back to the top.</a>"
msgstr "<a href=\"#blfsfaq\">Retour au debut.</a>"

#. type: Content of: <dl><h3>
#: complete.html:548
msgid "Compilation issues"
msgstr "Problèmes de compilation"

#. type: Content of: <dl><dl><dt>
#: complete.html:550
msgid ""
"I'm getting errors building a package that requires GTK+, but I've installed "
"GTK+ 2.x."
msgstr ""
"Je rencontre une erreur en construisant un paquet demandant GTK+, mais j'ai "
"installéGTK+ 2.x."

#. type: Content of: <dl><dl><dd><p>
#: complete.html:552
msgid ""
"GTK+ 2.x and 1.2.x aren't compatible. The package you're installing may need "
"GTK+ (and GLIB) 1.2.x. You can install GTK+ (and GLIB) 1.2.x next to 2.x."
msgstr ""
"GTK+ 2.x et 1.2.x ne sont pas compatible. Le paquet que vous installez doit "
"demander GTK+ (et GLIB) 1.2.x. Vous pouvez installer GTL+ (et GLIB) 1.2.x à "
"coté de 2.x."

#. type: Content of: <dl><dl><dt>
#: complete.html:554
msgid "undefined reference to `deflate'"
msgstr "référence indéfini à \"deflate\""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:556
msgid ""
"If, when compiling XFree86, ghostscript, or anything else that uses libpng, "
"you get an error including the following line:<code>/usr/lib/gcc-lib/i686-pc-"
"linux-gnu/3.2/../../../libpng.so: undefined reference to `deflate'</code>."
msgstr ""
"Si, pendant la compilation de XFree86, ghostscript, ou n'importe quoi "
"utilisant libpng, vous avec une erreur donnant la ligne "
"suivante&nbsp;:<code>/usr/lib/gcc-lib/i686-pc-linux-"
"gnu/3.2/../../../libpng.so: undefined reference to `deflate'</code>."

#. type: Content of: <dl><dl><dd><p>
#: complete.html:557
msgid ""
"Then rebuild libpng with the patch at <a href=\""
"http://linuxfromscratch.org/%7Esklein/libpng-1.2.5-lz.patch\""
">http://linuxfromscratch.org/~sklein/libpng-1.2.5-lz.patch</a>.  Make sure "
"you apply the patch immediately after unpacking the sources. Like this:"
msgstr ""
"Ensuite reconstruisez libpng avec le correctif <a href=\""
"http://linuxfromscratch.org/%7Esklein/libpng-1.2.5-lz.patch\""
">http://linuxfromscratch.org/~sklein/libpng-1.2.5-lz.patch</a>. Assurez-vous "
"d'appliquer le correctif immédiatement après avoir désarchivé les sources. "
"Comme ceci&nbsp;:"

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:559
msgid "tar --no-same-owner -xvjf libpng-1.2.5.tar.bz2"
msgstr "tar --no-same-owner -xvjf libpng-1.2.5.tar.bz2"

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:560
msgid "cd libpng-1.2.5"
msgstr "cd libpng-1.2.5"

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:561
msgid "cat ../libpng-1.2.5-lz.patch | patch -p0"
msgstr "cat ../libpng-1.2.5-lz.patch | patch -p0"

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:562
msgid "ln -s scripts/makefile.linux Makefile"
msgstr "ln -s scripts/makefile.linux Makefile"

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:563
msgid "make ZLIBLIB=/lib ZLIBINC=/usr/include"
msgstr "make ZLIBLIB=/lib ZLIBINC=/usr/include"

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:564
msgid "make ZLIBLIB=/lib ZLIBINC=/usr/include install"
msgstr "make ZLIBLIB=/lib ZLIBINC=/usr/include install"

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:565
msgid "cd .."
msgstr "cd .."

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:566
msgid "rm -r libpng-1.2.5"
msgstr "rm -r libpng-1.2.5"

#. type: Content of: <dl><dl><dd><p>
#: complete.html:568
msgid ""
"Needless to say, if you originally put zlib in /usr/local or did something "
"else different, you'll have to adjust those instructions accordingly."
msgstr ""
"Inutile de le dire, si vous avez mis zlib dans /usr/local au départ ou avez "
"fait quelque chose de différent, vous devrez ajuster ces instructions en "
"fonction."

#. type: Content of: <dl><dl><dt>
#: complete.html:570
msgid "X11/Xlib.h: No such file or directory"
msgstr "X11/Xlib.h: No such file or directory"

#. type: Content of: <dl><dl><dd><p>
#: complete.html:572
#: complete.html:1098
msgid "Typical symptoms look like this:"
msgstr "Les symptômes typiques ressemblent à ceci&nbsp;:"

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:574
msgid ""
"$ echo -en 'x11:\\n"
"\\tgcc x11.c\\n"
"' &gt; Makefile"
msgstr ""
"$ echo -en 'x11:\\n"
"\\tgcc x11.c\\n"
"' &gt; Makefile"

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:575
msgid ""
"$ echo -en '#include &lt;X11/Xlib.h&gt;\\n"
"main() { }\\n"
"' &gt; x11.c"
msgstr ""
"$ echo -en '#include &lt;X11/Xlib.h&gt;\\n"
"main() { }\\n"
"' &gt; x11.c"

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:576
msgid "$ make"
msgstr "$ make"

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:577
msgid "gcc x11.c"
msgstr "gcc x11.c"

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:578
msgid "<strong>x11.c:1: X11/Xlib.h: No such file or directory</strong>"
msgstr "<strong>x11.c:1: X11/Xlib.h: No such file or directory</strong>"

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:579
msgid "<strong>make: *** [x11] Error 1</strong>"
msgstr "<strong>make: *** [x11] Error 1</strong>"

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:580
msgid "$ rm Makefile x11.c"
msgstr "$ rm Makefile x11.c"

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:581
msgid "$"
msgstr "$"

#. type: Content of: <dl><dl><dd><p>
#: complete.html:583
msgid "Creating a couple symlinks will fix it. Here are the commands:"
msgstr ""
"La création de liens symboliques corrigera le problème. Il y a les commandes "
"&nbsp;: "

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:585
msgid "cd /usr"
msgstr "cd /usr"

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:586
msgid "ln -s X11R6 X11"
msgstr "ln -s X11R6 X11"

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:587
msgid "cd include"
msgstr "cd include"

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:588
msgid "ln -s ../X11/include/X11 X11"
msgstr "ln -s ../X11/include/X11 X11"

#. type: Content of: <dl><dl><dt>
#: complete.html:591
msgid "Any error while building part of Gnome"
msgstr "N'importe quelle erreur en construisant une partie de Gnome"

#. type: Content of: <dl><dl><dd><p>
#: complete.html:593
msgid ""
"Using the latest version of every Gnome package doesn't work. You have to "
"use versions that are known to work together and are used in the BLFS book."
msgstr ""
"Utiliser la dernière version de chaque paquet Gnome ne fonctionne pas. Vous "
"devez utiliser les versions qui sont connues pour fonctionner ensemble et "
"sont utilisées dans le livre BLFS."

#. type: Content of: <dl><dl><dd><p>
#: complete.html:594
msgid ""
"To find a list of such versions go to <a href=\""
"http://ftp.gnome.org/pub/GNOME/desktop/\""
">http://ftp.gnome.org/pub/GNOME/desktop/</a>, drill down to the version "
"which is mentioned in BLFS and use those."
msgstr ""
"Pour trouver une liste de ces versions rendez-vous sur <a href=\""
"http://ftp.gnome.org/pub/GNOME/desktop/\""
">http://ftp.gnome.org/pub/GNOME/desktop/</a>, descendez jusqu'à la version "
"mentionnée dans BLFS et utilisez-la."

#. type: Content of: <dl><dl><dt>
#: complete.html:596
msgid "XFree86: Makefile.proto:32: *** missing separator"
msgstr "XFree86: Makefile.proto:32: *** missing separator"

#. type: Content of: <dl><dl><dd><p>
#: complete.html:598
msgid "If you get the following error while building XFree86:"
msgstr "Si vous avez l'erreur suivante en construisant XFree86&nbsp;:"

#. type: Content of: <dl><dl><dd><p>
#: complete.html:599
msgid "<code>Makefile.proto:32: *** missing separator. Stop.</code>"
msgstr "<code>Makefile.proto:32: *** missing separator. Stop.</code>"

#. type: Content of: <dl><dl><dd><p>
#: complete.html:600
msgid ""
"Or something which resembles that, you've probably made a mistake in your "
"host.def. Check the file carefully for errors and try recreating it by "
"copying the example in BLFS."
msgstr ""
"Ou quelque chose qui ressemble à ça, vous avez sans doute fait une erreur "
"dans votre fichier host.def. Vérifiez le fichier consciencieusement et "
"essayez de le recréer en copiant les exemples dans BLFS."

#. type: Content of: <dl><h3>
#: complete.html:605
msgid "Configuration issues"
msgstr "Problèmesde configuration"

#. type: Content of: <dl><dl><dt>
#: complete.html:607
msgid "How do I print?"
msgstr "Comment imprimer?"

#. type: Content of: <dl><dl><dd><p>
#: complete.html:609
msgid ""
"See <a href=\"/hints/downloads/files/\">one of the various printing hints</a>"
msgstr ""
"Voir <a href=\"/hints/downloads/files/\">l'une des astuces sur "
"l'impression</a>"

#. type: Content of: <dl><dl><dd><p>
#: complete.html:610
msgid ""
"Before you try any of the advanced printer daemons (for example CUPS) make "
"sure your printer works by following the <a href=\""
"/hints/downloads/files/pfs.txt\">Printing From Scratch hint</a>. For most "
"people, this hint is all that is required to setup basic printing."
msgstr ""
"Avant d'essayer les démons d'impression avancés (par exemple CUPS), assurez-"
"vous que votre imprimante fonctionne en suivant l'astuce <a href=\""
"/hints/downloads/files/pfs.txt\">Imprimer de zéro</a>. Pour la plupart des "
"gens, cette astuce est tout ce dont ils ont besoin pour une configuration "
"basique."

#. type: Content of: <dl><dl><dd><p>
#: complete.html:611
msgid ""
"When reporting problems with CUPS, please indicate whether the following "
"commands work:"
msgstr ""
"Lorsque vous rapportez des problèmes avec CUPS, merci d'indiquer si les "
"commandes suivantes fonctionnent&nbsp;:"

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:613
msgid "# This is an image, so ghostscript is not called"
msgstr "# Ceci est une image, donc ghostscript n'est pas appelé"

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:614
msgid "lpr -o ppi=100 /usr/share/doc/cups/images/cups-block-diagram.gif"
msgstr "lpr -o ppi=100 /usr/share/doc/cups/images/cups-block-diagram.gif"

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:615
msgid "# This PostScript file doesn't use any fonts"
msgstr "# Ce fichier PostScript n'utilise aucune police de caractères"

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:616
msgid "lpr /usr/share/ghostscript/&lt;version&gt;/examples/tiger.ps"
msgstr "lpr /usr/share/ghostscript/&lt;version&gt;/examples/tiger.ps"

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:617
msgid "# This PostScript file uses fonts"
msgstr "# Ce fichier PostScript utilise des polices de caractères"

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:618
msgid "lpr /usr/share/ghostscript/&lt;version&gt;/examples/alphabet.ps"
msgstr "lpr /usr/share/ghostscript/&lt;version&gt;/examples/alphabet.ps"

#. type: Content of: <dl><dl><dt>
#: complete.html:621
msgid "How do I set PS1 in Konsole?"
msgstr "Comment initialiser PS1 dans Konsole?"

#. type: Content of: <dl><dl><dd><p>
#: complete.html:623
msgid ""
"Follow the instructions on the <a href=\"/blfs/view/svn/postlfs/profile."
"html\">BLFS Bash Shell Startup Files</a> to properly setup your enviroment."
msgstr ""
"Suivez les instructions sur <a href=\"/view/bsvn/postlfs/profile.html\">Les "
"fichiers de démarrage du shell Bash</a> pour configurer correctement votre "
"environnement."

#. type: Content of: <dl><dl><dd><p>
#: complete.html:624
msgid "Alternatively, you can try the following solutions:"
msgstr "Autrement, vous pouvez essayer les solutions suivantes&nbsp;:"

#. type: Content of: <dl><dl><dd><p>
#: complete.html:625
msgid "Start konsole as a login shell:"
msgstr "Démarrez konsole en tant que shell de connexion&nbsp;:"

#. type: Content of: <dl><dl><dd><p>
#: complete.html:626
msgid "<code>konsole --ls</code>"
msgstr "<code>konsole --ls</code>"

#. type: Content of: <dl><dl><dd><p>
#: complete.html:627
msgid ""
"Change the session in Konsole to start <code>/bin/bash --login</code> "
"instead of <code>/bin/bash</code>."
msgstr ""
"Changez la session dans Konsole pour démarrer <code>/bin/bash --login</code> "
"au lieu de <code>/bin/bash</code>."

#. type: Content of: <h1>
#: faq-en.html:2
msgid "LFS Frequently Asked Questions"
msgstr "Foire Aux Questions"

#. type: Content of: <h3>
#: faq-en.html:9
msgid "<a href=\"#fre\">Frequently Requested Enhancements</a>"
msgstr "<a href=\"#fre\">Améliorations fréquemment demandées</a>"

#. type: Content of: <ul><li>
#: faq-en.html:11
msgid "<a href=\"#add-grub\">Why not use LILO instead of GRUB?</a>"
msgstr ""
"<a href=\"#add-grub\">Pourquoi ne pas utiliser LILO plutôt que GRUB ?</a>"

#. type: Content of: <ul><li>
#: faq-en.html:12
msgid ""
"<a href=\"#why-not-new-lilo\">Why not upgrade LILO to the latest version?</a>"
msgstr ""
"<a href=\"#why-not-new-lilo\">Pourquoi ne pas mettre à jour LILO à la "
"dernière version&nbsp;?</a>"

#. type: Content of: <ul><li>
#: faq-en.html:13
msgid "<a href=\"#why-not-faq\">Why not include the FAQ in the book?</a>"
msgstr ""
"<a href=\"#why-not-faq\">Pourquoi ne pas inclure la FAQ au livre&nbsp;?</a>"

#. type: Content of: <ul><li>
#: faq-en.html:14
msgid "<a href=\"#why-vim\">Why is vim in the book?</a>"
msgstr ""
"<a href=\"#why-vim\">Pourquoi est-ce que Vim est dans le livre&nbsp;?</a>"

#. type: Content of: <ul><li>
#: faq-en.html:15
msgid "<a href=\"#hjl-binutils\">Why is HJL's Binutils not in the book?</a>"
msgstr ""
"<a href=\"#hjl-binutils\">Pourquoi est-ce que la version HJL de Binutils "
"n'est pas dans le livre&nbsp;?</a>"

#. type: Content of: <ul><li>
#: faq-en.html:16
msgid ""
"<a href=\"#why-not-package-management\">Why isn't some package manager in "
"the book?</a>"
msgstr ""
"<a href=\"#why-not-package-management\">Pourquoi n'y a-t'il pas de "
"gestionnaire de paquets dans le livre&nbsp;?</a>"

#. type: Content of: <ul><li>
#: faq-en.html:17
msgid ""
"<a href=\"#no-poweroff\">How do I make my machine poweroff when shut "
"down?</a>"
msgstr ""
"<a href=\"#no-poweroff\">Comment provoquer l'arrêt électrique de la machine "
"à la sortie du système&nbsp;?</a>"

#. type: Content of: <h3>
#: faq-en.html:19
msgid "<a href=\"#resources\">When reading and building LFS</a>"
msgstr "<a href=\"#resources\">Pendant la lecture et la construction de LFS</a>"

#. type: Content of: <ul><li>
#: faq-en.html:21
msgid ""
"<a href=\"#what-dist\">What distribution should I use to start from?</a>"
msgstr ""
"<a href=\"#what-dist\">Quelle distribution devrais-je utiliser, pour "
"démarrer&nbsp;?</a>"

#. type: Content of: <ul><li>
#: faq-en.html:22
msgid ""
"<a href=\"#kernel-modules\">How do I compile a kernel or set up modules?</a>"
msgstr ""
"<a href=\"#kernel-modules\">Comment compiler un noyau ou configurer un "
"module&nbsp;?</a>"

#. type: Content of: <ul><li>
#: faq-en.html:23
msgid "<a href=\"#gcc-warnings\">Are compiler warnings from GCC bad?</a>"
msgstr ""
"<a href=\"#gcc-warnings\">Est-ce que c'est mal, les avertissements de "
"compilation de Gcc&nbsp;?</a>"

#. type: Content of: <ul><li>
#: faq-en.html:24
msgid ""
"<a href=\"#dirty-sources\">Do I need to keep the source after installing?</a>"
msgstr ""
"<a href=\"#dirty-sources\">Dois-je conserver les sources après "
"l'installation&nbsp;?</a>"

#. type: Content of: <ul><li>
#: faq-en.html:25
msgid ""
"<a href=\"#really-small\">How do I make that really small install the book "
"mentions?</a>"
msgstr ""
"<a href=\"#really-small\">Comment puis-je procéder à cette toute petite "
"installation dont parle le livre&nbsp;?</a>"

#. type: Content of: <ul><li>
#: faq-en.html:26
msgid ""
"<a href=\"#procs-lfs\">Is there information about building LFS on other "
"processors?</a>"
msgstr ""
"<a href=\"#procs-lfs\">Existe-t'il des informations sur la façon de "
"construire LFS sur d'autres architectures&nbsp;?</a>"

#. type: Content of: <ul><li>
#: faq-en.html:27
msgid "<a href=\"#cross-compile\">How do I cross compile LFS?</a>"
msgstr ""
"<a href=\"#cross-compile\">Comment faire une compilation croisée avec "
"LFS&nbsp;?</a>"

#. type: Content of: <ul><li>
#: faq-en.html:28
msgid "<a href=\"#dos-text\">What's a DOS format text file?</a>"
msgstr ""
"<a href=\"#dos-text\">Qu'est qu'un fichier texte au format DOS&nbsp;?</a>"

#. type: Content of: <ul><li>
#: faq-en.html:29
msgid ""
"<a href=\"#wget\">Is there a way to download all current files at one "
"time?</a>"
msgstr ""
"<a href=\"#wget\">Y a-t-il moyen de télécharger tous les fichiers actuels en "
"une seule fois&nbsp;?</a>"

#. type: Content of: <h3>
#: faq-en.html:31
msgid "<a href=\"#generrors\">General compilation errors</a>"
msgstr "<a href=\"#generrors\">Erreurs de compilation usuelles</a>"

#. type: Content of: <ul><li>
#: faq-en.html:33
msgid ""
"<a href=\"#gnu-patches\">I used a patch from GNU to upgrade. Is that OK?</a>"
msgstr ""
"<a href=\"#gnu-patches\">J'ai utilisé un patch provenant de GNU pour faire "
"des mises à jour&nbsp;? C'est bon&nbsp;?</a>"

#. type: Content of: <ul><li>
#: faq-en.html:34
msgid ""
"<a href=\"#optimizations\">When using optimization flags (setting CFLAGS)</a>"
msgstr ""
"<a href=\"#optimizations\">Utilisation des paramètres d'optimisation ("
"paramétrage des CFLAGS)</a>"

#. type: Content of: <ul><li>
#: faq-en.html:35
msgid ""
"<a href=\"#config-hang-size_t\">Why does configure hang at &quot;checking "
"for signed size_t type...&quot;?</a>"
msgstr ""
"<a href=\"#config-hang-size_t\">Pourquoi est-ce que configure se fige à "
"«&nbsp;checking for signed size_t type...&nbsp;»&nbsp;?</a>"

#. type: Content of: <ul><li>
#: faq-en.html:36
msgid ""
"<a href=\"#dirty-sources\">I didn't delete the source tree after my last "
"attempt. Do I need to?</a>"
msgstr ""
"<a href=\"#dirty-sources\">Je n'ai pas effacé l'arborescence des sources "
"après mon dernier essai. Faut-il le faire&nbsp;?</a>"

#. type: Content of: <ul><li>
#: faq-en.html:37
msgid "<a href=\"#perm-denied\">I'm getting `/dev/null: Permission denied'</a>"
msgstr ""
"<a href=\"#perm-denied\">J'obtiens le message «&nbsp;/dev/null: Permission "
"denied&nbsp;»</a>"

#. type: Content of: <ul><li>
#: faq-en.html:38
msgid "<a href=\"#sig11\">signal 11 (internal error: Segmentation fault)</a>"
msgstr "<a href=\"#sig11\">signal 11 (internal error: Segmentation fault)</a>"

#. type: Content of: <ul><li>
#: faq-en.html:39
msgid "<a href=\"#any-no-such-file\">No such file or directory</a>"
msgstr "<a href=\"#any-no-such-file\">No such file or directory</a>"

#. type: Content of: <ul><li>
#: faq-en.html:40
msgid ""
"<a href=\"#configure-no-such-file\">bash: ./configure: No such file or "
"directory</a>"
msgstr ""
"<a href=\"#configure-no-such-file\">bash: ./configure: No such file or "
"directory</a>"

#. type: Content of: <ul><li>
#: faq-en.html:41
msgid ""
"<a href=\"#bad-interpreter-permission-denied\">./configure: bad interpreter: "
"Permission denied</a>"
msgstr ""
"<a href=\"#bad-interpreter-permission-denied\">./configure: bad interpreter: "
"Permission denied</a>"

#. type: Content of: <ul><li>
#: faq-en.html:42
msgid "<a href=\"#conf-guess-fail\">configure can't guess my host type.</a>"
msgstr ""
"<a href=\"#conf-guess-fail\">configure n'arrive pas à déterminer le type de "
"mon hôte.</a>"

#. type: Content of: <ul><li>
#: faq-en.html:43
msgid ""
"<a href=\"#config-not-gnu-c\">checking whether we are using GNU C... no</a>"
msgstr ""
"<a href=\"#config-not-gnu-c\">checking whether we are using GNU C... no</a>"

#. type: Content of: <ul><li>
#: faq-en.html:44
msgid ""
"<a href=\"#no-ptys\">The system has no more ptys.  Ask your system "
"administrator to create more.</a>"
msgstr ""
"<a href=\"#no-ptys\">Le système n'a plus de ptys. Demandez à votre "
"administrateur d'en créer d'autres.</a>"

#. type: Content of: <h3>
#: faq-en.html:46
msgid "<a href=\"#packerrors\">Package-specific errors</a>"
msgstr "<a href=\"#packerrors\">Erreurs spécifiques à certains paquets</a>"

#. type: Content of: <ul><li>
#: faq-en.html:48
msgid ""
"<a href=\"#unknown-pseudo-op-hidden\">GCC: Error: Unknown pseudo-op: "
"`.hidden'</a>"
msgstr ""
"<a href=\"#unknown-pseudo-op-hidden\">GCC: Error: Unknown pseudo-op: "
"`.hidden'</a>"

#. type: Content of: <ul><li>
#: faq-en.html:49
msgid "<a href=\"#glibc-awk-fail\">Glibc fails and mentions BEGIN and END.</a>"
msgstr ""
"<a href=\"#glibc-awk-fail\">Glibc sort en erreur et évoque BEGIN et END.</a>"

#. type: Content of: <ul><li>
#: faq-en.html:50
msgid ""
"<a href=\"#glibc-nss\">Glibc compilation errors out due to a missing nss.h "
"header file</a>"
msgstr ""
"<a href=\"#glibc-nss\">La compilation de Glibc sort en erreur à cause de "
"l'absence de l'entête de fichier nss.h.</a>"

#. type: Content of: <ul><li>
#: faq-en.html:51
msgid ""
"<a href=\"#cpp-fails-sanity-check\">Ncurses: C++ preprocessor "
"&quot;/lib/cpp&quot; fails sanity check</a>"
msgstr ""
"<a href=\"#cpp-fails-sanity-check\">Ncurses: le préprocesseur C++ \"/lib/"
"cpp\" échoue lors de la vérification de conformité</a>"

#. type: Content of: <h3>
#: faq-en.html:53
msgid "<a href=\"#confboot\">Configuration and booting issues</a>"
msgstr "<a href=\"#confboot\">Problèmes de configuration et de démarrage</a>"

#. type: Content of: <ul><li>
#: faq-en.html:55
msgid ""
"<a href=\"#unable-to-mount-root\">Kernel panic: VFS: unable to mount root "
"fs</a>"
msgstr ""
"<a href=\"#unable-to-mount-root\">Kernel panic: VFS: unable to mount root "
"fs</a>"

#. type: Content of: <ul><li>
#: faq-en.html:56
msgid ""
"<a href=\"#respawning-too-fast\">init: Id &quot;1&quot; respawning too fast: "
"disabled for 5 minutes</a>"
msgstr ""
"<a href=\"#respawning-too-fast\">init: Id &quot;1&quot; respawning too fast: "
"disabled for 5 minutes</a>"

#. type: Content of: <ul><li>
#: faq-en.html:57
msgid ""
"<a href=\"#char-major-10-135\">modprobe: Can't locate module char-"
"major-10-135</a>"
msgstr ""
"<a href=\"#char-major-10-135\">modprobe: Can't locate module char-"
"major-10-135</a>"

#. type: Content of: <ul><li>
#: faq-en.html:58
msgid "<a href=\"#no-dev-rtc\">modprobe: Can't locate module /dev/rtc</a>"
msgstr "<a href=\"#no-dev-rtc\">modprobe: Can't locate module /dev/rtc</a>"

#. type: Content of: <ul><li>
#: faq-en.html:59
msgid "<a href=\"#eth0-unknown-interface\">eth0:unknown interface</a>"
msgstr "<a href=\"#eth0-unknown-interface\">eth0:unknown interface</a>"

#. type: Content of: <ul><li>
#: faq-en.html:60
msgid ""
"<a href=\"#spurious-8259A-interrupt\">spurious 8259A interrupt: IRQ14</a>"
msgstr ""
"<a href=\"#spurious-8259A-interrupt\">spurious 8259A interrupt: IRQ14</a>"

#. type: Content of: <ul><li>
#: faq-en.html:61
msgid ""
"<a href=\"#less-prints-ad\">Why does less (and therefore man) print "
"&lt;AD&gt; instead of hyphens?</a>"
msgstr ""
"<a href=\"#less-prints-ad\">Pourquoi est-ce que less (et par conséquent man) "
"affiche &lt;AD&gt; au lieu des tirets&nbsp;?</a>"

#. type: Content of: <h3>
#: faq-en.html:65
msgid "Frequently Requested Enhancements"
msgstr "Améliorations fréquemment demandées"

#. type: Content of: <dl><dl><dt>
#: complete.html:698
msgid "Why not use LILO instead of GRUB?"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:700
msgid ""
"Since LFS-5.0, released 5 November 2003, LFS uses Grub instead of Lilo. Grub "
"was chosen because it doesn't require reinstallation after a kernel upgrade "
"and has a very nice rescue console."
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:703
msgid ""
"If your current setup uses LILO or you'd like to use it anyway, you can, but "
"beware you will also need to install BIN86 and, for the latest LILO "
"versions, NASM. However, don't preach about it on the LFS mailinglists, "
"since we've had many flamewars about it in the past."
msgstr ""

#. type: Content of: <dl><dl><dt>
#: complete.html:709
msgid "Why not include the FAQ in the book?"
msgstr "Pourquoi ne pas inclure la FAQ dans le livre ?"

#. type: Content of: <dl><dl><dd><p>
#: complete.html:711
msgid "Marc Heerdink may have said it best in a post to lfs-dev:"
msgstr ""

#. type: Content of: <dl><dl><dd><blockquote><p>
#: complete.html:712
msgid ""
"The problem is that the FAQ is a dynamic document. The FAQ for a book "
"release is released only after the book version itself, because the FAQ is "
"updated to reflect the Qs asked about the current version of the book. A "
"link is better, since you'll always have the most up-to-date answers handy."
msgstr ""

#. type: Content of: <dl><dl><dt>
#: complete.html:718
msgid "Why is vim in the book?"
msgstr "Pourquoi vim est dans le livre ?"

#. type: Content of: <dl><dl><dd><p>
#: complete.html:720
msgid ""
"This is fairly well discussed in the thread starting at <a href=\""
"http://linuxfromscratch.org/pipermail/lfs-dev/2002-February/023030.html\""
">http://linuxfromscratch.org/pipermail/lfs-dev/2002-February/023030.html</a>."
msgstr ""

#. type: Content of: <dl><dl><dt>
#: complete.html:723
msgid "Why is HJL's Binutils not in the book?"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:725
msgid ""
"The binutils release that you typically find on ftp.gnu.org is commonly "
"known as the &quot;FSF&quot; binutils. Noted hacker H.J. Lu also makes "
"releases out of the main CVS repository and these are commonly known as the "
"&quot;HJL&quot; binutils and can usually be found on ftp.kernel.org. Debate "
"often arises over which version to use due to the fact that most mainstream "
"distros tend to use the HJL releases even though they are typically marked "
"as &quot;beta&quot;."
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:733
msgid "Here is our interpretation of the differences between the two:"
msgstr ""

#. type: Content of: <dl><dl><dd><h4>
#: complete.html:734
msgid "HJL:"
msgstr "HJL&nbsp;:"

#. type: Content of: <dl><dl><dd><ul><li>
#: complete.html:736
msgid "For Linux OS only"
msgstr "Pour les OS linux seulement"

#. type: Content of: <dl><dl><dd><ul><li>
#: complete.html:737
msgid "Marked as &quot;beta&quot;"
msgstr "Marqué comme &quot;beta&quot;"

#. type: Content of: <dl><dl><dd><ul><li>
#: complete.html:738
msgid "Closely follows the CVS HEAD"
msgstr ""

#. type: Content of: <dl><dl><dd><ul><li>
#: complete.html:739
msgid "Usually contains the latest subtle bug fixes"
msgstr ""

#. type: Content of: <dl><dl><dd><ul><li>
#: complete.html:740
msgid "Usually has latest bug fixes for non-x86 arch's"
msgstr ""

#. type: Content of: <dl><dl><dd><ul><li>
#: complete.html:741
msgid ""
"Usually a new release every time a significant bug that affects Linux gets "
"fixed"
msgstr ""

#. type: Content of: <dl><dl><dd><ul><li>
#: complete.html:742
msgid "Theoretically less stable due to newness of code"
msgstr ""

#. type: Content of: <dl><dl><dd><h4>
#: complete.html:744
msgid "FSF:"
msgstr ""

#. type: Content of: <dl><dl><dd><ul><li>
#: complete.html:746
msgid "Supports more OS's (not only Linux)"
msgstr ""

#. type: Content of: <dl><dl><dd><ul><li>
#: complete.html:747
msgid "Latest code from the stable branch of CVS"
msgstr ""

#. type: Content of: <dl><dl><dd><ul><li>
#: complete.html:748
msgid ""
"Sometimes not up-to-date WRT to the latest bleeding edge kernel, gcc and "
"glibc subtleties"
msgstr ""

#. type: Content of: <dl><dl><dd><ul><li>
#: complete.html:749
msgid ""
"Often includes features backported from the CVS HEAD after a period of "
"testing"
msgstr ""

#. type: Content of: <dl><dl><dd><ul><li>
#: complete.html:750
msgid "Theoretically more stable"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:752
msgid ""
"You'll notice in the above points words like &quot;usually&quot; and "
"&quot;sometimes&quot;. This demonstrates how the situation can be different "
"depending on which particular point in time you happen to be referring to. "
"For example, from time to time there will be a new bleeding edge feature in "
"gcc or glibc that requires support from binutils. During these times you "
"will often hear the developers say &quot;you must be using the latest HJL "
"binutils version x.y.z.a.b&quot;."
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:760
msgid ""
"The only way to correctly choose the most appropriate release to use is to:-"
msgstr ""

#. type: Content of: <dl><dl><dd><ul><li>
#: complete.html:762
msgid ""
"Stay abreast of the issues on the project mailing lists of the core "
"toolchain packages"
msgstr ""

#. type: Content of: <dl><dl><dd><ul><li>
#: complete.html:763
msgid ""
"Have a large dose of technical prowess and/or programming talent to "
"understand all the issues"
msgstr ""

#. type: Content of: <dl><dl><dd><ul><li>
#: complete.html:764
msgid "Test like crazy by running the test suites"
msgstr ""

#. type: Content of: <dl><dl><dd><ul><li>
#: complete.html:765
msgid "Test like crazy by building full systems"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:767
msgid ""
"The facts of the matter are that the core toolchain packages are all very "
"tightly bound and must be tested to ensure they work together. You basically "
"have to build a full working distro and test every aspect of it to be fully "
"satisfied."
msgstr ""

#. type: Content of: <dl><dl><dt>
#: complete.html:780
msgid "Why isn't some package manager in the book?"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:771
msgid ""
"If you follow the project mailing lists of the core toolchain packages for "
"long enough, you'll soon realise that the developers do not care much "
"whether a particular release of &quot;Package A&quot; works with a "
"particular release of &quot;Package B&quot;. In other words, release "
"coordination between the projects is not a priority.  In reality, this means "
"that Alan Cox is right when he says that you cannot just go to ftp.gnu.org "
"and grab the latest of everything and always expect it to just work."
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:782
msgid ""
"Package management - beyond that provided by tarballs and makefiles - is "
"beyond the scope of the book. If nothing else does, the number of different "
"\"solutions\" should hint at some of the reasons."
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:786
msgid "Here are a few of the options:"
msgstr ""

#. type: Content of: <dl><dl><dd><ul><li>
#: complete.html:788
msgid ""
"No package management is really necessary. Unless it is desirable to monitor "
"package file placement minutely, any package large enough to warrent removal "
"for disk space reasons can be installed in /opt as detailed by the FHS ("
"perhaps in /opt/foo-x.x with a link from /opt/foo), and new releases can "
"usually be installed over the old, although major upgrades and libraries are "
"generally best done by rebuilding the system from the bottom up."
msgstr ""

#. type: Content of: <dl><dl><dd><ul><li>
#: complete.html:796
msgid ""
"RPM, the Redhat Package Manager, is used by a number of distributions. It is "
"available from <a href=\"http://www.rpm.org/\">http://www.rpm.org/</a>, and "
"there is an <a href=\"../hints/downloads/files/\">RPM Hint</a> to help with "
"installation."
msgstr ""

#. type: Content of: <dl><dl><dd><ul><li>
#: complete.html:801
msgid "There are several implementations of symlink style package management:"
msgstr ""

#. type: Content of: <dl><dl><dd><ul><li><ul><li>
#: complete.html:803
msgid ""
"Epkg is available from <a href=\"http://www.encap.org/epkg/\""
">http://www.encap.org/epkg/</a>."
msgstr ""

#. type: Content of: <dl><dl><dd><ul><li><ul><li>
#: complete.html:804
msgid ""
"Graft is available from <a href=\"http://peters.gormand.com.au/Home/tools\" "
">http://peters.gormand.com.au/Home/tools</a>."
msgstr ""

#. type: Content of: <dl><dl><dd><ul><li><ul><li>
#: complete.html:805
msgid ""
"GNU Stow is available from <a href=\"http://www.gnu.org/software/stow/\""
">http://www.gnu.org/software/stow/</a>."
msgstr ""

#. type: Content of: <dl><dl><dd><ul><li><ul><li>
#: complete.html:806
msgid ""
"And several more are listed in the Graft documentation at <a href=\""
"http://peters.gormand.com.au/Home/tools/graft/graft-html#research\""
">http://peters.gormand.com.au/Home/tools/graft/graft-html#research</a>."
msgstr ""

#. type: Content of: <dl><dl><dd><ul><li>
#: complete.html:810
msgid ""
"The NetBSD package manager, pkgsrc, is available on other systems including "
"Linux. It is at <a href=\"ftp://ftp.netbsd.org/pub/pkgsrc/stable/\""
">ftp://ftp.netbsd.org/pub/pkgsrc/stable/</a>."
msgstr ""

#. type: Content of: <dl><dl><dd><ul><li>
#: complete.html:813
msgid ""
"Originally based on a script written by LFS' own Gerard Beekmans, install-"
"log records a list of files installed by a package as the package is "
"installed. It is available from <a href=\"http://install-log.sourceforge.net/"
"\">http://install-log.sourceforge.net/</a>."
msgstr ""

#. type: Content of: <dl><dl><dd><ul><li>
#: complete.html:817
msgid ""
"Gerard has since made additions to his script. It is available from <a href="
"\"http://linuxfromscratch.org/~gerard/log-install\""
">http://linuxfromscratch.org/~gerard/log-install</a>."
msgstr ""

#. type: Content of: <dl><dl><dd><ul><li>
#: complete.html:820
msgid ""
"CheckInstall attempts log system calls made by \"make install\".  It is "
"available from <a href=\"http://asic-linux.com.mx/%7Eizto/checkinstall/\""
">http://asic-linux.com.mx/~izto/checkinstall/</a>."
msgstr ""

#. type: Content of: <dl><dl><dd><ul><li>
#: complete.html:823
msgid ""
"pkgutils, used by the CRUX distribution, is available from <a href=\""
"http://www.fukt.bsnet.se/%7Eper/pkgutils/\""
">http://www.fukt.bsnet.se/~per/pkgutils/</a>."
msgstr ""

#. type: Content of: <dl><dl><dd><ul><li>
#: complete.html:825
msgid ""
"There are some <a href=\"../hints/downloads/files/\">hints</a> available for "
"package managers."
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:827
msgid ""
"If you have an addition to the list, please do email its id, URL, and other "
"information, to the FAQ maintainer or an appropriate LFS mailing list so it "
"can be added here."
msgstr ""

#. type: Content of: <dl><dl><dt>
#: complete.html:831
msgid "How do I make my machine poweroff when shut down?"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:833
msgid ""
"Power Management is a kernel function, you need to enable it in the kernel. "
"In the 2.4 kernel, you have to enable the options for <code>Power Management "
"Support</code> under <code>General Setup</code>. For older machines, you'll "
"probably want the APM options, newer machines often require ACPI. Make sure "
"that either APM or ACPI be enabled in the kernel, but definitely "
"<strong>not</strong> both at the same time - this has been known to cause "
"problems such as neither actually taking effect. Also try disabling SMP if "
"you only have one processor; it's also known to prevent a proper poweroff.  "
"Make sure you read the help with each option."
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:843
msgid ""
"After rebooting into the new kernel you should be able to poweroff your "
"machine with the command <code>shutdown -h now</code> or "
"<code>poweroff</code> (also read <code>man shutdown</code> and <code>man "
"halt</code>). If you compiled APM or ACPI as modules, make sure they are "
"loaded before you try to power off.  Some machines require that APM or ACPI "
"is compiled into the kernel because it needs to be initialised at boottime."
msgstr ""

#. type: Content of: <dl><p>
#: complete.html:852
#: complete.html:983
#: complete.html:1191
#: complete.html:1250
msgid "<a href=\"#lfsfaq\">Back to the top.</a>"
msgstr ""

#. type: Content of: <dl><h3>
#: complete.html:854
msgid "When reading and building LFS"
msgstr ""

#. type: Content of: <dl><dl><dt>
#: complete.html:856
msgid "What distribution should I use to start from?"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:858
msgid ""
"Most relatively recent distributions should be fine. Do not use Fedora Core "
"4 as its version of GCC does not work with the current stable version of "
"LFS. Make sure you have installed and/or updated the development packages. ("
"Look for ones starting in \"gcc\", \"glibc\", or \"libstdc++\" or ending in "
"\"-dev\".). If you want to use LFS as your main system and you wish to "
"install it without first installing a distribution, try <a href=\""
"http://www.knopper.net/knoppix/index-en.html\">Knoppix</a>."
msgstr ""

#. type: Content of: <dl><dl><dt>
#: complete.html:867
msgid "How do I compile a kernel or set up modules?"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:869
msgid ""
"In addition to the kernel documentation at <a href=\"file:///usr/src/linux/"
"Documentation\">/usr/src/linux/Documentation</a> or wherever you unpacked "
"your kernel source and the help in kernel config tool (make menuconfig), see "
"the Module-HOWTO at <a href=\"http://www.tldp.org/HOWTO/Module-HOWTO/\""
">http://www.tldp.org/HOWTO/Module-HOWTO/</a>."
msgstr ""

#. type: Content of: <dl><dl><dt>
#: complete.html:875
msgid "Are compiler warnings from GCC bad?"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:877
msgid "Short answer: no."
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:878
msgid ""
"Long answer: probably, but only to someone working on the package you're "
"trying to compile. Mostly, everything will be fine unless make quits with an "
"error."
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:881
msgid "Here's an example:"
msgstr ""

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:883
msgid "sk ~/tmp $ cat &gt; Makefile"
msgstr ""

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:884
msgid "main:"
msgstr ""

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:885
#: complete.html:889
#: complete.html:897
msgid "gcc main.c"
msgstr ""

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:886
#: complete.html:894
msgid "sk ~/tmp $ cat &gt; main.c"
msgstr ""

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:887
msgid "void main() { exit(0); }"
msgstr ""

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:888
#: complete.html:896
msgid "sk ~/tmp $ make"
msgstr ""

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:890
#: complete.html:898
msgid "<strong>main.c: In function `main':</strong>"
msgstr ""

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:891
msgid "<strong>main.c:1: warning: return type of `main' is not `int'</strong>"
msgstr ""

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:892
msgid "sk ~/tmp $ ######## that worked ########"
msgstr ""

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:893
#: complete.html:902
msgid "sk ~/tmp $"
msgstr ""

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:895
msgid "int main() { e<span class=\"strong\">xx</span>it(0) }"
msgstr ""

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:899
msgid "<strong>main.c:1: parse error before `}'</strong>"
msgstr ""

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:900
msgid "<strong>make: *** [main] Error 1</strong>"
msgstr ""

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:901
msgid "sk ~/tmp $ ######## that failed ########"
msgstr ""

#. type: Content of: <dl><dl><dt>
#: complete.html:905
msgid "How do I make that really small install the book mentions?"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:907
msgid ""
"Gerard describes the process of making a 5MB LFS install in <a href=\""
"http://linuxfromscratch.org/pipermail/lfs-support/2001-October/000202.html\">"
"an email to lfs-support</a>, and there are links to many resources in <a "
"href=\"http://linuxfromscratch.org/pipermail/lfs-support/2002-June/007255."
"html\">a post by Cor Lem</a> and a reply to it."
msgstr ""

#. type: Content of: <dl><dl><dt>
#: complete.html:914
msgid "Is there information about building LFS on other processors?"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:916
msgid ""
"For information about building LFS for a wide array of systems, take a look "
"at the <a href=\"http://trac.clfs.org/wiki/read\">Cross-LFS branch</a> of "
"LFS."
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:920
msgid ""
"For Alpha systems, Kelledin maintains a list of fixes for building on the "
"Alpha platform at <a href=\"http://skarpsey.dyndns.org/alpha-lfs/alpha.html\""
">http://skarpsey.dyndns.org/alpha-lfs/alpha.html</a>."
msgstr ""

#. type: Content of: <dl><dl><dt>
#: complete.html:924
msgid "How do I cross compile LFS?"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:926
msgid ""
"It's often useful to compile LFS for one machine on another machine. Say "
"using that fast 1Ghz Athlon to build an install for an old 486. While this "
"is technically not cross compiling, binaries compiled for the Athlon cannot "
"be run on the 486 because binaries compiled for the newer processor use "
"features the older processor doesn't have."
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:932
msgid ""
"The LFS book specifically for cross compiling is the <a href=\""
"http://trac.clfs.org/wiki/read\">Cross-LFS</a> book.  Another source of "
"information would be the <a href=\"/hints/downloads/files/\">cross-compiling "
"hint</a>."
msgstr ""

#. type: Content of: <dl><dl><dt>
#: complete.html:937
msgid "What's a DOS format text file?"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:939
msgid "It has to do with the characters used to end lines."
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:940
msgid "There are two that may be used:"
msgstr ""

#. type: Content of: <dl><dl><dd><ul><li>
#: complete.html:942
msgid ""
"Line Feed: (LF) Octal:012 Decimal:10 Hex:0A C Style Escape:'\\n"
"' Moves down one line."
msgstr ""

#. type: Content of: <dl><dl><dd><ul><li>
#: complete.html:943
msgid ""
"Carriage Return: (CR) Octal:015 Decimal:13 Hex:0D C Style Excape:'\\r' Move "
"to the left margin."
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:945
msgid ""
"Unix, DOS, and MacOS each use a different combination to end lines in text "
"files:"
msgstr ""

#. type: Content of: <dl><dl><dd><ul><li>
#: complete.html:947
msgid ""
"Unix: LF only. This is why when a Unix format text file is sent to a printer "
"raw, it prints out"
msgstr ""

#. type: Content of: <dl><dl><dd><ul><li>
#: complete.html:948
msgid "&nbsp;&nbsp;like"
msgstr ""

#. type: Content of: <dl><dl><dd><ul><li>
#: complete.html:949
msgid "&nbsp;&nbsp;&nbsp;&nbsp;stairs"
msgstr ""

#. type: Content of: <dl><dl><dd><ul><li>
#: complete.html:950
msgid "&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;steps."
msgstr ""

#. type: Content of: <dl><dl><dd><ul><li>
#: complete.html:951
msgid ""
"DOS: CRLF both. Which is why if you do \"cat -v\" on a DOS file you'll see a "
"\"^M\" (control m is carriage return) at the end of each line. And that is "
"why scripts don't work when written with Microsoft Notepad. The kernel looks "
"for \"/bin/sh^M\" which doesn't exist. There's a \"/bin/sh\", but nothing "
"with a \"^M\" appended."
msgstr ""

#. type: Content of: <dl><dl><dd><ul><li>
#: complete.html:956
msgid ""
"MacOs: CR only. Printers probably print every line atop the first, and Unix "
"tools think the whole file is one line with \"^M\" all through it."
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:960
msgid "To change DOS to Unix, use"
msgstr ""

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:962
msgid "cp &lt;fileid&gt; &lt;fileid&gt;.dos &amp;&amp;"
msgstr ""

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:963
msgid "cat &lt;fileid&gt;.dos | tr -d '\\r' &gt; &lt;fileid&gt;"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:965
msgid ""
"Or in <code>vim</code>, you can convert a file with <code>:set ff={unix, "
"dos, mac}</code>. Other conversions will probably require sed or a different "
"use of tr and are left as an exercise for the reader."
msgstr ""

#. type: Content of: <dl><dl><dt>
#: complete.html:972
msgid "Is there a way to download all current files at one time?"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:974
msgid ""
"Yes. You can download the file LFS-BOOK-x.y-wget-list <a href= \""
"http://www.linuxfromscratch.org/lfs/downloads/stable\"> "
"http://www.linuxfromscratch.org/lfs/downloads/stable</a>. To download all "
"the files, use the version of <code>wget</code> on your host distribution to "
"run:"
msgstr ""

#. type: Content of: <dl><dl><dd>
#: complete.html:979
msgid "<code>wget --input-file=LFS-BOOK-x.y-wget-list</code>"
msgstr ""

#. type: Content of: <dl><h3>
#: complete.html:985
msgid "General compilation errors"
msgstr ""

#. type: Content of: <dl><dl><dt>
#: complete.html:987
msgid "I used a patch from GNU to upgrade. Is that OK?"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:989
msgid ""
"Patches from GNU don't usually work. You can either download the full "
"archive and try again or try the solution given by Gerard Beekmans:"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:992
msgid ""
"The problem is that executable marked scripts are patched too and they then "
"lose the executable bit, so you can't execute those scripts anymore until "
"you run a \"chmod +x\" on them (or something similar, like chmod 755) before "
"installing Glibc. Try chmod +x glibc-2.2.5/scripts/* (not 100% sure about "
"the directory paths but it should be obvious where to do it when running an "
"'ls' on the glibc-2.2.5 directory)."
msgstr ""

#. type: Content of: <dl><dl><dt>
#: complete.html:1000
msgid "When using optimization flags (setting CFLAGS)"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1002
msgid ""
"If you're getting errors and you're setting CFLAGS or otherwise passing "
"optimization flags to the compiler that may be the problem."
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1005
msgid ""
"If you ask on the list and they can't figure it out immediately, they'll "
"likely suggest trying it without optimization. So if you just retry it "
"without before asking, you'll be one step ahead of them :)"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1009
msgid ""
"Of particular note is that optimizing binutils, gcc, or glibc may cause any "
"other package to fail to compile or run or to otherwise misbehave in strange "
"and mysterious ways. Also, optimization that works for someone else may not "
"work for you. Flags that used to work may mysteriously stop working. Even "
"some small innocent hardware change can make the difference."
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1015
msgid ""
"(If you don't know what optimization flags are, don't worry, you really "
"don't need to.)"
msgstr ""

#. type: Content of: <dl><dl><dt>
#: complete.html:1017
msgid "Why does configure hang at \"checking for signed size_t type...\"?"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1019
msgid "You over optimized gcc."
msgstr ""

#. type: Content of: <dl><dl><dt>
#: complete.html:1021
msgid "I didn't delete the source tree after my last attempt. Do I need to?"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1023
msgid ""
"Yes. In general <code>make clean</code> or <code>make dist-clean</code> "
"can't be relied upon for clean sources. Especially when you have manually "
"hacked the sources or applied patches to it you should first try again with "
"a fresh unpacked package. The only exception to this rule is the linux "
"kernel, which requires its sources to be present when third-party modules, "
"such as the NVidia drivers, are needed."
msgstr ""

#. type: Content of: <dl><dl><dt>
#: complete.html:1031
msgid "I'm getting `/dev/null: Permission denied'"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1033
msgid "Does /dev/null look like this:"
msgstr ""

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:1035
msgid "$ ls -l /dev/null"
msgstr ""

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:1036
msgid "crw-rw-rw- 1 root root 1, 3 Aug 3 2000 /dev/null"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1038
msgid ""
"If not, it should. See the chmod(1), chown(1), and mknod(1) man pages and "
"/usr/src/linux/Documentation/devices.txt if you need help fixing it."
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1041
msgid ""
"If it does look right, the problem is probably your mount options.  See the "
"answer to \"<a href=\"#bad-interpreter-permission-denied\">./configure: bad "
"interpreter: Permission denied</a>\", above."
msgstr ""

#. type: Content of: <dl><dl><dt>
#: complete.html:1046
msgid "signal 11 (internal error: Segmentation fault)"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1048
msgid ""
"The long answer is at <a href=\"http://www.bitwizard.nl/sig11/\""
">http://www.bitwizard.nl/sig11/</a>."
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1050
msgid ""
"The short answer is that if restarting make gets a little further every "
"time, you have a hardware problem. (If make, or whatever you're running, "
"fails at the same place every time, then it is not hardware.)"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1054
msgid ""
"Assuming you're not overclocking, the most likely hardware problem is bad "
"memory which you can check with Memtest86 from <a href=\""
"http://www.memtest86.com/\">http://www.memtest86.com/</a>. If that isn't it, "
"see the long answer."
msgstr ""

#. type: Content of: <dl><dl><dt>
#: complete.html:1059
msgid "No such file or directory"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1061
msgid "Examples of this error are:"
msgstr ""

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:1063
msgid "/usr/bin/env: /tools/bin/bash: No such file or directory"
msgstr ""

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:1064
msgid "gcc: No such file or directory"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1066
msgid ""
"This usually indicates a typo in the GCC Pass 2 installation. For older LFS "
"versions, the most common cause of this problem would be forgetting to apply "
"the specs patch."
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1069
msgid ""
"What happens is that the path to the dynamic linker embedded inside the "
"executable is still pointing at /lib/ld-linux.so.2 and when one goes to run "
"the binary inside the chroot where /lib/ld-linux.so.2 does not exist yet, "
"the very unhelpful <code>No such file or directory</code> error message is "
"shown."
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1074
msgid ""
"You can test this with <code>readelf -l {binary} | grep interpreter</code>. "
"Its output should be: <code>Requesting program interpreter: /tools/lib/ld-"
"linux.so.2</code>."
msgstr ""

#. type: Content of: <dl><dl><dt>
#: complete.html:1078
msgid "bash: ./configure: No such file or directory"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1080
msgid ""
"You forgot to <code>cd</code> into the extracted directory of the package "
"after you've extracted it."
msgstr ""

#. type: Content of: <dl><dl><dt>
#: complete.html:1082
msgid "./configure: bad interpreter: Permission denied"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1084
msgid ""
"You're most likely getting this while building binutils in Chapter 5 of the "
"LFS Book. The problem is most likely your mount options. You probably have a "
"line in /etc/fstab like:"
msgstr ""

#. type: Content of: <dl><dl><dd>
#: complete.html:1087
msgid "<code>/dev/hda10 /mnt/lfs ext2 user 1 2</code>"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1088
msgid ""
"'user' is the mount flag, and it's the problem. To quote from the mount man "
"page:"
msgstr ""

#. type: Content of: <dl><dl><dd>
#: complete.html:1089
msgid ""
"<cite>user: Allow an ordinary user to mount the file system. This option "
"implies the options noexec, nosuid, and nodev (unless overridden by "
"subsequent options, as in the option line user,exec,dev,suid).</cite>"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1093
msgid "So change the line in /etc/fstab like this:"
msgstr ""

#. type: Content of: <dl><dl><dd>
#: complete.html:1094
msgid "<code>/dev/hda10 /mnt/lfs ext2 defaults 1 2</code>"
msgstr ""

#. type: Content of: <dl><dl><dt>
#: complete.html:1096
msgid "configure can't guess my host type."
msgstr ""

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:1100
msgid "sk ~/tmp-0.0 $ ./configure"
msgstr ""

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:1101
msgid "creating cache ./config.cache"
msgstr ""

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:1102
msgid "checking host system type..."
msgstr ""

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:1103
msgid ""
"<strong>configure: error: can not guess host type; you must specify "
"one</strong>"
msgstr ""

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:1104
msgid "sk ~/tmp-0.0 $"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1106
msgid ""
"The problem is usually that the script can't run the compiler.  Usually it's "
"just a missing /usr/bin/cc symlink. You can fix it like this:"
msgstr ""

#. type: Content of: <dl><dl><dd>
#: complete.html:1109
msgid "<code>cd /usr/bin &amp;&amp; ln -s gcc cc</code>"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1110
msgid ""
"If that doesn't do it, check the file config.log created by configure. "
"Errors are recorded there and may indicate the problem."
msgstr ""

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:1114
#: complete.html:1118
msgid "checking whether we are using GNU C... no"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1116
msgid "If you're getting an error from configure like:"
msgstr ""

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:1119
msgid "configure: error: GNU libc must be compiled using GNU CC"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1121
msgid ""
"It may be because egrep isn't working. Since egrep is a shell-script which "
"calls grep, this actually means there's a problem with grep."
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1124
msgid ""
"To test if grep is working <em>before</em> reinstalling the grep package in "
"Chapter 6, run the following command from <em>outside</em> chroot:"
msgstr ""

#. type: Content of: <dl><dl><dd>
#: complete.html:1127
msgid "<code>file $LFS/bin/grep</code>"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1128
msgid ""
"If it doesn't say <code>statically linked</code> you have a problem and need "
"to reinstall the grep package according to the instruction in chapter 5."
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1131
msgid ""
"To test if egrep is working <em>after</em> reinstalling the grep package in "
"Chapter 6, run the following command from <em>inside</em> chroot:"
msgstr ""

#. type: Content of: <dl><dl><dd>
#: complete.html:1134
msgid "<code>egrep root /etc/passwd</code>"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1135
msgid ""
"If it doesn't print root's line from /etc/passwd, again, you have a problem. "
"(This test also works if you encounter the problem after rebooting into the "
"new LFS system.)"
msgstr ""

#. type: Content of: <dl><dl><dt>
#: complete.html:1139
msgid ""
"The system has no more ptys.  Ask your system administrator to create more."
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1142
msgid "If you run"
msgstr ""

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:1144
msgid "expect -c &quot;spawn ls&quot;"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1146
msgid "and get the following error:"
msgstr ""

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:1148
msgid "The system has no more ptys."
msgstr ""

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:1149
msgid "Ask your system administrator to create more."
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1151
msgid ""
"then your linux distribution is either not setup to use Unix98 PTYs or to "
"use the /dev/pts file system."
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1153
msgid ""
"The solution may require recompiling your kernel. First, go to your kernel's "
"source directory and look at the .config file. If you do not have a .config "
"file, and you are running the pre-compiled kernel that was installed with "
"rpm, aptget, or whatever your distribution uses, then you need to seek "
"support from your distribution's support FAQ's, mailing lists or IRC "
"channels."
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1159
msgid ""
"If you do have a .config file, look inside it for the following 2 options:"
msgstr ""

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:1161
msgid "CONFIG_UNIX98_PTYS=y"
msgstr ""

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:1162
msgid "CONFIG_DEVPTS_FS=y"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1164
msgid ""
"If either of these has 'n' instead of 'y', then change it and recompile the "
"kernel."
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1165
msgid ""
"If they both have 'y', then you probably will not have to recompile the "
"kernel."
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1166
msgid ""
"Next, we need to ensure that the system is actually using both Unix98 PTYs "
"and the /dev/pts file system."
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1168
msgid ""
"First, look for a device called /dev/ptmx.  If it doesn't exist, create it "
"with:"
msgstr ""

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:1170
msgid "mknod /dev/ptmx c 5 2"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1172
msgid "Then, whether it existed or you just created it, run:"
msgstr ""

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:1174
msgid "chmod 666 /dev/ptmx"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1176
msgid ""
"Next, ensure that there is a directory called /dev/pts.  The permissions "
"should be 755.  Create it and/or chmod it if needed."
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1178
msgid "The final setup is to add the following line to /etc/fstab:"
msgstr ""

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:1180
msgid ""
"devpts&nbsp;&nbsp;&nbsp;&nbsp;/dev/pts&nbsp;&nbsp;&nbsp;&nbsp;devpts&nbsp;&nb"
"sp;&nbsp;&nbsp;gid=5,mode=620&nbsp;&nbsp;&nbsp;&nbsp;0&nbsp;&nbsp;0"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1182
msgid ""
"NOTE: Look for the tty group in /etc/group and note the group id number.  "
"Change the gid=5 option to match the group id number of the tty group.  The "
"group id of 5 is just an example and may differ on your system."
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1186
msgid "Now that everything is setup, you have two options."
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1187
msgid "1.  Mount /dev/pts and test it by rerunning the above expect command."
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1188
msgid ""
"2.  Reboot the computer and test it by rerunning the above expect command."
msgstr ""

#. type: Content of: <dl><h3>
#: complete.html:1193
msgid "Package-specific errors"
msgstr ""

#. type: Content of: <dl><dl><dt>
#: complete.html:1195
msgid "GCC: Error: Unknown pseudo-op: `.hidden'"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1197
msgid "If compiling GCC in Chapter 5 errors out with"
msgstr ""

#. type: Content of: <dl><dl><dd>
#: complete.html:1198
msgid "<code>Error: Unknown pseudo-op: `.hidden'</code>"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1199
msgid ""
"Try the solution given in <a href=\"http://linuxfromscratch.org/pipermail"
"/lfs-support/2002-September/009562.html\">the lfs-support archives</a> and "
"replies."
msgstr ""

#. type: Content of: <dl><dl><dt>
#: complete.html:1203
msgid "Glibc fails and mentions BEGIN and END."
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1205
msgid "If glibc fails to build with an error like this:"
msgstr ""

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:1207
msgid "'BEGIN { subdirs = \"\"; inhibit = \"\" }; \\"
msgstr ""

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:1208
msgid "^# { next }; \\"
msgstr ""

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:1209
msgid "^[^-] { subdirs = subdirs \" \" $0 }; \\"
msgstr ""

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:1210
msgid "^- { inhibit = inhibit \" \" substr($0, 2) }; \\"
msgstr ""

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:1211
msgid ""
"END { printf \"sysdep-subdirs =%s\\n"
"\", subdirs; \\"
msgstr ""

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:1212
msgid ""
"printf \"sysdep-inhibit-subdirs =%s\\n"
"\", inhibit; \\"
msgstr ""

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:1213
msgid "print \"sysd-dirs-done = t\" }' \\"
msgstr ""

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:1214
msgid "/dev/null linuxthreads/sysdeps/pthread/Subdirs"
msgstr ""

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:1215
msgid "sysdeps/unix/inet/Subdirs sysdeps/unix/Subdirs &gt;"
msgstr ""

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:1216
msgid "/usr/src/glibc-build/sysd-dirs-tmp"
msgstr ""

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:1217
msgid "/bin/sh: line 1: BEGIN { subdirs = \"\"; inhibit = \"\" };"
msgstr ""

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:1218
msgid "^# { next };"
msgstr ""

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:1219
msgid "^[^-] { subdirs = subdirs \" \" $0 }; ^- { inhibit ="
msgstr ""

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:1220
msgid "inhibit \" \" substr($0, 2) }; END"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1222
msgid ""
"then gawk is failing. The key is the BEGIN and END in the output.  The "
"probable reason is that it is linked incorrectly. This can be fixed by "
"recompiling it as the lfs user, according to the directions in Chapter 5."
msgstr ""

#. type: Content of: <dl><dl><dt>
#: complete.html:1227
msgid "Glibc compilation errors out due to a missing nss.h header file"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1229
msgid ""
"This usually indicates that you are compiling LFS onto a Reiser4 partition. "
"Unfortunately, there is currently no known solution, other than to use a "
"different type of filesystem."
msgstr ""

#. type: Content of: <dl><dl><dt>
#: complete.html:1233
msgid "NCurses: C++ preprocessor &quot;/lib/cpp&quot; fails sanity check"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1235
msgid "Ncurses in chapter six ends with:"
msgstr ""

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:1237
msgid "checking how to run the C++ preprocessor... /lib/cpp"
msgstr ""

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:1238
msgid "configure: error: C++ preprocessor \"/lib/cpp\" fails sanity check"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1240
msgid ""
"The problem is that you have no c++ compiler. In chapter five, gcc is first "
"built without the C++ compiler. Before building ncurses, gcc is rebuilt with "
"the C++ compiler. Most probably, you forgot to extract the g++ tarball, or "
"did not specify \"c++\" in the --enable-languages configure switch, on the "
"2nd gcc build. There are more details in <a href=\""
"http://archives.linuxfromscratch.org/mail-archives/lfs-"
"support/2003-July/018757.html\">the mail archive</a>."
msgstr ""

#. type: Content of: <dl><h3>
#: complete.html:1252
msgid "Configuration and booting issues"
msgstr ""

#. type: Content of: <dl><dl><dt>
#: complete.html:1254
msgid "Kernel panic: VFS: unable to mount root fs"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1256
msgid ""
"There are several reasons why the kernel might be unable to mount the root "
"filesystem."
msgstr ""

#. type: Content of: <dl><dl><dd><ul><li>
#: complete.html:1258
msgid ""
"Did you specify the correct partition in <code>/boot/grub/menu.lst</code>?"
msgstr ""

#. type: Content of: <dl><dl><dd><ul><li>
#: complete.html:1260
msgid ""
"Is support for the hard drive enabled in the kernel. For SCSI this means "
"support for the specific SCSI adapter."
msgstr ""

#. type: Content of: <dl><dl><dd><ul><li>
#: complete.html:1262
msgid ""
"Is support for the hard drive compiled into the kernel, not just as a "
"module. (Modules are stored on the filesystem. If a driver needed to access "
"the filesystem is stored as a module on that filesystem, well ... you know "
"... ;)"
msgstr ""

#. type: Content of: <dl><dl><dd><ul><li>
#: complete.html:1266
msgid ""
"Is support for the filesystem compiled into the kernel. Again, not a module. "
"Support for ext2 is enabled by default, but others like ext3, reiser, jfs, "
"and xfs are not."
msgstr ""

#. type: Content of: <dl><dl><dt>
#: complete.html:1271
msgid "init: Id \"1\" respawning too fast: disabled for 5 minutes"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1273
msgid "When you see, in your syslogs, this line:"
msgstr ""

#. type: Content of: <dl><dl><dd>
#: complete.html:1274
msgid "<code>init: Id \"1\" respawning too fast: disabled for 5 minutes</code>"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1275
msgid ""
"It means you have an error in the /etc/inittab line beginning with the given "
"id (\"1\" in this example)."
msgstr ""

#. type: Content of: <dl><dl><dt>
#: complete.html:1277
msgid "modprobe: Can't locate module char-major-10-135"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1279
msgid ""
"<code>char-major-10-135</code> refers to the character device, major 10, "
"minor 135, which is /dev/rtc. It provides access to the BIOS clock, or RTC, "
"the Real Time Clock. See /usr/src/linux/Documentation/rtc.txt for more "
"information."
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1283
msgid ""
"The error is because something, most likely hwclock, is trying to use /dev/"
"rtc but you haven't configured kernel support for it in your kernel. Either "
"delete /dev/rtc so hwclock won't try to use it or enable RTC support in your "
"kernel. It's located in make menuconfig under \"Character devices\" -&gt; \""
"Enhanced Real Time Clock Support\"."
msgstr ""

#. type: Content of: <dl><dl><dt>
#: complete.html:1290
msgid "modprobe: Can't locate module /dev/rtc"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1292
msgid ""
"See the question <a href=\"#char-major-10-135\">\"modprobe: Can't locate "
"module char-major-10-135\"</a>."
msgstr ""

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:1294
#: complete.html:1298
msgid "eth0:unknown interface:No such device [failed]"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1296
msgid "The full error looks like this:"
msgstr ""

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:1299
msgid "Setting up default gateway..."
msgstr ""

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:1300
msgid "SIOCADDRT:No such device [failed]"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1302
msgid ""
"eth0 is a virtual device with no /dev entry. It refers to the first detected "
"network card in your system. The reason the kernel can't find this device is "
"because you forgot to add support for your network card in the kernel. The "
"kernel detected the card but doesn't have a driver for it. The LFS boot "
"script tries to bring up the network but fails because of this."
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1308
msgid ""
"Recompile your kernel with the proper driver, either built in or as a "
"module. If you compiled the network driver as a module, then also adjust "
"/etc/modules.conf to alias the network card module as eth0; for example: "
"<code>alias eth0 8139too</code>. If you don't know which network card you "
"have, you can use <code>dmesg</code>, /proc/pci or <code>lspci</code> to "
"find out."
msgstr ""

#. type: Content of: <dl><dl><dt>
#: complete.html:1315
msgid "spurious 8259A interrupt: IRQ14"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1317
msgid ""
"Short summary: It's a hardware problem (usually). Transient Line-noise/"
"crosstalk persuades the PIC that something happened; this can result in a "
"'dummy' interrupt being raised, which happens to be IRQ7 with intel's 8259 "
"design.The problem could possibly also be caused by (or instead be caused by)"
" a device driver not properly masking its interrupts before servicing, this "
"would be the suspect if the IRQ7's were happening in bursts, or more often "
"than 'several' per day. (<a href=\"http://groups.google.com/groups?q=spurious"
"+interrupt+8259&amp;hl=de&amp;scoring=d&amp;selm=3C174EDD.9090306%40hotmail.c"
"om&amp;rnum=10\">Source and additional information</a>)"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1327
msgid ""
"Since the message itself is harmless, it's enough to adjust the default "
"loglevel outplut of klogd (the -c opion) in the syslogd bootscript. See "
"<code>man klogd</code> for details. You can also try recompiling the kernel "
"and unset CONFIG_LOCAL_APIC."
msgstr ""

#. type: Content of: <dl><dl><dt>
#: complete.html:1332
msgid "Why does less (and therefore man) print &lt;AD&gt; instead of hyphens?"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1334
msgid ""
"Because the LANG and LC_ALL environment variables aren't set. To fix that, "
"set them in both the ~/.bash_profile and ~/.bashrc files for each user or in "
"/etc/profile, which will take care of all users, by adding lines like this:"
msgstr ""

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:1339
msgid "export LANG=en_US"
msgstr ""

#. type: Content of: <dl><dl><dd><div><p>
#: complete.html:1340
msgid "export LC_ALL=POSIX"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1342
msgid "Those lines can be added to /etc/profile with the following command:"
msgstr ""

#. type: Content of: <dl><dl><dd>
#: complete.html:1343
msgid ""
"<code>echo -e 'export LANG=en_US\\n"
"export LC_ALL=POSIX' &gt;&gt; /etc/profile</code>"
msgstr ""

#. type: Content of: <dl><dl><dd><p>
#: complete.html:1344
msgid ""
"If you don't use US English you'll have to change the \"en_US\" part and "
"possibly the values of various LC_* variables as well. Running the locale "
"command lists many (all?) of the LC_* variables."
msgstr ""