Duke University
Department of
Computer Science

Boot Server

As mentioned earlier, this must exist on the same network segment as the client. May have multiple boot servers.
  • Make a /tftpboot directory owned by root and with permissions 711.

    • in.rarpd and rpc.bootparamd will be started at boot time if this exists

    • uncomment tftp in /etc/inetd.conf and send a HUP signal to the inetd process.

  • Make sure /etc/ethers contains the client's MAC address.

  • Make sure the boot server can resolve the clients IP address. Can use either/etc/hosts or a name service (NIS, DNS).

  • Make sure all the daemons are restarted; best practice is to reboot.

  • Some of this is done when individual clients are added (we will see shortly).
[Previous| Next]

   © 2001, Duke University Computer Science Department. All rights reserved.
   Comments to braun@cs.duke.edu