6 files changed, 320 insertions, 27 deletions
diff --git a/it/using-d-i/components.xml b/it/using-d-i/components.xml
index 0415bec7c..92342d3c3 100644
--- a/it/using-d-i/components.xml
+++ b/it/using-d-i/components.xml
@@ -1,5 +1,5 @@
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 53452 -->
+<!-- original version: 56257 -->
 
  <sect1 id="module-details">
  <!-- <title>Using Individual Components</title> -->
@@ -74,6 +74,23 @@ Poiché non tutti i driver possono essere disponibili durante questa
 prima esecuzione, è necessario ripetere il rilevamento dell'hardware
 più avanti, nel processo.
 
+</para><para arch="not-s390">
+
+<!--
+During hardware detection &d-i; checks if any of the drivers for the
+hardware devices in your system require firmware to be loaded. If any
+firmware is requested but unavailable, a dialog will be displayed that
+allows the missing firmware to be loaded from a removable medium.
+See <xref linkend="loading-firmware"/> for further details.
+-->
+
+Durante la rilevazione dell'hardware il &d-i; verifica se i driver per
+i dispositivi hardware presenti nel sistema richiedono il caricamento
+di un firmware. Se è richiesto un firmware ma questo non è disponibile
+viene mostrato un messaggio che permette di caricare il firmware
+mancante da un supporto removibile. Si veda 
+<xref linkend="loading-firmware"/> per maggiori dettagli.
+
 </para>
 
 &module-lowmem.xml;
diff --git a/it/using-d-i/loading-firmware.xml b/it/using-d-i/loading-firmware.xml
new file mode 100644
index 000000000..2df5a9a61
--- /dev/null
+++ b/it/using-d-i/loading-firmware.xml
@@ -0,0 +1,136 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 56290 untranslated -->
+
+ <sect1 id="loading-firmware" arch="not-s390">
+ <title>Loading Missing Firmware</title>
+<para>
+
+As described in <xref linkend="hardware-firmware"/>, some devices require
+firmware to be loaded. In most cases the device will not work at all
+if the firmware is not available; sometimes basic functionality is not
+impaired if it is missing and the firmware is only needed to enable
+additional features.
+
+</para><para>
+
+If a device driver requests firmware that is not available, &d-i; will
+display a dialog offering to load the missing firmware. If this option
+is selected, &d-i; will scan available devices for either loose firmware
+files or packages containing firmware. If found, the firmware will be
+copied to the correct location (<filename>/lib/firmware</filename>) and
+the driver module will be reloaded.
+
+</para>
+<note><para>
+
+Which devices are scanned and which file systems are supported depends on
+the architecture, the installation method and the stage of the installation.
+Especially during the early stages of the installation, loading the firmware
+is most likely to succeed from a FAT-formatted floppy disk or USB stick.
+<phrase arch="x86">On i386 and amd64 firmware can also be loaded from an
+MMC or SD card.</phrase>
+
+</para></note>
+<para>
+
+Note that it is possible to skip loading the firmware if you know the
+device will also function without it, or if the device is not needed during
+the installation.
+
+</para>
+<warning><para>
+
+Support for loading firmware is still relatively basic and is likely to
+be improved in future releases of the installer. Currently &d-i; will
+for example not display any warning if you choose to load missing firmware,
+but the requested firmware is not found.
+Please report any issues you encounter by filing an installation report
+(see <xref linkend="submit-bug"/>).
+
+</para></warning>
+
+  <sect2>
+  <title>Preparing a medium</title>
+<para>
+
+Although in some cases the firmware can also be loaded from a partition on
+a hard disk, the most common method to load firmware will be from some
+removable medium such as a floppy disk or a USB stick.
+The firmware files or packages must be placed in either the root directory
+or a directory named <filename>/firmware</filename> of the file system on
+the medium. The recommended file system to use is FAT as that is most
+certain to be supported during the early stages of the installation.
+
+</para><para>
+
+Tarballs containing current packages for the most common firmware are
+available from:
+
+<itemizedlist>
+<listitem><para>
+<ulink url="&url-firmware-tarballs;"/>
+</para></listitem>
+</itemizedlist>
+
+Just download the tarball for the correct release and unpack it to the file
+system on the medium.
+
+</para><para>
+
+If the firmware you need is not included in the tarball, you can also
+download specific firmware packages from the (non-free section of the)
+archive. The following overview should list most available firmware
+packages but is not guaranteed to be complete and may also contain
+non-firmware packages:
+
+<itemizedlist>
+<listitem><para>
+<ulink url="&url-firmware-packages;"/>
+</para></listitem>
+</itemizedlist>
+
+</para><para>
+
+It is also possible to copy individual firmware files to the medium. Loose
+firmware could be obtained for example from an already installed system or
+from a hardware vendor.
+
+</para>
+  </sect2>
+
+  <sect2>
+  <title>Firmware and the Installed System</title>
+<para>
+
+Any firmware loaded during the installation will be copied automatically
+to the installed system. In most cases this will ensure that the device
+that requires the firmware will also work correctly after the system is
+rebooted into the installed system. However, if the installed system runs
+a different kernel version from the installer there is a slight chance that
+the firmware cannot be loaded due to version skew.
+
+</para><para>
+
+If the firmware was loaded from a firmware package, &d-i; will also install
+this package for the installed system and will automatically add the non-free
+section of the package archive in APT's <filename>sources.list</filename>.
+This has the advantage that the firmware should be updated automatically if
+a new version becomes available.
+
+</para><para>
+
+If loading the firmware was skipped during the installation, the relevant
+device will probably not work with the installed system until the firmware
+(package) is installed manually.
+
+</para>
+<note><para>
+
+If the firmware was loaded from loose firmware files, the firmware copied to
+the installed system will <emphasis>not</emphasis> be automatically updated
+unless the corresponding firmware package (if available) is installed after
+the installation is completed.
+
+</para></note>
+  </sect2>
+ </sect1>
diff --git a/it/using-d-i/modules/mdcfg.xml b/it/using-d-i/modules/mdcfg.xml
index 2dbdbb227..3f99315c8 100644
--- a/it/using-d-i/modules/mdcfg.xml
+++ b/it/using-d-i/modules/mdcfg.xml
@@ -1,9 +1,9 @@
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 51911 -->
+<!-- original version: 56134 -->
 
    <sect3 id="mdcfg">
    <!-- <title>Configuring Multidisk Devices (Software RAID)</title> -->
-   <title>Configurazione di device multidisk (RAID software)</title>
+   <title>Configurazione di device multidisco (RAID software)</title>
 <para>
 
 <!--
@@ -183,6 +183,70 @@ informazioni di parità.
 
 </para></listitem>
 </varlistentry>
+<varlistentry>
+
+<term>RAID6</term><listitem><para>
+
+<!--
+Is similar to RAID5 except that it uses two parity devices instead of
+one.
+-->
+
+Simile a RAID5 con l'eccezione che utilizza due dispositivi per la parità
+anziché uno.
+
+</para><para>
+
+<!--
+A RAID6 array can survive up to two disk failures.
+-->
+
+Un array RAID6 può sopravvivere alla rottura di due dischi.
+
+</para></listitem>
+</varlistentry>
+<varlistentry>
+
+<term>RAID10</term><listitem><para>
+
+<!--
+RAID10 combines striping (as in RAID0) and mirroring (as in RAID1).
+It creates <replaceable>n</replaceable> copies of incoming data and
+distributes them across the partitions so that none of the copies of
+the same data are on the same device.
+The default value of <replaceable>n</replaceable> is 2, but it can be
+set to something else in expert mode. The number of partitions used
+must be at least <replaceable>n</replaceable>.
+RAID10 has different layouts for distributing the copies. The default is
+near copies. Near copies have all of the copies at about the same offset
+on all of the disks. Far copies have the copies at different offsets on
+the disks. Offset copies copy the stripe, not the individual copies.
+-->
+
+RAID10 combina lo striping (come in RAID0) e il mirroring (come in RAID1).
+Vengono create <replaceable>n</replaceable> copie dei dati in arrivo che
+sono distribuite fra le partizioni in modo che nessuna copia dei dati sia
+scritta sullo stesso dispositivo. Il valore predefinito per
+<replaceable>n</replaceable> è 2, ma può essere cambiato in modalità
+esperto. Il numero di partizioni usato deve essere almeno
+<replaceable>n</replaceable>. RAID10 può distribuire le copie usando
+diversi layout. Il layout predefinito prevede copie vicine. Con le copie
+vicine, tutte le copie hanno lo stesso offset sui dischi. Invece le
+copie lontane hanno offset diversi. Le copie offset copiano l'intera
+striscia, non la singola copia.
+
+</para><para>
+
+<!--
+RAID10 can be used to achieve reliability and redundancy without the
+drawback of having to calculate parity.
+-->
+
+RAID10 può essere usato per avere affidalibità e ridondanza senza lo
+svantaggio di dover calcolare la parità.
+
+</para></listitem>
+</varlistentry>
 </variablelist>
 
 <!--
@@ -247,6 +311,34 @@ Riassumendo:
   </entry>
 </row>
 
+<row>
+  <entry>RAID6</entry>
+  <entry>4</entry>
+  <entry><!-- optional -->Opzionale</entry>
+  <entry><!-- yes -->sì</entry>
+  <entry>
+<!--    Size of the smallest partition multiplied by (number of devices in
+    RAID minus two)
+-->
+    La dimensione della partizione più piccola moltiplicata per il numero
+    di device in RAID meno 2.
+  </entry>
+</row>
+
+<row>
+  <entry>RAID10</entry>
+  <entry>2</entry>
+  <entry><!-- optional -->Opzionale</entry>
+  <entry><!-- yes -->sì</entry>
+  <entry>
+<!--
+    Total of all partitions divided by the number of chunk copies (defaults to two)
+-->
+    La somma di tutte le partizioni diviso per il numero di pezzi per copia
+    (il numero predefinito è 2)
+  </entry>
+</row>
+
 </tbody></tgroup></informaltable>
 
 </para><para>
@@ -389,6 +481,41 @@ eccezione, è necessario usare almeno <emphasis>tre</emphasis> partizioni
 attive.
 
 </para></listitem>
+<listitem><para>
+
+<!--
+RAID6 also has a similar setup procedure as RAID1 except that at least
+<emphasis>four</emphasis> active partitions are required.
+-->
+
+RAID6 ha una procedura di configurazione simile a quella per RAID1 con
+un'eccezione: sono necessarie almeno <emphasis>quattro</emphasis>
+partizioni.
+
+</para></listitem>
+<listitem><para>
+
+<!--
+RAID10 again has a similar setup procedure as RAID1 except in expert
+mode. In expert mode, &d-i; will ask you for the layout.
+The layout has two parts. The first part is the layout type. It is either
+<literal>n</literal> (for near copies), <literal>f</literal> (for far
+copies), or <literal>o</literal> (for offset copies). The second part is
+the number of copies to make of the data. There must be at least that
+many active devices so that all of the copies can be distributed onto
+different disks.
+-->
+
+Anche RAID10 ha una procedura di configurazione simile a quella per RAID1
+tranne quando viene eseguita in modalità esperto. Infatti, in tale
+modalità, &d-i; chiede il layout che può essere <literal>n</literal> (per
+le copie vicine), <literal>f</literal> (per le copie lontane) oppure
+<literal>o</literal> (per copie in offset). La seconda parte è il numero
+di copie dei dati da fare. Deve essere almeno uguale al numero di
+dispositivi attivi in modo che tutte le copie siano scritte su dischi
+diversi.
+
+</para></listitem>
 </itemizedlist>
 
 <para>
diff --git a/it/using-d-i/modules/network-console.xml b/it/using-d-i/modules/network-console.xml
index d9bdf9817..2905d875a 100644
--- a/it/using-d-i/modules/network-console.xml
+++ b/it/using-d-i/modules/network-console.xml
@@ -1,5 +1,5 @@
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 50787 -->
+<!-- original version: 56141 -->
 
    <sect3 id="network-console">
    <!-- <title>Installation Over the Network</title> -->
@@ -256,17 +256,5 @@ la configurazione del nuovo sistema e quindi provocare il blocco
 dell'installazione oppure dei problemi nel sistema una volta conclusa
 l'installazione.
 
-</para><para>
-
-<!--
-Also, if you are running the SSH session from an X terminal, you should
-not resize the window as that will result in the connection being
-terminated.
--->
-
-Inoltre, se si esegue la sessione SSH da un terminale X, non si dove
-ridimensionare la finestra dato che questa operazione comporta la
-chiusura della connessione.
-
 </para></warning>
    </sect3>
diff --git a/it/using-d-i/modules/pkgsel.xml b/it/using-d-i/modules/pkgsel.xml
index 5336be6e5..dda95b33a 100644
--- a/it/using-d-i/modules/pkgsel.xml
+++ b/it/using-d-i/modules/pkgsel.xml
@@ -1,5 +1,5 @@
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 52083 -->
+<!-- original version: 56140 -->
 
    <sect3 id="pkgsel">
    <!-- <title>Selecting and Installing Software</title> -->
@@ -147,7 +147,7 @@ Mail server: <classname>exim4</classname>, <classname>spamassassin</classname>,
 <classname>uw-imap</classname>;
 Print server: <classname>cups</classname>;
 SQL database: <classname>postgresql</classname>;
-Web server: <classname>apache</classname>.
+Web server: <classname>apache2</classname>.
 -->
 
 Con i diversi task di tipo server sono installati i seguenti programmi.
@@ -157,7 +157,7 @@ Mail server: <classname>exim4</classname>, <classname>spamassassin</classname>,
 <classname>uw-imap</classname>;
 Print server: <classname>cups</classname>;
 SQL database: <classname>postgresql</classname>;
-Web server: <classname>apache</classname>.
+Web server: <classname>apache2</classname>.
 
 </para></note>
 <para>
diff --git a/it/using-d-i/using-d-i.xml b/it/using-d-i/using-d-i.xml
index e0a8bd53b..9eac71d26 100644
--- a/it/using-d-i/using-d-i.xml
+++ b/it/using-d-i/using-d-i.xml
@@ -1,5 +1,5 @@
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 52273 -->
+<!-- original version: 56257 -->
 
 <chapter id="d-i-intro">
 <!-- <title>Using the Debian Installer</title> -->
@@ -110,17 +110,42 @@ Expert mode gives you full control over &d-i;.
 
 Se l'hardware richiede di passare opzioni ai moduli del kernel man mano
 che sono installati, sarà necessario avviare l'installatore in modalità
-<quote>expert</quote>. Ciò può essere fatto sia usando il comando
+<quote>expert</quote> (esperto). Ciò può essere fatto sia usando il comando
 <command>expert</command> per avviare l'installatore, sia aggiungendo il
 parametro di avvio <userinput>priority=low</userinput>. La
 modalità <quote>expert</quote> fornisce il controllo totale su &d-i;.
 
+</para><para condition="gtk">
+
+<!--
+For this architecture the &d-i; supports two different user interfaces: a
+character-based one and a graphical one. The character-based interface is
+used by default unless you selected the <quote>Graphical install</quote>
+option in the initial boot menu. For more information about the
+graphical installer, please refer to <xref linkend="graphical"/>.
+-->
+
+Per questa architettura il &d-i; supporta due diverse interfacce utente:
+una a caratteri e una grafica. L'interfaccia a caratteri è quella
+normalmente utilizzata a meno che si scelga <quote>Graphical install</quote>
+dal menu iniziale. Per ulteriori informazioni sull'installatore grafico
+si veda <xref linkend="graphical"/>.
+
+</para><para condition="not-gtk">
+
+<!--
+For this architecture the installer uses a character-based user interface.
+A graphical user interface is currently not available.
+-->
+
+Per questa architettura l'installatore utilizza un'interfaccia utente a
+caratteri. Attualmente non è disponibile un'interfaccia grafica.
+
 </para><para>
 
 <!--
-The normal installer display is character-based (as opposed to the now
-more familiar graphical interface). The mouse is not operational in
-this environment. Here are the keys you can use to navigate within the
+In the character-based environment the use of a mouse is not supported.
+Here are the keys you can use to navigate within the
 various dialogs.  The <keycap>Tab</keycap> or <keycap>right</keycap>
 arrow keys move <quote>forward</quote>, and the <keycombo> <keycap>Shift</keycap>
 <keycap>Tab</keycap> </keycombo> or <keycap>left</keycap> arrow keys
@@ -135,9 +160,8 @@ letter you typed and use <keycap>Pg-Up</keycap> and
 &enterkey; to activate choices.
 -->
 
-La normale visualizzazione dell'installatore è basata su caratteri (in
-contrapposizione alla ormai più familiare interfaccia grafica). In questo
-ambiente il mouse non è operativo. Ecco i tasti che si possono usare per
+Nell'ambiente d'installazione a caratteri non è supportato l'uso del
+mouse. Questi sono i tasti che si possono usare per
 navigare all'interno delle varie finestre di dialogo. I tasti
 <keycap>Tab</keycap> o freccia <keycap>destra</keycap> muovono
 <quote>avanti</quote> e i tasti <keycombo> <keycap>Shift</keycap>
@@ -647,6 +671,7 @@ dell'installatore agli sviluppatori Debian.
  </sect1>
 
 &using-d-i-components.xml;
+&loading-firmware.xml;
 
 </chapter>