diff options
Diffstat (limited to 'it/install-methods/install-tftp.xml')
| -rw-r--r-- | it/install-methods/install-tftp.xml | 217 |
1 files changed, 143 insertions, 74 deletions
diff --git a/it/install-methods/install-tftp.xml b/it/install-methods/install-tftp.xml index c0b24bcb8..b2ceb98a4 100644 --- a/it/install-methods/install-tftp.xml +++ b/it/install-methods/install-tftp.xml @@ -4,26 +4,30 @@ <sect1 condition="supports-tftp" id="install-tftp"> <!-- <title>Preparing Files for TFTP Net Booting</title> --> - <title>Preparare i file per l'avvio TFTP da rete</title> + <title>Preparazione dei file per l'avvio TFTP da rete</title> <para> -<!-- If your machine is connected to a local area network, you may be able +<!-- +If your machine is connected to a local area network, you may be able to boot it over the network from another machine, using TFTP. If you intend to boot the installation system from another machine, the boot files will need to be placed in specific locations on that machine, -and the machine configured to support booting of your specific machine. --> +and the machine configured to support booting of your specific machine. +--> Se la propria macchina è connessa a una rete locale allora è possibile avviarla tramite TFTP da un'altra macchina. Se si vuole -avviare il sistema di installazione da un'altra macchina è necessario che -i file di avvio siano contenuti in particolari directory di questa macchina +avviare il sistema d'installazione da un'altra macchina è necessario che +i file d'avvio siano contenuti in particolari directory di questa macchina e che sia configurata per gestire l'avvio della propria macchina. </para><para> -<!-- You need to setup a TFTP server, and for many machines, a BOOTP server +<!-- +You need to setup a TFTP server, and for many machines, a BOOTP server <phrase condition="supports-rarp">, or RARP server</phrase> -<phrase condition="supports-dhcp">, or DHCP server</phrase>. --> +<phrase condition="supports-dhcp">, or DHCP server</phrase>. +--> È necessario attivare un server TFTP e, per più macchine, un server BOOTP<phrase condition="supports-rarp"> o un server @@ -31,32 +35,40 @@ RARP</phrase><phrase condition="supports-dhcp"> o un server DHCP</phrase>. </para><para> -<!-- <phrase condition="supports-rarp">The Reverse Address Resolution +<!-- +<phrase condition="supports-rarp">The Reverse Address Resolution Protocol (RARP) is one way to tell your client what IP address to use for -itself. Another way is to use the BOOTP protocol. </phrase> --> +itself. Another way is to use the BOOTP protocol. </phrase> +--> <phrase condition="supports-rarp">Il RARP (Reverse Address Resolution Protocol) è un metodo per comunicare ai client quale indirizzo IP usare. In alternativa è possibile usare il protocollo BOOTP. </phrase> -<!-- <phrase condition="supports-bootp">BOOTP is an IP protocol that +<!-- +<phrase condition="supports-bootp">BOOTP is an IP protocol that informs a computer of its IP address and where on the network to obtain -a boot image. </phrase> --> +a boot image. </phrase> +--> <phrase condition="supports-bootp">BOOTP è un protocollo IP che comunica a un computer qual è il proprio indirizzo IP e dove può recuperare dalla rete un'immagine per l'avvio. </phrase> -<!-- <phrase arch="m68k"> Yet another alternative exists on VMEbus -systems: the IP address can be manually configured in boot ROM. </phrase> --> +<!-- +<phrase arch="m68k"> Yet another alternative exists on VMEbus +systems: the IP address can be manually configured in boot ROM. </phrase> +--> <phrase arch="m68k">Sui sistemi VMEbus esiste un'altra alternativa: l'indirizzo IP può essere configurato manualmente nella ROM di avvio. </phrase> -<!-- <phrase condition="supports-dhcp">The DHCP (Dynamic Host Configuration +<!-- +<phrase condition="supports-dhcp">The DHCP (Dynamic Host Configuration Protocol) is a more flexible, backwards-compatible extension of BOOTP. -Some systems can only be configured via DHCP. </phrase> --> +Some systems can only be configured via DHCP. </phrase> +--> <phrase condition="supports-dhcp">Il DHCP (Dynamic Host Configuration Protocol) è una estensione più flessibile ma compatibile all'indietro di @@ -64,9 +76,11 @@ BOOTP. Alcuni sistemi possono essere configurati solo tramite DHCP. </phrase> </para><para arch="powerpc"> -<!-- For PowerPC, if you have a NewWorld Power Macintosh machine, it is a +<!-- +For PowerPC, if you have a NewWorld Power Macintosh machine, it is a good idea to use DHCP instead of BOOTP. Some of the latest machines -are unable to boot using BOOTP. --> +are unable to boot using BOOTP. +--> Su PowerPC, se si possiede una macchina Power Macintosh NewWorld, è consigliabile usare DHCP anziché BOOTP. Alcune delle macchine più recenti @@ -74,10 +88,12 @@ non sono capaci di fare l'avvio usando BOOTP. </para><para arch="alpha"> -<!-- Unlike the Open Firmware found on Sparc and PowerPC machines, the SRM +<!-- +Unlike the Open Firmware found on Sparc and PowerPC machines, the SRM console will <emphasis>not</emphasis> use RARP to obtain its IP address, and therefore you must use BOOTP for net booting your -Alpha<footnote> --> +Alpha<footnote> +--> Diversamente dall'Open Firmware presente sulle macchine Sparc e PowerPC, la console SRM <emphasis>non</emphasis> usa RARP per procurarsi l'indirizzo IP @@ -86,10 +102,12 @@ Alpha<footnote> <para> -<!-- Alpha systems can also be net-booted using the DECNet MOP (Maintenance +<!-- +Alpha systems can also be net-booted using the DECNet MOP (Maintenance Operations Protocol), but this is not covered here. Presumably, your local OpenVMS operator will be happy to assist you should you have -some burning need to use MOP to boot Linux on your Alpha. --> +some burning need to use MOP to boot Linux on your Alpha. +--> I sistemi Alpha possono essere avviati dalla rete anche usando DECNet MOP (Maintenance Operations Protocol) ma questo metodo non è trattato in questo @@ -98,15 +116,18 @@ prestare il proprio aiuto per poter usare MOP per l'avvio di Linux su Alpha. </para> -<!-- </footnote>. You can also enter the IP configuration for network -interfaces directly in the SRM console. --> +<!-- +</footnote>. You can also enter the IP configuration for network +interfaces directly in the SRM console. +--> </footnote>. È anche possibile inserire la configurazione IP per le interfacce di rete direttamente dalla console SRM. </para><para arch="hppa"> -<!-- Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP. +<!-- +Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP. There is an <classname>rbootd</classname> package available in Debian. --> @@ -116,11 +137,13 @@ BOOTP, in Debian è disponibile il pacchetto <classname>rbootd</classname>. </para><para> -<!-- The Trivial File Transfer Protocol (TFTP) is used to serve the boot +<!-- +The Trivial File Transfer Protocol (TFTP) is used to serve the boot image to the client. Theoretically, any server, on any platform, which implements these protocols, may be used. In the examples in this section, we shall provide commands for SunOS 4.x, SunOS 5.x -(a.k.a. Solaris), and GNU/Linux. --> +(a.k.a. Solaris), and GNU/Linux. +--> Il TFTP (Trivial File Transfer Protocol) è usato per fornire l'immagine di avvio al client. Teoricamente si può usare un qualsiasi server, su qualsiasi @@ -130,11 +153,13 @@ Solaris) e GNU/Linux. <note arch="i386"><para> -<!-- To use the Pre-boot Execution Environment (PXE) method of TFTP +<!-- +To use the Pre-boot Execution Environment (PXE) method of TFTP booting, you will need a TFTP server with <userinput>tsize</userinput> support. On a &debian; server, the <classname>atftpd</classname> and <classname>tftpd-hpa</classname> packages qualify; we recommend -<classname>tftpd-hpa</classname>. --> +<classname>tftpd-hpa</classname>. +--> Per usare il metodo di avvio PXE (Pre-boot Execution Environment) di TFTP è necessario un server TFTP con supporto per <userinput>tsize</userinput>. @@ -152,12 +177,14 @@ consiglia l'uso di quest'ultimo. <sect2 id="tftpd"> <!-- <title>Enabling the TFTP Server</title> --> - <title>Attivare il server TFTP</title> + <title>Attivazione del server TFTP</title> <para> -<!-- To get the TFTP server ready to go, you should first make sure that +<!-- +To get the TFTP server ready to go, you should first make sure that <command>tftpd</command> is enabled. This is usually enabled by having -something like the following line in <filename>/etc/inetd.conf</filename>: --> +something like the following line in <filename>/etc/inetd.conf</filename>: +--> Per avere un server TFTP pronto all'uso è necessario assicurarsi che <command>tftpd</command> sia attivo. Di solito viene attivato da una riga @@ -167,15 +194,18 @@ simile a questa in <filename>/etc/inetd.conf</filename>: tftp dgram udp wait nobody /usr/sbin/tcpd in.tftpd /tftpboot </screen></informalexample> -<!-- Debian packages will in general set this up correctly by default when they -are installed. --> +<!-- +Debian packages will in general set this up correctly by default when they +are installed. +--> Solitamente i pacchetti Debian impostano correttamente il server durante l'installazione. </para><para> -<!-- Look in that file and remember the directory which is used as the +<!-- +Look in that file and remember the directory which is used as the argument of <command>in.tftpd</command>; you'll need that below. The <userinput>-l</userinput> argument enables some versions of <command>in.tftpd</command> to log all requests to the system logs; @@ -185,7 +215,8 @@ running <command>inetd</command> process that the file has changed. On a Debian machine, run <userinput>/etc/init.d/inetd reload</userinput>; on other machines, find out the process ID for <command>inetd</command>, and run -<userinput>kill -HUP <replaceable>inetd-pid</replaceable></userinput>. --> +<userinput>kill -HUP <replaceable>inetd-pid</replaceable></userinput>. +--> Cercare all'interno di questo file la directory usata come argomento di <command>in.tftpd</command> e prenderne nota, sarà necessaria in seguito. @@ -201,9 +232,11 @@ processo <command>inetd</command> ed eseguire <userinput>kill -HUP </para><para arch="mips"> -<!-- If you intend to install Debian on an SGI machine and your TFTP server +<!-- +If you intend to install Debian on an SGI machine and your TFTP server is a GNU/Linux box running Linux 2.4, you'll need to set the following on -your server: --> +your server: +--> Se si intende installare Debian su una macchina SGI e il server TFTP è su una macchina GNU/Linux con Linux 2.4 è necessario eseguire comando seguente sul @@ -213,11 +246,13 @@ server: # echo 1 > /proc/sys/net/ipv4/ip_no_pmtu_disc </screen></informalexample> -<!-- to turn off Path MTU discovery, otherwise the SGI's PROM can't +<!-- +to turn off Path MTU discovery, otherwise the SGI's PROM can't download the kernel. Furthermore, make sure TFTP packets are sent from a source port no greater than 32767, or the download will stall after the first packet. Again, it's Linux 2.4.X tripping this bug in the -PROM, and you can avoid it by setting --> +PROM, and you can avoid it by setting +--> per disattivare il Path MTU discovery, in caso contrario la PROM delle SGI non può scaricare il kernel. Inoltre, assicurarsi che i pacchetti TFTP siano @@ -229,7 +264,9 @@ aggirato con Linux 2.4.X eseguendo il comando seguente # echo "2048 32767" > /proc/sys/net/ipv4/ip_local_port_range </screen></informalexample> -<!-- to adjust the range of source ports the Linux TFTP server uses. --> +<!-- +to adjust the range of source ports the Linux TFTP server uses. +--> per regolare l'intervallo delle porte sorgente usate sul server TFTP Linux. @@ -241,13 +278,15 @@ per regolare l'intervallo delle porte sorgente usate sul server TFTP Linux. <title>Posizionamento delle immagini TFTP</title> <para> -<!-- Next, place the TFTP boot image you need, as found in +<!-- +Next, place the TFTP boot image you need, as found in <xref linkend="where-files"/>, in the <command>tftpd</command> boot image directory. Generally, this directory will be <filename>/tftpboot</filename>. You'll have to make a link from that file to the file which <command>tftpd</command> will use for booting a particular client. Unfortunately, the file name is determined by the -TFTP client, and there are no strong standards. --> +TFTP client, and there are no strong standards. +--> Spostare le immagini TFTP di cui si ha bisogno (come descritto in <xref linkend="where-files"/>) nella directory delle immagini di avvio per @@ -259,12 +298,14 @@ esiste uno standard. </para><para arch="powerpc"> -<!-- On NewWorld Power Macintosh machines, you will need to set up the +<!-- +On NewWorld Power Macintosh machines, you will need to set up the <command>yaboot</command> boot loader as the TFTP boot image. <command>Yaboot</command> will then retrieve the kernel and RAMdisk images via TFTP itself. For net booting, use the <filename>yaboot-netboot.conf</filename>. Just rename this to -<filename>yaboot.conf</filename> in the TFTP directory. --> +<filename>yaboot.conf</filename> in the TFTP directory. +--> Sulle macchine Power Machintosh NewWorld è necessario configurare il bootloader <command>yaboot</command> come immagine di avvio TFTP. Sarà poi @@ -275,11 +316,13 @@ TFTP e poi rinominarlo in <filename>yaboot.conf</filename>. </para><para arch="i386"> -<!-- For PXE booting, everything you should need is set up in the +<!-- +For PXE booting, everything you should need is set up in the <filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this tarball into the <command>tftpd</command> boot image directory. Make sure your dhcp server is configured to pass <filename>/pxelinux.0</filename> -to <command>tftpd</command> as the filename to boot. --> +to <command>tftpd</command> as the filename to boot. +--> Per l'avvio PXE tutte le operazioni necessarie sono già state fatte in <filename>netboot/netboot.tar.gz</filename>. Estrarre questo tarball nella @@ -289,12 +332,14 @@ come file da avviare a <command>tftpd</command>. </para><para arch="ia64"> -<!-- For PXE booting, everything you should need is set up in the +<!-- +For PXE booting, everything you should need is set up in the <filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this tarball into the <command>tftpd</command> boot image directory. Make sure your dhcp server is configured to pass <filename>/debian-installer/ia64/elilo.efi</filename> -to <command>tftpd</command> as the filename to boot. --> +to <command>tftpd</command> as the filename to boot. +--> Per l'avvio PXE tutte le operazioni necessarie sono già state fatte in <filename>netboot/netboot.tar.gz</filename>. Estrarre questo tarball nella @@ -310,12 +355,14 @@ a <command>tftpd</command>. <title>Immagini TFTP per DECstation</title> <para> -<!-- For DECstations, there are tftpimage files for each subarchitecture, +<!-- +For DECstations, there are tftpimage files for each subarchitecture, which contain both kernel and installer in one file. The naming convention is <replaceable>subarchitecture</replaceable>/netboot-boot.img. Copy the tftpimage file you would like to use to <userinput>/tftpboot/tftpboot.img</userinput> if you work with the -example BOOTP/DHCP setups described above. --> +example BOOTP/DHCP setups described above. +--> Per le DECstation esistono più file tftpimage, uno per ciascuna sottoarchitettura, che contengono sia il kernel che l'installatore. @@ -327,13 +374,15 @@ il file tftpimage che si vuole usare come </para><para> -<!-- The DECstation firmware boots by TFTP with the command <userinput>boot +<!-- +The DECstation firmware boots by TFTP with the command <userinput>boot <replaceable>#</replaceable>/tftp</userinput>, where <replaceable>#</replaceable> is the number of the TurboChannel device from which to boot. On most DECstations this is <quote>3</quote>. If the BOOTP/DHCP server does not supply the filename or you need to pass additional parameters, they can optionally be appended with the -following syntax: --> +following syntax: +--> Il firmware DECstation fa l'avvio del sistema con TFTP usando il comando <userinput>boot <replaceable>#</replaceable>/tftp</userinput>, dove @@ -344,17 +393,20 @@ passare altri parametri, si possono aggiungere usando questa sintassi: </para><para> -<!-- <userinput>boot #/tftp/filename param1=value1 param2=value2 -...</userinput> --> +<!-- +<userinput>boot #/tftp/filename param1=value1 param2=value2 ...</userinput> +--> <userinput>boot #/tftp/nomefile param1=valore1 param2=valore2 ...</userinput> </para><para> -<!-- Several DECstation firmware revisions show a problem with regard to +<!-- +Several DECstation firmware revisions show a problem with regard to net booting: the transfer starts, but after some time it stops with an <computeroutput>a.out err</computeroutput>. This can have several -reasons: --> +reasons: +--> Parecchie versioni del firmware DECstation hanno un problema relativo all'avvio da rete: il trasferimento inizia ma dopo un po' si ferma restituendo @@ -364,7 +416,8 @@ cause: <orderedlist> <listitem><para> -<!-- The firmware does not respond to ARP requests during a TFTP +<!-- +The firmware does not respond to ARP requests during a TFTP transfer. This leads to an ARP timeout and the transfer stops. The solution is to add the MAC address of the Ethernet card in the DECstation statically to the ARP table of the TFTP server. This is @@ -373,7 +426,8 @@ done by running <userinput>arp -s <replaceable>MAC-address</replaceable></userinput> as root on the machine acting as TFTP server. The MAC-address of the DECstation can be read out by entering <command>cnfg</command> at the DECstation -firmware prompt. --> +firmware prompt. +--> Il firmware non risponde alle richieste ARP durante i trasferimenti TFTP. Questo può comportare un timeout ARP e il blocco del trasferimento. La @@ -388,8 +442,9 @@ letto inserendo <command>cnfg</command> al prompt del firmware DECstation. </para></listitem> <listitem><para> -<!-- The firmware has a size limit on the files that can be booted -by TFTP. --> +<!-- +The firmware has a size limit on the files that can be booted by TFTP. +--> Il firmware ha un limite sulla dimensione dei file che possono essere avviati tramite TFTP. @@ -397,10 +452,12 @@ tramite TFTP. </para></listitem> </orderedlist> -<!-- There are also firmware revisions that cannot boot via TFTP at all. An +<!-- +There are also firmware revisions that cannot boot via TFTP at all. An overview about the different firmware revisions can be found at the NetBSD web pages: -<ulink url="http://www.netbsd.org/Ports/pmax/board-list.html#proms"></ulink>. --> +<ulink url="http://www.netbsd.org/Ports/pmax/board-list.html#proms"></ulink>. +--> Ci sono delle versioni del firmware che non possono essere assolutamente avviate tramite TFTP. Una panoramica sulle varie versioni del firmware può @@ -415,7 +472,8 @@ essere trovata nelle pagine web di NetBSD: <title>Avvio TFTP di macchine Alpha</title> <para> -<!-- On Alpha, you must specify the filename (as a relative path to the +<!-- +On Alpha, you must specify the filename (as a relative path to the boot image directory) using the <userinput>-file</userinput> argument to the SRM <userinput>boot</userinput> command, or by setting the <userinput>BOOT_FILE</userinput> environment variable. Alternatively, @@ -423,7 +481,8 @@ the filename can be given via BOOTP (in ISC <command>dhcpd</command>, use the <userinput>filename</userinput> directive). Unlike Open Firmware, there is <emphasis>no default filename</emphasis> on SRM, so you <emphasis>must</emphasis> specify a filename by either one of -these methods. --> +these methods. +--> Su Alpha si deve specificare il nome del file (come percorso relativo alla directory con l'immagine di avvio) usando l'opzione @@ -444,14 +503,16 @@ appena descritti. <title>Avvio TFTP di macchine SPARC</title> <para> -<!-- SPARC architectures for instance use the subarchitecture names, such +<!-- +SPARC architectures for instance use the subarchitecture names, such as <quote>SUN4M</quote> or <quote>SUN4C</quote>; in some cases, the architecture is left blank, so the file the client looks for is just <filename>client-ip-in-hex</filename>. Thus, if your system subarchitecture is a SUN4C, and its IP is 192.168.1.3, the filename would be <filename>C0A80103.SUN4C</filename>. An easy way to determine this is to enter the following command in a shell (assuming the -machine's intended IP is 10.0.0.4). --> +machine's intended IP is 10.0.0.4). +--> Le architetture SPARC usano dei nomi per le sottoarchitetture, per esempio <quote>SUN4M</quote> o <quote>SUN4C</quote> e in alcuni casi non c'è il nome @@ -467,9 +528,11 @@ sia 10.0.0.4). $ printf '%.2x%.2x%.2x%.2x\n' 10 0 0 4 </screen></informalexample> -<!-- This will spit out the IP in hexadecimal; to get to the correct +<!-- +This will spit out the IP in hexadecimal; to get to the correct filename, you will need to change all letters to uppercase and -if necessary append the subarchitecture name. --> +if necessary append the subarchitecture name. +--> Questo comando restituisce l'IP in esadecimale; per ottenere il corretto nome del file è necessario cambiare tutte le lettere in maiuscole e, se @@ -477,10 +540,12 @@ necessario, aggiungere il nome della sottoarchitettura. </para><para> -<!-- You can also force some sparc systems to look for a specific file name +<!-- +You can also force some sparc systems to look for a specific file name by adding it to the end of the OpenPROM boot command, such as <userinput>boot net my-sparc.image</userinput>. This must still reside -in the directory that the TFTP server looks in. --> +in the directory that the TFTP server looks in. +--> È anche possibile forzare alcuni sistemi sparc a cercare un particolare file aggiungendone il nome alla fine del comando boot di OpenPROM, per esempio @@ -495,19 +560,23 @@ nella directory in cui il server TFTP ricerca i file. <title>Avvio TFTP di macchine BVM/Motorola</title> <para> -<!-- For BVM and Motorola VMEbus systems copy the files -&bvme6000-tftp-files; to <filename>/tftpboot/</filename>. --> +<!-- +For BVM and Motorola VMEbus systems copy the files +&bvme6000-tftp-files; to <filename>/tftpboot/</filename>. +--> Per i sistemi BVM e Motorola VMEbus copiare i file &bvme6000-tftp-files; in <filename>/tftpboot/</filename>. </para><para> -<!-- Next, configure your boot ROMs or BOOTP server to initially load the +<!-- +Next, configure your boot ROMs or BOOTP server to initially load the <filename>tftplilo.bvme</filename> or <filename>tftplilo.mvme</filename> files from the TFTP server. Refer to the <filename>tftplilo.txt</filename> file for your subarchitecture -for additional system-specific configuration information. --> +for additional system-specific configuration information. +--> Poi configurare le ROM di avvio o il server BOOTP per caricare inizialmente i file <filename>tftplilo.bvme</filename> o <filename>tftplilo.mvme</filename> |