LAN Boot -- bootp Server Setup README

1. Configure the client's /etc/bootptab file -- slight differences exist in configuring the /etc/bootptab
file depending on whether you are configuring the file for an HP 9000 client or an HP Integrity client.
Use 1 of the following 2 configurations to configure the /etc/bootptab file:
Configure the /etc/bootptab file for an HP 9000 (PA-RISC) client.
Edit the /etc/bootptab file to contain the following information:
(Remember to change the ha, ip, and sm fields as appropriate)
System-Name:\
ht=ethernet:\
bf=/opt/ignite/boot/boot_lif:\
ha=001122334455:\
ip=100.101.102.103:\
sm=255.255.248.0
Configure the /etc/bootptab file for an HP Integrity (Itanium-based) client
Edit the /etc/bootptab file to contain the following information:
(Remember to change the ha, ip, and sm fields as appropriate)
System-Name:\
ht=ethernet:\
bf=/opt/ignite/boot/nbp.efi:\
ha=001122334455:\
ip=100.101.102.103:\
sm=255.255.248.0
NOTE:In the above examples, the boot file is the only difference.
It is important that you use the correct boot file for the corresponding
architecture.
Verify that there are no trailing white spaces after the backslashes.
2. Configure the /etc/inetd.conf file
The inetd.conf file contains protocols that are subsumed by
inetd. Inetd will use this file to determine what services it can
spawn when requested. Bootp is configured to run via inetd. So
we must uncomment the bootps entry within the inetd.conf file to
enable the inetd daemon to spawn the bootps when requested.
Tftp is also necessary for the file transfer of the boot_lif/nbp.efi
and subsequent files.
The entries for tftp and bootps in the inetd.conf file should look
like the following:
tftp dgram udp wait root /usr/lbin/tftpd tftpd\
/opt/tftpboot\
/opt/ignite\
/var/opt/ignite
bootps dgram udp wait root /usr/lbin/bootpd bootpd -d 3