|
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
|
|
177.
|
|
|
BVM/Motorola TFTP Booting
|
|
|
Tag: title
|
|
|
|
(no translation yet)
|
|
|
|
Located in
install-methods.xml:1576
|
|
178.
|
|
|
For BVM and Motorola VMEbus systems copy the files &bvme6000-tftp-files; to <filename>/tftpboot/</filename>.
|
|
|
Tag: para
|
|
|
|
(no translation yet)
|
|
|
|
Located in
install-methods.xml:1577
|
|
179.
|
|
|
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.
|
|
|
Tag: para
|
|
|
|
(no translation yet)
|
|
|
|
Located in
install-methods.xml:1582
|
|
180.
|
|
|
SGI TFTP Booting
|
|
|
Tag: title
|
|
|
|
(no translation yet)
|
|
|
|
Located in
install-methods.xml:1594
|