Update userguide translations
Also purge old documents
This commit is contained in:
Autocommitter
committed by
waddlesplash
waddlesplash
parent
4fd69b6cc2
commit
7852aa0525
@@ -4,7 +4,7 @@
|
||||
<head>
|
||||
<!--
|
||||
*
|
||||
* Copyright 2008-2015, Haiku. All rights reserved.
|
||||
* Copyright 2008-2018, Haiku. All rights reserved.
|
||||
* Distributed under the terms of the MIT License.
|
||||
*
|
||||
* Authors:
|
||||
@@ -102,58 +102,62 @@ Si Haiku est le seul système d'exploitation de votre machine, Vous pouvez comme
|
||||
Disables Advanced Configuration and Power Interface hardware support, overriding the ACPI setting in the kernel settings file.</p>
|
||||
<p><span class="menu">Blacklist entries</span><br />
|
||||
Allows to select system files that shall be ignored. Useful e.g. to disable drivers temporarily. See <a href="#troubleshooting">Troubleshooting</a> below.</p></td></tr>
|
||||
<tr><td><b>Select debug options</b></td><td> </td><td>Here you'll find several options that help with debugging or getting details for a <a href="../../welcome/en/bugreports.html">bug report</a>. Again, a short explanation for each option is displayed at the bottom.</td></tr>
|
||||
<tr><td><b>Select debug options</b>
|
||||
</td><td> </td><td>Ici, vous trouverez plusieurs options qui vous aideront à déboguer ou à récuperer le détail pour un <a href="../../welcome/fr/bugreports.html">rapport de bogue</a>.
|
||||
Voici, une courte explication pour chaque option affichée ci-dessous.</td></tr>
|
||||
<tr><td></td><td></td><td>
|
||||
<p><span class="menu">Enable serial debug output</span><br />
|
||||
Turns on forwarding the syslog output to the serial interface (default: 115200, 8N1).</p>
|
||||
active l'envoi du journal vers l'interface série (default: 115200, 8N1).</p>
|
||||
<p><span class="menu">Enable on screen debug output</span><br />
|
||||
Display debug output on screen while the system is booting, instead of the normal boot logo.</p>
|
||||
Affiche la sortie de débogage à l'écran pendant le démarrage à la place du logo habituel.</p>
|
||||
<p><span class="menu">Disable on screen paging</span><br />
|
||||
Disables paging when on screen debug output is enabled.</p>
|
||||
Désactive la pagination lorsque la sortie de débogage à l'écran est activé</p>
|
||||
<p><span class="menu">Enable debug syslog</span><br />
|
||||
Enables a special in-memory syslog buffer for this session that the boot loader will be able to access after rebooting.</p>
|
||||
Active le journal dans une mémoire tampon spéciale pour cette session afin que le chargeur d'amorce puisse y accéder après le redémarrage.</p>
|
||||
<p><span class="menu">Display current boot loader log</span><br />
|
||||
Displays the debug info the boot loader has logged (press <span class="key">Q</span> to exit the log)</p>
|
||||
Affiche les informations de débogage que le chargeur d'amorce a jounalisé. (pressez <span class="key">Q</span> pour sortir du journal)</p>
|
||||
<p><span class="menu">Add advanced debug option</span><br />
|
||||
Allows advanced debugging options to be entered directly.</p></td></tr>
|
||||
<tr><td></td><td></td><td>If <span class="menu">Enable debug syslog</span> is activated, a warm reboot after a crash shows these additional options:</td></tr>
|
||||
Permet d’entrer directement des options de débogage avancées.</p></td></tr>
|
||||
<tr><td></td><td></td><td>Si « <i>Enable debug syslog</i> » est activé, un redémarrage à chaud après un plantage montre les options supplémentaires suivantes :
|
||||
</td></tr>
|
||||
<tr><td></td><td></td><td> <p><span class="menu">Save syslog from previous session during boot</span><br />
|
||||
Saves the syslog from the previous Haiku session to <span class="path">/var/log/previous_syslog</span> when booting.</p>
|
||||
<p><span class="menu">Display syslog from previous session</span><br />
|
||||
Displays the syslog from the previous Haiku session.</p>
|
||||
<p><span class="menu">Save syslog from previous session</span><br />
|
||||
Saves the syslog from the previous Haiku session to disk. Currently only FAT32 volumes are supported.</p></td></tr>
|
||||
<tr><td class="onelinetop"><b>Select screen resolution</b></td><td> </td><td>Lets you force a certain screen resolution and color depth.</td></tr>
|
||||
<tr><td class="onelinetop"><b>Select fail safe video mode</b></td><td> </td><td>Permet de forcer une résolution et une profondeur de couleur.</td></tr>
|
||||
</table>
|
||||
<h2>
|
||||
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="troubleshooting" name="troubleshooting">Troubleshooting</a></h2>
|
||||
<p>If Haiku refuses to boot on your hardware from the get-go, try out setting different options under <span class="menu">Select safe mode options</span>. Consider filing a <a href="../../welcome/en/bugreports.html">bug report</a> in any case.</p>
|
||||
<p>On the other hand, if Haiku only suddenly acts up after you have installed some software, especially hardware drivers, you have several options to get Haiku bootable again so you can uninstall the offending package:</p>
|
||||
<a id="troubleshooting" name="troubleshooting">Dépannage</a></h2>
|
||||
<p>Si, dès le départ, Haiku refuse de démarrer sur votre matériel, essayez les différentes options de réglage sous <span class="menu">Select safe mode options</span>. Dans tous les cas, Envisagez de sousmettre un <a href="../../welcome/fr/bugreports.html">rapport de bug</a>.</p>
|
||||
<p>Si, au contraire, Haiku cesse de démarrer seulement après avoir installé un logiciel, en particulier un pilote, plusieurs options s’offrent à vous pour permettre à Haiku de démarrer de nouveau et désinstaller le logiciel en cause :</p>
|
||||
<ul>
|
||||
<li><p>Activating <span class="menu">Safe mode</span> will prevent most servers, daemons and the UserBootscript from being started.</p></li>
|
||||
<li><p>Activating <span class="menu">Disable user add-ons</span> will prevent using any add-ons (drivers, translators, etc.) you have installed in the user hierarchy under your Home folder.</p></li>
|
||||
<li><p>If the offending driver, add-on etc. is installed in the system hierarchy, things get a bit more complicated, because that area is read-only. Here, the <span class="menu">Blacklist entries</span> comes into play. With it, you can navigate through the whole system hierarchy and disable the component that's messing things up for you by checking an entry with the <span class="key">SPACE</span> or <span class="key">RETURN</span> key. <span class="key">ESC</span> returns you up one level to the parent directory.</p>
|
||||
<p>Online, there's the article <a href="http://www.haiku-os.org/blog/barrett/2013-12-15_how_permanently_blacklist_package_file">How to Permanently Blacklist a Package File</a> showing how to make that setting stick.</p></li>
|
||||
<li><p>Activer <span class="menu">Safe mode</span> empêchera la plupart des serveurs, des daemons et du UserBootScript de se lancer.</p></li>
|
||||
<li><p>Activer <span class="menu">Disable user add-ons</span> empêchera l’utilisation de toute extension (pilote, traducteur, etc…) que vous avez installée dans votre dossier personnel.</p></li>
|
||||
<li><p>If activating <span class="menu">Use fail-safe graphics driver</span> solves your troubles by falling back to VESA graphics, you can make the setting permanent by removing the <tt>#</tt> of the line <i>#fail_safe_video_mode true</i> in the text file <span class="path">/boot/home/config/settings/kernel/drivers/kernel</span>.</p></li>
|
||||
<li><p>Si le pilote ou l’extension en cause est installé dans un dossier système, cela devient plus complexe car cette partie est en lecture-seule. C’est à cela que sert <span class="menu">Blacklist entries</span>. Vous pourrez alors naviguer dans les dossiers système et désactiver les composants fautifs en cochant une entrée avec la touche <span class="key">Espace</span> ou <span class="key">Entrée</span>. La touche <span class="key">Esc</span> permet de retourner au dossier parent.</p>
|
||||
<p>L’article <a href="http://www.haiku-os.org/blog/barrett/2013-12-15_how_permanently_blacklist_package_file">How to Permanently Blacklist a Package File</a> (en anglais) vous montrera comment rendre ce réglage permanent.</p></li>
|
||||
<li><p>Under <span class="menu">Select boot volume</span> you can specify what former "version" of Haiku to boot. Every time you un/install a package, the old state is saved and you can boot into it by choosing it from the list presented in the boot loader options.<br />
|
||||
So, if you encounter boot problems after installing some package, boot a Haiku state from before that time and uninstall the offending package.</p></li>
|
||||
</ul>
|
||||
<h2>
|
||||
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="booting" name="booting">Booting Haiku</a></h2>
|
||||
<p>After activating one or more options, you return to the main menu and continue booting, which presents you with this boot screen:</p>
|
||||
<a id="booting" name="booting">Démarrer Haiku</a></h2>
|
||||
<p>Après avoir activé une ou plusieurs options, vous pourrez retourner au menu principal et continuer le démarrage. Pendant celui-ci, un écran de démarrage sera affiché :</p>
|
||||
<img src="../images/bootloader-images/boot-screen.png" alt="boot-screen.png" />
|
||||
|
||||
<p>If everything works OK, one symbol after another quickly lights up.<br />
|
||||
The different symbols roughly correspond to these boot stages:</p>
|
||||
<p>Si tout fonctionne correctement, chaque symbole devrait s'illuminer, l'un après l'autre.<br />
|
||||
Ces symboles correspondent grossièrement aux étapes de démarrage suivantes :</p>
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td><b>Atom</b></td><td style="width:10px;"> </td><td>Initializing modules.</td></tr>
|
||||
<tr><td><b>Disk + magnifier</b></td><td> </td><td>Creating rootfs (<span class="path">/</span>) and mounting devfs (<span class="path">/dev</span>).</td></tr>
|
||||
<tr><td><b>Plug-in card</b></td><td> </td><td>Initializing device manager.</td></tr>
|
||||
<tr><td><b>Boot disk</b></td><td> </td><td>Mounting boot disk.</td></tr>
|
||||
<tr><td><b>Chip</b></td><td> </td><td>Loading CPU specific modules.</td></tr>
|
||||
<tr><td><b>Folder</b></td><td> </td><td>Final initialization of subsystems.</td></tr>
|
||||
<tr><td><b>Rocket</b></td><td> </td><td>Launch_daemon has started the system.</td></tr>
|
||||
<tr><td><b>Atome</b></td><td style="width:10px;"> </td><td>Initialisation du noyau et des modules.</td></tr>
|
||||
<tr><td><b>Disque dur avec loupe</b></td><td> </td><td>Création du système de fichier racine (<span class="path">/</span>) et montage du système de fichiers devfs (<span class="path">/dev</span>).</td></tr>
|
||||
<tr><td><b>Carte d'extension</b></td><td> </td><td>Initialisation du gestionnaire de périphériques.</td></tr>
|
||||
<tr><td><b>Disque de démarrage</b></td><td> </td><td>Montage du disque de démarrage.</td></tr>
|
||||
<tr><td><b>Puce</b></td><td> </td><td>Activation des fonctionnalités spécifiques au processeur.</td></tr>
|
||||
<tr><td><b>Dossier</b></td><td> </td><td>Initialisation des sous-systèmes.</td></tr>
|
||||
<tr><td><b>Fusée</b></td><td> </td><td>Launch_daemon démarre les services systèmes.</td></tr>
|
||||
</table>
|
||||
|
||||
</div>
|
||||
|
||||
Reference in New Issue
Block a user