Filter
Top Products
• ha: Client’s network hardware address
• ip: Client’s IP address
4 The .ris93.alpha entry defines characteristics for the current version
of the operating system RIS area. The fields specify the following:
• tc: Table continuation
The tc field lets you follow pointers back to common entries. For
example, the tc entry for .ris93.alpha in Example 5–1 points to
the .ris.dec entry. The .ris.dec entry contains the common
hardware type (ht) and vendor specific (vm) information. The
.ris93.alpha entry contains common information about the boot
file location.
• bf: Name of the boot file
• rp: The client will mount its root on the server.
The general format for entries in the bootptab file is a label followed
by one or more colon-separated fields. Each of these fields consists of a
two-character tag field tg followed by an equal sign (=) and the tag value
value:
[label]:tg[=value][:tg[=value]:…]
See bootptab(4) for additional information. See dhcptags
(4)
for
information about valid tg tags.
5.1.4 The tftpd Daemon
The tftpd daemon uses the Trivial File Transfer Protocol (TFTP) to transfer
the boot file during a remote boot process. The tftpd daemon starts
when a file is ready to be transferred. See tftp
(1) and tftpd(8) for more
information.
5.2 Remote Boot Process Flow
Client systems use the bootp protocol to perform the remote boot operation
from a RIS server. The command used to initiate a remote boot is processor
specific. For additional information, see the Installation Guide — Advanced
Topics. However, after the remote boot operation has started, the underlying
process is the same for all versions of the operating system that support
network booting:
1. The processor-specific remote boot command is issued at the client
console prompt.
2. The client processor firmware sends a BOOTP packet over the Ethernet
contining the client’s hardware Ethernet address.
5–4 Booting a RIS Client