Update pxeboot(8) manual page to reflect the next-server change in the ISC DHCP v3 server.

PR:		123484
Submitted by:	edwin@mavetju.org
Reviewed by:	AllanJude
MFC after:	1 week
This commit is contained in:
Guangyuan Yang 2018-11-25 09:37:57 +00:00
parent ee73fef96e
commit 2dfc267231

View File

@ -58,7 +58,7 @@ The
.Nm .Nm
binary is loaded just like any other boot file, binary is loaded just like any other boot file,
by specifying it in the DHCP server's configuration file. by specifying it in the DHCP server's configuration file.
Below is a sample configuration for the ISC DHCP v2 server: Below is a sample configuration for the ISC DHCP v3 server:
.Bd -literal -offset indent .Bd -literal -offset indent
option domain-name "example.com"; option domain-name "example.com";
option routers 10.0.0.1; option routers 10.0.0.1;
@ -67,6 +67,7 @@ option broadcast-address 10.0.0.255;
option domain-name-servers 10.0.0.1; option domain-name-servers 10.0.0.1;
server-name "DHCPserver"; server-name "DHCPserver";
server-identifier 10.0.0.1; server-identifier 10.0.0.1;
next-server 10.0.0.1;
default-lease-time 120; default-lease-time 120;
max-lease-time 120; max-lease-time 120;
@ -80,10 +81,11 @@ subnet 10.0.0.0 netmask 255.255.255.0 {
} }
.Ed .Ed
.Va next-server
is the IP address of the next server in the bootstrap process, i.e.
your TFTP server or NFS server.
.Nm .Nm
recognizes recognizes
.Va next-server
and
.Va option root-path .Va option root-path
directives as the server and path to NFS mount for file requests, directives as the server and path to NFS mount for file requests,
respectively, or the server to make TFTP requests to. respectively, or the server to make TFTP requests to.