i2p/haiku-beta6
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update userguide translations

Browse Source 
Also purge old documents
This commit is contained in:
Autocommitter
2018-10-20 16:28:58 -04:00
committed by waddlesplash
parent 4fd69b6cc2
commit 7852aa0525
323 changed files with 2291 additions and 7101 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/userguide/it/bootloader.html
+13 -11
View File
@@ -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:
@@ -131,6 +131,7 @@
<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 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>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 />
@@ -139,19 +140,20 @@ So, if you encounter boot problems after installing some package, boot a Haiku s
<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>
<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>
<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>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>
<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>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>
</table>
</div>