#
# $Header: /tmp_mnt/vol/nwd/tools/media/X11/XP/src/bootp/RCS/bootptab,v 1.5 1992/07/06 18:06:10 bwa Exp $
#
# /etc/bootptab: database for bootp server (/etc/bootpd)
# Last update Mon 11/7/88 18:03
# Blank lines and lines beginning with '#' are ignored.
#
# Legend:
#
#	first field -- hostname
#			(may be full domain name and probably should be)
#
#	hd -- The full path of the home directory (typically /tftpboot)
#	bf -- The path and name of the boot file within the home directory 
#	cs -- The internet address of the cookie server(s) 
#	ds -- The internet address of the domain name server(s)
#	gw -- The internet address of the gateway servers(s)
#	ha -- The requester's hardware address (typically ethernet address)
#	ht -- The requester's hardware type (typically ethernet) 
#	im -- The internet address of the impress server(s)
#	ip -- The requester's internet address  
#	lg -- The internet address of the log server(s)
#	lp -- The internet address of the LPR server(s)
#	ns -- The internet address of the IEN-116 name server(s)
#	rl -- Resource location protocol server(s) 
#	sm -- The subnet mask
#	tc -- The template command 
#	to -- The time offset in seconds
#	ts -- The internet address of the time server(s) 
#	
#	The 'requester' is an X-terminal, PC, or other remote
#	device that queries the bootp server for network or boot
#	information. 
#
# Entries in this file should be confined to one per line. If one wishes
# to enter part of an entry on the next line, a backslash should be
# used to indicate this. If a backslash is omitted where one is 
# needed, undesired events may happen and/or desired events may not. 
#

# First, we define a global entry which specifies the stuff every host uses.

global.d:\
	:sm=255.255.255.0:\
	:ds=128.07.5.200 128.07.61.150: \
	:hn:\
	:hd=/tftpboot:


# Next, we can define different master entries for each subnet. . .

subnet60: :tc=global.d:gw=128.07.60.100:
subnet61: :tc=global.d:gw=128.07.61.100:

# Individual X terminal entries (no secure TFTP) 
#
# If the 'bf' field does not have a leading '/', the complete boot file
# path will be formed by concatenating the 'bf' field onto the 'hd'
# field. If a leading '/' does exist, the 'bf' field will be treated
# as an absolute path. If the resultant file path does not exist,
# an empty path, "", will be returned.
#
#       if "hd=/tftpboot:bf=XP10/os" then path = /tftpboot/XP10/os
#
#       if "hd=/tftpboot:bf=/usr/XP10/os" then path = /usr/XP10/os
#

portland: tc=subnet60: ht=ethernet: ha=080011010045:\
	ip=128.07.60.30: bf=/tftpboot/XP10/os

corvallis: tc=subnet60: ht=ethernet: ha=080011010046:\
	ip=128.07.60.31: bf=/tftpboot/XP10/os

astoria: tc=subnet60: ht=ethernet: ha=080011010047:\
	ip=128.07.60.32: bf=/tftpboot/XP330/os

# When secure tftp is used, file requests to tftp will be looked for
# in the tftp's 'secure' directory. This is a problem with most bootp
# implementations. Bootp creates a path using the 'hd' and 'bf' fields
# and checks to see if a file exists at that location. If a requester 
# uses that path to down load a file via tftp, it will fail because
# tftp will prepend the 'secure' directory onto the requested file path. 
# However, the implementation included on the Tektronix Utility tape, 
# for use with XP series X-terminals, includes a switch to enable bootp 
# to be used in a tftp-secure environment.
#
#	-r 	this switch will allow bootp to use the full path
#		to determine if a file exists but will strip off
#		the 'hd' portion of the path and send only the 'bf'
#		portion. When the file specified by 'bf' is used 
#		in a tftp request, tftp will prepend the secure
#		directory and, if 'hd' is the same as the 'secure'
#		directory, the tftp should find and transport the file.  
#
#	if "hd=/secure:bf=/XP10/os", bootp will ensure that the
#	file, /secure/XP10/os, exists, but the -r switch will cause
#	bootpd to send only /XP10/os to the device making the 
#	bootp request. 
