blob: bd3a4fc0246f28a9b8216a456949747e435748d7 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
|
.\" bootpef.8
.Dd June 12, 1999
.Dt BOOTPEF 8
.Os
.Sh NAME
.Nm bootpef
.Nd BOOTP Extension File compiler
.Sh SYNOPSIS
.Nm bootpef
.Op Fl c Ar chdir
.Op Fl d Ar debug-level
.Op Fl f Ar config-file
.Op Ar client-name Op Ar ...
.Sh DESCRIPTION
.Nm
builds the
.Sy Extension Path
files described by
.Tn RFC 2132
(tag 18).
If any
.Ar client-name
arguments are specified, then
.Nm
compiles the extension files for only those clients.
.Pp
The options are as follows:
.Bl -tag -width Ds
.It Fl c Ar chdir-path
Sets the current directory used by
.Nm
while creating extension files.
This is useful when the
extension file names are specified as relative pathnames, and
.Nm
needs to use the same current directory as the TFTP server
(typically
.Pa /tftpboot ) .
.It Fl d Ar debug-level
Sets the
.Ar debug-level
variable that controls the amount of debugging messages generated.
For example,
.Fl d Ns 4
or
.Fl d No 4
will set the debugging level to 4.
.It Fl f Ar config-file
Sets the name of the config file that specifies the option
data to be sent to each client.
.El
.Sh SEE ALSO
.Xr bootpd 8 ,
.Xr tftpd 8
.Pp
.Bl -tag -width "RFC 2132" -compact
.It Tn RFC 951
Bootstrap Protocol (BOOTP),
.It RFC 2132
DHCP Options and BOOTP Vendor Extensions
.El
|
