No subject

	Clients that do not specify boot files in their boot
	requests always elicit a reply from the server.  The exact
	reply depends on the values of the hd and bf tags.  If the
	bf tag specifies an absolute path name, and the file is
	accessible, that path name is returned in the reply packet.
	Otherwise, if the hd and bf tags together specify an
	accessible file, that file name is returned in the reply.
	If a complete file name cannot be determined, or the file is
	not accessible publicly, the reply contains a zeroed-out
	bootfile field.

	If the tftp pseudouser exists, bootpd treats all path names
	(absolute or relative) as being relative to the home
	directory of tftp and checks there first.  If the file is
	not accessible under the tftp home directory or the tftp
	pseudouser does not exist, bootpd checks for the file
	relative to /.


(hmm, the HP version of bootpd is strange, relative to the CMU
edition I'm running on other hosts..)

--
Eric Schnoebelen		eric at cirr.com		 http://www.cirr.com
		"Strange things are afoot at the Circle-K"
			 -- Bill and Ted's Excellent Adventure