[D-I Manual] Italian translation:

 - translation updated

2 files changed, 7 insertions, 22 deletions

diff --git a/it/install-methods/install-tftp.xml b/it/install-methods/install-tftp.xml
index 0dc257e19..0fa02905e 100644
--- a/it/install-methods/install-tftp.xml
+++ b/it/install-methods/install-tftp.xml
@@ -1,5 +1,5 @@
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 58446 -->
+<!-- original version: 59840 -->
 
  <sect1 condition="supports-tftp" id="install-tftp">
  <!-- <title>Preparing Files for TFTP Net Booting</title> -->
@@ -568,22 +568,6 @@ con l'opzione <userinput>filename=</userinput> in
 
 </para>
    </sect3>
-
-   <sect3 arch="mips;mipsel">
-   <!-- <title>Broadcom BCM91250A and BCM91480B TFTP Booting</title> -->
-   <title>Avvio di Broadcom BCM91250A e BCM91480B con TFTP</title>
-<para>
-
-<!--
-You don't have to configure DHCP in a special way because you'll pass the
-full path of the file to be loaded to CFE.
--->
-
-Non è necessario fare una particolare configurazione di DHCP perché si deve
-passare il percorso completo del file da caricare a CFE.
-
-</para>
-   </sect3>
   </sect2>
 
 <!-- FIXME: commented out since it seems too old to be usable and a current
diff --git a/it/install-methods/tftp/bootp.xml b/it/install-methods/tftp/bootp.xml
index c9df19216..7f1e98722 100644
--- a/it/install-methods/tftp/bootp.xml
+++ b/it/install-methods/tftp/bootp.xml
@@ -1,6 +1,5 @@
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 43558 -->
-
+<!-- original version: 59293 -->
 
   <sect2 condition="supports-bootp" id="tftp-bootp">
   <!-- <title>Setting up a BOOTP server</title> -->
@@ -106,10 +105,11 @@ 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
-those, read the section <xref linkend="dhcpd"/>.  In that case, you
+those, read the section <xref linkend="dhcpd"/>.  Otherwise you
 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
+block for the subnet containing the client in
+<filename>/etc/dhcp3/dhcpd.conf</filename>, and restart
 <command>dhcpd</command> with <userinput>/etc/init.d/dhcpd3-server
 restart</userinput>.
 -->
@@ -121,7 +121,8 @@ configurazione dei client per l'avvio con BOOTP, se si possiede una di
 queste leggere la sezione <xref linkend="dhcpd"/>. In caso contrario
 per proseguire è sufficiente aggiungere la direttiva <userinput>allow
 bootp</userinput> al blocco di configurazione della subnet a cui appartiene
-il client e riavviare <command>dhcpd</command> usando
+il client in <filename>/etc/dhcp3/dhcpd.conf</filename> e riavviare
+<command>dhcpd</command> usando
 <userinput>/etc/init.d/dhcpd3-server restart</userinput>.
 
 </para>