Update userguide and welcome pages.
This is the first userguide export on the Postgres-based translation tool (previously it used MySQL), so please double-check it extra carefully. (I spotted a few minor problems in the export and fixed the relevant bugs already.)
This commit is contained in:
waddlesplash
@@ -10,10 +10,10 @@
|
||||
* Authors:
|
||||
* Humdinger <[email protected]>
|
||||
* Translators:
|
||||
* keepeasy
|
||||
* MichaelPeppers
|
||||
* Barrett
|
||||
* Humdinger
|
||||
* keepeasy
|
||||
* MichaelPeppers
|
||||
*
|
||||
-->
|
||||
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
|
||||
@@ -65,14 +65,14 @@
|
||||
|
||||
<h1>Il Boot Loader</h1>
|
||||
|
||||
<p>Haiku's Boot Loader can help when you experience hardware related problems or want to choose which Haiku installation to start, if you have more than one (maybe on an installation CD or USB stick). It's also handy if you have installed a software component that acts up and prevents you from booting Haiku, see <a href="#troubleshooting">Troubleshooting</a> below.</p>
|
||||
<p>Haiku's Boot Loader Options can help when you experience hardware related problems or want to choose which Haiku installation to start, if you have more than one (maybe on an installation CD or USB stick). It's also handy if you have installed a software component that acts up and prevents you from booting Haiku, see <a href="#troubleshooting">Troubleshooting</a> below.</p>
|
||||
<p>Per entrare nelle opzioni del Boot Loader di Haiku bisogna premere il tasto <span class="key">SHIFT</span> prima dell'inizio del processo di avvio. Se è presente un boot manager, è possibile cominciare a premere il tasto <span class="key">SHIFT</span> prima di selezionare la voce di Haiku. Altrimenti se Haiku è l'unico sistema operativo installato nella macchina, è sufficiente premere il tasto appena compaiono i messaggi di avvio del BIOS.</p>
|
||||
<h2>
|
||||
<a href="#"><img src="../images/up.png" style="border:none;float:right" alt="index" /></a>
|
||||
<a id="options" name="options">Boot Loader Options</a></h2>
|
||||
<p>Una volta caricato, appariranno quattro menu:</p>
|
||||
<table summary="bootloader menus" border="0" cellspacing="0" cellpadding="2">
|
||||
<tr><td><b>Select boot volume</b> (Seleziona il disco di avvio) </td><td> </td><td>Choose which Haiku installation/version to start.</td></tr>
|
||||
<tr><td><b>Select boot volume</b> (Seleziona il disco di avvio) </td><td> </td><td>Choose which Haiku installation/state to start (see <a href="#troubleshooting">Troubleshooting</a> below).</td></tr>
|
||||
<tr><td><b>Select safe mode options</b></td><td> </td><td>There are several options to try in case of hardware related trouble or if the system becomes unstable or unbootable because of a misbehaving add-on. When moving the selection bar to an option, a short explanation appears at the bottom of the screen.</td></tr>
|
||||
<tr><td></td><td></td><td>
|
||||
<p><span class="menu">Safe mode</span><br />
|
||||
@@ -114,11 +114,11 @@
|
||||
Displays the debug info the boot loader has logged (press <span class="key">Q</span> to exit the log)</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 "<i>Enable debug syslog</i>" is activated, a warm reboot after a crash shows these additional options:</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>
|
||||
<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 /var/log/previous_syslog when booting.</p>
|
||||
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>
|
||||
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>
|
||||
@@ -129,30 +129,29 @@
|
||||
<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>
|
||||
<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">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>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 version from before that time and uninstall the offending package.</p></li>
|
||||
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>Dopo aver attivato una o più opzioni, è possibile tornare al menu principale e avviare normalmente il sistema che si presenterà con questa schermata di avvio:
|
||||
</p>
|
||||
<p>After activating one or more options, you return to the main menu and continue booting, which presents you with this boot screen:</p>
|
||||
<img src="../images/bootloader-images/boot-screen.png" alt="boot-screen.png" />
|
||||
|
||||
<p>Se tutto funziona perfettamente, le icone nella schermata si illumineranno una dopo l'altra.<br />
|
||||
Le icone corrispondono grossomodo alle diverse fasi di caricamento dell'OS e sono:</p>
|
||||
<p>If everything works OK, one symbol after another quickly lights up.<br />
|
||||
The different symbols roughly correspond to these boot stages:</p>
|
||||
<table summary="layout" border="0" cellpadding="2" cellspacing="0">
|
||||
<tr><td><b>Atomo</b></td><td style="width:10px;"> </td><td>Inizializza i moduli del kernel.</td></tr>
|
||||
<tr><td><b>La lente di ingrandimento sul disco</b></td><td> </td><td>Crea "rootfs" (<span class="path">/</span>) e monta "devfs" (<span class="path">/dev</span>).</td></tr>
|
||||
<tr><td><b>Scheda elettronica</b></td><td> </td><td> Inizializza il gestore delle periferiche.</td></tr>
|
||||
<tr><td><b>Disco di avvio</b></td><td> </td><td>Monta il disco di boot.</td></tr>
|
||||
<tr><td><b>Il chip</b></td><td> </td><td>Carica i moduli specifici della CPU.</td></tr>
|
||||
<tr><td><b>La cartella</b></td><td> </td><td>Finisce di inizializzare il sottosistema.</td></tr>
|
||||
<tr><td><b>Il razzo</b></td><td> </td><td>Launch_daemon has started the system.</td></tr>
|
||||
<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>
|
||||
</table>
|
||||
|
||||
</div>
|
||||
|
||||
Reference in New Issue
Block a user