Installing and Administering Internet Services

170 Chapter 5
Configuring TFTP and BOOTP Servers
Booting RMP Clients
its local system. rbootd uses either NFS or TFTP to transfer boot files
from the remote server to its local system. (TFTP is the default file
transfer method.) rbootd then transfers bootable images to the client in
the form of RMP packets.
If TFTP is used to transfer boot files from a remote server, the boot files
must be accessible via TFTP. For more information, see “Configuring the
TFTP Server” on page 171. There must also be temporary file space
available in /var/rbootd/C0809* on the rbootd server. Generally, at
least 6 to 8 Mbytes of space should be allowed for each BOOTP client.
The temporary files are removed automatically after a certain period of
inactivity; by default, this time period is 10 minutes. You can specify a
different time period by using the -t option when starting rbootd.
If NFS is used to transfer boot files from a remote server, use the NFS
mount command to mount the path of the boot files on the rbootd server
system. The path that is specified with the mount command must be
defined with the bf tag for the client configuration in the
/etc/bootptab file. (See “Adding Client or Relay Information” on page
176.) Note that a directory or file must be exported with the exportfs
command before it can be NFS-mounted.
To start the rbootd daemon:
1. Set the environment variable START_RBOOTD to 1 in the file
/etc/rc.config.d/netdaemons. This causes rbootd to start
automatically whenever the system is booted.
2. Run the rbootd startup script with the following command:
/sbin/init.d/rbootd start