| 28 |
informs a computer of its IP address and where on the network to obtain |
informs a computer of its IP address and where on the network to obtain |
| 29 |
a boot image.</phrase> |
a boot image.</phrase> |
| 30 |
|
|
|
<phrase arch="m68k">Yet another alternative exists on VMEbus |
|
|
systems: the IP address can be manually configured in boot ROM.</phrase> |
|
|
|
|
| 31 |
The DHCP (Dynamic Host Configuration Protocol) is a more flexible, |
The DHCP (Dynamic Host Configuration Protocol) is a more flexible, |
| 32 |
backwards-compatible extension of BOOTP. |
backwards-compatible extension of BOOTP. |
| 33 |
Some systems can only be configured via DHCP. |
Some systems can only be configured via DHCP. |
| 273 |
|
|
| 274 |
</para> |
</para> |
| 275 |
</sect3> |
</sect3> |
|
|
|
|
<sect3 arch="m68k"> |
|
|
<title>BVM/Motorola TFTP Booting</title> |
|
|
<para> |
|
|
|
|
|
For BVM and Motorola VMEbus systems copy the files |
|
|
&bvme6000-tftp-files; to <filename>/tftpboot/</filename>. |
|
|
|
|
|
</para><para> |
|
|
|
|
|
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. |
|
|
|
|
|
</para> |
|
|
</sect3> |
|
| 276 |
|
|
| 277 |
<sect3 arch="mips"> |
<sect3 arch="mips"> |
| 278 |
<title>SGI TFTP Booting</title> |
<title>SGI TFTP Booting</title> |