Italian translation updated

3 files changed, 75 insertions, 50 deletions

diff --git a/it/install-methods/tftp/bootp.xml b/it/install-methods/tftp/bootp.xml
index 9384b1752..c33e61edd 100644
--- a/it/install-methods/tftp/bootp.xml
+++ b/it/install-methods/tftp/bootp.xml
@@ -4,14 +4,16 @@
 
   <sect2 condition="supports-bootp" id="tftp-bootp">
   <!-- <title>Setting up BOOTP server</title> -->
-  <title>Attivare un server BOOTP</title>
+  <title>Attivazione di un server BOOTP</title>
 <para>
 
-<!-- There are two BOOTP servers available for GNU/Linux, the CMU
+<!--
+There are two BOOTP servers available for GNU/Linux, the CMU
 <command>bootpd</command> and the other is actually a DHCP server, ISC
 <command>dhcpd</command>, which are contained in the
 <classname>bootp</classname> and <classname>dhcp</classname> packages
-in &debian;. -->
+in &debian;.
+-->
 
 Per GNU/Linux sono disponibili due server BOOTP, <command>bootpd</command>
 di CMU e attualmente l'altro è un server DHCP, <command>dhcpd</command> di
@@ -20,12 +22,14 @@ ISC che sono rispettivamente contenuti nei pacchetti &debian;
 
 </para><para>
 
-<!-- To use CMU <command>bootpd</command>, you must first uncomment (or
+<!--
+To use CMU <command>bootpd</command>, you must first uncomment (or
 add) the relevant line in <filename>/etc/inetd.conf</filename>.  On
 &debian;, you can run <userinput>update-inetd -enable
 bootps</userinput>, then <userinput>/etc/init.d/inetd
 reload</userinput> to do so. Elsewhere, the line in question should
-look like: -->
+look like:
+-->
 
 Per usare <command>bootpd</command> di CMU è necessario togliere i commenti
 (o aggiungere) la relativa riga in <filename>/etc/inetd.conf</filename>.
@@ -38,14 +42,16 @@ essere simile a questa:
 bootps  dgram  udp  wait  root  /usr/sbin/bootpd  bootpd -i -t 120
 </screen></informalexample>
 
-<!-- Now, you must create an <filename>/etc/bootptab</filename> file.  This
+<!--
+Now, you must create an <filename>/etc/bootptab</filename> file.  This
 has the same sort of familiar and cryptic format as the good old BSD
 <filename>printcap</filename>, <filename>termcap</filename>, and
 <filename>disktab</filename> files.  See the
 <filename>bootptab</filename> manual page for more information.  For
 CMU <command>bootpd</command>, you will need to know the hardware
 (MAC) address of the client.  Here is an example
-<filename>/etc/bootptab</filename>: -->
+<filename>/etc/bootptab</filename>:
+-->
 
 Adesso è necessario creare il file <filename>/etc/bootptab</filename>.
 Questo file ha lo stesso formato criptico dei file
@@ -78,11 +84,13 @@ l'indirizzo hardware del client. L'opzione <quote>bf</quote> specifica
 quale file deve essere recuperato dal client tramite TFTP; si consulti
 <xref linkend="tftp-images"/> per ulteriori dettagli.
 
-<!-- <phrase arch="mips">
+<!--
+<phrase arch="mips">
 On SGI machines you can just enter the command monitor and type
 <userinput>printenv</userinput>.  The value of the
 <userinput>eaddr</userinput> variable is the machine's MAC address.
-</phrase> -->
+</phrase>
+-->
 
 <phrase arch="mips">
 Sulle macchine SGI si può usare il commando monitor e inserire
@@ -92,7 +100,8 @@ Sulle macchine SGI si può usare il commando monitor e inserire
 
 </para><para>
 
-<!-- By contrast, setting up BOOTP with ISC <command>dhcpd</command> is
+<!--
+By contrast, setting up BOOTP with ISC <command>dhcpd</command> is
 really easy, because it treats BOOTP clients as a moderately special
 case of DHCP clients.  Some architectures require a complex
 configuration for booting clients via BOOTP.  If yours is one of
@@ -101,7 +110,8 @@ will probably be able to get away with simply adding the
 <userinput>allow bootp</userinput> directive to the configuration
 block for the subnet containing the client, and restart
 <command>dhcpd</command> with <userinput>/etc/init.d/dhcpd
-restart</userinput>. -->
+restart</userinput>.
+-->
 
 Al contrario l'impostazione di BOOTP con <command>dhcpd</command> di ISC è
 veramente semplice poiché tratta i client BOOTP come un caso moderatamente
diff --git a/it/install-methods/tftp/dhcp.xml b/it/install-methods/tftp/dhcp.xml
index dfb6bdbc3..06d5aa332 100644
--- a/it/install-methods/tftp/dhcp.xml
+++ b/it/install-methods/tftp/dhcp.xml
@@ -4,14 +4,15 @@
 
   <sect2 condition="supports-dhcp" id="dhcpd">
   <!-- <title>Setting up a DHCP server</title> -->
-  <title>Attivare un server DHCP</title>
-
+  <title>Attivazione di un server DHCP</title>
 <para>
 
-<!-- One free software DHCP server is ISC <command>dhcpd</command>.
+<!--
+One free software DHCP server is ISC <command>dhcpd</command>.
 In &debian;, this is available in the <classname>dhcp</classname>
 package. Here is a sample configuration file for it (usually
-<filename>/etc/dhcpd.conf</filename>): -->
+<filename>/etc/dhcpd.conf</filename>):
+-->
 
 Un server DHCP libero è <command>dhcpd</command> di ISC. In &debian; è
 disponibile nel pacchetto <classname>dhcp</classname>. Questo è un esempio
@@ -40,33 +41,39 @@ host clientname {
 }
 </screen></informalexample>
 
-<!-- Note: the new (and preferred) <classname>dhcp3</classname> package uses
-<filename>/etc/dhcp3/dhcpd.conf</filename>. -->
+<!--
+Note: the new (and preferred) <classname>dhcp3</classname> package uses
+<filename>/etc/dhcp3/dhcpd.conf</filename>.
+-->
 
 Nota: il nuovo (e da preferire) pacchetto <classname>dhcp3</classname> usa il
 file <filename>/etc/dhcp3/dhcpd.conf</filename>.
 
 </para><para>
 
-<!-- In this example, there is one server
+<!--
+In this example, there is one server
 <replaceable>servername</replaceable> which performs all of the work
 of DHCP server, TFTP server, and network gateway.  You will almost
 certainly need to change the domain-name options, as well as the
 server name and client hardware address.  The
 <replaceable>filename</replaceable> option should be the name of the
-file which will be retrieved via TFTP. -->
+file which will be retrieved via TFTP.
+-->
 
 In questo esempio c'è una macchina <replaceable>servername</replaceable>
 che fa da server DHCP, da server TFTP e da gateway di rete. Sicuramente è
-necessario cambiare le opzioni domain-name e anche il nome del server e
+necessario cambiare le opzioni domain-name, il nome del server e anche
 l'indirizzo hardware del client. Il valore dell'opzione
 <replaceable>filename</replaceable> deve essere il nome del file che
 verrà recuperato tramite TFTP.
 
 </para><para>
 
-<!-- After you have edited the <command>dhcpd</command> configuration file,
-restart it with <userinput>/etc/init.d/dhcpd restart</userinput>. -->
+<!--
+After you have edited the <command>dhcpd</command> configuration file,
+restart it with <userinput>/etc/init.d/dhcpd restart</userinput>.
+-->
 
 Dopo aver modificato il file di configurazione di <command>dhcpd</command>
 riavviarlo con <userinput>/etc/init.d/dhcpd restart</userinput>.
@@ -76,11 +83,12 @@ riavviarlo con <userinput>/etc/init.d/dhcpd restart</userinput>.
    <sect3 arch="i386">
    <!-- <title>Enabling PXE Booting in the DHCP configuration</title> -->
    <title>Abilitare l'avvio PXE nella configurazione di DHCP</title>
-
 <para>
 
-<!-- Here is another example for a <filename>dhcp.conf</filename> using the
-Pre-boot Execution Environment (PXE) method of TFTP. -->
+<!--
+Here is another example for a <filename>dhcp.conf</filename> using the
+Pre-boot Execution Environment (PXE) method of TFTP.
+-->
 
 Questo è un altro esempio di <filename>dhcp.conf</filename> che usa il
 metodo PXE (Pre-boot Execution Environment) di TFTP.
@@ -115,9 +123,11 @@ group {
 }
 </screen></informalexample>
 
-<!-- Note that for PXE booting, the client filename
+<!--
+Note that for PXE booting, the client filename
 <filename>pxelinux.0</filename> is a boot loader, not a kernel image
-(see <xref linkend="tftp-images"/> below). -->
+(see <xref linkend="tftp-images"/> below).
+-->
 
 Notare che con l'avvio PXE, il nome del file client
 <filename>pxelinux.0</filename> è il bootloader, non l'immagine del kernel
diff --git a/it/install-methods/tftp/rarp.xml b/it/install-methods/tftp/rarp.xml
index 679186fb1..02c81b8b9 100644
--- a/it/install-methods/tftp/rarp.xml
+++ b/it/install-methods/tftp/rarp.xml
@@ -4,37 +4,34 @@
 
   <sect2 condition="supports-rarp" id="tftp-rarp">
   <!-- <title>Setting up RARP server</title> -->
-  <title>Attivare un server RARP</title>
-
+  <title>Attivazione di un server RARP</title>
 <para>
 
-<!-- To setup RARP, you need to know the Ethernet address (a.k.a. the MAC
+<!--
+To setup RARP, you need to know the Ethernet address (a.k.a. the MAC
 address) of the client computers to be installed.
-If you don't know this information, you can -->
+If you don't know this information, you can
+<phrase arch="sparc"> pick it off the initial OpenPROM boot messages,
+use the OpenBoot <userinput>.enet-addr</userinput> command, or </phrase>
+boot into <quote>Rescue</quote> mode (e.g., from the rescue floppy) and use the
+command <userinput>/sbin/ifconfig eth0</userinput>.
+-->
 
 Per impostare RARP è necessario conoscere l'indirizzo Ethernet (noto anche
 come indirizzo MAC) dei computer client da installare. Se non si conoscono
 queste informazioni è possibile
-
-<!-- <phrase arch="sparc"> pick it off the initial OpenPROM boot messages,
-use the OpenBoot <userinput>.enet-addr</userinput> command, or </phrase> -->
-
 <phrase arch="sparc">leggerlo nei primi messaggi durante l'avvio di OpenPROM,
 usare il comando <userinput>.enet-addr</userinput> di OpenBoot oppure</phrase>
-
-<!--
-boot into <quote>Rescue</quote> mode (e.g., from the rescue floppy) and use the
-command <userinput>/sbin/ifconfig eth0</userinput>.
--->
-
 avviare in modalità <quote>Ripristino</quote> (p.e. da un dischetto di
 ripristino) e usare il comando <userinput>/sbin/ifconfig eth0</userinput>.
 
 </para><para>
 
-<!-- On a RARP server system using a Linux 2.2.x kernel,
+<!--
+On a RARP server system using a Linux 2.2.x kernel,
 you need to populate the kernel's RARP table.
-To do this, run the following commands: -->
+To do this, run the following commands:
+-->
 
 Su un sistema con Linux 2.2.x e un server RARP è necessario popolare la
 tabella RARP del kernel. Per farlo usare i seguenti comandi:
@@ -49,7 +46,9 @@ tabella RARP del kernel. Per farlo usare i seguenti comandi:
 <replaceable>client-enet-addr</replaceable></userinput>
 </screen></informalexample>
 
-<!-- If you get -->
+<!--
+If you get
+-->
 
 Se si ottiene
 
@@ -57,9 +56,11 @@ Se si ottiene
 SIOCSRARP: Invalid argument
 </screen></informalexample>
 
-<!-- you probably need to load the RARP kernel module or else recompile the
+<!--
+you probably need to load the RARP kernel module or else recompile the
 kernel to support RARP.  Try <userinput>modprobe rarp</userinput> and
-then try the <command>rarp</command> command again. -->
+then try the <command>rarp</command> command again.
+-->
 
 probabilmente si deve caricare il modulo del kernel RARP oppure
 ricompilare il kernel inserendo il supporto RARP. Eseguire
@@ -68,11 +69,13 @@ comando <command>rarp</command>.
 
 </para><para>
 
-<!-- On a RARP server system using a Linux 2.4.x kernel,
+<!--
+On a RARP server system using a Linux 2.4.x kernel,
 there is no RARP module, and
 you should instead use the <command>rarpd</command> program.  The
 procedure is similar to that used under SunOS in the following
-paragraph. -->
+paragraph.
+-->
 
 Su un sistema con Linux 2.4.x e un server RARP non esiste il modulo RARP e
 al suo posto si deve usare il programma <command>rarpd</command>. La
@@ -81,13 +84,15 @@ paragrafo.
 
 </para><para>
 
-<!-- Under SunOS, you need to ensure that the Ethernet hardware address for
+<!--
+Under SunOS, you need to ensure that the Ethernet hardware address for
 the client is listed in the <quote>ethers</quote> database (either in the
 <filename>/etc/ethers</filename> file, or via NIS/NIS+) and in the
 <quote>hosts</quote> database. Then you need to start the RARP daemon.  In SunOS
 4, issue the command (as root):
 <userinput>/usr/etc/rarpd -a</userinput>; in SunOS 5, use
-<userinput>/usr/sbin/rarpd -a</userinput>. -->
+<userinput>/usr/sbin/rarpd -a</userinput>.
+-->
 
 Sotto SunOS ci si deve assicurare che l'indirizzo Ethernet del
 client sia elencato nel database <quote>ethers</quote> (nel file