HP-UX Reference (11i v1 05/09) - 1M System Administration Commands A-M (vol 3)

b
bootpd(1M) bootpd(1M)
not accessible, the request is discarded; no reply is sent. If the client specifies a relative path
name, bootpd constructs a full path name by appending the relative path name to the value of
the hd tag, and tests to determine if the full path name is accessible. If the full path name is
accessible, it is returned in the boot reply packet; if not, the request is discarded.
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 con-
tains a zeroed-out bootfile field.
If the tftp pseudo-user 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 pseudo-user does not exist,
bootpd checks for the file
relative to
/.
For a file to be available, it must exist, and be publicly readable.
All file names are first tried as filename.hostname and then simply as filename. However, in
the case when the
tftp pseudo-user exists, but filename.hostname and filename are not acces-
sible under the
tftp home directly, only filename is checked relative to /.
Note that a file considered to be accessible relative to / might not actually be accessible via
tftp if the command line arguments to tftpd disallow that path.
bs=size
This tag specifies the size of the bootfile. The parameter size can be either a decimal, octal, or
hexadecimal integer specifying the size of the bootfile in 512-octet blocks, or the keyword
auto
,
which causes the server to automatically calculate the bootfile size at each request. Specifying
the
bs symbol as a boolean has the same effect as specifying auto as its value.
ci=client_ID
This tag specifies the client identifier of the client. The parameter client_ID can be either a hex-
adecimal integer, or a string contained in double quotes. The client_ID is a unique identifier that
the DHCP client may use to identify itself to the server. If present, the client identifier super-
sedes the hardware address, so a client and an entry will only match in one of two situations:
one, they both have the same client identifier, or two they both have the same hardware address
and neither has a client identifier. If a request has a client identifier, then that is used to match
the client up with an entry in the
bootp configuration file. One common client ID used is to
concatenate the hardware type (e.g. 0x01 for ethernet) with the hardware address.
cs=ip_address_list
This tag specifies the IP addresses of RFC865 Quote of the Day (cookie) servers.
dn=domain_name
This tag specifies the domain name of the client for Domain Name Server resolution (see
RFC1034).
ds=ip_address_list
This tag specifies the IP addresses of RFC1034 Domain Name servers.
ef=filename
Specifies the name of an extensions file. The file, retrievable via TFTP, contains information
which can be interpreted in the same way as the 64-octet vendor-extension field within the
BOOTP response. The maximum length of the file is unconstrained. All references to an exten-
sions filename within the file are ignored.
gw=ip_address_list
This tag specifies the IP addresses of gateways for the client’s subnet. If one of multiple gate-
ways is preferred, it should be listed first.
hd=home-directory
This tag specifies a directory name to which the bootfile is appended (see the bf tag above). The
default value of the hd tag is /.
hn The presence of this tag indicates that the client’s host name should be sent in the boot reply.
The hn tag is a boolean tag. bootpd attempts to send the entire host name as it is specified in
the configuration file or hosts database. The configuration file is checked first, if the host name
HP-UX 11i Version 1: September 2005 − 4 − Hewlett-Packard Company Section 1M−−109