diff options
| author | Luca Monducci <luca.mo@tiscali.it> | 2006-12-31 16:40:02 +0000 |
|---|---|---|
| committer | Luca Monducci <luca.mo@tiscali.it> | 2006-12-31 16:40:02 +0000 |
| commit | 9945ad98e5637bc3c5762ec4cdbabe2ef6f239b0 (patch) | |
| tree | 4dc3a1faac0f00f0e3eeb956d42665d408a8fdee /it/install-methods/tftp/bootp.xml | |
| parent | 0ef7d00bd3acf578050a227bd27ea39fee8d04b3 (diff) | |
| download | installation-guide-9945ad98e5637bc3c5762ec4cdbabe2ef6f239b0.zip | |
Updated Italian translation of d-i manual
Diffstat (limited to 'it/install-methods/tftp/bootp.xml')
| -rw-r--r-- | it/install-methods/tftp/bootp.xml | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/it/install-methods/tftp/bootp.xml b/it/install-methods/tftp/bootp.xml index a89982818..c9df19216 100644 --- a/it/install-methods/tftp/bootp.xml +++ b/it/install-methods/tftp/bootp.xml @@ -1,9 +1,9 @@ <!-- retain these comments for translator revision tracking --> -<!-- original version: 36841 --> +<!-- original version: 43558 --> <sect2 condition="supports-bootp" id="tftp-bootp"> - <!-- <title>Setting up BOOTP server</title> --> + <!-- <title>Setting up a BOOTP server</title> --> <title>Attivazione di un server BOOTP</title> <para> @@ -11,15 +11,15 @@ There are two BOOTP servers available for GNU/Linux. The first is CMU <command>bootpd</command>. The other is actually a DHCP server: ISC <command>dhcpd</command>. In &debian; these are contained in the -<classname>bootp</classname> and <classname>dhcp</classname> packages -respectively. +<classname>bootp</classname> and <classname>dhcp3-server</classname> +packages respectively. --> Per GNU/Linux sono disponibili due server BOOTP. Il primo è <command>bootpd</command> di CMU, l'altro è un server DHCP: <command>dhcpd</command> di ISC. Questi server sono rispettivamente contenuti nei pacchetti &debian; <classname>bootp</classname> e -<classname>dhcp</classname>. +<classname>dhcp3-server</classname>. </para><para> @@ -106,11 +106,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"/>. Otherwise, you +those, read the section <xref linkend="dhcpd"/>. In that case, 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 -<command>dhcpd</command> with <userinput>/etc/init.d/dhcpd +<command>dhcpd</command> with <userinput>/etc/init.d/dhcpd3-server restart</userinput>. --> @@ -122,7 +122,7 @@ 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 -<userinput>/etc/init.d/dhcpd restart</userinput>. +<userinput>/etc/init.d/dhcpd3-server restart</userinput>. </para> </sect2> |