[RFR] d-i-manual://preparing.po

To: debian-l10n-french@lists.debian.org <debian-l10n-french@lists.debian.org>
Subject: [RFR] d-i-manual://preparing.po
From: Baptiste Jammet <baptiste@mailoo.org>
Date: Mon, 20 Apr 2015 16:39:09 +0200
Message-id: <[🔎] 20150420163909.06db730e.baptiste@mailoo.org>

Bonjour,

Voici une dernière grosse mise à jour du guide d'installation. Notez
que la date limite, pour que les corrections soient intégrées à Jessie,
est jeudi. Merci d'avance pour vos relectures.

Baptiste

Index: po/fr/preparing.po
===================================================================
--- po/fr/preparing.po	(rÃ©vision 69383)
+++ po/fr/preparing.po	(copie de travail)
@@ -6,8 +6,8 @@
 msgstr ""
 "Project-Id-Version: preparing\n"
 "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
-"POT-Creation-Date: 2014-08-05 21:38+0000\n"
-"PO-Revision-Date: 2014-09-15 21:07+0100\n"
+"POT-Creation-Date: 2015-04-15 20:29+0000\n"
+"PO-Revision-Date: 2015-04-20 15:16+0100\n"
 "Last-Translator: Baptiste Jammet <baptiste@mailoo.org>\n"
 "Language-Team: debian-l10n-french <debian-l10n-french@lists.debian.org>\n"
 "Language: fr\n"
@@ -1720,7 +1720,7 @@
 "touche Ã  utiliser."
 
 #. Tag: title
-#: preparing.xml:1138 preparing.xml:1290
+#: preparing.xml:1138 preparing.xml:1479
 #, no-c-format
 msgid "Boot Device Selection"
 msgstr "SÃ©lection du pÃ©riphÃ©rique d'amorÃ§age"
@@ -1758,8 +1758,8 @@
 #: preparing.xml:1154
 #, no-c-format
 msgid ""
-"Most BIOS versions allow to call up a boot menu on system startup in which "
-"you select from which device the computer should start for the current "
+"Most BIOS versions allow you to call up a boot menu on system startup in "
+"which you select from which device the computer should start for the current "
 "session. If this option is available, the BIOS usually displays a short "
 "message like <quote>press <keycap>F12</keycap> for boot menu</quote> on "
 "system startup. The actual key used to select this menu varies from system "
@@ -1784,7 +1784,7 @@
 #, no-c-format
 msgid ""
 "If your BIOS does not provide you with a boot menu to do ad-hoc choices of "
-"the current boot device, you have to change your BIOS setup to make the "
+"the current boot device, you will have to change your BIOS setup to make the "
 "device from which the &d-i; shall be booted the primary boot device."
 msgstr ""
 "Si le BIOS ne vous donne pas cette possibilitÃ©, vous devez modifier sa "
@@ -1928,13 +1928,396 @@
 "pour installer les routines pour le microprogramme dans la nvram."
 
 #. Tag: title
-#: preparing.xml:1257
+#: preparing.xml:1253
 #, no-c-format
+msgid "How to update bare metal ppc64el firmware"
+msgstr "Comment mettre Ã  jour le microcode d'un systÃ¨me ppc64el"
+
+#. Tag: para
+#: preparing.xml:1254
+#, no-c-format
+msgid ""
+"This is an excerpt from <ulink url=\"&url-ibm-powerkvm;\">IBM PowerKVM on "
+"IBM POWER8</ulink>"
+msgstr ""
+"Ce qui suit est un extrait de <ulink url=\"&url-ibm-powerkvm;\">IBM PowerKVM "
+"sur IBM POWER8</ulink>"
+
+#. Tag: para
+#: preparing.xml:1259
+#, no-c-format
+msgid ""
+"Open Power Abstraction Layer (OPAL) is the system firmware in the stack of "
+"POWER processor-based server."
+msgstr ""
+"Open Abstraction Layer (OPAL) est le microcode du systÃ¨me dans la pile "
+"serveur basÃ©e sur les processeur POWER."
+
+#. Tag: para
+#: preparing.xml:1264
+#, no-c-format
+msgid ""
+"There may be instances when the user might have to upgrade the Power Systems "
+"firmware to a more recent level to acquire new features or additional "
+"support for devices."
+msgstr ""
+"Il peut y avoir des cas oÃ¹ l'utilisateur devrait mettre Ã  niveau le "
+"microcode Power Systems pour obtenir de nouvelles fonctionnalitÃ©s ou "
+"davantages de prises en charge de pÃ©riphÃ©riques."
+
+#. Tag: para
+#: preparing.xml:1270
+#, no-c-format
+msgid "Make sure that the following requirements are met:"
+msgstr "Assurez-vous que les conditions suivantes sont rÃ©uniesÂ :"
+
+#. Tag: para
+#: preparing.xml:1275
+#, no-c-format
+msgid "an OS to be running on the system;"
+msgstr "un systÃ¨me d'exploitation fonctionne sur le systÃ¨meÂ ;"
+
+#. Tag: para
+#: preparing.xml:1277
+#, no-c-format
+msgid "the .img file of the OPAL level that the user needs to update to;"
+msgstr ""
+"le fichier .img du niveau OPAL vers lequel l'utilisateur veut mettre Ã  "
+"niveau est disponibleÂ ;"
+
+#. Tag: para
+#: preparing.xml:1279
+#, no-c-format
+msgid "the machine isn't under HMC control."
+msgstr "la machine n'est pas contrÃ´lÃ©e par HMC."
+
+#. Tag: para
+#: preparing.xml:1283
+#, no-c-format
+msgid ""
+"Power Systems has two sides of flash to boot firmware from, namely permanent "
+"and temporary. This provides a way to test firmware updates on the temporary "
+"side of the flash before committing the tested changes to the permanent "
+"side, thereby committing the new updates."
+msgstr ""
+"Les machines Power Systems ont deux parties de mÃ©moire d'oÃ¹ charger le "
+"microcode, une permanente et une temporaire. Cela permet de tester les mises "
+"Ã  jour du microcode dans la mÃ©moire temporaire avant d'envoyer les "
+"modifications testÃ©e dans la mÃ©moire permanente et, grÃ¢ce Ã  cela, utiliser "
+"ces mise Ã  jour."
+
+#. Tag: para
+#: preparing.xml:1290
+#, no-c-format
+msgid "Perform the following steps for the update:"
+msgstr "Pour la mise Ã  jour, voici les Ã©tapes Ã  effectuerÂ :"
+
+#. Tag: para
+#: preparing.xml:1295
+#, no-c-format
+msgid ""
+"Save the level of the existing firmware before really updating. In ASM, in "
+"the system menu, click <command>Service Aids ??? Service Processor Command "
+"Line</command>, and run the following command:"
+msgstr ""
+"Sauvergardez la version actuelle avant de faire la mise Ã  jour. Dans le menu "
+"system de ASM, cliquez sur <command>Service Aids ??? Service Processor "
+"Command Line</command> et lancez la commande suivanteÂ :"
+
+#. Tag: screen
+#: preparing.xml:1299
+#, no-c-format
+msgid "cupdcmd -f"
+msgstr "cupdcmd -f"
+
+#. Tag: para
+#: preparing.xml:1300
+#, no-c-format
+msgid ""
+"Download the .img file of the level of firmware to be updated to a location "
+"in the host filesystem. Refer to IBM Fix Central for downloading the image "
+"file."
+msgstr ""
+"TÃ©lÃ©chargez le fichier .img de la version du microcode vers laquelle migrer "
+"sur le systÃ¨me de fichiers hÃ´te.Veuillez vous rÃ©fÃ©rer au Fix Central d'IBM "
+"pour tÃ©lÃ©charger le fichier image."
+
+#. Tag: para
+#: preparing.xml:1304
+#, no-c-format
+msgid ""
+"Verify the image downloaded by running the following command and save the "
+"output."
+msgstr ""
+"VÃ©rifiez l'image chargÃ©es en lanÃ§ant la commande suivante et en enregistrant "
+"la sortieÂ :"
+
+#. Tag: screen
+#: preparing.xml:1307
+#, no-c-format
+msgid "$update_flash -v -f &lt;file_name.img&gt;"
+msgstr "$update_flash -v -f &lt;nom_de_fichier.img&gt;"
+
+#. Tag: para
+#: preparing.xml:1309
+#, no-c-format
+msgid "Update the firmware by running the following command."
+msgstr "Mettez Ã  jour le microcode en exÃ©cutant la commande suivanteÂ :"
+
+#. Tag: screen
+#: preparing.xml:1311
+#, no-c-format
+msgid "$update_flash -f &lt;file_name.img&gt;"
+msgstr "$update_flash -f &lt;nom_de_fichier.img&gt;"
+
+#. Tag: para
+#: preparing.xml:1317
+#, no-c-format
+msgid ""
+"The command reboots the system and therefore, sessions if any, would be lost."
+msgstr ""
+"Cett commande redÃ©marre le systÃ¨me et, par consÃ©quence, les sessions seront "
+"perdues."
+
+#. Tag: para
+#: preparing.xml:1320
+#, no-c-format
+msgid "Do not reboot or switch off the system until it is back."
+msgstr "Ne redÃ©marrez ni n'Ã©teignez le systÃ¨me tant qu'il n'est pas rÃ©amorcÃ©."
+
+#. Tag: para
+#: preparing.xml:1327
+#, no-c-format
+msgid ""
+"Verify the updated firmware level of the temporary side of the flash as in "
+"step 1."
+msgstr ""
+"VÃ©rifiez la version du microcode dans la mÃ©moire temporaire de la mÃ©moire, "
+"comme Ã  la premiÃ¨re Ã©tape."
+
+#. Tag: para
+#: preparing.xml:1330
+#, no-c-format
+msgid ""
+"In case the update has to be reverted, the user can do so by running this "
+"command: <informalexample><screen>\n"
+"    $update_flash -r\n"
+"</screen></informalexample> Rejection would reject only the temporary side "
+"of the flash. Therefore, the new level should be committed to the permanent "
+"side only after thorough testing of the new firmware."
+msgstr ""
+"Dans le cas ou la mise Ã  jour doit Ãªtre annulÃ©e, cela peut Ãªtre fait en "
+"exÃ©cutant <informalexample><screen>\n"
+"    $update_flash -r\n"
+"</screen></informalexample> Cela n'affectera que la mÃ©moire temporaire. "
+"Autrement, la nouvelle version ne devrait Ãªtre envoyÃ©e dans la mÃ©moire "
+"permanente qu'aprÃ¨s avoir suffisamment testÃ© le nouveau microcode."
+
+#. Tag: para
+#: preparing.xml:1337
+#, no-c-format
+msgid ""
+"The new updated level can be committed to the permanent side of the flash by "
+"running the following command."
+msgstr ""
+"La nouvelle version peut Ãªtre envoyÃ©e dans la mÃ©moire permanente en "
+"exÃ©cutant la commande suivanteÂ :"
+
+#. Tag: screen
+#: preparing.xml:1340
+#, no-c-format
+msgid "$update_flash -c"
+msgstr "$update_flash -c"
+
+#. Tag: title
+#: preparing.xml:1348
+#, no-c-format
+msgid "Updating KVM guest firmware (SLOF)"
+msgstr "Mise Ã  jour du microcode invitÃ© de KVM (SLOF)"
+
+#. Tag: para
+#: preparing.xml:1349
+#, no-c-format
+msgid ""
+"Slimline Open Firmware (SLOF) is an implementation of the IEEE 1275 "
+"standard. It can be used as partition firmware for pSeries machines running "
+"on QEMU or KVM."
+msgstr ""
+"Slimline Open Firmware (SLOF) est une implÃ©mentation du standard IEEEÂ 1275. "
+"Il peut Ãªtre utilisÃ© comme microcode de partition pour les machines pSeries "
+"s'exÃ©cutant dans QEMU ou KVM."
+
+#. Tag: para
+#: preparing.xml:1356
+#, no-c-format
+msgid ""
+"The package qemu-slof is, in fact, a dependency of package qemu-system-ppc "
+"(which also provides the virtual package qemu-system-ppc64), and can be "
+"installed or updated via <command>apt-get</command> tool on Debian-based "
+"distros. Like so: <informalexample><screen>\n"
+"# apt-get install qemu-slof\n"
+"</screen></informalexample> SLOF can also be installed into rpm-based "
+"distribution systems, given the proper repository or rpm package. "
+"Additionally, the upstream source code is available at http://github.com/";
+"leilihh/SLOF."
+msgstr ""
+"La paquetqemu-slof est en fait une dÃ©pendance du paquet qemu-system-ppc (qui "
+"fournit aussi le paquet virtuel qemu-system-ppc64) et peut Ãªtre installÃ© ou "
+"mis Ã  jour avec <command>apt-get</command> sur les distributions basÃ©es sur "
+"DebianÂ :<informalexample><screen>\n"
+"# apt-get install qemu-slof\n"
+"</screen></informalexample> SLOF peut aussi Ãªtre installÃ© sur les "
+"distributions basÃ©es sur rpm. De plus, le code source amont est disponible Ã  "
+"l'adresse http://github.com/leilihh/SLOF.";
+
+#. Tag: para
+#: preparing.xml:1370
+#, no-c-format
+msgid ""
+"Thus, one can use a different SLOF file rather than the default, when "
+"running <command>qemu-system</command>, by adding the command line argument "
+"<userinput>-bios &lt;slof_file&gt; </userinput> when starting qemu."
+msgstr ""
+"Il est possible d'utiliser un fichier SLOF diffÃ©rent de celui par dÃ©faut en "
+"ajoutant l'argument <userinput>-bios &lt;fichier_slof&gt; </userinput> Ã  la "
+"commande <command>qemu-system</command>."
+
+#. Tag: title
+#: preparing.xml:1380
+#, no-c-format
+msgid "Updating PowerKVM hypervisor"
+msgstr "Mise Ã  jour de l'hyperviseur PowerKVM"
+
+#. Tag: title
+#: preparing.xml:1381
+#, no-c-format
+msgid "Instructions for Netboot installation"
+msgstr "Instructions pour les installations de type netboot"
+
+#. Tag: para
+#: preparing.xml:1382
+#, no-c-format
+msgid ""
+"You will need a DHCP/TFTP (BOOTP) server, as well as a web server. After "
+"downloading ibm-powerkvm-*-ppc64-service-*.iso, mount loop it and unpack it "
+"into some directory within your HTTP server www root structure (say "
+"wwwroot): <informalexample><screen>\n"
+"# cd &lt;directory-where-the-iso-is&gt;\n"
+"# mkdir ./iso\n"
+"# sudo mount -o loop ibm-powerkvm-*-ppc64-service-*.iso ./iso\n"
+"# cp -a ./iso/* &lt;path-to-wwwroot&gt;\n"
+"</screen></informalexample> Create the petitboot.conf file in a directory "
+"under your tftproot, say /tftproot/powerkvm, with the following contents: "
+"<informalexample><screen>\n"
+"label PowerKVM Automated Install\n"
+"kernel http://YOUR-SERVER-IP/SOME-PATH-TO-wwwroot/ppc/ppc64/vmlinuz\n";
+"initrd http://YOUR-SERVER-IP/SOME-PATH-TO-wwwroot/ppc/ppc64/initrd.img\n";
+"append root=live:http://YOUR-SERVER-IP/SOME-PATH-TO-wwwroot/LiveOS/squashfs.";
+"img repo=http://YOUR-SERVER-IP/SOME-PATH-TO-wwwroot/packages rd.dm=0 rd.md=0 "
+"console=hvc0 console=tty0\n"
+"</screen></informalexample> Editing your dhcpd.conf, set this directive at "
+"the beginning: <informalexample><screen>\n"
+"option conf-file code 209 = text;\n"
+"</screen></informalexample> Add the system directive: "
+"<informalexample><screen>\n"
+"host &lt;your-system&gt; {\n"
+"    hardware ethernet &lt;system macaddr&gt;\n"
+"    fixed-address &lt;system ip&gt;;\n"
+"    option host-name \"&lt;system hostname&gt;\";\n"
+"    option conf-file \"&lt;powerkvm/petitboot.conf&gt;\";\n"
+" }\n"
+"</screen></informalexample> Reboot the dhcp server."
+msgstr ""
+"Vous aurez besoin d'un serveur DHCP/TFTP (BOOTP) ainsi que d'un serveur web. "
+"AprÃ¨s avoir tÃ©lÃ©chargÃ© l'image ibm-powerkvm-*-ppc64-service-*.iso, montez-la "
+"et dÃ©compressez-la dans la structure www de votre serveur HTTP (par exemple "
+"wwwroot)Â : <informalexample><screen>\n"
+"# cd &lt;rÃ©pertoire_de_l_image&gt;\n"
+"# mkdir ./iso\n"
+"# sudo mount -o loop ibm-powerkvm-*-ppc64-service-*.iso ./iso\n"
+"# cp -a ./iso/* &lt;chemin_vers_wwwroot&gt;\n"
+"</screen></informalexample> CrÃ©ez le fichier petitboot.conf dans un "
+"rÃ©pertoire de votre serveur TFTP (par exemple (/tftproot/powerkvm) contenant "
+"ce qui suitÂ : <informalexample><screen>\n"
+"label PowerKVM Automated Install\n"
+"kernel http://IP_DU_SERVEUR/chemin_vers_wwwroot/ppc/ppc64/vmlinuz\n";
+"initrd http://IP_DU_SERVEUR/chemin_vers_wwwroot/ppc/ppc64/initrd.img\n";
+"append root=live:http://IP_DU_SERVEUR/chemin_vers_wwwroot/LiveOS/squashfs.";
+"img repo=http://IP_DU_SERVEUR/chemin_vers_wwwroot/packages rd.dm=0 rd.md=0 "
+"console=hvc0 console=tty0\n"
+"</screen></informalexample> Ã?ditez votre fichier dhcpd.conf et ajoutez ces "
+"directives au dÃ©butÂ : <informalexample><screen>\n"
+"option conf-file code 209 = text;\n"
+"</screen></informalexample> Ajoutez la directive systÃ¨meÂ : "
+"<informalexample><screen>\n"
+"host &lt;your-system&gt; {\n"
+"    hardware ethernet &lt;adrsse_MAC_du_systÃ¨me&gt;\n"
+"    fixed-address &lt;adresse_IP_du_systÃ¨me&gt;;\n"
+"    option host-name \"&lt;hostname_du_systÃ¨me&gt;\";\n"
+"    option conf-file \"&lt;powerkvm/petitboot.conf&gt;\";\n"
+" }\n"
+"</screen></informalexample> RedÃ©marrez votre serveur DHCP."
+
+#. Tag: para
+#: preparing.xml:1406
+#, no-c-format
+msgid "Boot your PowerLinux machine."
+msgstr "DÃ©marrez votre machine PowerLinux"
+
+#. Tag: para
+#: preparing.xml:1410
+#, no-c-format
+msgid ""
+"There should be the following option at petitboot (select it): "
+"<informalexample><screen>\n"
+"\"Power KVM Automated Install\" \n"
+"</screen></informalexample> The installer menu should appear automatically."
+msgstr ""
+"L'option suivante devrait vous Ãªtre prÃ©sentÃ©e dans le menu petitbootÂ : "
+"<informalexample><screen>\n"
+"\"Power KVM Automated Install\" \n"
+"</screen></informalexample> Le menu de l'installateur devrait ensuite "
+"apparaÃ®tre."
+
+#. Tag: title
+#: preparing.xml:1421
+#, no-c-format
+msgid "Instructions for DVD"
+msgstr "Instructions pour les DVD"
+
+#. Tag: para
+#: preparing.xml:1422
+#, no-c-format
+msgid ""
+"Boot the ISO ibm-powerkvm-*-ppc64-service-*.iso (either burn a DVD or make "
+"it virtual if using QEMU) and simply wait for the boot."
+msgstr ""
+"Amorcez sur l'image ISO ibm-powerkvm-*-ppc64-service-*.iso (gravÃ©e sur un "
+"DVD ou virtualisÃ©e si utilisÃ©e dans QEMU) et attendez le dÃ©marrage."
+
+#. Tag: para
+#: preparing.xml:1425
+#, no-c-format
+msgid ""
+"There should be the following option at petitboot (select it): "
+"<informalexample><screen>\n"
+"\"POWERKVM_LIVECD\" \n"
+"</screen></informalexample> The installer menu should appear automatically."
+msgstr ""
+"L'option suivante devrait vous Ãªtre prÃ©sentÃ©e dans le menu petitbootÂ : "
+"<informalexample><screen>\n"
+"\"POWERKVM_LIVECD\" \n"
+"</screen></informalexample> Le menu de l'installateur devrait ensuite "
+"apparaÃ®tre."
+
+#. Tag: title
+#: preparing.xml:1446
+#, no-c-format
 msgid "Invoking OpenBoot"
 msgstr "Appel d'OpenBoot"
 
 #. Tag: para
-#: preparing.xml:1259
+#: preparing.xml:1448
 #, no-c-format
 msgid ""
 "OpenBoot provides the basic functions needed to boot the &arch-title; "
@@ -1950,7 +2333,7 @@
 "pas mal de choses, comme des tests, des scripts simples,Â etc."
 
 #. Tag: para
-#: preparing.xml:1267
+#: preparing.xml:1456
 #, no-c-format
 msgid ""
 "To get to the boot prompt you need to hold down the <keycap>Stop</keycap> "
@@ -1972,7 +2355,7 @@
 "la touche <keycap>n</keycap> pour obtenir le nouveau modÃ¨le d'invite."
 
 #. Tag: para
-#: preparing.xml:1279
+#: preparing.xml:1468
 #, no-c-format
 msgid ""
 "If you are using a serial console, send a break to the machine. With "
@@ -1987,7 +2370,7 @@
 "utilisez un programme diffÃ©rent."
 
 #. Tag: para
-#: preparing.xml:1292
+#: preparing.xml:1481
 #, no-c-format
 msgid ""
 "You can use OpenBoot to boot from specific devices, and also to change your "
@@ -2008,7 +2391,7 @@
 "openboot;\">rÃ©fÃ©rence OpenBoot Sun </ulink>."
 
 #. Tag: para
-#: preparing.xml:1302
+#: preparing.xml:1491
 #, no-c-format
 msgid ""
 "Typically, with newer revisions, you can use OpenBoot devices such as "
@@ -2053,7 +2436,7 @@
 "ulink>."
 
 #. Tag: para
-#: preparing.xml:1325
+#: preparing.xml:1514
 #, no-c-format
 msgid ""
 "To boot from a specific device, use the command <userinput>boot "
@@ -2085,19 +2468,19 @@
 "</screen></informalexample> et sous SolarisÂ :"
 
 #. Tag: screen
-#: preparing.xml:1344
+#: preparing.xml:1533
 #, no-c-format
 msgid "eeprom boot-device=disk1:1"
 msgstr "# eeprom boot-device=disk1:1"
 
 #. Tag: title
-#: preparing.xml:1354
+#: preparing.xml:1543
 #, no-c-format
 msgid "BIOS Setup"
 msgstr "ParamÃ©trage du BIOS"
 
 #. Tag: para
-#: preparing.xml:1355
+#: preparing.xml:1544
 #, no-c-format
 msgid ""
 "In order to install &debian-gnu; on a &arch-title; or zSeries machine you "
@@ -2121,7 +2504,7 @@
 "ligne et non caractÃ¨re."
 
 #. Tag: para
-#: preparing.xml:1367
+#: preparing.xml:1556
 #, no-c-format
 msgid ""
 "Linux on this platform runs either natively on the bare machine, in a so-"
@@ -2140,7 +2523,7 @@
 "LPAR si la HMC et cette option sont disponibles."
 
 #. Tag: para
-#: preparing.xml:1376
+#: preparing.xml:1565
 #, no-c-format
 msgid ""
 "Before you actually perform an installation, you have to go over some design "
@@ -2166,13 +2549,13 @@
 "spÃ©cifiques Ã  &debian;."
 
 #. Tag: title
-#: preparing.xml:1393
+#: preparing.xml:1582
 #, no-c-format
 msgid "Native and LPAR installations"
 msgstr "Installations en mode natif et sur LPAR"
 
 #. Tag: para
-#: preparing.xml:1394
+#: preparing.xml:1583
 #, no-c-format
 msgid ""
 "Please refer to chapter 5 of the <ulink url=\"http://www.redbooks.ibm.com/";
@@ -2189,13 +2572,13 @@
 "Linux."
 
 #. Tag: title
-#: preparing.xml:1408
+#: preparing.xml:1597
 #, no-c-format
 msgid "Installation as a VM guest"
 msgstr "Installation en tant qu'invitÃ© VM"
 
 #. Tag: para
-#: preparing.xml:1410
+#: preparing.xml:1599
 #, no-c-format
 msgid ""
 "Please refer to chapter 6 of the <ulink url=\"http://www.redbooks.ibm.com/";
@@ -2212,7 +2595,7 @@
 "pour Linux."
 
 #. Tag: para
-#: preparing.xml:1420
+#: preparing.xml:1609
 #, no-c-format
 msgid ""
 "You need to copy all the files from the <filename>generic</filename> sub-"
@@ -2235,13 +2618,13 @@
 "les fichiers dans le bon ordre, se trouve avec les images."
 
 #. Tag: title
-#: preparing.xml:1437
+#: preparing.xml:1626
 #, no-c-format
 msgid "Setting up an installation server"
 msgstr "Configurer un serveur d'installation"
 
 #. Tag: para
-#: preparing.xml:1439
+#: preparing.xml:1628
 #, no-c-format
 msgid ""
 "If you don't have a connection to the Internet (either directly or via a web "
@@ -2255,7 +2638,7 @@
 "voulez installer et doit les rendre accessibles avec NFS, HTTP ou FTP."
 
 #. Tag: para
-#: preparing.xml:1447
+#: preparing.xml:1636
 #, no-c-format
 msgid ""
 "The installation server needs to copy the exact directory structure from any "
@@ -2269,19 +2652,19 @@
 "utiliser le contenu des CD d'installation."
 
 #. Tag: emphasis
-#: preparing.xml:1456
+#: preparing.xml:1645
 #, no-c-format
 msgid "FIXME: more information needed &mdash; from a Redbook?"
 msgstr "FIXME: more information needed &mdash; from a Redbook?"
 
 #. Tag: title
-#: preparing.xml:1466
+#: preparing.xml:1655
 #, no-c-format
 msgid "ARM firmware"
 msgstr "Microprogramme ARM"
 
 #. Tag: para
-#: preparing.xml:1468
+#: preparing.xml:1657
 #, no-c-format
 msgid ""
 "As already mentioned before, there is unfortunately no standard for system "
@@ -2306,7 +2689,7 @@
 "microprogramme original."
 
 #. Tag: para
-#: preparing.xml:1480
+#: preparing.xml:1669
 #, no-c-format
 msgid ""
 "As a result even newly sold systems often use a firmware that is based on a "
@@ -2327,15 +2710,61 @@
 "fournir des instructions utilisables pour tous les systÃ¨mes basÃ©s sur ARM."
 
 #. Tag: title
-#: preparing.xml:1493
+#: preparing.xml:1682
 #, no-c-format
-msgid "Setting the ethernet MAC address in u-boot"
-msgstr "Configurer l'adresse MAC Ethernet dans u-boot"
+msgid "Debian-provided U-Boot (system firmware) images"
+msgstr "Images U-Boot fournies par Debian (microcode systÃ¨me)"
 
 #. Tag: para
-#: preparing.xml:1494
+#: preparing.xml:1683
 #, no-c-format
 msgid ""
+"Debian provides U-Boot images for various armhf systems that can load their "
+"U-Boot from an SD card at &armmp-uboot-img;. The U-Boot builds are offered "
+"in two formats: raw U-Boot components and a ready-made card image that can "
+"easily be written onto an SD card. The raw U-Boot components are provided "
+"for advanced users; the generally recommended way is to use one of the ready-"
+"made SD card images. They are named &lt;system-type&gt;.sdcard.img.gz and "
+"can be written to a card e.g. with <informalexample><screen>zcat &lt;system-"
+"type&gt;.sdcard.img.gz > /dev/SD_CARD_DEVICE</screen></informalexample> As "
+"with all images, please be aware that writing the image to an SD card wipes "
+"all previous contents of the card!"
+msgstr ""
+"Debian fournit des images U-Boot Ã  &armmp-uboot-img;, pour divers systÃ¨mes "
+"armhf qui peuvent charger U-Boot depuis une carte SD. Les images U-Boot sont "
+"fournies dans deux formatÂ : les composants bruts U-Boot ou une image toute "
+"faite et prÃªte Ã  Ãªtre Ã©crite sur une carte SD. Les composants bruts sont "
+"destinÃ©s aux utilisateurs confirmÃ©s car la mÃ©thode recommandÃ©e est "
+"d'utiliser une des images prÃ©compilÃ©es. Ces derniÃ¨res sont appelÃ©es &lt;"
+"type_de_systÃ¨me&gt;.sdcard.img.gz et peuvent Ãªtre Ã©crites sur une carte par "
+"exemple avecÂ : <informalexample><screen>zcat &lt;type_de_systÃ¨me&gt;.sdcard."
+"img.gz > /dev/PÃ?RIPHÃ?RIQUE_DE_CARTE_SD</screen></informalexample> Comme pour "
+"toutes les images, soyez conscient que cela supprimera tout ce qu'il y avait "
+"sur la carteÂ !"
+
+#. Tag: para
+#: preparing.xml:1698
+#, no-c-format
+msgid ""
+"If Debian provides a U-Boot image for your system, it is recommended that "
+"you use this image instead of the vendor-provided U-Boot, as the version in "
+"Debian is usually newer and has more features."
+msgstr ""
+"Si Debian fornit une image U-Boot pour votre systÃ¨me, il est recommandÃ© "
+"d'utiliser cette image plutÃ´t qu'une version de U-Boot du distributeur, car "
+"la version de Debian est gÃ©nÃ©ralement plus Ã  jour et contient plus de "
+"fonctionnalitÃ©s."
+
+#. Tag: title
+#: preparing.xml:1706
+#, no-c-format
+msgid "Setting the ethernet MAC address in U-Boot"
+msgstr "Configurer l'adresse MAC Ethernet dans U-Boot"
+
+#. Tag: para
+#: preparing.xml:1707
+#, no-c-format
+msgid ""
 "The MAC address of every ethernet interface should normally be globally "
 "unique, and it technically has to be unique within its ethernet broadcast "
 "domain. To achieve this, the manufacturer usually allocates a block of MAC "
@@ -2349,7 +2778,7 @@
 "prÃ©configurent une de ces adresses sur chaque Ã©lÃ©ment vendu."
 
 #. Tag: para
-#: preparing.xml:1502
+#: preparing.xml:1715
 #, no-c-format
 msgid ""
 "In the case of development boards, sometimes the manufacturer wants to avoid "
@@ -2373,7 +2802,7 @@
 "client, ne fonctionnerait Ã©videmment pas correctement."
 
 #. Tag: para
-#: preparing.xml:1513
+#: preparing.xml:1726
 #, no-c-format
 msgid ""
 "To avoid conflicts with existing officially-assigned MAC addresses, there is "
@@ -2394,95 +2823,95 @@
 "administrÃ©e localement."
 
 #. Tag: para
-#: preparing.xml:1523
+#: preparing.xml:1736
 #, no-c-format
 msgid ""
-"On systems using u-boot as system firmware, the ethernet MAC address is "
+"On systems using U-Boot as system firmware, the ethernet MAC address is "
 "placed in the <quote>ethaddr</quote> environment variable. It can be checked "
-"at the u-boot command prompt with the command <quote>printenv ethaddr</"
+"at the U-Boot command prompt with the command <quote>printenv ethaddr</"
 "quote> and can be set with the command <quote>setenv ethaddr ca:ff:"
 "ee:12:34:56</quote>. After setting the value, the command <quote>saveenv</"
 "quote> makes the assignment permanent."
 msgstr ""
-"Sur les systÃ¨mes utilisant u-boot comme microprogramme systÃ¨me, l'adresse "
+"Sur les systÃ¨mes utilisant U-Boot comme microprogramme systÃ¨me, l'adresse "
 "MAC ethernet est placÃ©e dans la variable d'environnement <quote>ethaddr</"
-"quote>. Elle peut Ãªtre vÃ©rifiÃ©e Ã  l'invite de u-boot avec la commande "
+"quote>. Elle peut Ãªtre vÃ©rifiÃ©e Ã  l'invite de U-Boot avec la commande "
 "<quote>printenv ethaddr</quote> et peut Ãªtre positionnÃ©e avec <quote>setenv "
 "ethaddr ca:ff:ee:12:34:56</quote>. AprÃ¨s avoir positionnÃ©e la variable, la "
 "commande <quote>saveenv</quote> rend la modification permanente."
 
 #. Tag: title
-#: preparing.xml:1534
+#: preparing.xml:1747
 #, no-c-format
-msgid "Kernel/Initrd/Device-Tree relocation issues in u-boot"
+msgid "Kernel/Initrd/Device-Tree relocation issues in U-Boot"
 msgstr ""
 "ProblÃ¨mes de positionnement du noyau, de l'initrd et de l'arbre de "
-"pÃ©riphÃ©riques dans u-boot"
+"pÃ©riphÃ©riques dans U-Boot"
 
 #. Tag: para
-#: preparing.xml:1535
+#: preparing.xml:1748
 #, no-c-format
 msgid ""
-"On some systems with older u-boot versions there can be problems with "
+"On some systems with older U-Boot versions there can be problems with "
 "properly relocating the Linux kernel, the initial ramdisk and the device-"
-"tree blob in memory during the boot process. In this case, u-boot shows the "
+"tree blob in memory during the boot process. In this case, U-Boot shows the "
 "message <quote>Starting kernel ...</quote>, but the system freezes "
 "afterwards without further output. These issues have been solved with newer "
-"u-boot versions from v2014.07 onwards."
+"U-Boot versions from v2014.07 onwards."
 msgstr ""
-"Sur certains systÃ¨mes avec d'anciennes versions de u-boot, il peut y avoir "
+"Sur certains systÃ¨mes avec d'anciennes versions de U-Boot, il peut y avoir "
 "des problÃ¨mes de dÃ©placement du noyau Linux, de l'image mÃ©moire initiale ou "
 "de l'arbre des pÃ©riphÃ©riques dans la mÃ©moire lors du dÃ©marrage. Dans ce cas, "
-"u-boot affiche le message <quote>Starting kernel ...</quote>, mais le "
+"U-Boot affiche le message <quote>Starting kernel ...</quote>, mais le "
 "systÃ¨me gÃ¨le aprÃ¨s cela sans autre message. Ces problÃ¨mes ont Ã©tÃ© rÃ©solus "
-"dans les nouvelles versions de u-boot, postÃ©rieures Ã  v2014.07."
+"dans les nouvelles versions de U-Boot, postÃ©rieures Ã  v2014.07."
 
 #. Tag: para
-#: preparing.xml:1544
+#: preparing.xml:1757
 #, no-c-format
 msgid ""
-"If the system has originally used a u-boot version older than v2014.07 and "
+"If the system has originally used a U-Boot version older than v2014.07 and "
 "has been upgraded to a newer version later, the problem might still occur "
-"even after upgrading u-boot. Upgrading u-boot usually does not modify the "
-"existing u-boot environment variables and the fix requires an additional "
-"environment variable (bootm_size) to be set, which u-boot does automatically "
+"even after upgrading U-Boot. Upgrading U-Boot usually does not modify the "
+"existing U-Boot environment variables and the fix requires an additional "
+"environment variable (bootm_size) to be set, which U-Boot does automatically "
 "only on fresh installations without existing environment data. It is "
-"possible to manually set bootm_size to the new u-boot's default value by "
-"running the command <quote>env default bootm_size; saveenv</quote> at the u-"
-"boot prompt."
+"possible to manually set bootm_size to the new U-Boot's default value by "
+"running the command <quote>env default bootm_size; saveenv</quote> at the U-"
+"Boot prompt."
 msgstr ""
 "Si le systÃ¨me utilisait une version plus ancienne que la v2014.07, et mÃªme "
-"aprÃ¨s une mise Ã  niveau de u-boot, le problÃ¨me peut encore apparaÃ®tre. La "
-"mise Ã  niveau de u-boot ne modifie gÃ©nÃ©ralement pas les variables "
+"aprÃ¨s une mise Ã  niveau de U-Boot, le problÃ¨me peut encore apparaÃ®tre. La "
+"mise Ã  niveau de U-Boot ne modifie gÃ©nÃ©ralement pas les variables "
 "d'environnement existantes et le correctif nÃ©cessite une variable "
 "d'environnement supplÃ©mentaire (bootm_size), qui nâ??est crÃ©Ã©e automatiquement "
 "que sur les nouvelles installations sans variable dâ??environnement existante, "
 "Il est possible de positionner manuellement la variable bootm_size Ã  la "
 "nouvelle valeur par dÃ©faut en exÃ©cutant la commande <quote>env default "
-"bootm_size; saveenv</quote> Ã  l'invite de u-boot."
+"bootm_size; saveenv</quote> Ã  l'invite de U-Boot."
 
 #. Tag: para
-#: preparing.xml:1555
+#: preparing.xml:1768
 #, no-c-format
 msgid ""
 "Another possibility to circumvent relocation-related problems is to run the "
 "command <quote>setenv fdt_high ffffffff; setenv initrd_high 0xffffffff; "
-"saveenv</quote> at the u-boot prompt to completely disable the relocation of "
+"saveenv</quote> at the U-Boot prompt to completely disable the relocation of "
 "the initial ramdisk and the device-tree blob."
 msgstr ""
 "Une autre possibilitÃ© de contourner les problÃ¨mes liÃ©s au dÃ©placement est "
 "d'exÃ©cuter la commande <quote>setenv fdt_high ffffffff; setenv initrd_high "
-"0xffffffff; saveenv</quote> Ã  l'invite de u-boot, pour dÃ©sactiver totalement "
+"0xffffffff; saveenv</quote> Ã  l'invite de U-Boot, pour dÃ©sactiver totalement "
 "le dÃ©placement du disque mÃ©moire initial et de l'arbre de pÃ©riphÃ©riques."
 
 #. Tag: title
-#: preparing.xml:1565
+#: preparing.xml:1778
 #, no-c-format
 msgid "Systems with UEFI firmware"
 msgstr "SystÃ¨mes avec un microprogramme UEFI"
 
 #. Tag: para
-#: preparing.xml:1566
+#: preparing.xml:1779
 #, no-c-format
 msgid ""
 "UEFI (<quote>Unified Extensible Firmware Interface</quote>) is a new kind of "
@@ -2495,7 +2924,7 @@
 "autre, pour remplacer le BIOS classique des PC."
 
 #. Tag: para
-#: preparing.xml:1572
+#: preparing.xml:1785
 #, no-c-format
 msgid ""
 "Currently most PC systems that use UEFI also have a so-called "
@@ -2504,7 +2933,7 @@
 "BIOS, so that software written for the classic PC BIOS can be used "
 "unchanged. Nonetheless UEFI is intended to one day completely replace the "
 "old PC BIOS without being fully backwards-compatible and there are already a "
-"few systems with UEFI but without CSM."
+"lot of systems with UEFI but without CSM."
 msgstr ""
 "Actuellement, la majoritÃ© des systÃ¨mes PC qui utilisent l'UEFI intÃ¨grent "
 "aussi un module de compatibilitÃ© (<quote>Compatibility Support Module</"
@@ -2515,14 +2944,14 @@
 "rÃ©trocompatible, et il existe dÃ©jÃ  certains systÃ¨mes avec UEFI mais sans CSM."
 
 #. Tag: para
-#: preparing.xml:1582
+#: preparing.xml:1795
 #, no-c-format
 msgid ""
 "On systems with UEFI there are a few things to take into consideration when "
 "installing an operating system. The way the firmware loads an operating "
 "system is fundamentally different between the classic BIOS (or UEFI in CSM "
 "mode) and native UEFI. One major difference is the way the harddisk "
-"partitions get recorded on the harddisk. While the classic BIOS and UEFI in "
+"partitions are recorded on the harddisk. While the classic BIOS and UEFI in "
 "CSM mode use a DOS partition table, native UEFI uses a different "
 "partitioning scheme called <quote>GUID Partition Table</quote> (GPT). On a "
 "single disk, for all practical purposes only one of the two can be used and "
@@ -2531,10 +2960,10 @@
 "from a disk with GPT is only possible in native UEFI mode, but using GPT "
 "becomes more and more common as hard disk sizes grow, because the classic "
 "DOS partition table cannot address disks larger than about 2 Terabytes while "
-"GPT allows for by far larger disks. The other major difference between BIOS "
-"(or UEFI in CSM mode) and native UEFI is from where boot code is loaded and "
-"in which format it has to be, so that different bootloaders are needed for "
-"both systems."
+"GPT allows for far larger disks. The other major difference between BIOS (or "
+"UEFI in CSM mode) and native UEFI is the location where boot code is stored "
+"and in which format it has to be. This means that different bootloaders are "
+"needed for each system."
 msgstr ""
 "Sur les systÃ¨mes avec UEFI, il y a certains dÃ©tails Ã  prendre en compte "
 "lorsqu'on installe un systÃ¨me d'exploitation. La faÃ§on dont le "
@@ -2556,7 +2985,7 @@
 "diffÃ©rents sont utilisÃ©s pour chaque systÃ¨me."
 
 #. Tag: para
-#: preparing.xml:1602
+#: preparing.xml:1815
 #, no-c-format
 msgid ""
 "The latter becomes important when booting &d-i; on a UEFI system with CSM "
@@ -2590,7 +3019,7 @@
 "UEFI natif."
 
 #. Tag: para
-#: preparing.xml:1618
+#: preparing.xml:1831
 #, no-c-format
 msgid ""
 "Another UEFI-related topic is the so-called <quote>secure boot</quote> "
@@ -2602,10 +3031,10 @@
 "Microsoft used for signing the Windows bootloader. As the boot code used by "
 "&d-i; is not signed by Microsoft, booting the installer requires prior "
 "deactivation of secure boot in case it is enabled. Secure boot is often "
-"enabled by default on systems that come preinstalled with a 64Bit version of "
-"Windows 8 and there is unfortunately no standard where in the UEFI setup it "
-"can be disabled. On some systems, the option to disable secure boot is only "
-"made visible when a BIOS password has been set by the user, so if you have a "
+"enabled by default on systems that come preinstalled with a 64-bit version "
+"of Windows 8 and there is unfortunately no standard way to disable it in the "
+"UEFI setup. On some systems, the option to disable secure boot is only made "
+"visible when a BIOS password has been set by the user, so if you have a "
 "system with secure boot enabled, but cannot find an option to disable it, "
 "try setting a BIOS password, powercycle the machine and look again for an "
 "appropriate option."
@@ -2631,28 +3060,28 @@
 "nouveau une option appropriÃ©e."
 
 #. Tag: title
-#: preparing.xml:1640
+#: preparing.xml:1853
 #, no-c-format
 msgid "Disabling the Windows 8 <quote>fast boot</quote> feature"
 msgstr "DÃ©sactiver le dÃ©marrage rapide de WindowsÂ 8 (<quote>fast boot</quote>)"
 
 #. Tag: para
-#: preparing.xml:1641
+#: preparing.xml:1854
 #, no-c-format
 msgid ""
-"Windows 8 offers a feature called <quote>fast boot</quote> to cut down the "
-"time needed to boot itself. Technically, when this feature is enabled, "
-"Windows 8 does not do a real shutdown and a real cold boot afterwards when "
-"ordered to shut down, but instead does something resembling a partial "
-"suspend to disk to reduce the <quote>boot</quote> time. As long as Windows 8 "
-"is the only operating system on the machine, this is unproblematic, but it "
-"can result in problems and data loss when you have a dual boot setup in "
-"which another operating system accesses the same filesystems as Windows 8 "
-"does. In that case the real state of the filesystem can be different from "
-"what Windows 8 believes it to be after the <quote>boot</quote> and this "
-"could cause filesystem corruption upon further write accesses to the "
-"filesystem. Therefore in a dual boot setup, to avoid filesystem corruption "
-"the <quote>fast boot</quote> feature has to be disabled within Windows."
+"Windows 8 offers a feature called <quote>fast boot</quote> to cut down "
+"system startup time. Technically, when this feature is enabled, Windows 8 "
+"does not do a real shutdown and a real cold boot afterwards when ordered to "
+"shut down, but instead does something resembling a partial suspend to disk "
+"to reduce the <quote>boot</quote> time. As long as Windows 8 is the only "
+"operating system on the machine, this is unproblematic, but it can result in "
+"problems and data loss when you have a dual boot setup in which another "
+"operating system accesses the same filesystems as Windows 8 does. In that "
+"case the real state of the filesystem can be different from what Windows 8 "
+"believes it to be after the <quote>boot</quote> and this could cause "
+"filesystem corruption upon further write accesses to the filesystem. "
+"Therefore in a dual boot setup, to avoid filesystem corruption the "
+"<quote>fast boot</quote> feature has to be disabled within Windows."
 msgstr ""
 "WindowsÂ 8 offre une fonctionnalitÃ© appelÃ©e dÃ©marrage rapide (<quote>fast "
 "boot</quote>) pour rÃ©duire le temps de dÃ©marrage. Techniquement, lorsque "
@@ -2671,20 +3100,39 @@
 "corruption du systÃ¨me de fichiers, la fonctionnalitÃ© <quote>fast boot</"
 "quote> doit Ãªtre dÃ©sactivÃ©e depuis Windows."
 
+#. Tag: para
+#: preparing.xml:1870
+#, no-c-format
+msgid ""
+"It may also be necessary to disable <quote>fast boot</quote> to even allow "
+"access to UEFI setup to choose to boot another operating system or &d-i;. On "
+"some UEFI systems, the firmware will reduce <quote>boot</quote> time by not "
+"initialising the keyboard controller or USB hardware; in these cases, it is "
+"necessary to boot into Windows and disable this feature to allow for a "
+"change of boot order."
+msgstr ""
+"Il peut aussi Ãªtre nÃ©cessaire de dÃ©sactiver la fonction <quote>fast boot</"
+"quote> pour permettre l'accÃ¨s Ã  la configuration UEFI et choisir d'amorcer "
+"un autre systÃ¨me d'exploitation ou l'&d-i;. Sur certains systÃ¨mes UEFI, le "
+"microcode peut rÃ©duire la durÃ©e du <quote>boot</quote> en n'initialisant pas "
+"le contrÃ´leur de clavier ou le matÃ©riel USB. Dans ce cas, il est nÃ©cessaire "
+"de dÃ©marrer Windows po dÃ©sactiver cette fonctionnalitÃ© et autoriser un "
+"changement de l'ordre d'amorÃ§age."
+
 #. Tag: title
-#: preparing.xml:1659
+#: preparing.xml:1882
 #, no-c-format
 msgid "Hardware Issues to Watch Out For"
 msgstr "ProblÃ¨mes matÃ©riels Ã  surveiller"
 
 #. Tag: title
-#: preparing.xml:1662
+#: preparing.xml:1885
 #, no-c-format
 msgid "USB BIOS support and keyboards"
 msgstr "BIOS et Claviers USB"
 
 #. Tag: para
-#: preparing.xml:1663
+#: preparing.xml:1886
 #, no-c-format
 msgid ""
 "If you have no PS/2-style keyboard, but only a USB model, on some very old "
@@ -2704,13 +3152,13 @@
 "support&nbsp;Â»."
 
 #. Tag: title
-#: preparing.xml:1676
+#: preparing.xml:1899
 #, no-c-format
 msgid "Display-visibility on OldWorld Powermacs"
 msgstr "ProblÃ¨mes d'affichage sur OldWorld Powermacs"
 
 #. Tag: para
-#: preparing.xml:1678
+#: preparing.xml:1901
 #, no-c-format
 msgid ""
 "Some OldWorld Powermacs, most notably those with the <quote>control</quote> "

# French translation of the Debian Installer Manual
# Philippe Batailler - ?-2013
# Baptiste Jammet - 2014
#
msgid ""
msgstr ""
"Project-Id-Version: preparing\n"
"Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n"
"POT-Creation-Date: 2015-04-15 20:29+0000\n"
"PO-Revision-Date: 2015-04-20 15:16+0100\n"
"Last-Translator: Baptiste Jammet <baptiste@mailoo.org>\n"
"Language-Team: debian-l10n-french <debian-l10n-french@lists.debian.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: Poedit 1.5.4\n"

#. Tag: title
#: preparing.xml:5
#, no-c-format
msgid "Before Installing &debian-gnu;"
msgstr "Avant d'installer &debian-gnu;"

#. Tag: para
#: preparing.xml:6
#, no-c-format
msgid ""
"This chapter deals with the preparation for installing &debian; before you "
"even boot the installer. This includes backing up your data, gathering "
"information about your hardware, and locating any necessary information."
msgstr ""
"Ce chapitre traite de la prÃ©paration nÃ©cessaire Ã  l'installation d'un "
"systÃ¨me &debian;, avant mÃªme tout amorÃ§age de l'installateur. Cela concerne "
"la sauvegarde des donnÃ©es, la connaissance de votre matÃ©riel et des "
"informations nÃ©cessaires."

#. Tag: title
#: preparing.xml:19
#, no-c-format
msgid "Overview of the Installation Process"
msgstr "Vue gÃ©nÃ©rale du processus d'installation"

#. Tag: para
#: preparing.xml:20
#, no-c-format
msgid ""
"First, just a note about re-installations. With &debian;, a circumstance "
"that will require a complete re-installation of your system is very rare; "
"perhaps mechanical failure of the hard disk would be the most common case."
msgstr ""
"D'abord, une note au sujet des rÃ©installations. Avec &debian;, il est trÃ¨s "
"rare d'avoir Ã  rÃ©installer complÃ¨tement son systÃ¨me. La cause la plus "
"commune d'une rÃ©installation est sans doute une dÃ©faillance mÃ©canique du "
"disque dur."

#. Tag: para
#: preparing.xml:27
#, no-c-format
msgid ""
"Many common operating systems may require a complete installation to be "
"performed when critical failures take place or for upgrades to new OS "
"versions. Even if a completely new installation isn't required, often the "
"programs you use must be re-installed to operate properly in the new OS."
msgstr ""
"Beaucoup de systÃ¨mes d'exploitation nÃ©cessitent une installation complÃ¨te "
"quand des erreurs critiques se produisent ou lors d'une mise Ã  jour du "
"systÃ¨me. Et mÃªme s'il n'est pas nÃ©cessaire de refaire entiÃ¨rement une "
"installation, les programmes que vous utilisez doivent Ãªtre rÃ©installÃ©s pour "
"fonctionner correctement."

#. Tag: para
#: preparing.xml:35
#, no-c-format
msgid ""
"Under &debian-gnu;, it is much more likely that your OS can be repaired "
"rather than replaced if things go wrong. Upgrades never require a wholesale "
"installation; you can always upgrade in-place. And the programs are almost "
"always compatible with successive OS releases. If a new program version "
"requires newer supporting software, the &debian; packaging system ensures "
"that all the necessary software is automatically identified and installed. "
"The point is, much effort has been put into avoiding the need for re-"
"installation, so think of it as your very last option. The installer is "
"<emphasis>not</emphasis> designed to re-install over an existing system."
msgstr ""
"Avec &debian-gnu;, quand les choses tournent mal, vous devrez sans doute "
"rÃ©parer le systÃ¨me, mais pas le remplacer entiÃ¨rement. Les mises Ã  jour "
"n'exigent jamais une installation complÃ¨te&nbsp;; vous pouvez toujours les "
"faire Ã  partir du systÃ¨me existant. Les programmes sont presque toujours "
"compatibles avec les versions successives du systÃ¨me. Quand la nouvelle "
"version d'un programme exige d'autres logiciels, le systÃ¨me de gestion des "
"paquets fait en sorte que tous les logiciels nÃ©cessaires soient listÃ©s et "
"installÃ©s. Beaucoup d'efforts ont Ã©tÃ© dÃ©ployÃ©s pour Ã©viter le besoin d'une "
"rÃ©installation&nbsp;: c'est la derniÃ¨re option&nbsp;! Et l'installateur "
"<emphasis>n'est pas</emphasis> conÃ§u pour procÃ©der Ã  une installation sur un "
"systÃ¨me existant."

#. Tag: para
#: preparing.xml:48
#, no-c-format
msgid ""
"Here's a road map for the steps you will take during the installation "
"process."
msgstr "Voici les Ã©tapes qui composent le processus d'installation&nbsp;:"

#. Tag: para
#: preparing.xml:56
#, no-c-format
msgid ""
"Back up any existing data or documents on the hard disk where you plan to "
"install."
msgstr ""
"sauvegarder toutes les donnÃ©es du disque dur sur lequel l'installation sera "
"faite&nbsp;;"

#. Tag: para
#: preparing.xml:62
#, no-c-format
msgid ""
"Gather information about your computer and any needed documentation, before "
"starting the installation."
msgstr ""
"rassembler les informations concernant l'ordinateur, ainsi que la "
"documentation nÃ©cessaire&nbsp;;"

#. Tag: para
#: preparing.xml:68
#, no-c-format
msgid "Create partitionable space for &debian; on your hard disk."
msgstr "prÃ©parer de l'espace libre sur le disque dur&nbsp;;"

#. Tag: para
#: preparing.xml:73
#, no-c-format
msgid ""
"Locate and/or download the installer software and any specialized driver or "
"firmware files your machine requires."
msgstr ""
"tÃ©lÃ©charger l'installateur et tous les pilotes et microprogrammes "
"nÃ©cessaires&nbsp;;"

#. Tag: para
#: preparing.xml:79
#, no-c-format
msgid ""
"Set up boot media such as CDs/DVDs/USB sticks or provide a network boot "
"infrastructure from which the installer can be booted."
msgstr ""
"prÃ©parer les pÃ©riphÃ©riques d'amorÃ§age, CD, DVD, clÃ© USB, ou prÃ©parer un "
"systÃ¨me d'amorÃ§age par le rÃ©seau pour amorcer l'installateur&nbsp;;"

#. Tag: para
#: preparing.xml:85
#, no-c-format
msgid "Boot the installation system."
msgstr "amorcer l'installateur&nbsp;;"

#. Tag: para
#: preparing.xml:90
#, no-c-format
msgid "Select the installation language."
msgstr "choisir une langue&nbsp;;"

#. Tag: para
#: preparing.xml:95
#, no-c-format
msgid "Activate the ethernet network connection, if available."
msgstr "si nÃ©cessaire, mettre en place la connexion rÃ©seau par ethernet&nbsp;;"

#. Tag: para
#: preparing.xml:101
#, no-c-format
msgid "Configure one network interface."
msgstr "configurer une interface rÃ©seau&nbsp;;"

#. Tag: para
#: preparing.xml:106
#, no-c-format
msgid "Open an ssh connection to the new system."
msgstr "ouvrir une connexion ssh vers le nouveau systÃ¨me&nbsp;;"

#. Tag: para
#: preparing.xml:111
#, no-c-format
msgid "Attach one or more DASDs (Direct Access Storage Device)."
msgstr ""
"attacher un ou plusieurs DASD (<emphasis>Direct Access Storage Device)</"
"emphasis>&nbsp;;"

#. Tag: para
#: preparing.xml:117
#, no-c-format
msgid ""
"If necessary, resize existing partitions on your target harddisk to make "
"space for the installation."
msgstr ""
"si nÃ©cessaire, redimensionner les partitions du disque dur pour faire de la "
"place pour l'installationÂ ;"

#. Tag: para
#: preparing.xml:122
#, no-c-format
msgid "Create and mount the partitions on which &debian; will be installed."
msgstr ""
"crÃ©er et monter les partitions sur lesquelles &debian; sera installÃ©e&nbsp;;"

#. Tag: para
#: preparing.xml:127
#, no-c-format
msgid ""
"Watch the automatic download/install/setup of the <firstterm>base system</"
"firstterm>."
msgstr ""
"attendre la fin du processus automatique de tÃ©lÃ©chargement/installation/"
"configuration du <firstterm>systÃ¨me de base</firstterm>&nbsp;;"

#. Tag: para
#: preparing.xml:133
#, no-c-format
msgid ""
"Install a <firstterm>boot loader</firstterm> which can start up &debian-gnu; "
"and/or your existing system."
msgstr ""
"installer un <firstterm>programme d'amorÃ§age</firstterm> qui puisse dÃ©marrer "
"&debian-gnu; ou un autre systÃ¨me&nbsp;;"

#. Tag: para
#: preparing.xml:139
#, no-c-format
msgid "Load the newly installed system for the first time."
msgstr "charger le nouveau systÃ¨me pour la premiÃ¨re fois."

#. Tag: para
#: preparing.xml:146
#, no-c-format
msgid ""
"For &arch-title; you have the option of using <phrase arch=\"any-x86\">a</"
"phrase> <phrase arch=\"powerpc\">an experimental</phrase> graphical version "
"of the installation system. For more information about this graphical "
"installer, see <xref linkend=\"graphical\"/>."
msgstr ""
"Sur &arch-title; il est possible d'utiliser la version graphique <phrase "
"arch=\"powerpc\">expÃ©rimentale </phrase>du systÃ¨me d'installation. Pour "
"d'autres informations sur cette mÃ©thode d'installation, voyez la <xref "
"linkend=\"graphical\"/>."

#. Tag: para
#: preparing.xml:154
#, no-c-format
msgid ""
"If you have problems during the installation, it helps to know which "
"packages are involved in which steps. Introducing the leading software "
"actors in this installation drama:"
msgstr ""
"ConnaÃ®tre les paquets qui sont impliquÃ©s dans chaque Ã©tape peut aider Ã  la "
"rÃ©solution des problÃ¨mes qui peuvent se produire durant l'installation. "
"Voici les principaux acteurs de cette piÃ¨ce&nbsp;:"

#. Tag: para
#: preparing.xml:160
#, no-c-format
msgid ""
"The installer software, <classname>debian-installer</classname>, is the "
"primary concern of this manual. It detects hardware and loads appropriate "
"drivers, uses <classname>dhcp-client</classname> to set up the network "
"connection, runs <classname>debootstrap</classname> to install the base "
"system packages, and runs <classname>tasksel</classname> to allow you to "
"install certain additional software. Many more actors play smaller parts in "
"this process, but <classname>debian-installer</classname> has completed its "
"task when you load the new system for the first time."
msgstr ""
"L'<classname>installateur &debian;</classname> est le sujet principal de ce "
"manuel. Il dÃ©tecte le matÃ©riel et charge les pilotes nÃ©cessaires, il met en "
"place la connexion au rÃ©seau avec <classname>dhcp-client</classname>, il "
"installe les paquets du systÃ¨me de base avec <classname>debootstrap</"
"classname> et il lance <classname>tasksel</classname> pour vous permettre "
"d'installer d'autres logiciels. Il y a bien d'autres acteurs mineurs, mais "
"l'<classname>installateur &debian;</classname> a terminÃ© sa tÃ¢che quand vous "
"dÃ©marrez pour la premiÃ¨re fois le nouveau systÃ¨me."

#. Tag: para
#: preparing.xml:172
#, no-c-format
msgid ""
"To tune the system to your needs, <classname>tasksel</classname> allows you "
"to choose to install various predefined bundles of software like a Web "
"server or a Desktop environment."
msgstr ""
"Pour installer ce dont vous avez besoin, vous disposez du programme "
"<classname>tasksel</classname> qui peut installer des ensembles thÃ©matiques "
"de paquets, comme par exemple un serveur web ou un environnement de bureau."

#. Tag: para
#: preparing.xml:178
#, no-c-format
msgid ""
"One important option during the installation is whether or not to install a "
"graphical desktop environment, consisting of the X Window System and one of "
"the available graphical desktop environments. If you choose not to select "
"the <quote>Desktop environment</quote> task, you will only have a relatively "
"basic, command line driven system. Installing the Desktop environment task "
"is optional because in relation to a text-mode-only system it requires a "
"comparatively large amount of disk space and because many &debian-gnu; "
"systems are servers which don't really have any need for a graphical user "
"interface to do their job."
msgstr ""
"Une option importante lors de l'installation est d'installer ou non un "
"environnement de bureau avec le systÃ¨me XÂ Window. Si vous n'avez pas choisi "
"la tÃ¢che <quote>Desktop environment</quote>, vous aurez un systÃ¨me minimal "
"avec ligne de commande. L'installation d'un environnement de bureau est "
"facultative car cela demande beaucoup plus d'espace disque que "
"l'installation en mode texte. D'autre part, beaucoup de systÃ¨mes &debian; "
"sont des serveurs qui n'ont pas vraiment besoin d'une interface graphique "
"pour Ãªtre opÃ©rationnels."

#. Tag: para
#: preparing.xml:191
#, no-c-format
msgid ""
"Just be aware that the X Window System is completely separate from "
"<classname>debian-installer</classname>, and in fact is much more "
"complicated. Troubleshooting of the X Window System is not within the scope "
"of this manual."
msgstr ""
"Notez que l'installateur et le systÃ¨me XÂ Window sont distincts. Les "
"problÃ¨mes liÃ©s Ã  ce dernier ne sont pas du ressort de ce manuel."

#. Tag: title
#: preparing.xml:206
#, no-c-format
msgid "Back Up Your Existing Data!"
msgstr "Sauvegardez vos donnÃ©es&nbsp;!"

#. Tag: para
#: preparing.xml:207
#, no-c-format
msgid ""
"Before you start, make sure to back up every file that is now on your "
"system. If this is the first time a non-native operating system is going to "
"be installed on your computer, it is quite likely you will need to re-"
"partition your disk to make room for &debian-gnu;. Anytime you partition "
"your disk, you run a risk of losing everything on the disk, no matter what "
"program you use to do it. The programs used in the installation are quite "
"reliable and most have seen years of use; but they are also quite powerful "
"and a false move can cost you. Even after backing up, be careful and think "
"about your answers and actions. Two minutes of thinking can save hours of "
"unnecessary work."
msgstr ""
"Avant de commencer, assurez-vous d'avoir effectuÃ© une sauvegarde de tous les "
"fichiers qui se trouvent sur votre systÃ¨me. Si c'est la premiÃ¨re fois que "
"vous installez un autre systÃ¨me d'exploitation sur votre machine, il est "
"probable que vous devrez repartitionner votre disque dur afin de faire de la "
"place pour &debian-gnu;. Ã? chaque partitionnement, il y a un risque de "
"perdre toutes les donnÃ©es du disque, quel que soit le programme utilisÃ© pour "
"cette opÃ©ration. Les programmes utilisÃ©s Ã  l'installation sont assez fiables "
"et la plupart ont Ã©tÃ© utilisÃ©s pendant des annÃ©es, mais ils sont trÃ¨s "
"puissants et un faux mouvement peut vous coÃ»ter cher. MÃªme aprÃ¨s la "
"sauvegarde, soyez attentif et rÃ©flÃ©chissez Ã  vos rÃ©ponses. Deux minutes de "
"rÃ©flexion peuvent vous Ã©pargner des heures de travail."

#. Tag: para
#: preparing.xml:220
#, no-c-format
msgid ""
"If you are creating a multi-boot system, make sure that you have the "
"distribution media of any other present operating systems on hand. Even "
"though this is normally not necessary, there might be situations in which "
"you could be required to reinstall your operating system's boot loader to "
"make the system boot or in a worst case even have to reinstall the complete "
"operating system and restore your previously made backup."
msgstr ""
"Si vous voulez pouvoir amorcer plusieurs systÃ¨mes, assurez-vous de disposer "
"du support de distribution des autres systÃ¨mes d'exploitation prÃ©sents. Dans "
"quelques rares situations, vous pouvez Ãªtre amenÃ© Ã  rÃ©installer le programme "
"d'amorÃ§age de votre systÃ¨me d'exploitation, ou mÃªme, Ã  rÃ©installer "
"complÃ¨tement le systÃ¨me d'exploitation et restaurer vos donnÃ©es Ã  partir de "
"la sauvegarde que vous avez effectuÃ©e."

#. Tag: title
#: preparing.xml:239
#, no-c-format
msgid "Information You Will Need"
msgstr "Informations utiles"

#. Tag: title
#: preparing.xml:242
#, no-c-format
msgid "Documentation"
msgstr "La documentation"

#. Tag: title
#: preparing.xml:245
#, no-c-format
msgid "Installation Manual"
msgstr "Le manuel d'installation"

#. Tag: para
#: preparing.xml:247
#, no-c-format
msgid "This document you are now reading, in plain ASCII, HTML or PDF format."
msgstr "Le document que vous lisez, au format texte, HTML ou PDF."

#. Tag: itemizedlist
#: preparing.xml:253
#, no-c-format
msgid "&list-install-manual-files;"
msgstr "&list-install-manual-files;"

#. Tag: para
#: preparing.xml:259
#, no-c-format
msgid ""
"The document you are now reading, which is the official version of the "
"Installation Guide for the &releasename; release of &debian;; available in "
"<ulink url=\"&url-release-area;/installmanual\">various formats and "
"translations</ulink>."
msgstr ""
"Le document que vous lisez est la version officielle du manuel "
"d'installation pour la distribution &debian; &releasename;&nbsp;; des <ulink "
"url=\"&url-release-area;/installmanual\">traductions</ulink> sont "
"disponibles dans diffÃ©rents formats."

#. Tag: para
#: preparing.xml:268
#, no-c-format
msgid ""
"The document you are now reading, which is a development version of the "
"Installation Guide for the next release of &debian;; available in <ulink url="
"\"&url-d-i-alioth-manual;\">various formats and translations</ulink>."
msgstr ""
"Le document que vous lisez est la version de dÃ©veloppement du manuel "
"d'installation pour la prochaine distribution &debian;. Des <ulink url="
"\"&url-d-i-alioth-manual;\">traductions</ulink> sont disponibles dans "
"diffÃ©rents formats."

#. Tag: title
#: preparing.xml:280
#, no-c-format
msgid "Hardware documentation"
msgstr "La documentation du matÃ©riel"

#. Tag: para
#: preparing.xml:281
#, no-c-format
msgid ""
"Often contains useful information on configuring or using your hardware."
msgstr ""
"Elle contient souvent des informations utiles pour l'utilisation et la "
"configuration de votre matÃ©riel."

#. Tag: ulink
#: preparing.xml:292
#, no-c-format
msgid "The Debian Wiki hardware page"
msgstr "La page Â«Â MatÃ©rielÂ Â» sur le wiki Debian\""

#. Tag: ulink
#: preparing.xml:298
#, no-c-format
msgid "Linux for SPARC Processors FAQ"
msgstr "FAQ pour les processeurs SPARC sous Linux"

#. Tag: ulink
#: preparing.xml:304
#, no-c-format
msgid "Linux/Mips website"
msgstr "Site web Linux/Mips"

#. Tag: title
#: preparing.xml:313
#, no-c-format
msgid "&arch-title; Hardware References"
msgstr "RÃ©fÃ©rences pour le matÃ©riel &arch-title;"

#. Tag: para
#: preparing.xml:314
#, no-c-format
msgid ""
"Documentation of &arch-title;-specific boot sequence, commands and device "
"drivers (e.g. DASD, XPRAM, Console, OSA, HiperSockets and z/VM interaction)"
msgstr ""
"Documentation sur la sÃ©quence de dÃ©marrage spÃ©cifique Ã  &arch-title;, ainsi "
"que sur les commandes et pilotes de pÃ©riphÃ©riques (par exemple, DASD, XPRAM, "
"Console, OSA, HiperSockets et interaction z/VM)."

#. Tag: ulink
#: preparing.xml:325
#, no-c-format
msgid "Device Drivers, Features, and Commands (Linux Kernel 3.2)"
msgstr "Pilotes de pÃ©riphÃ©riques, spÃ©cificitÃ©s et commandes (noyau LinuxÂ 3.2)"

#. Tag: para
#: preparing.xml:330
#, no-c-format
msgid ""
"IBM Redbook describing how Linux can be combined with z/VM on zSeries and "
"&arch-title; hardware."
msgstr ""
"Le livre rouge d'IBM dÃ©crit comment combiner Linux avec z/VM sur matÃ©riel "
"zSeries et &arch-title;."

#. Tag: ulink
#: preparing.xml:340
#, no-c-format
msgid "Linux for &arch-title;"
msgstr "Linux pour &arch-title;"

#. Tag: para
#: preparing.xml:346
#, no-c-format
msgid ""
"IBM Redbook describing the Linux distributions available for the mainframe. "
"It has no chapter about &debian; but the basic installation concepts are the "
"same across all &arch-title; distributions."
msgstr ""
"Le livre rouge d'IBM indique les distributions Linux disponibles sur un "
"serveur <emphasis>mainframe</emphasis>. Il n'a pas de chapitre spÃ©cifique Ã  "
"&debian;, mais les concepts de base pour l'installation sont les mÃªmes pour "
"toutes les distributions sur &arch-title;&nbsp;;"

#. Tag: ulink
#: preparing.xml:357
#, no-c-format
msgid "Linux for IBM eServer zSeries and &arch-title;: Distributions"
msgstr "Linux pour IBM eServer zSeries et distributions &arch-title;"

#. Tag: title
#: preparing.xml:367
#, no-c-format
msgid "Finding Sources of Hardware Information"
msgstr "Comment trouver les sources d'informations sur le matÃ©rielÂ ?"

#. Tag: para
#: preparing.xml:368
#, no-c-format
msgid ""
"In many cases, the installer will be able to automatically detect your "
"hardware. But to be prepared, we do recommend familiarizing yourself with "
"your hardware before the install."
msgstr ""
"La plupart du temps, l'installateur dÃ©tectera automatiquement votre "
"matÃ©riel. Mais nous vous conseillons de bien connaÃ®tre votre matÃ©riel avant "
"de commencer l'installation."

#. Tag: para
#: preparing.xml:374
#, no-c-format
msgid "Hardware information can be gathered from:"
msgstr "On peut trouver des informations sur plusieurs sources&nbsp;:"

#. Tag: para
#: preparing.xml:381
#, no-c-format
msgid "The manuals that come with each piece of hardware."
msgstr "les manuels accompagnant chaque Ã©lÃ©ment&nbsp;;"

#. Tag: para
#: preparing.xml:386
#, no-c-format
msgid ""
"The BIOS setup screens of your computer. You can view these screens when you "
"start your computer by pressing a combination of keys. Check your manual for "
"the combination. Often, it is the <keycap>Delete</keycap> or the <keycap>F2</"
"keycap> key, but some manufacturers use other keys or key combinations. "
"Usually upon starting the computer there will be a message stating which key "
"to press to enter the setup screen."
msgstr ""
"les Ã©crans de configuration du BIOS de votre ordinateur. Vous pouvez accÃ©der "
"Ã  ces Ã©crans pendant le dÃ©marrage de l'ordinateur en appuyant sur une "
"combinaison de touches. Consultez votre manuel pour connaÃ®tre cette "
"combinaison. Il s'agit souvent de la touche <keycap>Suppr</keycap> ou de la "
"touche <keycap>F2</keycap>. Cependant certains fabricants peuvent utiliser "
"d'autres touches. Le plus souvent, au dÃ©marrage de l'ordinateur, un message "
"indique la touche Ã  utiliser&nbsp;;"

#. Tag: para
#: preparing.xml:396
#, no-c-format
msgid "The cases and boxes for each piece of hardware."
msgstr "les boÃ®tes et cartons de chaque Ã©lÃ©ment&nbsp;;"

#. Tag: para
#: preparing.xml:402
#, no-c-format
msgid "The System window in the Windows Control Panel."
msgstr ""
"la fenÃªtre Â«&nbsp;SystÃ¨me&nbsp;Â» dans le panneau de configuration de "
"Windows&nbsp;;"

#. Tag: para
#: preparing.xml:408
#, no-c-format
msgid ""
"System commands or tools in another operating system, including file manager "
"displays. This source is especially useful for information about RAM and "
"hard drive memory."
msgstr ""
"les commandes systÃ¨me ou les outils d'un autre systÃ¨me d'exploitation, "
"incluant les affichages d'un gestionnaire de fichiers. Cette source est "
"particuliÃ¨rement utile pour trouver des informations sur la mÃ©moire vive et "
"les disques durs&nbsp;;"

#. Tag: para
#: preparing.xml:415
#, no-c-format
msgid ""
"Your system administrator or Internet Service Provider. These sources can "
"tell you the settings you need to set up your networking and e-mail."
msgstr ""
"votre administrateur systÃ¨me ou votre fournisseur d'accÃ¨s Ã  Internet. Ces "
"sources peuvent vous indiquer les rÃ©glages nÃ©cessaires Ã  la configuration du "
"rÃ©seau et du courrier Ã©lectronique."

#. Tag: title
#: preparing.xml:427
#, no-c-format
msgid "Hardware Information Helpful for an Install"
msgstr "Informations sur le matÃ©riel utiles pour l'installation"

#. Tag: entry
#: preparing.xml:431
#, no-c-format
msgid "Hardware"
msgstr "MatÃ©riel"

#. Tag: entry
#: preparing.xml:431
#, no-c-format
msgid "Information You Might Need"
msgstr "Informations dont vous pouvez avoir besoin"

#. Tag: entry
#: preparing.xml:437
#, no-c-format
msgid "Hard Drives"
msgstr "Disques durs"

#. Tag: entry
#: preparing.xml:438
#, no-c-format
msgid "How many you have."
msgstr "Leur nombre"

#. Tag: entry
#: preparing.xml:440
#, no-c-format
msgid "Their order on the system."
msgstr "Leur ordre dans le systÃ¨me"

#. Tag: entry
#: preparing.xml:442
#, no-c-format
msgid "Whether IDE (also known as PATA), SATA or SCSI."
msgstr "S'ils sont de type IDE (PATA), SATA ou SCSI"

#. Tag: entry
#: preparing.xml:444 preparing.xml:493
#, no-c-format
msgid "Available free space."
msgstr "L'espace disponible"

#. Tag: entry
#: preparing.xml:445
#, no-c-format
msgid "Partitions."
msgstr "Les partitions"

#. Tag: entry
#: preparing.xml:447
#, no-c-format
msgid "Partitions where other operating systems are installed."
msgstr "Les partitions contenant d'autres systÃ¨mes d'exploitation"

#. Tag: entry
#: preparing.xml:475
#, no-c-format
msgid "Network interfaces"
msgstr "Interfaces rÃ©seau"

#. Tag: entry
#: preparing.xml:476
#, no-c-format
msgid "Type/model of available network interfaces."
msgstr "Type/modÃ¨le des interfaces rÃ©seau disponibles"

#. Tag: entry
#: preparing.xml:480
#, no-c-format
msgid "Printer"
msgstr "Imprimante"

#. Tag: entry
#: preparing.xml:481
#, no-c-format
msgid "Model and manufacturer."
msgstr "Le modÃ¨le et la marque"

#. Tag: entry
#: preparing.xml:485
#, no-c-format
msgid "Video Card"
msgstr "Carte vidÃ©o"

#. Tag: entry
#: preparing.xml:486
#, no-c-format
msgid "Type/model and manufacturer."
msgstr "Le modÃ¨le et la marque"

#. Tag: entry
#: preparing.xml:490
#, no-c-format
msgid "DASD"
msgstr "DASD"

#. Tag: entry
#: preparing.xml:491
#, no-c-format
msgid "Device number(s)."
msgstr "NumÃ©ro du pÃ©riphÃ©rique"

#. Tag: entry
#: preparing.xml:496
#, no-c-format
msgid "Network"
msgstr "rÃ©seau"

#. Tag: entry
#: preparing.xml:497
#, no-c-format
msgid "Type of adapter."
msgstr "Le type d'interface"

#. Tag: entry
#: preparing.xml:499
#, no-c-format
msgid "Device numbers."
msgstr "NumÃ©ros des pÃ©riphÃ©riques"

#. Tag: entry
#: preparing.xml:500
#, no-c-format
msgid "Relative adapter number for OSA cards."
msgstr "NumÃ©ro de l'adaptateur associÃ© pour les cartes OSA"

#. Tag: title
#: preparing.xml:508
#, no-c-format
msgid "Hardware Compatibility"
msgstr "CompatibilitÃ© matÃ©rielle"

#. Tag: para
#: preparing.xml:510
#, no-c-format
msgid ""
"Many products work without trouble on &arch-kernel;. Moreover, hardware "
"support in &arch-kernel; is improving daily. However, &arch-kernel; still "
"does not run as many different types of hardware as some operating systems."
msgstr ""
"Beaucoup de produits fonctionnent sans problÃ¨me sous &arch-kernel;. La "
"gestion des matÃ©riels est amÃ©liorÃ©e chaque jour. Cependant, &arch-kernel; ne "
"peut pas utiliser autant de matÃ©riels que d'autres systÃ¨mes d'exploitation."

#. Tag: para
#: preparing.xml:516
#, no-c-format
msgid ""
"Drivers in &arch-kernel; in most cases are not written for a certain "
"<quote>product</quote> or <quote>brand</quote> from a specific manufacturer, "
"but for a certain hardware/chipset. Many seemingly different products/brands "
"are based on the same hardware design; it is not uncommon that chip "
"manufacturers provide so-called <quote>reference designs</quote> for "
"products based on their chips which are then used by several different "
"device manufacturers and sold under lots of different product or brand names."
msgstr ""
"Les pilotes pour &arch-kernel; ne sont pas Ã©crits pour tel ou tel produit de "
"tel ou tel constructeur mais pour tel matÃ©riel (puce). Beaucoup de produits "
"apparemment diffÃ©rents sont basÃ©s sur le mÃªme matÃ©riel. Il n'est pas "
"inhabituel que des constructeurs de puces fournissent de prÃ©tendues "
"Â«Â conceptions de rÃ©fÃ©renceÂ Â» pour des produits basÃ©s sur leurs puces qui "
"sont ensuite utilisÃ©es par plusieurs constructeurs diffÃ©rents et vendues "
"sous diffÃ©rentes marques."

#. Tag: para
#: preparing.xml:527
#, no-c-format
msgid ""
"This has advantages and disadvantages. An advantage is that a driver for one "
"chipset works with lots of different products from different manufacturers, "
"as long as their product is based on the same chipset. The disadvantage is "
"that it is not always easy to see which actual chipset is used in a certain "
"product/brand. Unfortunately sometimes device manufacturers change the "
"hardware base of their product without changing the product name or at least "
"the product version number, so that when having two items of the same brand/"
"product name bought at different times, they can sometimes be based on two "
"different chipsets and therefore use two different drivers or there might be "
"no driver at all for one of them."
msgstr ""
"Cette situation comporte des avantages et des inconvÃ©nients. Un avantage est "
"qu'un pilote de puce fonctionne pour diffÃ©rents produits de diffÃ©rents "
"constructeurs. Le problÃ¨me est qu'il n'est pas toujours facile de savoir "
"quelle puce est rÃ©ellement utilisÃ©e par tel produit. Parfois les "
"constructeurs modifient le matÃ©riel d'un produit sans changer ni le nom ni "
"la version de ce produit. Ainsi, deux exemplaires d'un mÃªme produit, achetÃ©s "
"Ã  diffÃ©rents moments, peuvent Ãªtre basÃ©s sur deux puces diffÃ©rentes et donc "
"utiliser deux pilotes diffÃ©rents. Il se peut alors qu'aucun pilote ne soit "
"disponible pour l'une des deux puces."

#. Tag: para
#: preparing.xml:540
#, no-c-format
msgid ""
"For USB and PCI/PCI-Express/ExpressCard devices, a good way to find out on "
"which chipset they are based is to look at their device IDs. All USB/PCI/PCI-"
"Express/ExpressCard devices have so called <quote>vendor</quote> and "
"<quote>product</quote> IDs, and the combination of these two is usually the "
"same for any product based on the same chipset."
msgstr ""
"Pour les pÃ©riphÃ©riques USB et PCI/PCI-Express/ExpressCard, un bon moyen de "
"connaÃ®tre la puce utilisÃ©e est de chercher les identifiants du pÃ©riphÃ©rique. "
"La combinaison de ces identifiants nommÃ©s Â«Â vendorÂ Â» et Â«Â productÂ Â» est "
"habituellement la mÃªme pour tout produit basÃ© sur la mÃªme puce."

#. Tag: para
#: preparing.xml:548
#, no-c-format
msgid ""
"On Linux systems, these IDs can be read with the <command>lsusb</command> "
"command for USB devices and with the <command>lspci -nn</command> command "
"for PCI/PCI-Express/ExpressCard devices. The vendor and product IDs are "
"usually given in the form of two hexadecimal numbers, seperated by a colon, "
"such as <quote>1d6b:0001</quote>."
msgstr ""
"Sur un systÃ¨me Linux, ces identifiants peuvent Ãªtre lus par la commande "
"<command>lsusb</command> pour les pÃ©riphÃ©riques USB et par la commande "
"<command>lspci -nn</command> pour les pÃ©riphÃ©riques PCI/PCI-Express/"
"ExpressCard. Ils sont gÃ©nÃ©ralement donnÃ©s sous la forme de deux nombres "
"hexadÃ©cimaux, sÃ©parÃ©s par un deux-points, Â«Â 1d6b:0001Â Â» par exemple."

#. Tag: para
#: preparing.xml:556
#, no-c-format
msgid ""
"An example for the output of <command>lsusb</command>: <quote>Bus 001 Device "
"001: ID 1d6b:0002 Linux Foundation 2.0 root hub</quote>, whereby 1d6b is the "
"vendor ID and 0002 is the product ID."
msgstr ""
"RÃ©sultat de la commande <command>lsusb</command>Â : \"Bus 001 Device 001: ID "
"1d6b:0002 Linux Foundation 2.0 root hub\", oÃ¹ 1d6b est l'identifiant "
"Â«Â vendorÂ Â» et 0002 l'identifiant Â«Â productÂ Â»."

#. Tag: para
#: preparing.xml:562
#, no-c-format
msgid ""
"An example for the output of <command>lspci -nn</command> for an Ethernet "
"card: <quote>03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., "
"Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev "
"06)</quote>. The IDs are given inside the rightmost square brackets, i.e. "
"here 10ec is the vendor- and 8168 is the product ID."
msgstr ""
"RÃ©sultat de la commande <command>lspci -nn</command> pour une carte "
"ethernetÂ : \"03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., "
"Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev "
"06)\". Les identifiants sont donnÃ©s dans les crochets les plus Ã  droite, "
"10ec le Â«Â vendorÂ Â» et 8168 le Â«Â productÂ Â»."

#. Tag: para
#: preparing.xml:570
#, no-c-format
msgid ""
"As another example, a graphics card could give the following output: "
"<quote>04:00.0 VGA compatible controller [0300]: Advanced Micro Devices "
"[AMD] nee ATI RV710 [Radeon HD 4350] [1002:954f]</quote>."
msgstr ""
"Un exemple pour une carte graphiqueÂ : \"04:00.0 VGA compatible controller "
"[0300]: Advanced Micro Devices [AMD] nee ATI RV710 [Radeon HD 4350] "
"[1002:954f]\"."

#. Tag: para
#: preparing.xml:576
#, no-c-format
msgid ""
"On Windows systems, the IDs for a device can be found in the Windows device "
"manager on the tab <quote>details</quote>, where the vendor ID is prefixed "
"with VEN_ and the product ID is prefixed with DEV_. On Windows 7 systems, "
"you have to select the property <quote>Hardware IDs</quote> in the device "
"manager's details tab to actually see the IDs, as they are not displayed by "
"default."
msgstr ""
"Sur les systÃ¨mes Windows, les identifiants d'un pÃ©riphÃ©rique peuvent Ãªtre "
"trouvÃ©s dans le gestionnaire de pÃ©riphÃ©riques, onglet Â«Â detailsÂ Â». "
"L'identifiant Â«Â vendorÂ Â» est prÃ©fixÃ© par VEN_ et Â«Â productÂ Â» par DEV_. Sur "
"les systÃ¨mes WindowsÂ 7, vous devez sÃ©lectionner la propriÃ©tÃ© Â«Â Hardware IDs "
"Â» dans l'onglet Â«Â detailsÂ Â» du gestionnaire de pÃ©riphÃ©riques car ils ne sont "
"pas visibles par dÃ©faut."

#. Tag: para
#: preparing.xml:586
#, no-c-format
msgid ""
"Searching on the internet with the vendor/product ID, <quote>&arch-kernel;</"
"quote> and <quote>driver</quote> as the search terms often results in "
"information regarding the driver support status for a certain chipset. If a "
"search for the vendor/product ID does not yield usable results, a search for "
"the chip code names, which are also often provided by lsusb and lspci "
"(<quote>RTL8111</quote>/<quote>RTL8168B</quote> in the network card example "
"and <quote>RV710</quote> in the graphics card example), can help."
msgstr ""
"Une recherche sur Internet avec ces identifiants, &arch-kernel; et "
"Â«Â driverÂ Â» donne souvent des informations sur le pilote nÃ©cessaire Ã  telle "
"puce. Si ce n'est pas le cas, une recherche peut Ãªtre effectuÃ©e avec les "
"noms des puces, donnÃ©s aussi par les commandes lsusb et lspci, \"RTL8111\"/"
"\"RTL8168B\" pour la carte rÃ©seau et \"RV710\" pour la carte graphique des "
"prÃ©cÃ©dents exemples."

#. Tag: title
#: preparing.xml:599
#, no-c-format
msgid "Testing hardware compatibility with a Live-System"
msgstr "Tester le matÃ©riel avec un systÃ¨me autonome"

#. Tag: para
#: preparing.xml:601
#, no-c-format
msgid ""
"&debian-gnu; is also available as a so-called <quote>live system</quote> for "
"certain architectures. A live system is a preconfigured ready-to-use system "
"in a compressed format that can be booted and used from a read-only medium "
"like a CD or DVD. Using it by default does not create any permanent changes "
"on your computer. You can change user settings and install additional "
"programs from within the live system, but all this only happens in the "
"computer's RAM, i.e. if you turn off the computer and boot the live system "
"again, everything is reset to its defaults. If you want to see whether your "
"hardware is supported by &debian-gnu;, the easiest way is to run a &debian; "
"live system on it and try it out."
msgstr ""
"&debian-gnu; est disponible sous forme de systÃ¨me autonome pour quelques "
"architectures. Un systÃ¨me autonome est un systÃ¨me dans un format compressÃ©, "
"prÃ©configurÃ© et utilisable immÃ©diatement, qui peut Ãªtre amorcÃ© depuis un "
"support en lecture seule comme un CD ou un DVD. Son utilisation ne modifie "
"pas de faÃ§on permanente votre ordinateur. Vous pouvez modifier des "
"paramÃ¨tres, installer des programmes,Â etc., tout cela se passe dans la "
"mÃ©moire vive de l'ordinateur. Si vous Ã©teignez l'ordinateur et relancez le "
"systÃ¨me autonome, tout est remis en l'Ã©tat par dÃ©faut. ExÃ©cuter un systÃ¨me "
"autonome est le moyen le plus simple de savoir si votre matÃ©riel est reconnu "
"par &debian-gnu;."

#. Tag: para
#: preparing.xml:614
#, no-c-format
msgid ""
"There are a few limitations in using a live system. The first is that as all "
"changes you do within the live system must be held in your computer's RAM, "
"this only works on systems with enough RAM to do that, so installing "
"additional large software packages may fail due to memory constraints. "
"Another limitation with regards to hardware compatibility testing is that "
"the official &debian-gnu; live system contains only free components, i.e. "
"there are no non-free firmware files included in it. Such non-free packages "
"can of course be installed manually within the system, but there is no "
"automatic detection of required firmware files like in the &d-i;, so "
"installation of non-free components must be done manually if needed."
msgstr ""
"Un systÃ¨me autonome impose quelques limitations. La premiÃ¨re est que toutes "
"les modifications que vous apportez doivent Ãªtre contenues dans la mÃ©moire "
"vive de l'ordinateur. Il faut donc assez de mÃ©moire et l'installation de "
"certains logiciels peut Ã©chouer Ã  cause du manque de mÃ©moire. Une autre "
"limitation est que le systÃ¨me autonome officiel de &debian-gnu; ne contient "
"que des Ã©lÃ©ments libres. Des microprogrammes non libres peuvent bien sÃ»r "
"Ãªtre installÃ©s, mais aucune dÃ©tection automatique n'est effectuÃ©e comme "
"celle effectuÃ©e par l'installateur Debian. Vous devrez donc installer vous-"
"mÃªme les composants non libres."

#. Tag: para
#: preparing.xml:627
#, no-c-format
msgid ""
"Information about the available variants of the &debian; live images can be "
"found at the <ulink url=\"&url-debian-live-cd;\">Debian Live Images website</"
"ulink>."
msgstr ""
"Des informations sur les variantes disponibles des images autonomes de "
"&debian; se trouvent sur le <ulink url=\"&url-debian-live-cd;\">site web "
"Debian Live Images</ulink>."

#. Tag: title
#: preparing.xml:641
#, no-c-format
msgid "Network Settings"
msgstr "Configuration du rÃ©seau"

#. Tag: para
#: preparing.xml:643
#, no-c-format
msgid ""
"If your computer is connected to a fixed network (i.e. an Ethernet or "
"equivalent connection &mdash; not a dialup/PPP connection) which is "
"administered by somebody else, you should ask your network's system "
"administrator for this information:"
msgstr ""
"Si votre machine est connectÃ©e Ã  un rÃ©seau &mdash; avec une connexion "
"ethernet ou Ã©quivalente (pas une connexion PPP) &mdash;, vous devriez "
"demander Ã  votre administrateur systÃ¨me les Ã©lÃ©ments suivants&nbsp;:"

#. Tag: para
#: preparing.xml:651
#, no-c-format
msgid "Your host name (you may be able to decide this on your own)."
msgstr ""
"le nom de votre machine (Ã  choisir vous-mÃªme, si vous en avez le droit)"
"&nbsp;;"

#. Tag: para
#: preparing.xml:656
#, no-c-format
msgid "Your domain name."
msgstr "le nom de votre domaine&nbsp;;"

#. Tag: para
#: preparing.xml:661
#, no-c-format
msgid "Your computer's IP address."
msgstr "l'adresse IP de votre machine&nbsp;;"

#. Tag: para
#: preparing.xml:666
#, no-c-format
msgid "The netmask to use with your network."
msgstr "le masque rÃ©seau Ã  utiliser&nbsp;;"

#. Tag: para
#: preparing.xml:671
#, no-c-format
msgid ""
"The IP address of the default gateway system you should route to, if your "
"network <emphasis>has</emphasis> a gateway."
msgstr ""
"l'adresse IP de la passerelle qui sert de routeur, <emphasis>si</emphasis> "
"votre rÃ©seau possÃ¨de une passerelle&nbsp;;"

#. Tag: para
#: preparing.xml:677
#, no-c-format
msgid ""
"The system on your network that you should use as a DNS (Domain Name "
"Service) server."
msgstr ""
"la machine de votre rÃ©seau qui servira de serveur DNS (Domain Name Service)."

#. Tag: para
#: preparing.xml:685
#, no-c-format
msgid ""
"If the network you are connected to uses DHCP (Dynamic Host Configuration "
"Protocol) for configuring network settings, you don't need this information "
"because the DHCP server will provide it directly to your computer during the "
"installation process."
msgstr ""
"Quand un serveur DHCP est disponible sur votre rÃ©seau, vous n'avez pas "
"besoin de toutes ces informations. Le serveur DHCP les fournira directement "
"pendant le processus d'installation."

#. Tag: para
#: preparing.xml:692
#, no-c-format
msgid ""
"If you have internet access via DSL or cable modem (i.e. over a cable tv "
"network) and have a router (often provided preconfigured by your phone or "
"catv provider) which handles your network connectivity, DHCP is usually "
"available by default."
msgstr ""
"Si votre accÃ¨s Ã  Internet se fait par DSL ou par un modem cÃ¢ble (par un "
"rÃ©seau TV cÃ¢blÃ©), et si vous avez un routeur, souvent prÃ©configurÃ© par le "
"fournisseur d'accÃ¨s, un serveur DHCP est habituellement disponible."

#. Tag: para
#: preparing.xml:700
#, no-c-format
msgid ""
"As a rule of thumb: if you run a Windows system in your home network and did "
"not have to manually perform any network settings there to achieve Internet "
"access, network connectivity in &debian-gnu; will also be configured "
"automatically."
msgstr ""
"En rÃ¨gle gÃ©nÃ©raleÂ : si vous n'avez pas eu Ã  paramÃ©trer le rÃ©seau pour un "
"systÃ¨me Windows, la connexion au rÃ©seau pour &debian-gnu; sera aussi "
"automatiquement configurÃ©e."

#. Tag: para
#: preparing.xml:707
#, no-c-format
msgid "If you use a WLAN/WiFi network, you should find out:"
msgstr ""
"Pour un rÃ©seau WLAN/WiFi, vous aurez besoin des informations suivantes&nbsp;:"

#. Tag: para
#: preparing.xml:712
#, no-c-format
msgid "The ESSID (<quote>network name</quote>) of your wireless network."
msgstr "l'ESSID (nom) du rÃ©seau sans fil&nbsp;;"

#. Tag: para
#: preparing.xml:717
#, no-c-format
msgid "The WEP or WPA/WPA2 security key to access the network (if applicable)."
msgstr "la clÃ© WEP ou WPA/WPA2 pour accÃ©der au rÃ©seau (si nÃ©cessaire)."

#. Tag: title
#: preparing.xml:734
#, no-c-format
msgid "Meeting Minimum Hardware Requirements"
msgstr "MatÃ©riel minimum"

#. Tag: para
#: preparing.xml:735
#, no-c-format
msgid ""
"Once you have gathered information about your computer's hardware, check "
"that your hardware will let you do the type of installation that you want to "
"do."
msgstr ""
"Une fois rassemblÃ©es les informations sur votre matÃ©riel, vÃ©rifiez que vous "
"pouvez faire le type d'installation souhaitÃ©."

#. Tag: para
#: preparing.xml:741
#, no-c-format
msgid ""
"Depending on your needs, you might manage with less than some of the "
"recommended hardware listed in the table below. However, most users risk "
"being frustrated if they ignore these suggestions."
msgstr ""
"Selon vos besoins, vous pouvez continuer avec du matÃ©riel moins performant "
"que celui recommandÃ© dans le tableau ci-dessous. Cependant, la plupart des "
"utilisateurs seront frustrÃ©s s'ils ignorent ces suggestions."

#. Tag: para
#: preparing.xml:747
#, no-c-format
msgid ""
"A Pentium 4, 1GHz system is the minimum recommended for a desktop system."
msgstr ""
"Un PentiumÂ 4, 1&nbsp;GHz, est la configuration minimale recommandÃ©e pour une "
"machine de bureau."

#. Tag: para
#: preparing.xml:752
#, no-c-format
msgid "Any OldWorld or NewWorld PowerPC can serve well as a desktop system."
msgstr ""
"Tout PowerPC OldWorld ou NewWorld convient parfaitement pour une machine de "
"bureau."

#. Tag: title
#: preparing.xml:759
#, no-c-format
msgid "Recommended Minimum System Requirements"
msgstr "Configuration matÃ©rielle minimale recommandÃ©e"

#. Tag: entry
#: preparing.xml:763
#, no-c-format
msgid "Install Type"
msgstr "Type d'installation"

#. Tag: entry
#: preparing.xml:764
#, no-c-format
msgid "RAM (minimum)"
msgstr "RAM (minimum)"

#. Tag: entry
#: preparing.xml:765
#, no-c-format
msgid "RAM (recommended)"
msgstr "RAM (recommandÃ©e)"

#. Tag: entry
#: preparing.xml:766
#, no-c-format
msgid "Hard Drive"
msgstr "Disque dur"

#. Tag: entry
#: preparing.xml:772
#, no-c-format
msgid "No desktop"
msgstr "Sans bureau"

#. Tag: entry
#: preparing.xml:773
#, no-c-format
msgid "128 megabytes"
msgstr "128 mÃ©gaoctets"

#. Tag: entry
#: preparing.xml:774
#, no-c-format
msgid "512 megabytes"
msgstr "512 mÃ©gaoctets"

#. Tag: entry
#: preparing.xml:775
#, no-c-format
msgid "2 gigabytes"
msgstr "2 gigaoctet"

#. Tag: entry
#: preparing.xml:777
#, no-c-format
msgid "With Desktop"
msgstr "Avec bureau"

#. Tag: entry
#: preparing.xml:778
#, no-c-format
msgid "256 megabytes"
msgstr "256 mÃ©gaoctets"

#. Tag: entry
#: preparing.xml:779
#, no-c-format
msgid "1 gigabyte"
msgstr "1 mÃ©gaoctets"

#. Tag: entry
#: preparing.xml:780
#, no-c-format
msgid "10 gigabytes"
msgstr "10 gigaoctets"

#. Tag: para
#: preparing.xml:785
#, no-c-format
msgid ""
"The actual minimum memory requirements are a lot less than the numbers "
"listed in this table. Depending on the architecture, it is possible to "
"install &debian; with as little as 20MB (for s390) to 60MB (for amd64). The "
"same goes for the disk space requirements, especially if you pick and choose "
"which applications to install; see <xref linkend=\"tasksel-size-list\"/> for "
"additional information on disk space requirements."
msgstr ""
"La quantitÃ© de mÃ©moire minimale rÃ©ellement nÃ©cessaire est infÃ©rieure Ã  celle "
"donnÃ©e dans le tableau. Selon l'architecture, il est possible d'installer "
"&debian; avec 20&nbsp;Mo (sur s390) ou 60&nbsp;Mo (sur amd64). Il en va de "
"mÃªme pour l'espace disque, surtout si vous choisissez une Ã  une les "
"applications Ã  installer. Voyez la <xref linkend=\"tasksel-size-list\"/> "
"pour vous faire une idÃ©e de l'espace disque nÃ©cessaire."

#. Tag: para
#: preparing.xml:795
#, no-c-format
msgid ""
"It is possible to run a graphical desktop environment on older or low-end "
"systems, but in that case it is recommended to install a window manager that "
"is less resource-hungry than those of the GNOME or KDE desktop environments; "
"alternatives include <classname>xfce4</classname>, <classname>icewm</"
"classname> and <classname>wmaker</classname>, but there are others to choose "
"from."
msgstr ""
"Il est possible de faire fonctionner un environnement de bureau sur de "
"vieilles machines ou des machines bas de gamme mais il est alors recommandÃ© "
"d'installer un gestionnaire graphique moins gourmand en ressources que les "
"environnements de bureau de GNOME et KDE. Par exemple, <classname>xfce4</"
"classname>, <classname>icewm</classname> et <classname>wmaker</classname>, "
"mais il en existe d'autres."

#. Tag: para
#: preparing.xml:804
#, no-c-format
msgid ""
"It is practically impossible to give general memory or disk space "
"requirements for server installations as those very much depend on what the "
"server is to be used for."
msgstr ""
"Il n'est pas possible d'indiquer des valeurs minimales concernant la mÃ©moire "
"et l'espace disque nÃ©cessaires Ã  un serveur. Tout dÃ©pend de l'utilisation "
"qui en sera faite."

#. Tag: para
#: preparing.xml:810
#, no-c-format
msgid ""
"Remember that these sizes don't include all the other materials which are "
"usually to be found, such as user files, mail, and data. It is always best "
"to be generous when considering the space for your own files and data."
msgstr ""
"Il faut remarquer que ces mesures ne comptabilisent pas tous les fichiers, "
"comme les fichiers des utilisateurs, la messagerie et les donnÃ©es. Il vaut "
"toujours mieux prÃ©voir large quand il s'agit de ses propres fichiers et "
"donnÃ©es."

#. Tag: para
#: preparing.xml:817
#, no-c-format
msgid ""
"Disk space required for the smooth operation of the &debian-gnu; system "
"itself is taken into account in these recommended system requirements. "
"Notably, the <filename>/var</filename> partition contains a lot of state "
"information specific to &debian; in addition to its regular contents, like "
"logfiles. The <command>dpkg</command> files (with information on all "
"installed packages) can easily consume 40MB. Also, <command>apt-get</"
"command> puts downloaded packages here before they are installed. You should "
"usually allocate at least 200MB for <filename>/var</filename>, and a lot "
"more if you install a graphical desktop environment."
msgstr ""
"L'espace disque nÃ©cessaire au bon fonctionnement du systÃ¨me &debian-gnu; est "
"pris en compte dans ces valeurs recommandÃ©es. En particulier, la partition "
"<filename>/var</filename> dans &debian; contient beaucoup d'informations sur "
"l'Ã©tat du systÃ¨me. Les fichiers de <command>dpkg</command> (contenant des "
"informations sur tous les paquets installÃ©s) peuvent facilement atteindre "
"40&nbsp;Mo&nbsp;; <command>apt-get</command> y met les paquets tÃ©lÃ©chargÃ©s "
"avant de les installer. Au moins 200&nbsp;Mo devraient Ãªtre attribuÃ©s Ã  "
"<filename>/var</filename> et beaucoup plus si vous installez un "
"environnement de bureau."

#. Tag: title
#: preparing.xml:841
#, no-c-format
msgid "Pre-Partitioning for Multi-Boot Systems"
msgstr "Partitionnement prÃ©alable d'une machine multisystÃ¨me"

#. Tag: para
#: preparing.xml:842
#, no-c-format
msgid ""
"Partitioning your disk simply refers to the act of breaking up your disk "
"into sections. Each section is then independent of the others. It's roughly "
"equivalent to putting up walls inside a house; if you add furniture to one "
"room it doesn't affect any other room."
msgstr ""
"Partitionner votre disque dur est simplement le fait de le diviser en "
"plusieurs sections. Chaque section est alors indÃ©pendante des autres. C'est "
"en gros Ã©quivalent Ã  ajouter des cloisons dans une maison&nbsp;: ajouter des "
"meubles dans une piÃ¨ce n'affecte pas les autres piÃ¨ces."

#. Tag: para
#: preparing.xml:849
#, no-c-format
msgid ""
"Whenever this section talks about <quote>disks</quote> you should translate "
"this into a DASD or VM minidisk in the &arch-title; world. Also a machine "
"means an LPAR or VM guest in this case."
msgstr ""
"Dans cette section, vous devez remplacer les occurrences de <quote>disque</"
"quote> par mini-disque DASD ou VM du monde &arch-title;. De mÃªme, une "
"machine signifie une LPAR ou VM."

#. Tag: para
#: preparing.xml:855
#, no-c-format
msgid ""
"If you already have an operating system on your system <phrase arch=\"any-"
"x86\"> (Windows 9x, Windows NT/2000/XP/2003/Vista/7, OS/2, MacOS, Solaris, "
"FreeBSD, &hellip;) </phrase> <phrase arch=\"s390\"> (VM, z/OS, OS/390, "
"&hellip;) </phrase> which uses the whole disk and you want to stick &debian; "
"on the same disk, you will need to repartition it. &debian; requires its own "
"hard disk partitions. It cannot be installed on Windows or Mac OS X "
"partitions. It may be able to share some partitions with other Unix systems, "
"but that's not covered here. At the very least you will need a dedicated "
"partition for the &debian; root filesystem."
msgstr ""
"Si vous avez dÃ©jÃ  un systÃ¨me d'exploitation sur votre machine <phrase arch="
"\"any-x86\"> (WindowsÂ 9x, Windows NT/2000/XP/2003/Vista/7, OS/2, MacOS, "
"Solaris, FreeBSD&hellip;) </phrase><phrase arch=\"s390\"> (VM, z/OS, "
"OS/390&hellip;) </phrase>qui utilise tout le disque sur lequel vous dÃ©sirez "
"placer &debian;, vous devrez repartitionner ce disque. Le systÃ¨me &debian; a "
"besoin de partitions spÃ©cifiques. Il ne peut pas Ãªtre installÃ© sur des "
"partitions Windows ou MacÂ OSÂ X. Il peut partager des partitions avec "
"d'autres systÃ¨mes Unix, mais ce point n'est pas abordÃ© ici. Vous devez "
"attribuer au moins une partition Ã  la racine du systÃ¨me &debian;."

#. Tag: para
#: preparing.xml:874
#, no-c-format
msgid ""
"You can find information about your current partition setup by using a "
"partitioning tool for your current operating system<phrase arch=\"any-"
"x86\">, such as the integrated Disk Manager in Windows or fdisk in DOS</"
"phrase><phrase arch=\"powerpc\">, such as Disk Utility, Drive Setup, HD "
"Toolkit, or MacTools</phrase><phrase arch=\"s390\">, such as the VM diskmap</"
"phrase>. Partitioning tools always provide a way to show existing partitions "
"without making changes."
msgstr ""
"Vous pouvez trouver des informations sur le partitionnement actuel en "
"utilisant un outil appropriÃ© pour votre systÃ¨me d'exploitation<phrase arch="
"\"any-x86\">, tel que fdisk pour DOS ou le gestionnaire de disque intÃ©grÃ© "
"pour Windows</phrase><phrase arch=\"powerpc\">, tel que Disk Utility, Drive "
"Setup, HD Toolkit ou MacTools</phrase><phrase arch=\"s390\">, tel que le "
"diskmap VM</phrase>. Les outils de partitionnement permettent toujours de "
"montrer l'Ã©tat actuel sans rien modifier."

#. Tag: para
#: preparing.xml:884
#, no-c-format
msgid ""
"In general, changing a partition with a file system already on it will "
"destroy any information there. Thus you should always make backups before "
"doing any repartitioning. Using the analogy of the house, you would probably "
"want to move all the furniture out of the way before moving a wall or you "
"risk destroying it."
msgstr ""
"Modifier une partition contenant dÃ©jÃ  un systÃ¨me de fichiers dÃ©truit ces "
"fichiers. Vous devriez donc toujours faire des sauvegardes avant tout "
"partitionnement. En continuant l'analogie avec la maison, avant d'abattre "
"une cloison, vous dÃ©placeriez certainement les meubles afin de ne pas les "
"endommager."

#. Tag: para
#: preparing.xml:892
#, no-c-format
msgid ""
"Several modern operating systems offer the ability to move and resize "
"certain existing partitions without destroying their contents. This allows "
"making space for additional partitions without losing existing data. Even "
"though this works quite well in most cases, making changes to the "
"partitioning of a disk is an inherently dangerous action and should only be "
"done after having made a full backup of all data. <phrase arch=\"any-"
"x86\">For FAT/FAT32 and NTFS partitions as used by DOS and Windows systems, "
"the ability to move and resize them losslessly is provided both by &d-i; as "
"well as by the integrated Disk Manager of Windows 7. </phrase>"
msgstr ""
"Plusieurs systÃ¨mes d'exploitation modernes offrent la possibilitÃ© de "
"dÃ©placer et redimensionner des partitions existantes sans perdre leurs "
"donnÃ©es. De la place est ainsi crÃ©Ã©e pour ajouter des partitions. MÃªme si "
"cela fonctionne trÃ¨s bien dans la plupart des cas, modifier les partitions "
"d'un disque est une opÃ©ration fondamentalement dangereuse. Avant toute "
"modification, une sauvegarde des donnÃ©es doit Ãªtre effectuÃ©e. <phrase arch="
"\"any-x86\">Pour les partitions de type FAT/FAT32 et NTFS sur les systÃ¨mes "
"DOS et Windows, l'&d-i; et le gestionnaire de disque intÃ©grÃ© de WindowsÂ 7 "
"permettent de modifier les partitions.</phrase>"

#. Tag: para
#: preparing.xml:907
#, no-c-format
msgid ""
"To losslessly resize an existing FAT or NTFS partition from within &d-i;, go "
"to the partitioning step, select the option for manual partitioning, select "
"the partition to resize, and simply specify its new size."
msgstr ""
"Pour redimensionner une partition FAT ou NTFS avec l'&d-i;, il faut aller Ã  "
"l'Ã©tape du partitionnement, sÃ©lectionner l'option du partitionnement manuel, "
"choisir une partition Ã  redimensionner et simplement indiquer sa nouvelle "
"dimension."

#. Tag: emphasis
#: preparing.xml:915
#, no-c-format
msgid "FIXME: write about HP-UX disks?"
msgstr "FIXME: write about HP-UX disks?"

#. Tag: para
#: preparing.xml:917
#, no-c-format
msgid ""
"Creating and deleting partitions can be done from within &d-i; as well as "
"from an existing operating system. As a rule of thumb, partitions should be "
"created by the system for which they are to be used, i.e. partitions to be "
"used by &debian-gnu; should be created from within &d-i; and partitions to "
"be used from another operating system should be created from there. &d-i; is "
"capable of creating non-&arch-kernel; partitions, and partitions created "
"this way usually work without problems when used in other operating systems, "
"but there are a few rare corner cases in which this could cause problems, so "
"if you want to be sure, use the native partitioning tools to create "
"partitions for use by other operating systems."
msgstr ""
"CrÃ©er ou supprimer des partitions peut se faire avec l'&d-i; ou avec le "
"systÃ¨me d'exploitation existant. En rÃ¨gle gÃ©nÃ©rale, il vaut mieux utiliser "
"le systÃ¨me d'exploitation auquel sont destinÃ©es les partitions. Ainsi, les "
"partitions pour &debian-gnu; seront crÃ©Ã©es avec l'&d-i; et les partitions "
"pour un autre systÃ¨me seront crÃ©Ã©es avec cet autre systÃ¨me. L'&d-i; peut "
"crÃ©er sans problÃ¨me particulier des partitions pour d'autres systÃ¨mes "
"d'exploitation mais il existe quelques rares cas oÃ¹ cela peut poser des "
"problÃ¨mes. Il est donc plus sÃ»r de crÃ©er les partitions d'un systÃ¨me avec "
"les outils de partitionnement de ce systÃ¨me."

#. Tag: para
#: preparing.xml:930
#, no-c-format
msgid ""
"If you are going to install more than one operating system on the same "
"machine, you should install all other system(s) before proceeding with the "
"&debian; installation. Windows and other OS installations may destroy your "
"ability to start &debian;, or encourage you to reformat non-native "
"partitions."
msgstr ""
"Si vous installez plusieurs systÃ¨mes d'exploitation sur la mÃªme machine, "
"vous devriez commencer par les autres systÃ¨mes avant d'installer &debian;. "
"Windows ainsi que d'autres installateurs de systÃ¨me d'exploitation peuvent "
"vous empÃªcher de dÃ©marrer &debian;, ou vous encourager Ã  reformater les "
"partitions non reconnues."

#. Tag: para
#: preparing.xml:938
#, no-c-format
msgid ""
"You can recover from these actions or avoid them, but installing the native "
"system first saves you trouble."
msgstr ""
"Vous pouvez annuler ces actions ou les Ã©viter, mais installer en premier le "
"systÃ¨me natif vous Ã©pargnera des problÃ¨mes."

#. Tag: para
#: preparing.xml:943
#, no-c-format
msgid ""
"In order for OpenFirmware to automatically boot &debian-gnu; the &arch-"
"parttype; partitions should appear before all other partitions on the disk, "
"especially Mac OS X boot partitions. This should be kept in mind when pre-"
"partitioning; you should create a &arch-parttype; placeholder partition to "
"come <emphasis>before</emphasis> the other bootable partitions on the disk. "
"(The small partitions dedicated to Apple disk drivers are not bootable.) You "
"can delete the placeholder with the &debian; partition tools later during "
"the actual install, and replace it with &arch-parttype; partitions."
msgstr ""
"Pour qu'OpenFirmware puisse dÃ©marrer automatiquement &debian-gnu;, les "
"partitions &arch-parttype; doivent apparaÃ®tre avant toute autre partition "
"sur le disque, en particulier avant les partitions d'amorÃ§age de MacÂ OSÂ X. "
"Il faut absolument garder ceci Ã  l'esprit lorsque l'on partitionne le "
"disque&nbsp;; vous devez crÃ©er une place pour les partitions &arch-parttype; "
"<emphasis>avant</emphasis> les autres partitions amorÃ§ables du disque. Les "
"petites partitions dÃ©diÃ©es aux contrÃ´leurs de disques Apple ne sont pas "
"amorÃ§ables. Vous pourrez supprimer cet espace libre avec les outils de "
"partitionnement &debian; durant la phase d'installation, et le remplacer par "
"des partitions &arch-parttype;."

#. Tag: title
#: preparing.xml:1019
#, no-c-format
msgid "Partitioning from SunOS"
msgstr "Partitionnement sous SunOS"

#. Tag: para
#: preparing.xml:1021
#, no-c-format
msgid ""
"It's perfectly fine to partition from SunOS; in fact, if you intend to run "
"both SunOS and &debian; on the same machine, it is recommended that you "
"partition using SunOS prior to installing &debian;. The Linux kernel "
"understands Sun disk labels, so there are no problems there. SILO supports "
"booting Linux and SunOS from any of EXT2 (Linux), UFS (SunOS), romfs or "
"iso9660 (CDROM) partitions."
msgstr ""
"Il est tout Ã  fait possible de partitionner depuis SunOS&nbsp;; en fait, si "
"vous souhaitez avoir SunOS et &debian; sur la mÃªme machine, il est "
"recommandÃ© de partitionner avec SunOS avant d'installer &debian;. Le noyau "
"Linux comprend les Ã©tiquettes des disques Sun, il n'y aura donc aucun "
"problÃ¨me. SILO permet d'amorcer Linux et SunOS depuis des partitions EXT2 "
"(Linux), UFS (SunOS), romfs et iso9660 (CD)."

#. Tag: title
#: preparing.xml:1033
#, no-c-format
msgid "Partitioning from Linux or another OS"
msgstr "Partitionnement sous Linux ou sous un autre OS"

#. Tag: para
#: preparing.xml:1035
#, no-c-format
msgid ""
"Whatever system you are using to partition, make sure you create a "
"<quote>Sun disk label</quote> on your boot disk. This is the only kind of "
"partition scheme that the OpenBoot PROM understands, and so it's the only "
"scheme from which you can boot. In <command>fdisk</command>, the <keycap>s</"
"keycap> key is used to create Sun disk labels. You only need to do this on "
"drives that do not already have a Sun disk label. If you are using a drive "
"that was previously formatted using a PC (or other architecture) you must "
"create a new disk label, or problems with the disk geometry will most likely "
"occur."
msgstr ""
"Quel que soit le systÃ¨me utilisÃ© pour partitionner, vÃ©rifiez que vous crÃ©ez "
"une Ã©tiquette de disque Sun sur le disque d'amorÃ§age. C'est le seul schÃ©ma "
"de partitionnement que la PROM OpenBoot comprend, et donc c'est le seul "
"moyen d'amorÃ§age. Dans <command>fdisk</command>, la touche <keycap>s</"
"keycap> est utilisÃ©e pour crÃ©er des Ã©tiquettes de disque Sun. Vous n'avez "
"besoin de le faire que sur les disques sans Ã©tiquette de disque Sun. Si vous "
"utilisez un disque qui avait Ã©tÃ© formatÃ© sur PC (ou toute autre "
"architecture), vous devez crÃ©er une nouvelle Ã©tiquette, ou attendez-vous Ã  "
"avoir des problÃ¨mes Ã  cause dâ??une mauvaise reconnaissance de la gÃ©omÃ©trie du "
"disque."

#. Tag: para
#: preparing.xml:1047
#, no-c-format
msgid ""
"You will probably be using <command>SILO</command> as your boot loader (the "
"small program which runs the operating system kernel). <command>SILO</"
"command> has certain requirements for partition sizes and location; see "
"<xref linkend=\"partitioning\"/>."
msgstr ""
"Vous allez certainement utiliser <command>SILO</command> comme programme "
"d'amorÃ§age (le petit programme qui lance le noyau du systÃ¨me "
"d'exploitation). <command>SILO</command> impose certaines contraintes sur "
"l'emplacement et la taille des partitions. Voyez l'<xref linkend="
"\"partitioning\"/>."

#. Tag: title
#: preparing.xml:1062
#, no-c-format
msgid "Mac OS X Partitioning"
msgstr "Partitionnement sous MacÂ OSÂ X"

#. Tag: para
#: preparing.xml:1064
#, no-c-format
msgid ""
"The <application>Disk Utility</application> application can be found under "
"the <filename>Utilities</filename> menu in Mac OS X Installer. It will not "
"adjust existing partitions; it is limited to partitioning the entire disk at "
"once."
msgstr ""
"L'application <application>Disk Utility</application> se trouve dans le menu "
"<filename>Utilities</filename> de l'installateur MacÂ OSÂ X. Il ne permet pas "
"d'ajuster des partitions existantes&nbsp;; il se contente de crÃ©er une "
"partition unique occupant tout le disque."

#. Tag: para
#: preparing.xml:1070
#, no-c-format
msgid ""
"Remember to create a placeholder partition for GNU/Linux, preferably "
"positioned first in the disk layout. it doesn't matter what type it is, it "
"will be deleted and replaced later inside the &debian-gnu; installer."
msgstr ""
"N'oubliez pas de crÃ©er la place pour les partitions GNU/Linux, de prÃ©fÃ©rence "
"au dÃ©but du disque. Le type de cette partition importe peu&nbsp; la "
"partition sera modifiÃ©e plus tard par l'installateur &debian-gnu;."

#. Tag: para
#: preparing.xml:1076
#, no-c-format
msgid ""
"&debian; installer partition table editing tools are compatible with OS X, "
"but not with MacOS 9. If you are planning to use both MacOS 9 and OS X, it "
"is best to install OS X and &debian; on one hard drive, and put MacOS 9 on a "
"separate hard drive. Separate options for OS 9 and OS X will appear when "
"holding the <keycap>option</keycap> key at boot time, and separate options "
"can be installed in the <application>yaboot</application> boot menu as well."
msgstr ""
"Les outils de l'installateur &debian; pour modifier la table des partitions "
"sont compatibles avec OS&nbsp;X mais pas avec MacOS&nbsp;9. Si vous prÃ©voyez "
"d'utiliser les deux, il vaut mieux installer OSÂ X et &debian; sur un disque "
"et mettre MacOSÂ 9 sur un autre disque. Des options diffÃ©rentes pour "
"OS&nbsp;9 et OS&nbsp;X apparaÃ®tront en appuyant sur la touche "
"<keycap>option</keycap> pendant le dÃ©marrage, et d'autres options peuvent "
"aussi Ãªtre installÃ©es dans le menu de dÃ©marrage <application>yaboot</"
"application>."

#. Tag: para
#: preparing.xml:1086
#, no-c-format
msgid ""
"GNU/Linux is unable to access information on UFS partitions, but can access "
"HFS+ (aka MacOS Extended) partitions. OS X requires one of these two types "
"for its boot partition. MacOS 9 can be installed on either HFS (aka MacOS "
"Standard) or HFS+. To share information between the Mac OS X and GNU/Linux "
"systems, an exchange partition is handy. HFS, HFS+ and MS-DOS FAT file "
"systems are supported by MacOS 9, Mac OS X and GNU/Linux."
msgstr ""
"GNU/Linux ne peut accÃ©der aux informations des partitions UFS mais peut "
"accÃ©der Ã  celles des partitions HFS+ (MacOS Extended). OS&nbsp;X a besoin "
"d'un de ces types pour sa partition de dÃ©marrage. MacOS&nbsp;9 peut Ãªtre "
"installÃ© soit sur HFS (MacOS standard), soit sur HFS+. Pour partager des "
"informations entre les systÃ¨mes MacÂ OSÂ X et GNU/Linux, une partition "
"d'Ã©change est trÃ¨s pratique. Les systÃ¨mes de fichiers HFS, HFS+ et MS-DOS "
"FAT sont reconnus par MacOSÂ 9, MacÂ OSÂ X et GNU/Linux."

#. Tag: title
#: preparing.xml:1106
#, no-c-format
msgid "Pre-Installation Hardware and Operating System Setup"
msgstr "Configuration matÃ©rielle et systÃ¨me avant l'installation"

#. Tag: para
#: preparing.xml:1107
#, no-c-format
msgid ""
"This section will walk you through pre-installation hardware setup, if any, "
"that you will need to do prior to installing &debian;. Generally, this "
"involves checking and possibly changing BIOS/system firmware settings for "
"your system. The <quote>BIOS</quote> or <quote>system firmware</quote> is "
"the core software used by the hardware; it is most critically invoked during "
"the bootstrap process (after power-up)."
msgstr ""
"Cette section passe en revue les rÃ©glages matÃ©riels que vous devrez peut-"
"Ãªtre effectuer avant d'installer &debian;. En gÃ©nÃ©ral, cela implique de "
"vÃ©rifier, et parfois de modifier, les rÃ©glages du microprogramme systÃ¨me "
"(BIOS,Â etc.) sur votre machine. Le <quote>BIOS</quote> ou "
"<quote>microprogramme systÃ¨me</quote> est le logiciel de base utilisÃ© par le "
"matÃ©riel&nbsp;; il est plus spÃ©cifiquement exÃ©cutÃ© pendant le processus "
"d'amorÃ§age (aprÃ¨s la mise sous tension)."

#. Tag: title
#: preparing.xml:1122
#, no-c-format
msgid "Invoking the BIOS Set-Up Menu"
msgstr "Le menu de configuration du BIOS"

#. Tag: para
#: preparing.xml:1124
#, no-c-format
msgid ""
"The BIOS provides the basic functions needed to boot your machine and to "
"allow your operating system to access your hardware. Your system provides a "
"BIOS setup menu, which is used to configure the BIOS. To enter the BIOS "
"setup menu you have to press a key or key combination after turning on the "
"computer. Often it is the <keycap>Delete</keycap> or the <keycap>F2</keycap> "
"key, but some manufacturers use other keys. Usually upon starting the "
"computer there will be a message stating which key to press to enter the "
"setup screen."
msgstr ""
"Le BIOS fournit les fonctions de base nÃ©cessaires Ã  l'amorÃ§age de votre "
"machine pour permettre au systÃ¨me d'exploitation d'accÃ©der au matÃ©riel. Le "
"systÃ¨me fournit un menu destinÃ© Ã  la configuration du BIOS. Vous pouvez "
"accÃ©der Ã  ce menu en appuyant sur une touche ou sur une combinaison de "
"touches. Il s'agit souvent de la touche <keycap>Suppr</keycap> ou de la "
"touche <keycap>F2</keycap>. Certains constructeurs utilisent d'autres "
"touches. Au dÃ©marrage de l'ordinateur, un message indique gÃ©nÃ©ralement la "
"touche Ã  utiliser."

#. Tag: title
#: preparing.xml:1138 preparing.xml:1479
#, no-c-format
msgid "Boot Device Selection"
msgstr "SÃ©lection du pÃ©riphÃ©rique d'amorÃ§age"

#. Tag: para
#: preparing.xml:1140
#, no-c-format
msgid ""
"Within the BIOS setup menu, you can select which devices shall be checked in "
"which sequence for a bootable operating system. Possible choices usually "
"include the internal harddisks, the CD/DVD-ROM drive and USB mass storage "
"devices such as USB sticks or external USB harddisks. On modern systems "
"there is also often a possibility to enable network booting via PXE."
msgstr ""
"A l'intÃ©rieur du menu de configuration du BIOS vous pouvez choisir les "
"pÃ©riphÃ©riques utilisables pour l'amorÃ§age du systÃ¨me et leur ordre. Peuvent "
"Ãªtre sÃ©lectionnÃ©s des disques durs internes, un lecteur de CD/DVD ou des "
"pÃ©riphÃ©riques de stockage USB comme des clÃ©s ou des disques externes. Sur "
"des systÃ¨mes modernes, il existe aussi la possibilitÃ© d'amorcer par le "
"rÃ©seau (PXE)."

#. Tag: para
#: preparing.xml:1148
#, no-c-format
msgid ""
"Depending on the installation media (CD/DVD ROM, USB stick, network boot) "
"you have chosen you should enable the appropriate boot devices if they are "
"not already enabled."
msgstr ""
"Selon le support d'installation choisi (CD/DVD, clÃ© USB, amorÃ§age par le "
"rÃ©seau), vous devez activer, s'il ne l'est pas dÃ©jÃ , le pÃ©riphÃ©rique "
"d'amorÃ§age appropriÃ©."

#. Tag: para
#: preparing.xml:1154
#, no-c-format
msgid ""
"Most BIOS versions allow you to call up a boot menu on system startup in "
"which you select from which device the computer should start for the current "
"session. If this option is available, the BIOS usually displays a short "
"message like <quote>press <keycap>F12</keycap> for boot menu</quote> on "
"system startup. The actual key used to select this menu varies from system "
"to system; commonly used keys are <keycap>F12</keycap>, <keycap>F11</keycap> "
"and <keycap>F8</keycap>. Choosing a device from this menu does not change "
"the default boot order of the BIOS, i.e. you can start once from a USB stick "
"while having configured the internal harddisk as the normal primary boot "
"device."
msgstr ""
"La plupart des BIOS permettent d'appeler un menu au dÃ©marrage du systÃ¨me "
"dans lequel vous sÃ©lectionnez le pÃ©riphÃ©rique d'amorÃ§age pour la session "
"actuelle. Si cette option est disponible, le BIOS affiche un court message, "
"Â«Â press <keycap>F12</keycap> for boot menuÂ Â» par exemple. La touche peut "
"Ãªtre diffÃ©rente selon les systÃ¨mes, <keycap>F12</keycap>, <keycap>F11</"
"keycap> ou <keycap>F8</keycap>. Choisir un pÃ©riphÃ©rique dans ce menu ne "
"change pas l'ordre d'amorÃ§age par dÃ©faut du BIOS. Ainsi vous pouvez amorcer "
"Ã  partir d'une clÃ© USB alors que le disque dur interne reste le pÃ©riphÃ©rique "
"d'amorÃ§age prioritaire."

#. Tag: para
#: preparing.xml:1168
#, no-c-format
msgid ""
"If your BIOS does not provide you with a boot menu to do ad-hoc choices of "
"the current boot device, you will have to change your BIOS setup to make the "
"device from which the &d-i; shall be booted the primary boot device."
msgstr ""
"Si le BIOS ne vous donne pas cette possibilitÃ©, vous devez modifier sa "
"configuration et indiquer comme prioritaire le pÃ©riphÃ©rique qui contient "
"l'&d-i;"

#. Tag: para
#: preparing.xml:1174
#, no-c-format
msgid ""
"Unfortunately some computers contain buggy BIOS versions. Booting &d-i; from "
"a USB stick might not work even if there is an appropriate option in the "
"BIOS setup menu and the stick is selected as the primary boot device. On "
"some of these systems using a USB stick as boot medium is impossible; others "
"can be tricked into booting from the stick by changing the device type in "
"the BIOS setup from the default <quote>USB harddisk</quote> or <quote>USB "
"stick</quote> to <quote>USB ZIP</quote> or <quote>USB CDROM</quote>. <phrase "
"condition=\"isohybrid-supported\"> In particular if you use an isohybrid CD/"
"DVD image on a USB stick (see <xref linkend=\"usb-copy-isohybrid\"/>), "
"changing the device type to <quote>USB CDROM</quote> helps on some BIOSes "
"which will not boot from a USB stick in USB harddisk mode.</phrase>"
msgstr ""
"Quelques ordinateurs contiennent malheureusement des versions du BIOS "
"dÃ©fectueuses. Il est parfois impossible d'amorcer l'&d-i; Ã  partir d'une clÃ© "
"USB mÃªme si l'option appropriÃ©e existe dans le menu de configuration et la "
"clÃ© est choisie comme pÃ©riphÃ©rique d'amorÃ§age prioritaire. Sur certains "
"systÃ¨mes, on peut forcer l'amorÃ§age en changeant le type de pÃ©riphÃ©rique, de "
"<quote>USB harddisk</quote> ou <quote>USB stick</quote> Ã  <quote>USB ZIP</"
"quote> ou <quote>USB CDROM</quote>.<phrase condition=\"isohybrid-supported"
"\"> En particulier, si vous utilisez une image hybride (<quote>isohybrid</"
"quote>) de CD/DVD sur une clÃ© USB (voyez la <xref linkend=\"usb-copy-"
"isohybrid\"/>), modifier le type de pÃ©riphÃ©rique en <quote>USB CDROM</quote> "
"peut servir pour les BIOS qui ne permettent pas l'amorÃ§age sur une clÃ© en "
"mode <quote>USB harddisk</quote>. </phrase>"

#. Tag: para
#: preparing.xml:1189
#, no-c-format
msgid ""
"If you cannot manipulate the BIOS to boot directly from a USB stick you "
"still have the option of using an ISO copied to the stick. Boot &d-i; using "
"<xref linkend=\"boot-drive-files\"/> and, after scanning the hard drives for "
"an installer ISO image, select the USB device and choose an installation "
"image."
msgstr ""
"Si vous ne pouvez pas rÃ©gler le BIOS pour permettre l'amorÃ§age Ã  partir "
"d'une clÃ© USB, vous pouvez toujours copier une image ISO sur la clÃ©. Amorcez "
"l'&d-i; (consultez la <xref linkend=\"boot-drive-files\"/> et, lors de la "
"recherche d'une image ISO sur les disques, choisissez la clÃ© USB et l'image "
"d'installation."

#. Tag: title
#: preparing.xml:1207
#, no-c-format
msgid "Invoking OpenFirmware"
msgstr "ExÃ©cuter l'<emphasis>OpenFirmware</emphasis>"

#. Tag: para
#: preparing.xml:1208
#, no-c-format
msgid ""
"There is normally no need to set up the BIOS (called OpenFirmware) on &arch-"
"title; systems. PReP and CHRP are equipped with OpenFirmware, but "
"unfortunately, the means you use to invoke it vary from manufacturer to "
"manufacturer. You'll have to consult the hardware documentation which came "
"with your machine."
msgstr ""
"Il n'y a normalement pas besoin de configurer le BIOS (appelÃ© "
"<emphasis>OpenFirmware</emphasis>) sur les systÃ¨mes &arch-title;. PReP et "
"CHRP sont Ã©quipÃ©s de l'<emphasis>OpenFirmware</emphasis>, mais, "
"malheureusement, les mÃ©thodes utilisÃ©es pour l'invoquer varient d'un "
"constructeur Ã  l'autre. Vous devrez consulter la documentation du matÃ©riel "
"livrÃ©e avec votre machine."

#. Tag: para
#: preparing.xml:1216
#, no-c-format
msgid ""
"On &arch-title; Macintoshes, you invoke OpenFirmware with "
"<keycombo><keycap>Command (cloverleaf/Apple)</keycap><keycap>Option</"
"keycap><keycap>o</keycap><keycap>f</keycap></keycombo> while booting. "
"Generally it will check for these keystrokes after the chime, but the exact "
"timing varies from model to model. See <ulink url=\"&url-netbsd-powerpc-faq;"
"\"></ulink> for more hints."
msgstr ""
"Pour invoquer l'<emphasis>OpenFirmware</emphasis> sur les Macintosh &arch-"
"title;, appuyez sur <keycombo><keycap>Command (cloverleaf/Apple)</"
"keycap><keycap>Option</keycap> <keycap>o</keycap><keycap>f</keycap></"
"keycombo> pendant l'amorÃ§age. GÃ©nÃ©ralement, cette combinaison de touches est "
"testÃ©e aprÃ¨s le carillon, mais le moment exact du test varie selon les "
"modÃ¨les. Consultez <ulink url=\"&url-netbsd-powerpc-faq;\"></ulink> pour "
"obtenir d'autres conseils."

#. Tag: para
#: preparing.xml:1224
#, no-c-format
msgid ""
"The OpenFirmware prompt looks like this: <informalexample><screen>\n"
"ok\n"
"0 &gt;\n"
"</screen></informalexample> Note that on older model &arch-title; Macs, the "
"default and sometimes hardwired I/O for OpenFirmware user interaction is "
"through the serial (modem) port. If you invoke OpenFirmware on one of these "
"machines, you will just see a black screen. In that case, a terminal program "
"running on another computer, connected to the modem port, is needed to "
"interact with OpenFirmware."
msgstr ""
"L'invite de l'<emphasis>OpenFirmware</emphasis> ressemble Ã  ceci&nbsp;: "
"<informalexample><screen>\n"
"ok\n"
"0 &gt;\n"
"</screen></informalexample> Notez que sur les anciens modÃ¨les de Mac &arch-"
"title;, les entrÃ©es-sorties pour l'interaction avec "
"l'<emphasis>OpenFirmware</emphasis> se font par dÃ©faut Ã  travers un port "
"sÃ©rie (modem). Si vous appelez l'<emphasis>OpenFirmware</emphasis> depuis "
"une de ces machines, vous n'aurez droit qu'Ã  un Ã©cran noir. Dans ce cas, un "
"programme lancÃ© sur une autre machine et se connectant sur le port modem est "
"nÃ©cessaire pour interagir avec l'<emphasis>OpenFirmware</emphasis>."

#. Tag: para
#: preparing.xml:1237
#, no-c-format
msgid ""
"The OpenFirmware on OldWorld Beige G3 machines, OF versions 2.0f1 and 2.4, "
"is broken. These machines will most likely not be able to boot from the hard "
"drive unless the firmware is patched. A firmware patch is included in the "
"<application>System Disk 2.3.1</application> utility, available from Apple "
"at <ulink url=\"ftp://ftp.apple.com/developer/macosxserver/utilities/";
"SystemDisk2.3.1.smi.bin\"></ulink>. After unpacking the utility in MacOS, "
"and launching it, select the <guibutton>Save</guibutton> button to have the "
"firmware patches installed to nvram."
msgstr ""
"Sur les machines OldWorld Beige G3, les <emphasis>OpenFirmware</emphasis> "
"versionsÂ 2.0f1 etÂ 2.4 sont boguÃ©es. Ces machines ne seront certainement pas "
"capables d'amorcer depuis le disque dur Ã  moins que le microprogramme ne "
"soit corrigÃ©. Une rustine pour le microprogramme est incluse dans "
"l'utilitaire <application>System DiskÂ 2.3.1</application>, disponible chez "
"Apple Ã  <ulink url=\"ftp://ftp.apple.com/developer/macosxserver/utilities/";
"SystemDisk2.3.1.smi.bin\"></ulink>. AprÃ¨s avoir extrait l'utilitaire sur "
"MacOS, et l'avoir lancÃ©, choisissez le bouton <guibutton>Save</guibutton> "
"pour installer les routines pour le microprogramme dans la nvram."

#. Tag: title
#: preparing.xml:1253
#, no-c-format
msgid "How to update bare metal ppc64el firmware"
msgstr "Comment mettre Ã  jour le microcode d'un systÃ¨me ppc64el"

#. Tag: para
#: preparing.xml:1254
#, no-c-format
msgid ""
"This is an excerpt from <ulink url=\"&url-ibm-powerkvm;\">IBM PowerKVM on "
"IBM POWER8</ulink>"
msgstr ""
"Ce qui suit est un extrait de <ulink url=\"&url-ibm-powerkvm;\">IBM PowerKVM "
"sur IBM POWER8</ulink>"

#. Tag: para
#: preparing.xml:1259
#, no-c-format
msgid ""
"Open Power Abstraction Layer (OPAL) is the system firmware in the stack of "
"POWER processor-based server."
msgstr ""
"Open Abstraction Layer (OPAL) est le microcode du systÃ¨me dans la pile "
"serveur basÃ©e sur les processeur POWER."

#. Tag: para
#: preparing.xml:1264
#, no-c-format
msgid ""
"There may be instances when the user might have to upgrade the Power Systems "
"firmware to a more recent level to acquire new features or additional "
"support for devices."
msgstr ""
"Il peut y avoir des cas oÃ¹ l'utilisateur devrait mettre Ã  niveau le "
"microcode Power Systems pour obtenir de nouvelles fonctionnalitÃ©s ou "
"davantages de prises en charge de pÃ©riphÃ©riques."

#. Tag: para
#: preparing.xml:1270
#, no-c-format
msgid "Make sure that the following requirements are met:"
msgstr "Assurez-vous que les conditions suivantes sont rÃ©uniesÂ :"

#. Tag: para
#: preparing.xml:1275
#, no-c-format
msgid "an OS to be running on the system;"
msgstr "un systÃ¨me d'exploitation fonctionne sur le systÃ¨meÂ ;"

#. Tag: para
#: preparing.xml:1277
#, no-c-format
msgid "the .img file of the OPAL level that the user needs to update to;"
msgstr ""
"le fichier .img du niveau OPAL vers lequel l'utilisateur veut mettre Ã  "
"niveau est disponibleÂ ;"

#. Tag: para
#: preparing.xml:1279
#, no-c-format
msgid "the machine isn't under HMC control."
msgstr "la machine n'est pas contrÃ´lÃ©e par HMC."

#. Tag: para
#: preparing.xml:1283
#, no-c-format
msgid ""
"Power Systems has two sides of flash to boot firmware from, namely permanent "
"and temporary. This provides a way to test firmware updates on the temporary "
"side of the flash before committing the tested changes to the permanent "
"side, thereby committing the new updates."
msgstr ""
"Les machines Power Systems ont deux parties de mÃ©moire d'oÃ¹ charger le "
"microcode, une permanente et une temporaire. Cela permet de tester les mises "
"Ã  jour du microcode dans la mÃ©moire temporaire avant d'envoyer les "
"modifications testÃ©e dans la mÃ©moire permanente et, grÃ¢ce Ã  cela, utiliser "
"ces mise Ã  jour."

#. Tag: para
#: preparing.xml:1290
#, no-c-format
msgid "Perform the following steps for the update:"
msgstr "Pour la mise Ã  jour, voici les Ã©tapes Ã  effectuerÂ :"

#. Tag: para
#: preparing.xml:1295
#, no-c-format
msgid ""
"Save the level of the existing firmware before really updating. In ASM, in "
"the system menu, click <command>Service Aids ??? Service Processor Command "
"Line</command>, and run the following command:"
msgstr ""
"Sauvergardez la version actuelle avant de faire la mise Ã  jour. Dans le menu "
"system de ASM, cliquez sur <command>Service Aids ??? Service Processor "
"Command Line</command> et lancez la commande suivanteÂ :"

#. Tag: screen
#: preparing.xml:1299
#, no-c-format
msgid "cupdcmd -f"
msgstr "cupdcmd -f"

#. Tag: para
#: preparing.xml:1300
#, no-c-format
msgid ""
"Download the .img file of the level of firmware to be updated to a location "
"in the host filesystem. Refer to IBM Fix Central for downloading the image "
"file."
msgstr ""
"TÃ©lÃ©chargez le fichier .img de la version du microcode vers laquelle migrer "
"sur le systÃ¨me de fichiers hÃ´te.Veuillez vous rÃ©fÃ©rer au Fix Central d'IBM "
"pour tÃ©lÃ©charger le fichier image."

#. Tag: para
#: preparing.xml:1304
#, no-c-format
msgid ""
"Verify the image downloaded by running the following command and save the "
"output."
msgstr ""
"VÃ©rifiez l'image chargÃ©es en lanÃ§ant la commande suivante et en enregistrant "
"la sortieÂ :"

#. Tag: screen
#: preparing.xml:1307
#, no-c-format
msgid "$update_flash -v -f &lt;file_name.img&gt;"
msgstr "$update_flash -v -f &lt;nom_de_fichier.img&gt;"

#. Tag: para
#: preparing.xml:1309
#, no-c-format
msgid "Update the firmware by running the following command."
msgstr "Mettez Ã  jour le microcode en exÃ©cutant la commande suivanteÂ :"

#. Tag: screen
#: preparing.xml:1311
#, no-c-format
msgid "$update_flash -f &lt;file_name.img&gt;"
msgstr "$update_flash -f &lt;nom_de_fichier.img&gt;"

#. Tag: para
#: preparing.xml:1317
#, no-c-format
msgid ""
"The command reboots the system and therefore, sessions if any, would be lost."
msgstr ""
"Cett commande redÃ©marre le systÃ¨me et, par consÃ©quence, les sessions seront "
"perdues."

#. Tag: para
#: preparing.xml:1320
#, no-c-format
msgid "Do not reboot or switch off the system until it is back."
msgstr "Ne redÃ©marrez ni n'Ã©teignez le systÃ¨me tant qu'il n'est pas rÃ©amorcÃ©."

#. Tag: para
#: preparing.xml:1327
#, no-c-format
msgid ""
"Verify the updated firmware level of the temporary side of the flash as in "
"step 1."
msgstr ""
"VÃ©rifiez la version du microcode dans la mÃ©moire temporaire de la mÃ©moire, "
"comme Ã  la premiÃ¨re Ã©tape."

#. Tag: para
#: preparing.xml:1330
#, no-c-format
msgid ""
"In case the update has to be reverted, the user can do so by running this "
"command: <informalexample><screen>\n"
"    $update_flash -r\n"
"</screen></informalexample> Rejection would reject only the temporary side "
"of the flash. Therefore, the new level should be committed to the permanent "
"side only after thorough testing of the new firmware."
msgstr ""
"Dans le cas ou la mise Ã  jour doit Ãªtre annulÃ©e, cela peut Ãªtre fait en "
"exÃ©cutant <informalexample><screen>\n"
"    $update_flash -r\n"
"</screen></informalexample> Cela n'affectera que la mÃ©moire temporaire. "
"Autrement, la nouvelle version ne devrait Ãªtre envoyÃ©e dans la mÃ©moire "
"permanente qu'aprÃ¨s avoir suffisamment testÃ© le nouveau microcode."

#. Tag: para
#: preparing.xml:1337
#, no-c-format
msgid ""
"The new updated level can be committed to the permanent side of the flash by "
"running the following command."
msgstr ""
"La nouvelle version peut Ãªtre envoyÃ©e dans la mÃ©moire permanente en "
"exÃ©cutant la commande suivanteÂ :"

#. Tag: screen
#: preparing.xml:1340
#, no-c-format
msgid "$update_flash -c"
msgstr "$update_flash -c"

#. Tag: title
#: preparing.xml:1348
#, no-c-format
msgid "Updating KVM guest firmware (SLOF)"
msgstr "Mise Ã  jour du microcode invitÃ© de KVM (SLOF)"

#. Tag: para
#: preparing.xml:1349
#, no-c-format
msgid ""
"Slimline Open Firmware (SLOF) is an implementation of the IEEE 1275 "
"standard. It can be used as partition firmware for pSeries machines running "
"on QEMU or KVM."
msgstr ""
"Slimline Open Firmware (SLOF) est une implÃ©mentation du standard IEEEÂ 1275. "
"Il peut Ãªtre utilisÃ© comme microcode de partition pour les machines pSeries "
"s'exÃ©cutant dans QEMU ou KVM."

#. Tag: para
#: preparing.xml:1356
#, no-c-format
msgid ""
"The package qemu-slof is, in fact, a dependency of package qemu-system-ppc "
"(which also provides the virtual package qemu-system-ppc64), and can be "
"installed or updated via <command>apt-get</command> tool on Debian-based "
"distros. Like so: <informalexample><screen>\n"
"# apt-get install qemu-slof\n"
"</screen></informalexample> SLOF can also be installed into rpm-based "
"distribution systems, given the proper repository or rpm package. "
"Additionally, the upstream source code is available at http://github.com/";
"leilihh/SLOF."
msgstr ""
"La paquetqemu-slof est en fait une dÃ©pendance du paquet qemu-system-ppc (qui "
"fournit aussi le paquet virtuel qemu-system-ppc64) et peut Ãªtre installÃ© ou "
"mis Ã  jour avec <command>apt-get</command> sur les distributions basÃ©es sur "
"DebianÂ :<informalexample><screen>\n"
"# apt-get install qemu-slof\n"
"</screen></informalexample> SLOF peut aussi Ãªtre installÃ© sur les "
"distributions basÃ©es sur rpm. De plus, le code source amont est disponible Ã  "
"l'adresse http://github.com/leilihh/SLOF.";

#. Tag: para
#: preparing.xml:1370
#, no-c-format
msgid ""
"Thus, one can use a different SLOF file rather than the default, when "
"running <command>qemu-system</command>, by adding the command line argument "
"<userinput>-bios &lt;slof_file&gt; </userinput> when starting qemu."
msgstr ""
"Il est possible d'utiliser un fichier SLOF diffÃ©rent de celui par dÃ©faut en "
"ajoutant l'argument <userinput>-bios &lt;fichier_slof&gt; </userinput> Ã  la "
"commande <command>qemu-system</command>."

#. Tag: title
#: preparing.xml:1380
#, no-c-format
msgid "Updating PowerKVM hypervisor"
msgstr "Mise Ã  jour de l'hyperviseur PowerKVM"

#. Tag: title
#: preparing.xml:1381
#, no-c-format
msgid "Instructions for Netboot installation"
msgstr "Instructions pour les installations de type netboot"

#. Tag: para
#: preparing.xml:1382
#, no-c-format
msgid ""
"You will need a DHCP/TFTP (BOOTP) server, as well as a web server. After "
"downloading ibm-powerkvm-*-ppc64-service-*.iso, mount loop it and unpack it "
"into some directory within your HTTP server www root structure (say "
"wwwroot): <informalexample><screen>\n"
"# cd &lt;directory-where-the-iso-is&gt;\n"
"# mkdir ./iso\n"
"# sudo mount -o loop ibm-powerkvm-*-ppc64-service-*.iso ./iso\n"
"# cp -a ./iso/* &lt;path-to-wwwroot&gt;\n"
"</screen></informalexample> Create the petitboot.conf file in a directory "
"under your tftproot, say /tftproot/powerkvm, with the following contents: "
"<informalexample><screen>\n"
"label PowerKVM Automated Install\n"
"kernel http://YOUR-SERVER-IP/SOME-PATH-TO-wwwroot/ppc/ppc64/vmlinuz\n";
"initrd http://YOUR-SERVER-IP/SOME-PATH-TO-wwwroot/ppc/ppc64/initrd.img\n";
"append root=live:http://YOUR-SERVER-IP/SOME-PATH-TO-wwwroot/LiveOS/squashfs.";
"img repo=http://YOUR-SERVER-IP/SOME-PATH-TO-wwwroot/packages rd.dm=0 rd.md=0 "
"console=hvc0 console=tty0\n"
"</screen></informalexample> Editing your dhcpd.conf, set this directive at "
"the beginning: <informalexample><screen>\n"
"option conf-file code 209 = text;\n"
"</screen></informalexample> Add the system directive: "
"<informalexample><screen>\n"
"host &lt;your-system&gt; {\n"
"    hardware ethernet &lt;system macaddr&gt;\n"
"    fixed-address &lt;system ip&gt;;\n"
"    option host-name \"&lt;system hostname&gt;\";\n"
"    option conf-file \"&lt;powerkvm/petitboot.conf&gt;\";\n"
" }\n"
"</screen></informalexample> Reboot the dhcp server."
msgstr ""
"Vous aurez besoin d'un serveur DHCP/TFTP (BOOTP) ainsi que d'un serveur web. "
"AprÃ¨s avoir tÃ©lÃ©chargÃ© l'image ibm-powerkvm-*-ppc64-service-*.iso, montez-la "
"et dÃ©compressez-la dans la structure www de votre serveur HTTP (par exemple "
"wwwroot)Â : <informalexample><screen>\n"
"# cd &lt;rÃ©pertoire_de_l_image&gt;\n"
"# mkdir ./iso\n"
"# sudo mount -o loop ibm-powerkvm-*-ppc64-service-*.iso ./iso\n"
"# cp -a ./iso/* &lt;chemin_vers_wwwroot&gt;\n"
"</screen></informalexample> CrÃ©ez le fichier petitboot.conf dans un "
"rÃ©pertoire de votre serveur TFTP (par exemple (/tftproot/powerkvm) contenant "
"ce qui suitÂ : <informalexample><screen>\n"
"label PowerKVM Automated Install\n"
"kernel http://IP_DU_SERVEUR/chemin_vers_wwwroot/ppc/ppc64/vmlinuz\n";
"initrd http://IP_DU_SERVEUR/chemin_vers_wwwroot/ppc/ppc64/initrd.img\n";
"append root=live:http://IP_DU_SERVEUR/chemin_vers_wwwroot/LiveOS/squashfs.";
"img repo=http://IP_DU_SERVEUR/chemin_vers_wwwroot/packages rd.dm=0 rd.md=0 "
"console=hvc0 console=tty0\n"
"</screen></informalexample> Ã?ditez votre fichier dhcpd.conf et ajoutez ces "
"directives au dÃ©butÂ : <informalexample><screen>\n"
"option conf-file code 209 = text;\n"
"</screen></informalexample> Ajoutez la directive systÃ¨meÂ : "
"<informalexample><screen>\n"
"host &lt;your-system&gt; {\n"
"    hardware ethernet &lt;adrsse_MAC_du_systÃ¨me&gt;\n"
"    fixed-address &lt;adresse_IP_du_systÃ¨me&gt;;\n"
"    option host-name \"&lt;hostname_du_systÃ¨me&gt;\";\n"
"    option conf-file \"&lt;powerkvm/petitboot.conf&gt;\";\n"
" }\n"
"</screen></informalexample> RedÃ©marrez votre serveur DHCP."

#. Tag: para
#: preparing.xml:1406
#, no-c-format
msgid "Boot your PowerLinux machine."
msgstr "DÃ©marrez votre machine PowerLinux"

#. Tag: para
#: preparing.xml:1410
#, no-c-format
msgid ""
"There should be the following option at petitboot (select it): "
"<informalexample><screen>\n"
"\"Power KVM Automated Install\" \n"
"</screen></informalexample> The installer menu should appear automatically."
msgstr ""
"L'option suivante devrait vous Ãªtre prÃ©sentÃ©e dans le menu petitbootÂ : "
"<informalexample><screen>\n"
"\"Power KVM Automated Install\" \n"
"</screen></informalexample> Le menu de l'installateur devrait ensuite "
"apparaÃ®tre."

#. Tag: title
#: preparing.xml:1421
#, no-c-format
msgid "Instructions for DVD"
msgstr "Instructions pour les DVD"

#. Tag: para
#: preparing.xml:1422
#, no-c-format
msgid ""
"Boot the ISO ibm-powerkvm-*-ppc64-service-*.iso (either burn a DVD or make "
"it virtual if using QEMU) and simply wait for the boot."
msgstr ""
"Amorcez sur l'image ISO ibm-powerkvm-*-ppc64-service-*.iso (gravÃ©e sur un "
"DVD ou virtualisÃ©e si utilisÃ©e dans QEMU) et attendez le dÃ©marrage."

#. Tag: para
#: preparing.xml:1425
#, no-c-format
msgid ""
"There should be the following option at petitboot (select it): "
"<informalexample><screen>\n"
"\"POWERKVM_LIVECD\" \n"
"</screen></informalexample> The installer menu should appear automatically."
msgstr ""
"L'option suivante devrait vous Ãªtre prÃ©sentÃ©e dans le menu petitbootÂ : "
"<informalexample><screen>\n"
"\"POWERKVM_LIVECD\" \n"
"</screen></informalexample> Le menu de l'installateur devrait ensuite "
"apparaÃ®tre."

#. Tag: title
#: preparing.xml:1446
#, no-c-format
msgid "Invoking OpenBoot"
msgstr "Appel d'OpenBoot"

#. Tag: para
#: preparing.xml:1448
#, no-c-format
msgid ""
"OpenBoot provides the basic functions needed to boot the &arch-title; "
"architecture. This is rather similar in function to the BIOS in the x86 "
"architecture, although much nicer. The Sun boot PROMs have a built-in forth "
"interpreter which lets you do quite a number of things with your machine, "
"such as diagnostics and simple scripts."
msgstr ""
"OpenBoot fournit les fonctions de base nÃ©cessaires Ã  l'amorÃ§age de "
"l'architecture &arch-title;. Les fonctions sont Ã  peu prÃ¨s similaires Ã  "
"celles du BIOS de l'architecture x86, mais c'est plus joli. Les PROM "
"d'amorÃ§age Sun possÃ¨dent un interprÃ©teur Forth intÃ©grÃ© qui permet de faire "
"pas mal de choses, comme des tests, des scripts simples,Â etc."

#. Tag: para
#: preparing.xml:1456
#, no-c-format
msgid ""
"To get to the boot prompt you need to hold down the <keycap>Stop</keycap> "
"key (on older type 4 keyboards, use the <keycap>L1</keycap> key, if you have "
"a PC keyboard adapter, use the <keycap>Break</keycap> key) and press the "
"<keycap>A</keycap> key. The boot PROM will give you a prompt, either "
"<userinput>ok</userinput> or <userinput>&gt;</userinput>. It is preferred to "
"have the <userinput>ok</userinput> prompt. So if you get the old style "
"prompt, hit the <keycap>n</keycap> key to get the new style prompt."
msgstr ""
"Pour obtenir l'invite d'OpenBoot vous devez maintenir la touche "
"<keycap>Stop</keycap> (ou la touche <keycap>L1</keycap> sur les vieux "
"claviers TypeÂ 4) et appuyer sur la touche <keycap>A</keycap>. Si vous avez "
"un adaptateur de clavier PC, maintenez la touche <keycap>Pause</keycap> (ou "
"<keycap>Break</keycap>) et appuyez sur <keycap>A</keycap>. Cela vous donnera "
"une invite, soit <userinput>ok</userinput> soit <userinput>&gt;</userinput>. "
"Il est prÃ©fÃ©rable d'avoir l'invite <userinput>ok</userinput>. Si vous "
"obtenez le vieux modÃ¨le d'invite (<userinput>&gt;</userinput>), appuyez sur "
"la touche <keycap>n</keycap> pour obtenir le nouveau modÃ¨le d'invite."

#. Tag: para
#: preparing.xml:1468
#, no-c-format
msgid ""
"If you are using a serial console, send a break to the machine. With "
"Minicom, use <keycap>Ctrl-A F</keycap>, with cu, hit <keycap>Enter</keycap>, "
"then type <userinput>%~break</userinput>. Consult the documentation of your "
"terminal emulator if you are using a different program."
msgstr ""
"Si vous utilisez une console sÃ©rie, envoyez un <quote>break</quote> Ã  la "
"machine. Avec Minicom, utilisez <keycap>Ctrl-A F</keycap>&nbsp;; avec cu, "
"utilisez <keycap>Enter</keycap>. Puis saisissez <userinput>%~break</"
"userinput>. Veuillez consulter la documentation de votre terminal si vous "
"utilisez un programme diffÃ©rent."

#. Tag: para
#: preparing.xml:1481
#, no-c-format
msgid ""
"You can use OpenBoot to boot from specific devices, and also to change your "
"default boot device. However, you need to know some details about how "
"OpenBoot names devices; it's considerably different from Linux device "
"naming, described in <xref linkend=\"device-names\"/>. Also, the command "
"will vary a bit, depending on what version of OpenBoot you have. More "
"information about OpenBoot can be found in the <ulink url=\"&url-openboot;"
"\">Sun OpenBoot Reference</ulink>."
msgstr ""
"Vous pouvez utiliser OpenBoot pour dÃ©marrer Ã  partir de pÃ©riphÃ©riques "
"spÃ©cifiques, et aussi pour modifier le pÃ©riphÃ©rique de dÃ©marrage par dÃ©faut. "
"Cependant, vous devez connaÃ®tre certains dÃ©tails sur la maniÃ¨re dont "
"OpenBoot nomme les pÃ©riphÃ©riques&nbsp;; c'est trÃ¨s diffÃ©rent du nommage des "
"pÃ©riphÃ©riques sous Linux, dÃ©crit dans la <xref linkend=\"device-names\"/>. "
"De plus, la commande varie lÃ©gÃ¨rement, selon la version d'OpenBoot. Vous "
"trouverez plus d'informations sur OpenBoot dans la <ulink url=\"&url-"
"openboot;\">rÃ©fÃ©rence OpenBoot Sun </ulink>."

#. Tag: para
#: preparing.xml:1491
#, no-c-format
msgid ""
"Typically, with newer revisions, you can use OpenBoot devices such as "
"<quote>floppy</quote>, <quote>cdrom</quote>, <quote>net</quote>, "
"<quote>disk</quote>, or <quote>disk2</quote>. These have the obvious "
"meanings; the <quote>net</quote> device is for booting from the network. "
"Additionally, the device name can specify a particular partition of a disk, "
"such as <quote>disk2:a</quote> to boot disk2, first partition. Full OpenBoot "
"device names have the form: <informalexample> <screen>\n"
"<replaceable>driver-name</replaceable>@\n"
"<replaceable>unit-address</replaceable>:\n"
"<replaceable>device-arguments</replaceable>\n"
"</screen></informalexample> In older revisions of OpenBoot, device naming is "
"a bit different: the floppy device is called <quote>/fd</quote>, and SCSI "
"disk devices are of the form <quote>sd(<replaceable>controller</"
"replaceable>, <replaceable>disk-target-id</replaceable>, <replaceable>disk-"
"lun</replaceable>)</quote>. The command <userinput>show-devs</userinput> in "
"newer OpenBoot revisions is useful for viewing the currently configured "
"devices. For full information, whatever your revision, see the <ulink url="
"\"&url-openboot;\">Sun OpenBoot Reference</ulink>."
msgstr ""
"Dans les versions rÃ©centes, vous pouvez utiliser les pÃ©riphÃ©riques OpenBoot "
"tels que <quote>floppy</quote>, <quote>cdrom</quote>, <quote>net</quote>, "
"<quote>disk</quote> ou <quote>disk2</quote>. Ceux-ci ont des significations "
"Ã©videntes (N.D.T&nbsp;: pour les anglophones). Le pÃ©riphÃ©rique <quote>net</"
"quote> sert Ã  dÃ©marrer par le rÃ©seau. Le nom du pÃ©riphÃ©rique peut indiquer "
"une partition de disque comme <quote>disk2:a</quote> pour amorcer le second "
"disque. Le nom des pÃ©riphÃ©riques OpenBoot est de cette forme&nbsp;: "
"<informalexample> <screen>\n"
"<replaceable>nom-pilote</replaceable>@\n"
"<replaceable>adresse-unitÃ©</replaceable>:\n"
"<replaceable>arguments-pÃ©riphÃ©rique</replaceable>\n"
"</screen></informalexample> Avec les anciennes versions d'OpenBoot, le "
"nommage des pÃ©riphÃ©riques est lÃ©gÃ¨rement diffÃ©rent. Le lecteur de disquette "
"s'appelle <quote>/fd</quote>, et les noms des disques durs SCSI sont de la "
"forme <quote>sd(<replaceable>contrÃ´leur</replaceable>, <replaceable>disk-"
"target-id</replaceable>, <replaceable>unitÃ©-logique-du-disque</replaceable>)"
"</quote>. La commande <userinput>show-devs</userinput> dans les nouvelles "
"versions d'OpenBoot est utile pour voir les pÃ©riphÃ©riques actuellement "
"configurÃ©s. Pour des informations complÃ¨tes quelle que soit votre version "
"d'OpenBoot, voyez la <ulink url=\"&url-openboot;\">rÃ©fÃ©rence OpenBoot Sun</"
"ulink>."

#. Tag: para
#: preparing.xml:1514
#, no-c-format
msgid ""
"To boot from a specific device, use the command <userinput>boot "
"<replaceable>device</replaceable></userinput>. You can set this behavior as "
"the default using the <userinput>setenv</userinput> command. However, the "
"name of the variable to set changed between OpenBoot revisions. In OpenBoot "
"1.x, use the command <userinput>setenv boot-from <replaceable>device</"
"replaceable></userinput>. In later revisions of OpenBoot, use the command "
"<userinput>setenv boot-device <replaceable>device</replaceable></userinput>. "
"Note, this is also configurable using the <command>eeprom</command> command "
"on Solaris, or modifying the appropriate files in <filename>/proc/openprom/"
"options/</filename>, for example under Linux: <informalexample><screen>\n"
"# echo disk1:1 &gt; /proc/openprom/options/boot-device\n"
"</screen></informalexample> and under Solaris:"
msgstr ""
"Pour dÃ©marrer sur un pÃ©riphÃ©rique spÃ©cifique, utilisez la commande "
"<userinput>boot <replaceable>device</replaceable></userinput>. Vous pouvez "
"positionner ce comportement comme valeur par dÃ©faut en utilisant la commande "
"<userinput>setenv</userinput>. Cependant, le nom de la variable Ã  "
"positionner a changÃ© entre les versions d'OpenBoot. Dans OpenBootÂ 1.x, "
"utilisez la commande <userinput>setenv boot-from <replaceable>device</"
"replaceable></userinput>. Dans les versions ultÃ©rieures, utilisez la "
"commande <userinput>setenv boot-device <replaceable>device</replaceable></"
"userinput>. N.B. On peut faire ce rÃ©glage Ã  partir de la commande "
"<command>eeprom</command> sous Solaris, ou, sous Linux, en modifiant les "
"fichiers dans <filename>/proc/openprom/options/</filename>. Par exemple sous "
"Linux&nbsp;: <informalexample><screen>\n"
"# echo disk1:1 &gt; /proc/openprom/options/boot-device\n"
"</screen></informalexample> et sous SolarisÂ :"

#. Tag: screen
#: preparing.xml:1533
#, no-c-format
msgid "eeprom boot-device=disk1:1"
msgstr "# eeprom boot-device=disk1:1"

#. Tag: title
#: preparing.xml:1543
#, no-c-format
msgid "BIOS Setup"
msgstr "ParamÃ©trage du BIOS"

#. Tag: para
#: preparing.xml:1544
#, no-c-format
msgid ""
"In order to install &debian-gnu; on a &arch-title; or zSeries machine you "
"have first boot a kernel into the system. The boot mechanism of this "
"platform is inherently different to other ones, especially from PC-like "
"systems: there are no floppy devices available at all. You will notice "
"another big difference while you work with this platform: most (if not all) "
"of the time you will work remote, with the help of some client session "
"software like telnet, or a browser. This is due to that special system "
"architecture where the 3215/3270 console is line-based instead of character-"
"based."
msgstr ""
"Afin d'installer &debian-gnu; sur une machine de la gamme &arch-title; ou "
"zSeries, vous devez d'abord dÃ©marrer un noyau sur le systÃ¨me. Le mÃ©canisme "
"d'amorÃ§age est intrinsÃ¨quement diffÃ©rent des autres systÃ¨mes, en particulier "
"des PC&nbsp;: il n'y a pas de lecteur de disquette. Vous remarquerez une "
"autre diffÃ©rence lorsque vous travaillez sur cette plate-forme&nbsp;; la "
"plupart du temps (si ce n'est tout le temps), vous travaillerez Ã  distance, "
"avec l'aide d'un logiciel appropriÃ© comme telnet, ou un navigateur. C'est dÃ» "
"Ã  l'architecture spÃ©ciale du systÃ¨me, oÃ¹ la console 3215/3270 est orientÃ©e "
"ligne et non caractÃ¨re."

#. Tag: para
#: preparing.xml:1556
#, no-c-format
msgid ""
"Linux on this platform runs either natively on the bare machine, in a so-"
"called LPAR (Logical Partition) or in a virtual machine supplied by the VM "
"system. Boot media differs depending on the runtime mode. For example, you "
"can use the virtual card reader of a virtual machine, or boot from the HMC "
"(Hardware Management Console) of an LPAR if the HMC and this option is "
"available for you."
msgstr ""
"Linux sur cette plate-forme travaille soit nativement sur la machine nue, "
"dans une LPAR (partition logique), soit dans une machine virtuelle fournie "
"par le systÃ¨me VM. Les supports d'amorÃ§age varient en fonction du mode "
"d'exÃ©cution. Par exemple, vous pouvez utiliser le lecteur de carte virtuel "
"d'une machine virtuelle, ou dÃ©marrez depuis la HMC (<emphasis>Hardware "
"Management Console</emphasis>, console d'administration matÃ©rielle) d'une "
"LPAR si la HMC et cette option sont disponibles."

#. Tag: para
#: preparing.xml:1565
#, no-c-format
msgid ""
"Before you actually perform an installation, you have to go over some design "
"and preparation steps. IBM has made documentation available about the whole "
"process, e.g. how to prepare an installation medium and how actually to boot "
"from that medium. Duplicating that information here is neither possible nor "
"necessary. However, we will describe here which kind of &debian;-specific "
"data is needed and where to find it. Using both sources of information, you "
"have to prepare your machine and the installation medium before you can "
"perform a boot from it. When you see the welcome message in your client "
"session, return to this document to go through the &debian;-specific "
"installation steps."
msgstr ""
"Avant de vous lancer dans une installation, vous devez d'abord passer par "
"des Ã©tapes prÃ©liminaires. IBM fournit une documentation sur le processus, "
"par exemple sur la prÃ©paration du support d'installation et sur le dÃ©marrage "
"depuis ce support. Recopier cette information ici n'est ni possible, ni "
"nÃ©cessaire. Cependant, nous dÃ©crivons les points spÃ©cifiques Ã  &debian; et "
"comment les trouver. Quel que soit le mode d'installation choisi, vous devez "
"d'abord prÃ©parer votre machine et le support d'installation, puis dÃ©marrer "
"depuis celui-ci. Une fois le message de bienvenue affichÃ© dans votre client "
"de session, revenez lire ce document pour les Ã©tapes de l'installation "
"spÃ©cifiques Ã  &debian;."

#. Tag: title
#: preparing.xml:1582
#, no-c-format
msgid "Native and LPAR installations"
msgstr "Installations en mode natif et sur LPAR"

#. Tag: para
#: preparing.xml:1583
#, no-c-format
msgid ""
"Please refer to chapter 5 of the <ulink url=\"http://www.redbooks.ibm.com/";
"pubs/pdfs/redbooks/sg244987.pdf\"> Linux for &arch-title;</ulink> Redbook "
"and chapter 3.2 of the <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/";
"redbooks/sg246264.pdf\"> Linux for IBM eServer zSeries and &arch-title;: "
"Distributions</ulink> Redbook on how to set up an LPAR for Linux."
msgstr ""
"Veuillez consulter le chapitreÂ 5 du livre rouge <ulink url=\"http://www.";
"redbooks.ibm.com/pubs/pdfs/redbooks/sg244987.pdf\">Linux pour S/390</ulink> "
"et le chapitreÂ 3.2 du livre rouge <ulink url=\"http://www.redbooks.ibm.com/";
"pubs/pdfs/redbooks/sg246264.pdf\">Linux pour IBM eServer zSeries et les "
"distributions S/390</ulink> pour apprendre comment configurer une LPAR pour "
"Linux."

#. Tag: title
#: preparing.xml:1597
#, no-c-format
msgid "Installation as a VM guest"
msgstr "Installation en tant qu'invitÃ© VM"

#. Tag: para
#: preparing.xml:1599
#, no-c-format
msgid ""
"Please refer to chapter 6 of the <ulink url=\"http://www.redbooks.ibm.com/";
"pubs/pdfs/redbooks/sg244987.pdf\"> Linux for &arch-title;</ulink> Redbook "
"and chapter 3.1 of the <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/";
"redbooks/sg246264.pdf\"> Linux for IBM eServer zSeries and &arch-title;: "
"Distributions</ulink> Redbook on how to set up a VM guest for running Linux."
msgstr ""
"Veuillez consulter le chapitreÂ 6 du livre rouge <ulink url=\"http://www.";
"redbooks.ibm.com/pubs/pdfs/redbooks/sg244987.pdf\">Linux pour S/390</ulink> "
"et le chapitreÂ 3.1 du livre rouge <ulink url=\"http://www.redbooks.ibm.com/";
"pubs/pdfs/redbooks/sg246264.pdf\">Linux pour IBM eServer zSeries et "
"distributions S/390</ulink> pour apprendre comment configurer un invitÃ© VM "
"pour Linux."

#. Tag: para
#: preparing.xml:1609
#, no-c-format
msgid ""
"You need to copy all the files from the <filename>generic</filename> sub-"
"directory to your CMS disk. Be sure to transfer <filename>kernel.debian</"
"filename> and <filename>initrd.debian</filename> in binary mode with a fixed "
"record length of 80 characters (by specifying <userinput>BINARY</userinput> "
"and <userinput>LOCSITE FIX 80</userinput> in your FTP client). "
"<filename>parmfile.debian</filename> can be in either ASCII or EBCDIC "
"format. A sample <filename>debian.exec</filename> script, which will punch "
"the files in the proper order, is included with the images."
msgstr ""
"Vous devez copier tous les fichiers depuis le sous-rÃ©pertoire "
"<filename>generic</filename> sur votre disque CMS. Assurez-vous d'avoir "
"transfÃ©rÃ© <filename>kernel.debian</filename> et <filename>initrd.debian</"
"filename> en mode binaire avec une taille fixe de 80Â caractÃ¨res pour les "
"enregistrements. Vous devez spÃ©cifier les paramÃ¨tres <userinput>BINARY</"
"userinput> et <userinput>LOCSITE FIXÂ 80</userinput> Ã  votre client FTP. Le "
"format du fichier <filename>parmfile.debian</filename> peut Ãªtre ASCII ou "
"EBCDIC. Un script d'exemple <filename>debian.exec</filename>, qui introduira "
"les fichiers dans le bon ordre, se trouve avec les images."

#. Tag: title
#: preparing.xml:1626
#, no-c-format
msgid "Setting up an installation server"
msgstr "Configurer un serveur d'installation"

#. Tag: para
#: preparing.xml:1628
#, no-c-format
msgid ""
"If you don't have a connection to the Internet (either directly or via a web "
"proxy) you need to create a local installation server that can be accessed "
"from your S/390. This server keeps all the packages you want to install and "
"must make them available using NFS, HTTP or FTP."
msgstr ""
"Si vous n'avez pas de connexion Ã  Internet (directement ou Ã  travers un "
"mandataire web), vous devez crÃ©er un serveur d'installation local qui peut "
"Ãªtre atteint depuis votre S/390. Ce serveur garde tous les paquets que vous "
"voulez installer et doit les rendre accessibles avec NFS, HTTP ou FTP."

#. Tag: para
#: preparing.xml:1636
#, no-c-format
msgid ""
"The installation server needs to copy the exact directory structure from any "
"&debian-gnu; mirror, but only the s390 and architecture-independent files "
"are required. You can also copy the contents of all installation CDs into "
"such a directory tree."
msgstr ""
"Le serveur d'installation a besoin de copier l'arborescence exacte depuis "
"n'importe quel miroir &debian-gnu;, mais il n'a besoin de copier que les "
"fichiers s390 et ceux indÃ©pendants de l'architecture. Vous pouvez aussi "
"utiliser le contenu des CD d'installation."

#. Tag: emphasis
#: preparing.xml:1645
#, no-c-format
msgid "FIXME: more information needed &mdash; from a Redbook?"
msgstr "FIXME: more information needed &mdash; from a Redbook?"

#. Tag: title
#: preparing.xml:1655
#, no-c-format
msgid "ARM firmware"
msgstr "Microprogramme ARM"

#. Tag: para
#: preparing.xml:1657
#, no-c-format
msgid ""
"As already mentioned before, there is unfortunately no standard for system "
"firmware on ARM systems. Even the behaviour of different systems which use "
"nominally the same firmware can be quite different. This results from the "
"fact that a large part of the devices using the ARM architecture are "
"embedded systems, for which the manufacturers usually build heavily "
"customized firmware versions and include device-specific patches. "
"Unfortunately the manufacturers often do not submit their changes and "
"extensions back to the mainline firmware developers, so their changes are "
"not integrated into newer versions of the original firmware."
msgstr ""
"Comme Ã©voquÃ© plus haut, il n'y a malheureusement pas de standard de "
"microprogramme sur les systÃ¨mes ARM. MÃªme le comportement de deux systÃ¨mes "
"qui utilisent le mÃªme microprogramme peut Ãªtre diffÃ©rent. Cela vient du fait "
"que beaucoup de pÃ©riphÃ©riques utilisant l'architecture ARM sont des systÃ¨mes "
"embarquÃ©s, pour lesquels les constructeurs produisent des versions de "
"microprogramme largement personnalisÃ©es et incluent des correctifs "
"spÃ©cifiques au matÃ©riel. Malheureusement, ces constructeurs ne remontent pas "
"leurs modifications et extensions aux dÃ©veloppeurs de la branche principale, "
"et leurs changements ne sont pas intÃ©grÃ©s aux nouvelles versions du "
"microprogramme original."

#. Tag: para
#: preparing.xml:1669
#, no-c-format
msgid ""
"As a result even newly sold systems often use a firmware that is based on a "
"years-old manufacturer-modified version of a firmware whose mainline "
"codebase has evolved a lot further in the meantime and offers additional "
"features or shows different behaviour in certain aspects. In addition to "
"that, the naming of onboard devices is not consistent between different "
"manufacturer-modified versions of the same firmware, therefore it is nearly "
"impossible to provide usable product-independend instructions for ARM-based "
"systems."
msgstr ""
"En consÃ©quence de cela, mÃªme les nouveaux systÃ¨mes vendus utilisent souvent "
"un microprogramme basÃ© sur une ancienne version propre au constructeur, "
"alors que la branche principale a beaucoup Ã©voluÃ© et offre maintenant des "
"fonctionnalitÃ©s supplÃ©mentaires, ou se comporte diffÃ©remment. De plus, les "
"nommages des pÃ©riphÃ©riques embarquÃ©s ne sont pas cohÃ©rents d'un fabriquant Ã  "
"l'autre pour le mÃªme microprogramme. Il est donc presque impossible de "
"fournir des instructions utilisables pour tous les systÃ¨mes basÃ©s sur ARM."

#. Tag: title
#: preparing.xml:1682
#, no-c-format
msgid "Debian-provided U-Boot (system firmware) images"
msgstr "Images U-Boot fournies par Debian (microcode systÃ¨me)"

#. Tag: para
#: preparing.xml:1683
#, no-c-format
msgid ""
"Debian provides U-Boot images for various armhf systems that can load their "
"U-Boot from an SD card at &armmp-uboot-img;. The U-Boot builds are offered "
"in two formats: raw U-Boot components and a ready-made card image that can "
"easily be written onto an SD card. The raw U-Boot components are provided "
"for advanced users; the generally recommended way is to use one of the ready-"
"made SD card images. They are named &lt;system-type&gt;.sdcard.img.gz and "
"can be written to a card e.g. with <informalexample><screen>zcat &lt;system-"
"type&gt;.sdcard.img.gz > /dev/SD_CARD_DEVICE</screen></informalexample> As "
"with all images, please be aware that writing the image to an SD card wipes "
"all previous contents of the card!"
msgstr ""
"Debian fournit des images U-Boot Ã  &armmp-uboot-img;, pour divers systÃ¨mes "
"armhf qui peuvent charger U-Boot depuis une carte SD. Les images U-Boot sont "
"fournies dans deux formatÂ : les composants bruts U-Boot ou une image toute "
"faite et prÃªte Ã  Ãªtre Ã©crite sur une carte SD. Les composants bruts sont "
"destinÃ©s aux utilisateurs confirmÃ©s car la mÃ©thode recommandÃ©e est "
"d'utiliser une des images prÃ©compilÃ©es. Ces derniÃ¨res sont appelÃ©es &lt;"
"type_de_systÃ¨me&gt;.sdcard.img.gz et peuvent Ãªtre Ã©crites sur une carte par "
"exemple avecÂ : <informalexample><screen>zcat &lt;type_de_systÃ¨me&gt;.sdcard."
"img.gz > /dev/PÃ?RIPHÃ?RIQUE_DE_CARTE_SD</screen></informalexample> Comme pour "
"toutes les images, soyez conscient que cela supprimera tout ce qu'il y avait "
"sur la carteÂ !"

#. Tag: para
#: preparing.xml:1698
#, no-c-format
msgid ""
"If Debian provides a U-Boot image for your system, it is recommended that "
"you use this image instead of the vendor-provided U-Boot, as the version in "
"Debian is usually newer and has more features."
msgstr ""
"Si Debian fornit une image U-Boot pour votre systÃ¨me, il est recommandÃ© "
"d'utiliser cette image plutÃ´t qu'une version de U-Boot du distributeur, car "
"la version de Debian est gÃ©nÃ©ralement plus Ã  jour et contient plus de "
"fonctionnalitÃ©s."

#. Tag: title
#: preparing.xml:1706
#, no-c-format
msgid "Setting the ethernet MAC address in U-Boot"
msgstr "Configurer l'adresse MAC Ethernet dans U-Boot"

#. Tag: para
#: preparing.xml:1707
#, no-c-format
msgid ""
"The MAC address of every ethernet interface should normally be globally "
"unique, and it technically has to be unique within its ethernet broadcast "
"domain. To achieve this, the manufacturer usually allocates a block of MAC "
"addresses from a centrally-administered pool (for which a fee has to be "
"paid) and preconfigures one of these addresses on each item sold."
msgstr ""
"L'adresse MAC de chaque interface ethernet devrait normalement Ãªtre unique "
"de faÃ§on globale, et doit surtout Ãªtre unique au sein de son domaine rÃ©seau. "
"Pour y parvenir, les constructeurs rÃ©servent gÃ©nÃ©ralement un lot d'adresses "
"MAC depuis une rÃ©serve centrale (pour laquelle il faut payer) et "
"prÃ©configurent une de ces adresses sur chaque Ã©lÃ©ment vendu."

#. Tag: para
#: preparing.xml:1715
#, no-c-format
msgid ""
"In the case of development boards, sometimes the manufacturer wants to avoid "
"paying these fees and therefore provides no globally unique addresses. In "
"these cases the users themselves have to define MAC addresses for their "
"systems. When no MAC address is defined for an ethernet interface, some "
"network drivers generate a random MAC address that can change on every boot, "
"and if this happens, network access would be possible even when the user has "
"not manually set an address, but e.g. assigning semi-static IP addresses by "
"DHCP based on the MAC address of the requesting client would obviously not "
"work reliably."
msgstr ""
"Dans le cas des cartes de dÃ©veloppement, certains constructeurs veulent "
"Ã©viter de payer ces frais et ne fournissent pas d'adresse rÃ©ellement unique. "
"Dans ce cas, les utilisateurs doivent dÃ©finir eux-mÃªmes une adresse MAC pour "
"leurs systÃ¨mes. Si aucune adresse MAC n'est dÃ©finie pour une interface "
"ethernet, certains pilotes de rÃ©seau gÃ©nÃ¨rent une adresse MAC alÃ©atoire qui "
"peut changer Ã  chaque dÃ©marrage. Dans cette configuration, l'accÃ¨s au rÃ©seau "
"est possible mÃªme si l'utilisateur n'a pas configurÃ© d'adresse, mais p. ex. "
"assigner une adresse IP semi statique par DHCP, basÃ©e sur l'adresse MAC du "
"client, ne fonctionnerait Ã©videmment pas correctement."

#. Tag: para
#: preparing.xml:1726
#, no-c-format
msgid ""
"To avoid conflicts with existing officially-assigned MAC addresses, there is "
"an address pool which is reserved for so-called <quote>locally administered</"
"quote> addresses. It is defined by the value of two specific bits in the "
"first byte of the address (the article <quote>MAC address</quote> in the "
"English language Wikipedia gives a good explanation). In practice this means "
"that e.g. any address starting with hexadecimal ca (such as ca:ff:"
"ee:12:34:56) can be used as a locally administered address."
msgstr ""
"Pour Ã©viter les conflits avec les adresses MAC officiellement assignÃ©es, il "
"y a une rÃ©serve pour les adresses <quote>administrÃ©es localement</quote>. "
"Elles sont dÃ©finies par la valeur de deux bits spÃ©cifiques dans le premier "
"octet de leur adresse (l'article <quote>Adresse MAC</quote> sur WikipÃ©dia, "
"ou <quote> MAC address</quote> sur la page anglaise, donne une bonne "
"explication). En pratique, cela veut dire que toute adresse commenÃ§ant avec "
"la chaÃ®ne hexadÃ©cimale ca (comme ca:ff:ee:12:34:56) peut Ãªtre utilisÃ©e comme "
"administrÃ©e localement."

#. Tag: para
#: preparing.xml:1736
#, no-c-format
msgid ""
"On systems using U-Boot as system firmware, the ethernet MAC address is "
"placed in the <quote>ethaddr</quote> environment variable. It can be checked "
"at the U-Boot command prompt with the command <quote>printenv ethaddr</"
"quote> and can be set with the command <quote>setenv ethaddr ca:ff:"
"ee:12:34:56</quote>. After setting the value, the command <quote>saveenv</"
"quote> makes the assignment permanent."
msgstr ""
"Sur les systÃ¨mes utilisant U-Boot comme microprogramme systÃ¨me, l'adresse "
"MAC ethernet est placÃ©e dans la variable d'environnement <quote>ethaddr</"
"quote>. Elle peut Ãªtre vÃ©rifiÃ©e Ã  l'invite de U-Boot avec la commande "
"<quote>printenv ethaddr</quote> et peut Ãªtre positionnÃ©e avec <quote>setenv "
"ethaddr ca:ff:ee:12:34:56</quote>. AprÃ¨s avoir positionnÃ©e la variable, la "
"commande <quote>saveenv</quote> rend la modification permanente."

#. Tag: title
#: preparing.xml:1747
#, no-c-format
msgid "Kernel/Initrd/Device-Tree relocation issues in U-Boot"
msgstr ""
"ProblÃ¨mes de positionnement du noyau, de l'initrd et de l'arbre de "
"pÃ©riphÃ©riques dans U-Boot"

#. Tag: para
#: preparing.xml:1748
#, no-c-format
msgid ""
"On some systems with older U-Boot versions there can be problems with "
"properly relocating the Linux kernel, the initial ramdisk and the device-"
"tree blob in memory during the boot process. In this case, U-Boot shows the "
"message <quote>Starting kernel ...</quote>, but the system freezes "
"afterwards without further output. These issues have been solved with newer "
"U-Boot versions from v2014.07 onwards."
msgstr ""
"Sur certains systÃ¨mes avec d'anciennes versions de U-Boot, il peut y avoir "
"des problÃ¨mes de dÃ©placement du noyau Linux, de l'image mÃ©moire initiale ou "
"de l'arbre des pÃ©riphÃ©riques dans la mÃ©moire lors du dÃ©marrage. Dans ce cas, "
"U-Boot affiche le message <quote>Starting kernel ...</quote>, mais le "
"systÃ¨me gÃ¨le aprÃ¨s cela sans autre message. Ces problÃ¨mes ont Ã©tÃ© rÃ©solus "
"dans les nouvelles versions de U-Boot, postÃ©rieures Ã  v2014.07."

#. Tag: para
#: preparing.xml:1757
#, no-c-format
msgid ""
"If the system has originally used a U-Boot version older than v2014.07 and "
"has been upgraded to a newer version later, the problem might still occur "
"even after upgrading U-Boot. Upgrading U-Boot usually does not modify the "
"existing U-Boot environment variables and the fix requires an additional "
"environment variable (bootm_size) to be set, which U-Boot does automatically "
"only on fresh installations without existing environment data. It is "
"possible to manually set bootm_size to the new U-Boot's default value by "
"running the command <quote>env default bootm_size; saveenv</quote> at the U-"
"Boot prompt."
msgstr ""
"Si le systÃ¨me utilisait une version plus ancienne que la v2014.07, et mÃªme "
"aprÃ¨s une mise Ã  niveau de U-Boot, le problÃ¨me peut encore apparaÃ®tre. La "
"mise Ã  niveau de U-Boot ne modifie gÃ©nÃ©ralement pas les variables "
"d'environnement existantes et le correctif nÃ©cessite une variable "
"d'environnement supplÃ©mentaire (bootm_size), qui nâ??est crÃ©Ã©e automatiquement "
"que sur les nouvelles installations sans variable dâ??environnement existante, "
"Il est possible de positionner manuellement la variable bootm_size Ã  la "
"nouvelle valeur par dÃ©faut en exÃ©cutant la commande <quote>env default "
"bootm_size; saveenv</quote> Ã  l'invite de U-Boot."

#. Tag: para
#: preparing.xml:1768
#, no-c-format
msgid ""
"Another possibility to circumvent relocation-related problems is to run the "
"command <quote>setenv fdt_high ffffffff; setenv initrd_high 0xffffffff; "
"saveenv</quote> at the U-Boot prompt to completely disable the relocation of "
"the initial ramdisk and the device-tree blob."
msgstr ""
"Une autre possibilitÃ© de contourner les problÃ¨mes liÃ©s au dÃ©placement est "
"d'exÃ©cuter la commande <quote>setenv fdt_high ffffffff; setenv initrd_high "
"0xffffffff; saveenv</quote> Ã  l'invite de U-Boot, pour dÃ©sactiver totalement "
"le dÃ©placement du disque mÃ©moire initial et de l'arbre de pÃ©riphÃ©riques."

#. Tag: title
#: preparing.xml:1778
#, no-c-format
msgid "Systems with UEFI firmware"
msgstr "SystÃ¨mes avec un microprogramme UEFI"

#. Tag: para
#: preparing.xml:1779
#, no-c-format
msgid ""
"UEFI (<quote>Unified Extensible Firmware Interface</quote>) is a new kind of "
"system firmware that is used on many modern systems and is - among other "
"uses - intended to replace the classic PC BIOS."
msgstr ""
"UEFI (<quote>Interface micrologicielle extensible unifiÃ©e</quote> ou "
"<quote>Unified Extensible Firmware Interface</quote>) est un nouveau type de "
"microprogramme utilisÃ© sur de nombreux systÃ¨mes rÃ©cents et est prÃ©vu, entre "
"autre, pour remplacer le BIOS classique des PC."

#. Tag: para
#: preparing.xml:1785
#, no-c-format
msgid ""
"Currently most PC systems that use UEFI also have a so-called "
"<quote>Compatibility Support Module</quote> (CSM) in the firmware, which "
"provides excatly the same interfaces to an operating system as a classic PC "
"BIOS, so that software written for the classic PC BIOS can be used "
"unchanged. Nonetheless UEFI is intended to one day completely replace the "
"old PC BIOS without being fully backwards-compatible and there are already a "
"lot of systems with UEFI but without CSM."
msgstr ""
"Actuellement, la majoritÃ© des systÃ¨mes PC qui utilisent l'UEFI intÃ¨grent "
"aussi un module de compatibilitÃ© (<quote>Compatibility Support Module</"
"quote> (CSM)) dans le microprogramme, qui procure les mÃªmes interfaces que "
"le BIOS au systÃ¨me d'exploitation. Ainsi les logiciels Ã©crits pour le BIOS "
"classique peuvent Ãªtre utilisÃ©s sans changement. MalgrÃ© cela, l'UEFI est "
"prÃ©vu pour remplacer complÃ¨tement les anciens BIOS sans Ãªtre totalement "
"rÃ©trocompatible, et il existe dÃ©jÃ  certains systÃ¨mes avec UEFI mais sans CSM."

#. Tag: para
#: preparing.xml:1795
#, no-c-format
msgid ""
"On systems with UEFI there are a few things to take into consideration when "
"installing an operating system. The way the firmware loads an operating "
"system is fundamentally different between the classic BIOS (or UEFI in CSM "
"mode) and native UEFI. One major difference is the way the harddisk "
"partitions are recorded on the harddisk. While the classic BIOS and UEFI in "
"CSM mode use a DOS partition table, native UEFI uses a different "
"partitioning scheme called <quote>GUID Partition Table</quote> (GPT). On a "
"single disk, for all practical purposes only one of the two can be used and "
"in case of a multi-boot setup with different operating systems on one disk, "
"all of them must therefore use the same type of partition table. Booting "
"from a disk with GPT is only possible in native UEFI mode, but using GPT "
"becomes more and more common as hard disk sizes grow, because the classic "
"DOS partition table cannot address disks larger than about 2 Terabytes while "
"GPT allows for far larger disks. The other major difference between BIOS (or "
"UEFI in CSM mode) and native UEFI is the location where boot code is stored "
"and in which format it has to be. This means that different bootloaders are "
"needed for each system."
msgstr ""
"Sur les systÃ¨mes avec UEFI, il y a certains dÃ©tails Ã  prendre en compte "
"lorsqu'on installe un systÃ¨me d'exploitation. La faÃ§on dont le "
"microprogramme charge le systÃ¨me d'exploitation est trÃ¨s diffÃ©rente entre le "
"BIOS classique (ou l'UEFI avec CSM) et l'UEFI natif. Une des principales "
"diffÃ©rences est la faÃ§on d'enregistrer les partitions sur le disque dur. "
"Alors que le BIOS et l'UEFI avec CSM utilisent une table de partitionnement "
"DOS, l'UEFI utilise un schÃ©ma de partition diffÃ©rent appelÃ© <quote>GUID "
"Partition Table</quote> (GPT). Sur un seul disque, une seule faÃ§on peut Ãªtre "
"utilisÃ©e, et dans le cas d'une installation multi-boot avec diffÃ©rents "
"systÃ¨mes d'exploitation sur le mÃªme disque, tous doivent utiliser le mÃªme "
"type de table de partitions. Amorcer depuis un disque avec GPT n'est "
"possible qu'en mode UEFI natif, mais utiliser GPT devient de plus en plus "
"commun Ã  mesure que les disques grossissent, car la table de partitionnement "
"DOS classique ne peut pas adresser des disques de plus de 2Â TÃ©raoctets alors "
"que GPT le permet. L'autre principale diffÃ©rence entre le BIOS (ou l'UEFI "
"avec CSM) et l'UEFI natif rÃ©side dans la localisation et le format du code "
"d'amorÃ§age. Ainsi, des chargeurs d'amorÃ§age (<quote>bootloaders</quote>) "
"diffÃ©rents sont utilisÃ©s pour chaque systÃ¨me."

#. Tag: para
#: preparing.xml:1815
#, no-c-format
msgid ""
"The latter becomes important when booting &d-i; on a UEFI system with CSM "
"because &d-i; checks whether it was started on a BIOS- or on a native UEFI "
"system and installs the corresponding bootloader. Normally this simply works "
"but there can be a problem in multi-boot environments. On some UEFI systems "
"with CSM the default boot mode for removable devices can be different from "
"what is actually used when booting from hard disk, so when booting the "
"installer from a USB stick in a different mode from what is used when "
"booting another already installed operating system from the hard disk, the "
"wrong bootloader might be installed and the system might be unbootable after "
"finishing the installation. When choosing the boot device from a firmware "
"boot menu, some systems offer two seperate choices for each device, so that "
"the user can select whether booting shall happen in CSM or in native UEFI "
"mode."
msgstr ""
"Ce dernier point devient important au dÃ©marrage de l'&d-i; sur un systÃ¨me "
"UEFI avec CSM parce que l'installateur vÃ©rifie s'il a Ã©tÃ© dÃ©marrÃ© sur un "
"systÃ¨me BIOS ou UEFI natif, et installe le chargeur de d'amorÃ§age "
"correspondant. Habituellement, cela fonctionne sans problÃ¨me, mais peut en "
"poser dans les environnements multi-boot. Sur certains systÃ¨mes UEFI avec "
"CSM, le mode d'amorÃ§age par dÃ©faut des pÃ©riphÃ©riques amovibles peut Ãªtre "
"diffÃ©rent de celui utilisÃ© Ã  l'amorÃ§age depuis le disque dur. Ainsi, Ã  "
"l'amorÃ§age de l'&d-i; depuis une clef USB dans un mode diffÃ©rent de celui "
"utilisÃ© lors de l'amorÃ§age du systÃ¨me d'exploitation dÃ©jÃ  installÃ© sur le "
"disque dur, le mauvais chargeur de d'amorÃ§age peut Ãªtre installÃ© et le "
"systÃ¨me devient impossible Ã  dÃ©marrer aprÃ¨s l'installation. Au moment de "
"choisir le pÃ©riphÃ©rique d'amorÃ§age depuis le menu du microprogramme, "
"certains systÃ¨mes offrent deux choix pour chaque pÃ©riphÃ©rique, ainsi "
"l'utilisateur peut choisir si l'amorÃ§age doit se faire avec CSM ou en mode "
"UEFI natif."

#. Tag: para
#: preparing.xml:1831
#, no-c-format
msgid ""
"Another UEFI-related topic is the so-called <quote>secure boot</quote> "
"mechanism. Secure boot means a function of UEFI implementations that allows "
"the firmware to only load and execute code that is cryptographically signed "
"with certain keys and thereby blocking any (potentially malicious) boot code "
"that is unsigned or signed with unknown keys. In practice the only key "
"accepted by default on most UEFI systems with secure boot is a key from "
"Microsoft used for signing the Windows bootloader. As the boot code used by "
"&d-i; is not signed by Microsoft, booting the installer requires prior "
"deactivation of secure boot in case it is enabled. Secure boot is often "
"enabled by default on systems that come preinstalled with a 64-bit version "
"of Windows 8 and there is unfortunately no standard way to disable it in the "
"UEFI setup. On some systems, the option to disable secure boot is only made "
"visible when a BIOS password has been set by the user, so if you have a "
"system with secure boot enabled, but cannot find an option to disable it, "
"try setting a BIOS password, powercycle the machine and look again for an "
"appropriate option."
msgstr ""
"Un autre sujet relatif Ã  l'UEFI est le mÃ©canisme appelÃ© <quote>secure boot</"
"quote> (dÃ©marrage sÃ©curisÃ©). Le dÃ©marrage sÃ©curisÃ© correspond Ã  une fonction "
"de l'UEFI qui autorise le microprogramme Ã  charger et exÃ©cuter uniquement du "
"code signÃ© par cryptographie avec certaines clefs et ainsi bloquer tout code "
"d'amorÃ§age (potentiellement dangereux) signÃ© avec une clef inconnue ou pas "
"signÃ© du tout. En pratique, la seule clef acceptÃ©e par dÃ©faut sur la plupart "
"des systÃ¨mes UEFI avec dÃ©marrage sÃ©curisÃ© est une clef de Microsoft utilisÃ©e "
"pour signer le chargeur d'amorÃ§age de Windows. Comme le code d'amorÃ§age "
"utilisÃ© par l'&d-i; n'est pas signÃ© par Microsoft, l'amorÃ§age de "
"l'installateur nÃ©cessite la dÃ©sactivation du dÃ©marrage sÃ©curisÃ©. Le "
"dÃ©marrage sÃ©curisÃ© est souvent activÃ© par dÃ©faut sur les systÃ¨mes vendus "
"prÃ©installÃ©s avec une version 64Â bits de WindowsÂ 8 et il n'y a "
"malheureusement pas de faÃ§on standard de dÃ©sactiver la configuration UEFI. "
"Sur certains systÃ¨mes, l'option pour dÃ©sactiver le dÃ©marrage sÃ©curisÃ© est "
"visible uniquement lorsqu'un mot de passe BIOS a Ã©tÃ© configurÃ© par "
"l'utilisateur. Ainsi, si vous avez un systÃ¨me avec le dÃ©marrage sÃ©curisÃ© "
"activÃ©, mais ne trouvez pas l'option pour le dÃ©sactiver, essayez de "
"configurer un mot de passe BIOS, redÃ©marrez la machine et cherchez de "
"nouveau une option appropriÃ©e."

#. Tag: title
#: preparing.xml:1853
#, no-c-format
msgid "Disabling the Windows 8 <quote>fast boot</quote> feature"
msgstr "DÃ©sactiver le dÃ©marrage rapide de WindowsÂ 8 (<quote>fast boot</quote>)"

#. Tag: para
#: preparing.xml:1854
#, no-c-format
msgid ""
"Windows 8 offers a feature called <quote>fast boot</quote> to cut down "
"system startup time. Technically, when this feature is enabled, Windows 8 "
"does not do a real shutdown and a real cold boot afterwards when ordered to "
"shut down, but instead does something resembling a partial suspend to disk "
"to reduce the <quote>boot</quote> time. As long as Windows 8 is the only "
"operating system on the machine, this is unproblematic, but it can result in "
"problems and data loss when you have a dual boot setup in which another "
"operating system accesses the same filesystems as Windows 8 does. In that "
"case the real state of the filesystem can be different from what Windows 8 "
"believes it to be after the <quote>boot</quote> and this could cause "
"filesystem corruption upon further write accesses to the filesystem. "
"Therefore in a dual boot setup, to avoid filesystem corruption the "
"<quote>fast boot</quote> feature has to be disabled within Windows."
msgstr ""
"WindowsÂ 8 offre une fonctionnalitÃ© appelÃ©e dÃ©marrage rapide (<quote>fast "
"boot</quote>) pour rÃ©duire le temps de dÃ©marrage. Techniquement, lorsque "
"cette fonction est activÃ©e, WindowsÂ 8 ne s'arrÃªte pas vraiment pour "
"redÃ©marrer <quote>Ã  froid</quote>, mais effectue quelque chose qui ressemble "
"plutÃ´t Ã  une hibernation partielle pour rÃ©duire le temps de Â«Â dÃ©marrageÂ Â». "
"Tant que WindowsÂ 8 est le seul systÃ¨me d'exploitation sur la machine, cela "
"ne pose pas de problÃ¨me, mais peut conduire Ã  des pertes de donnÃ©es et "
"d'autres inconvÃ©nients lorsque vous avez une configuration en <quote>dual "
"boot</quote> dans laquelle un autre systÃ¨me d'exploitation accÃ¨de au mÃªme "
"systÃ¨me de fichiers que WindowsÂ 8. Dans ce cas, le systÃ¨me de fichiers peut "
"Ãªtre dans un Ã©tat diffÃ©rent de ce qu'attend WindowsÂ 8 aprÃ¨s le "
"Â«Â dÃ©marrageÂ Â», et peut provoquer une corruption du systÃ¨me de fichiers lors "
"des nouveaux accÃ¨s en Ã©criture sur ce mÃªme systÃ¨me de fichiers. Pour cela, "
"dans une configuration en <quote>dual boot</quote>, pour Ã©viter la "
"corruption du systÃ¨me de fichiers, la fonctionnalitÃ© <quote>fast boot</"
"quote> doit Ãªtre dÃ©sactivÃ©e depuis Windows."

#. Tag: para
#: preparing.xml:1870
#, no-c-format
msgid ""
"It may also be necessary to disable <quote>fast boot</quote> to even allow "
"access to UEFI setup to choose to boot another operating system or &d-i;. On "
"some UEFI systems, the firmware will reduce <quote>boot</quote> time by not "
"initialising the keyboard controller or USB hardware; in these cases, it is "
"necessary to boot into Windows and disable this feature to allow for a "
"change of boot order."
msgstr ""
"Il peut aussi Ãªtre nÃ©cessaire de dÃ©sactiver la fonction <quote>fast boot</"
"quote> pour permettre l'accÃ¨s Ã  la configuration UEFI et choisir d'amorcer "
"un autre systÃ¨me d'exploitation ou l'&d-i;. Sur certains systÃ¨mes UEFI, le "
"microcode peut rÃ©duire la durÃ©e du <quote>boot</quote> en n'initialisant pas "
"le contrÃ´leur de clavier ou le matÃ©riel USB. Dans ce cas, il est nÃ©cessaire "
"de dÃ©marrer Windows po dÃ©sactiver cette fonctionnalitÃ© et autoriser un "
"changement de l'ordre d'amorÃ§age."

#. Tag: title
#: preparing.xml:1882
#, no-c-format
msgid "Hardware Issues to Watch Out For"
msgstr "ProblÃ¨mes matÃ©riels Ã  surveiller"

#. Tag: title
#: preparing.xml:1885
#, no-c-format
msgid "USB BIOS support and keyboards"
msgstr "BIOS et Claviers USB"

#. Tag: para
#: preparing.xml:1886
#, no-c-format
msgid ""
"If you have no PS/2-style keyboard, but only a USB model, on some very old "
"PCs you may need to enable legacy keyboard emulation in your BIOS setup to "
"be able to use your keyboard in the bootloader menu, but this is not an "
"issue for modern systems. If your keyboard does not work in the bootloader "
"menu, consult your mainboard manual and look in the BIOS for <quote>Legacy "
"keyboard emulation</quote> or <quote>USB keyboard support</quote> options."
msgstr ""
"Si vous n'avez pas de clavier de type PS/2, mais seulement un modÃ¨le USB, "
"vous devrez peut-Ãªtre activer, sur quelques vieux systÃ¨mes, l'Ã©mulation "
"clavier dans la configuration du BIOS pour pouvoir utiliser votre clavier "
"dans le menu du programme d'amorÃ§age. Sur les systÃ¨mes modernes, il n'y a "
"pas de problÃ¨me. Si votre clavier ne rÃ©pond pas dans le menu du programme "
"d'amorÃ§age, consultez le manuel de votre carte mÃ¨re et cherchez dans le BIOS "
"une option Â«&nbsp;Legacy keyboard emulation&nbsp;Â» ou Â«&nbsp;USB keyboard "
"support&nbsp;Â»."

#. Tag: title
#: preparing.xml:1899
#, no-c-format
msgid "Display-visibility on OldWorld Powermacs"
msgstr "ProblÃ¨mes d'affichage sur OldWorld Powermacs"

#. Tag: para
#: preparing.xml:1901
#, no-c-format
msgid ""
"Some OldWorld Powermacs, most notably those with the <quote>control</quote> "
"display driver, may not reliably produce a colormap under Linux when the "
"display is configured for more than 256 colors. If you are experiencing such "
"issues with your display after rebooting (you can sometimes see data on the "
"monitor, but on other occasions cannot see anything) or, if the screen turns "
"black after booting the installer instead of showing you the user interface, "
"try changing your display settings under MacOS to use 256 colors instead of "
"<quote>thousands</quote> or <quote>millions</quote>."
msgstr ""
"Certaines machines OldWorld Powermacs, particuliÃ¨rement celles qui ont un "
"pilote d'affichage <quote>control</quote>, peuvent ne pas produire un "
"systÃ¨me des couleurs fiable pour un affichage avec plus de 256Â couleurs sous "
"Linux. Si vous rencontrez des problÃ¨mes aprÃ¨s le redÃ©marrage (parfois vous "
"voyez quelque chose, parfois rien) ou bien si l'Ã©cran devient noir aprÃ¨s le "
"lancement de l'installateur au lieu de montrer l'interface utilisateur, "
"essayez de rÃ©gler l'affichage sous MacOS Ã  256Â couleurs au lieu des "
"<quote>milliers</quote> ou <quote>millions</quote> de couleurs disponibles."

Attachment: signature.asc
Description: PGP signature

Reply to:

Follow-Ups:
- Re: [RFR] d-i-manual://preparing.po
  - From: Steve Petruzzello <dlist@bluewin.ch>

Prev by Date: Re: [RFR]dpkg://scripts/po/fr.po
Next by Date: [MAJ] ddp://release-notes/whats-new.po
Previous by thread: Re: [RFR2] wml://devel/debian-installer/News/2015/20150419.wml
Next by thread: Re: [RFR] d-i-manual://preparing.po
Index(es):
- Date
- Thread