Remove metion of the 'magic options.' Apparently PXE doesn't require the

special options on 0.99c (it mumbles something about 'PXE server not found'
but works anyway), and it won't work at all with PXE 2.0.

1 files changed, 1 insertions, 14 deletions

diff --git a/sys/boot/i386/pxeldr/pxeboot.8 b/sys/boot/i386/pxeldr/pxeboot.8
index 37aa5cf..198e775 100644
--- a/sys/boot/i386/pxeldr/pxeboot.8
+++ b/sys/boot/i386/pxeldr/pxeboot.8
@@ -53,9 +53,6 @@ The
 .Nm
 binary is loaded just like any other boot file,
 by specifying it in the DHCP server's configuration file.
-PXE, however,
-requires special
-DHCP options before it will recognize the server response.
 Below is a sample configuration for the ISC DHCP v2 server:
 .Bd -literal -offset indent
 option domain-name "example.com";
@@ -69,22 +66,12 @@ server-identifier 10.0.0.1;
 default-lease-time 120;
 max-lease-time 120;
 
-option vendor-encapsulated-options 01:04:00:00:00:00:ff;
-option dhcp-class-identifier "PXEClient";
-
 subnet 10.0.0.0 netmask 255.255.255.0 {
        filename "pxeboot";
        range 10.0.0.10 10.0.0.254;
 }
 
 .Ed
-The
-.Va vendor-encapsulated-options
-and
-.Va dhcp-class-identifier
-options are important to PXE;
-it will not recognize the DHCP server response otherwise.
-.Pp
 .Nm
 recognizes
 .Va next-server
@@ -127,4 +114,4 @@ was written by
 and
 .An Paul Saab Aq ps@freebsd.org .
 This manual page was written by
-.An Doug White Aq dwhite@freebsd.org .
\ No newline at end of file
+.An Doug White Aq dwhite@freebsd.org .