For BOOTP and DHCP support, I'd recommend to install ISC's dhcpd. It will handle both protocols.

rarpd responds to reverse ARP requests. It uses /etc/ethers (or NIS lookup, but that's not commonly configured) to get an IP address or hostname. If a hostname is presented in /etc/ethers, the hostname is looked up regulary to get an IP address.

/etc/ethers uses a quite simple format. One entry per line, each consisting of an MAC address (with ':' separated, hex digits in upper case) and (separated by space or tab) IP-Address or hostname.

But before it responds (after having found a match in /etc/ethers), it also checks if it can find a boot image for the IP address found. This IP address is used in hex format, uppercase with no interpunctuation (like C0A80A0F for 192.168.10.15). rarpd tries to find this file in the /tftpboot/ directory and only responds if it is found there. A symlink is okay, too, even a stale one...

rbootd typically reads a file (/etc/rbootd.conf) containing pairs of ethernet addresses (upper/lower case is ignored, colons to separate octets, leading zero of an octet isn't needed to be noted) and a filename. This is the file which will be served (if you don't specify a file, chances are that you may specify the filename at the workstation's command prompt).

All those boot image's filenames are relative to /var/lib/rbootd, so this directory contains all boot images.

There are several mopd variants available. I suggest you to use the one you can find at XXX. This one can read the ELF object format so you don't need to convert your freshly linked kernel image into proprietary MOP image format (I'm not even sure if there are conversion programs available at all...).

Generally, mopd tries to delive files from the /tftpboot/mop/ directory. It doesn't use the client's supplied machine type ID, but the client's MAC address, plus the suffix ".SYS". The MAX address is expected to be with leading zeros and hex digits in lowercase. It also accepts symlinks, so keep the images' real names readable and supply proper symbolic links for all your MOP-booting clients.