View | Details | Raw Unified | Return to bug 123484
Collapse All | Expand All

(-)pxeboot.8 (-3 / +5 lines)
Lines 55-61 Link Here
55
.Nm
55
.Nm
56
binary is loaded just like any other boot file,
56
binary is loaded just like any other boot file,
57
by specifying it in the DHCP server's configuration file.
57
by specifying it in the DHCP server's configuration file.
58
Below is a sample configuration for the ISC DHCP v2 server:
58
Below is a sample configuration for the ISC DHCP v3 server:
59
.Bd -literal -offset indent
59
.Bd -literal -offset indent
60
option domain-name "example.com";
60
option domain-name "example.com";
61
option routers 10.0.0.1;
61
option routers 10.0.0.1;
Lines 64-69 Link Here
64
option domain-name-servers 10.0.0.1;
64
option domain-name-servers 10.0.0.1;
65
server-name "DHCPserver";
65
server-name "DHCPserver";
66
server-identifier 10.0.0.1;
66
server-identifier 10.0.0.1;
67
next-server 10.0.0.1;
67
68
68
default-lease-time 120;
69
default-lease-time 120;
69
max-lease-time 120;
70
max-lease-time 120;
Lines 74-83 Link Here
74
}
75
}
75
76
76
.Ed
77
.Ed
78
.Va next-server
79
is the IP address of the next server in the bootstrap process, i.e.
80
your TFTP server or NFS server.
77
.Nm
81
.Nm
78
recognizes
82
recognizes
79
.Va next-server
80
and
81
.Va option root-path
83
.Va option root-path
82
directives as the server and path to NFS mount for file requests,
84
directives as the server and path to NFS mount for file requests,
83
respectively, or the server to make TFTP requests to.
85
respectively, or the server to make TFTP requests to.

Return to bug 123484