|
163.
|
|
|
Look in <filename>/etc/inetd.conf</filename> and remember the directory which is used as the argument of <command>in.tftpd</command><footnote> <para> All <command>in.tftpd</command> alternatives available in Debian should log TFTP requests to the system logs by default. Some of them support a <userinput>-v</userinput> argument to increase verbosity. It is recommended to check these log messages in case of boot problems as they are a good starting point for diagnosing the cause of errors. </para> </footnote>; you'll need that below. If you've had to change <filename>/etc/inetd.conf</filename>, you'll have to notify the 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>.
|
|
|
Tag: para
|
|
|
|
(no translation yet)
|
|
|
|
Located in
install-methods.xml:1417
|
|
164.
|
|
|
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: <informalexample><screen>
# 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 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 <informalexample><screen>
# 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.
|
|
|
Tag: para
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
install-methods.xml:1437
|
|
167.
|
|
|
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. You will need to download the following files from the <filename>netboot/</filename> directory:
|
|
|
Tag: para
|
|
|
|
(no translation yet)
|
|
|
|
Located in
install-methods.xml:1469
|
|
168.
|
|
|
boot.msg
|
|
|
Tag: filename
|
|
|
|
(no translation yet)
|
|
|
|
Located in
install-methods.xml:1500
|
|
171.
|
|
|
Alpha TFTP Booting
|
|
|
Tag: title
|
|
|
|
(no translation yet)
|
|
|
|
Located in
install-methods.xml:1525
|
|
172.
|
|
|
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, 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.
|
|
|
Tag: para
|
|
|
|
(no translation yet)
|
|
|
|
Located in
install-methods.xml:1526
|
|
173.
|
|
|
SPARC TFTP Booting
|
|
|
Tag: title
|
|
|
|
(no translation yet)
|
|
|
|
Located in
install-methods.xml:1541
|
|
174.
|
|
|
Some SPARC architectures add the subarchitecture names, such as <quote>SUN4M</quote> or <quote>SUN4C</quote>, to the filename. Thus, if your system's subarchitecture is a SUN4C, and its IP is 192.168.1.3, the filename would be <filename>C0A80103.SUN4C</filename>. However, there are also subarchitectures where the file the client looks for is just <filename>client-ip-in-hex</filename>. An easy way to determine the hexadecimal code for the IP address is to enter the following command in a shell (assuming the machine's intended IP is 10.0.0.4). <informalexample><screen>
$ printf '%.2x%.2x%.2x%.2x\n' 10 0 0 4
</screen></informalexample> To get to the correct filename, you will need to change all letters to uppercase and if necessary append the subarchitecture name.
|
|
|
Tag: para
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
install-methods.xml:1542
|
|
175.
|
|
|
If you've done all this correctly, giving the command <userinput>boot net</userinput> from the OpenPROM should load the image. If the image cannot be found, try checking the logs on your tftp server to see which image name is being requested.
|
|
|
Tag: para
|
|
|
|
(no translation yet)
|
|
|
|
Located in
install-methods.xml:1558
|
|
176.
|
|
|
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.
|
|
|
Tag: para
|
|
|
|
(no translation yet)
|
|
|
|
Located in
install-methods.xml:1565
|