/[d-i]/trunk/manual/en/install-methods/install-tftp.xml
ViewVC logotype

Diff of /trunk/manual/en/install-methods/install-tftp.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 43696 by fjp, Sun Dec 31 02:03:44 2006 UTC revision 56425 by fjp, Wed Oct 15 08:50:59 2008 UTC
# Line 13  and the machine configured to support bo Line 13  and the machine configured to support bo
13    
14  </para><para>  </para><para>
15    
16  You need to setup a TFTP server, and for many machines a DHCP  You need to set up a TFTP server, and for many machines a DHCP
17  server<phrase condition="supports-rarp">, or RARP  server<phrase condition="supports-rarp">, or RARP
18  server</phrase><phrase condition="supports-bootp">, or BOOTP  server</phrase><phrase condition="supports-bootp">, or BOOTP
19  server</phrase>.  server</phrase>.
# Line 105  are installed. Line 105  are installed.
105  </para>  </para>
106  <note><para>  <note><para>
107    
108  Historically TFTP servers used <filename>/tftpboot</filename> as directory  Historically, TFTP servers used <filename>/tftpboot</filename> as directory
109  to serve images from. However, &debian; packages may use other directories  to serve images from. However, &debian; packages may use other directories
110  to comply with the <ulink url="&url-fhs-home;">Filesystem Hierarchy  to comply with the <ulink url="&url-fhs-home;">Filesystem Hierarchy
111  Standard</ulink>. For example, <classname>tftpd-hpa</classname> by default  Standard</ulink>. For example, <classname>tftpd-hpa</classname> by default
# Line 119  Look in <filename>/etc/inetd.conf</filen Line 119  Look in <filename>/etc/inetd.conf</filen
119  is used as the argument of <command>in.tftpd</command><footnote>  is used as the argument of <command>in.tftpd</command><footnote>
120    
121  <para>  <para>
122  The <userinput>-l</userinput> argument enables some versions of  All <command>in.tftpd</command> alternatives available in Debian should
123  <command>in.tftpd</command> to log all requests to the system logs;  log TFTP requests to the system logs by default. Some of them support a
124  this is useful for diagnosing boot errors.  <userinput>-v</userinput> argument to increase verbosity.
125    It is recommended to check these log messages in case of boot problems
126    as they are a good starting point for diagnosing the cause of errors.
127  </para>  </para>
128    
129  </footnote>; you'll need that below.  </footnote>; you'll need that below.
# Line 172  TFTP client, and there are no strong sta Line 174  TFTP client, and there are no strong sta
174  On NewWorld Power Macintosh machines, you will need to set up the  On NewWorld Power Macintosh machines, you will need to set up the
175  <command>yaboot</command> boot loader as the TFTP boot image.  <command>yaboot</command> boot loader as the TFTP boot image.
176  <command>Yaboot</command> will then retrieve the kernel and RAMdisk  <command>Yaboot</command> will then retrieve the kernel and RAMdisk
177  images via TFTP itself.  For net booting, use the  images via TFTP itself. You will need to download the following files
178  <filename>yaboot-netboot.conf</filename>.  Just rename this to  from the <filename>netboot/</filename> directory:
179  <filename>yaboot.conf</filename> in the TFTP directory.  
180    <itemizedlist>
181    <listitem><para>
182    
183    <filename>vmlinux</filename>
184    
185    </para></listitem>
186    <listitem><para>
187    
188    <filename>initrd.gz</filename>
189    
190    </para></listitem>
191    <listitem><para>
192    
193    <filename>yaboot</filename>
194    
195    </para></listitem>
196    <listitem><para>
197    
198    <filename>yaboot.conf</filename>
199    
200    </para></listitem>
201    <listitem><para>
202    
203    <filename>boot.msg</filename>
204    
205    </para></listitem>
206    </itemizedlist>
207    
208  </para><para arch="x86">  </para><para arch="x86">
209    
# Line 195  to <command>tftpd</command> as the filen Line 224  to <command>tftpd</command> as the filen
224    
225  </para>  </para>
226    
    <sect3 arch="mipsel">  
    <title>DECstation TFTP Images</title>  
 <para>  
   
 For DECstations, there are tftpimage files for each subarchitecture,  
 which contain both kernel and installer in one file. The naming  
 convention is  
 <filename><replaceable>subarchitecture</replaceable>/netboot-boot.img</filename>.  
 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.  
   
 </para><para>  
   
 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:  
   
 </para><para>  
   
 <userinput>boot #/tftp/filename param1=value1 param2=value2 ...</userinput>  
   
 </para><para>  
   
 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:  
   
 <orderedlist>  
 <listitem><para>  
   
 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  
 done by running <userinput>arp -s  
 <replaceable>IP-address</replaceable>  
 <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.  
   
 </para></listitem>  
 <listitem><para>  
   
 The firmware has a size limit on the files that can be booted  
 by TFTP.  
   
 </para></listitem>  
 </orderedlist>  
   
 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>.  
   
 </para>  
    </sect3>  
   
227     <sect3 arch="alpha">     <sect3 arch="alpha">
228     <title>Alpha TFTP Booting</title>     <title>Alpha TFTP Booting</title>
229  <para>  <para>
Legend:
Removed from v.43696  
changed lines
  Added in v.56425
  ViewVC Help
Powered by ViewVC 1.1.5