| blob | e6d9c51e68db7a1c0a71a09e88c7aff5dedf2ef9 |
4 <head>
9 /* Shared CSS for AsciiDoc xhtml11 and html5 backends */
11 /* Default font. */
12 body {
14 }
16 /* Title font. */
24 }
26 body {
28 }
30 a {
33 }
36 }
38 em {
41 }
43 strong {
46 }
53 }
57 }
58 h2 {
60 }
61 h3 {
63 }
64 h3 + * {
66 }
67 h5 {
69 }
73 }
75 hr {
77 }
79 p {
82 }
86 }
96 }
103 }
105 }
107 }
114 }
118 }
122 }
127 }
133 }
139 }
143 }
145 /* Block element titles. */
152 }
155 }
159 }
162 }
165 }
172 }
179 }
187 }
192 }
197 }
201 }
202 /* DEPRECATED: Pre version 8.2.7 verse style literal block. */
205 }
214 }
218 }
223 }
229 dl {
232 }
233 dt {
238 }
241 }
245 }
248 }
251 }
254 }
257 }
260 }
267 }
269 tfoot {
271 }
274 }
279 }
282 }
285 }
291 }
294 }
298 }
302 }
306 }
310 }
315 }
319 }
329 }
335 }
338 }
342 }
346 }
354 }
359 }
363 }
367 }
371 }
417 /*
418 * xhtml11 specific
419 *
420 * */
425 }
428 }
432 }
435 }
436 /* Because the table frame attribute is overriden by CSS in most browsers. */
439 }
443 }
447 }
450 /*
451 * html5 specific
452 *
453 * */
458 }
462 }
465 }
472 }
478 }
483 }
487 }
490 }
494 }
497 }
500 }
504 }
507 }
510 }
513 /*
514 * manpage specific
515 *
516 * */
523 }
526 }
529 }
533 }
536 </style>
538 /*<![CDATA[*/
541 /////////////////////////////////////////////////////////////////////
542 // Table Of Contents generator
543 /////////////////////////////////////////////////////////////////////
545 /* Author: Mihai Bazon, September 2002
546 * http://students.infoiasi.ro/~mishoo
547 *
548 * Table Of Content generator
549 * Version: 0.4
550 *
551 * Feel free to use this script under the terms of the GNU General Public
552 * License, as long as you do not remove or alter this notice.
553 */
555 /* modified by Troy D. Hanson, September 2006. License: GPL */
556 /* modified by Stuart Rackham, 2006, 2009. License: GPL */
558 // toclevels = 1..4.
568 }
570 }
576 }
581 // Function that scans the DOM tree for header elements (the DOM2
582 // nodeIterator API would be a better technique but not supported by all
583 // browsers).
590 }
592 }
593 }
594 }
597 }
602 }
604 // Delete existing TOC entries in case we're reloading the TOC.
613 }
616 }
618 // Rebuild TOC entries.
631 }
634 },
637 /////////////////////////////////////////////////////////////////////
638 // Footnotes generator
639 /////////////////////////////////////////////////////////////////////
641 /* Based on footnote generation code from:
642 * http://www.brandspankingnew.net/archive/2005/07/format_footnote.html
643 */
646 // Delete existing footnote entries in case we're reloading the footnodes.
651 }
657 }
660 }
662 // Rebuild footnote entries.
669 n++;
672 // Use [\s\S] in place of . so multi-line matches work.
673 // Because JavaScript has no s (dotall) regex flag.
679 }
686 }
687 }
691 // Process footnoterefs.
700 }
701 }
702 }
703 },
712 }
713 }
718 }
723 else
725 }
727 }
729 /*]]>*/
730 </script>
731 </head>
734 <h1>
735 pxelinux(1) Manual Page
736 </h1>
739 <p>pxelinux -
740 The Syslinux derivative PXELINUX for PXE network booting
741 </p>
742 </div>
743 </div>
751 </div></div>
752 </div>
753 </div>
757 <div class="paragraph"><p><strong>PXELINUX</strong> is a Syslinux derivative, for booting Linux off a network
758 server, using a network ROM conforming to the Intel PXE (Pre-Execution
760 intended to be flashed or burned into a PROM on the network card; if
761 you want that, check out Etherboot (<a href="http://www.etherboot.org/">http://www.etherboot.org/</a>).
762 Etherboot 5.4 or later can also be used to create a PXE-compliant boot
763 PROM for many network cards.</p></div>
764 <div class="paragraph"><p>PXELINUX generally requires that full file pathnames are 127 characters or shorter in length.</p></div>
765 </div>
766 </div>
771 option 210 (pxelinux.pathprefix), the hardcoded path-prefix or the
772 parent directory of the PXELINUX file, as indicated by DHCP fields
776 <div class="paragraph"><p>All unqualified filenames are relative to the current directory.</p></div>
777 </div>
778 </div>
782 <div class="paragraph"><p>See <strong>syslinux.cfg</strong>(5) for the format of the contents.</p></div>
784 configuration file name depends on the IP address of the booting
785 machine. After attempting the file as specified in the DHCP or
786 hardcoded options, PXELINUX will probe the following paths, prefixed
789 <li>
790 <p>
791 The client UUID if provided by the PXE stack (note, some BIOSes don’t
793 This is in the standard UUID format using lower case hexadecimal digits,
795 </p>
796 </li>
797 <li>
798 <p>
799 The hardware type (using its ARP type code) and address, all in lower
800 case hexadecimal with dash separators; for example, for an Ethernet (ARP
803 </p>
804 </li>
805 <li>
806 <p>
809 hexadecimal IP address for any host.) followed by removing characters,
810 one at a time, from the end.
811 </p>
812 </li>
813 <li>
814 <p>
815 "default"
816 </p>
817 </li>
818 </ul></div>
819 <div class="paragraph"><p>Starting in release 3.20, if PXELINUX can not find a configuration file,
820 it will reboot after the timeout interval has expired. This keeps a
821 machine from getting stuck indefinitely due to a boot server failure.</p></div>
822 </div>
823 </div>
827 <div class="paragraph"><p><strong>PXELINUX</strong> (starting with version 1.62) supports the following
828 nonstandard DHCP options, which depending on your DHCP server you may be
830 5071 for some additional information about these options. Options for
832 binary.</p></div>
835 <div class="paragraph"><p>Hardcoded after-options are applied after DHCP options (and overrride)
836 while hardcoded before-options are applied prior to DHCP options and
837 default behavior takes the lowest priority.</p></div>
838 </div>
844 </dt>
845 <dd>
846 <p>
850 longer required.
851 </p>
852 </dd>
855 </dt>
856 <dd>
857 <p>
859 qualified or unqualified.
860 </p>
861 </dd>
864 </dt>
865 <dd>
866 <p>
868 the boot file name. This almost certainly needs to end in whatever
869 character the TFTP server OS uses as a pathname separator, e.g. slash
870 (/) for Unix.
871 </p>
872 </dd>
875 </dt>
876 <dd>
877 <p>
878 Specifies, in seconds, the time to wait before reboot in the event of
880 approximately 136 years.)
881 </p>
882 </dd>
883 </dl></div>
884 </div>
888 hard-code DHCP options into the pxelinux.0 image file; this is
889 sometimes useful when the DHCP server is under different
890 administrative control. Hardcoded options</p></div>
899 </div></div>
900 </div>
901 </div>
902 </div>
907 supports HTTP and FTP transfers, greatly increasing load speed and
908 allowing for standard HTTP scripts to present PXELINUX’s configuration
909 file. To use http or ftp, use standard URL syntax as filename; use the
910 DHCP options below to transmit a suitable URL prefix to the client, or
911 use the "pxelinux-options" tool provided in the utils directory to
913 </div>
914 </div>
918 <div class="paragraph"><p>PXELINUX supports the following special pathname conventions:</p></div>
922 </dt>
923 <dd>
924 <p>
925 Suppresses the common filename prefix, i.e. passes the string "filename"
926 unmodified to the server.
927 </p>
928 </dd>
931 </dt>
932 <dd>
933 <p>
934 Suppresses the common filename prefix, <strong>and</strong> sends a request to an alternate TFTP server. Instead of an IP address, a DNS name can be used. It will be assumed to be fully qualified if it contains dots; otherwise the local domain as reported by the DHCP server (option 15) will be added.
935 </p>
936 </dd>
937 </dl></div>
938 <div class="paragraph"><p>:: was chosen because it is unlikely to conflict with operating system
939 usage. However, if you happen to have an environment for which the
940 special treatment of :: is a problem, please contact the Syslinux
941 mailing list.</p></div>
942 <div class="paragraph"><p>Since version 4.00, PXELINUX also supports standard URL syntax.</p></div>
943 </div>
944 </div>
948 <div class="paragraph"><p>Normally, PXELINUX will unload the PXE and UNDI stacks before invoking
949 the kernel. In special circumstances (for example, when using MEMDISK
950 to boot an operating system with an UNDI network driver) it might be
951 desirable to keep the PXE stack in memory. If the option "keeppxe"
952 is given on the kernel command line, PXELINUX will keep the PXE and
953 UNDI stacks in memory. (If you don’t know what this means, you
955 </div>
956 </div>
962 <div class="paragraph"><p>For DHCP siaddr 192.168.2.3, file <em>mybootdir/pxelinux.0</em>, client UUID
965 this order will be attempted (after config-file options):</p></div>
970 mybootdir/pxelinux.cfg/C0A8025B
971 mybootdir/pxelinux.cfg/C0A8025
972 mybootdir/pxelinux.cfg/C0A802
973 mybootdir/pxelinux.cfg/C0A80
974 mybootdir/pxelinux.cfg/C0A8
975 mybootdir/pxelinux.cfg/C0A
976 mybootdir/pxelinux.cfg/C0
977 mybootdir/pxelinux.cfg/C
978 mybootdir/pxelinux.cfg/default</code></pre>
979 </div></div>
980 </div>
985 options, is available at:</p></div>
988 <pre><code>http://www.kernel.org/pub/software/network/tftp/
989 ftp://www.kernel.org/pub/software/network/tftp/</code></pre>
990 </div></div>
991 <div class="paragraph"><p>and on any kernel.org mirror (see <a href="http://www.kernel.org/mirrors/">http://www.kernel.org/mirrors/</a>).</p></div>
993 Lefebvre:</p></div>
997 </div></div>
998 <div class="paragraph"><p>If your boot server is running Windows (and you can’t fix that), try
999 tftpd32 by Philippe Jounin (you need version 2.11 or later; previous
1000 versions had a bug which made it incompatible with PXELINUX):</p></div>
1004 </div></div>
1005 </div>
1009 BOOTP. However, most PXE implementations — this includes all Intel
1012 support any very old or otherwise severely broken clients, this is
1013 probably the best configuration unless you already have a PXE boot
1014 server on your network.</p></div>
1016 would look something like the following, using ISC dhcp 2.0 dhcpd.conf
1017 syntax:</p></div>
1020 <pre><code>allow booting;
1021 allow bootp;
1023 # Standard configuration directives...
1025 option domain-name "<domain name>";
1031 # Group the PXE bootable hosts together
1032 group {
1033 # PXE-specific configuration directives...
1035 filename "/tftpboot/pxelinux.0";
1037 # You need an entry like this for every host
1038 # unless you're using dynamic addresses
1042 }
1043 }</code></pre>
1044 </div></div>
1046 will do this if you specify the -s (secure) option; this is highly
1047 recommended), you almost certainly should not include the /tftpboot
1048 prefix in the filename statement.</p></div>
1049 </div>
1052 <div class="paragraph"><p>If the simple config does not work for your environment, you probably
1054 free PXE boot server is available at:</p></div>
1055 <div class="paragraph"><p><a href="http://www.kano.org.uk/projects/pxe/">http://www.kano.org.uk/projects/pxe/</a></p></div>
1061 <pre><code>allow booting;
1062 allow bootp;
1064 # Standard configuration directives...
1066 option domain-name "<domain name>";
1072 # Group the PXE bootable hosts together
1073 group {
1074 # PXE-specific configuration directives...
1075 option dhcp-class-identifier "PXEClient";
1078 # You need an entry like this for every host
1079 # unless you're using dynamic addresses
1083 }
1084 }</code></pre>
1085 </div></div>
1087 </div>
1090 <div class="paragraph"><p>If the "conventional TFTP" configuration doesn’t work on your clients,
1091 and setting up a PXE boot server is not an option, you can attempt the
1092 following configuration. It has been known to boot some
1093 configurations correctly; however, there are no guarantees:</p></div>
1096 <pre><code>allow booting;
1097 allow bootp;
1099 # Standard configuration directives...
1101 option domain-name "<domain name>";
1107 # Group the PXE bootable hosts together
1108 group {
1109 # PXE-specific configuration directives...
1110 option dhcp-class-identifier "PXEClient";
1111 option vendor-encapsulated-options 09:0f:80:00:0c:4e:65:74:77:6f:72:6b:20:62:6f:6f:74:0a:07:00:50:72:6f:6d:70:74:06:01:02:08:03:80:00:00:47:04:80:00:00:00:ff;
1113 filename "/tftpboot/pxelinux.0";
1115 # You need an entry like this for every host
1116 # unless you're using dynamic addresses
1120 }
1121 }</code></pre>
1122 </div></div>
1123 <div class="paragraph"><p>Note that this <strong>will not</strong> boot some clients that <strong>will</strong> boot with the
1125 known to fall into this category.</p></div>
1126 </div>
1130 options; you can use the following syntax in dhcpd.conf if you are
1131 running this version of dhcpd:</p></div>
1134 <pre><code>option space pxelinux;
1135 option pxelinux.magic code 208 = string;
1136 option pxelinux.configfile code 209 = text;
1137 option pxelinux.pathprefix code 210 = text;
1139 </div></div>
1142 <pre><code>NOTE: In earlier versions of PXELINUX, this would only work as a
1145 (type 43 encapsulated.) This may avoid messing with the
1146 dhcp-parameter-request-list, as detailed below.</code></pre>
1147 </div></div>
1148 <div class="paragraph"><p>Then, inside your PXELINUX-booting group or class (whereever you have
1149 the PXELINUX-related options, such as the filename option), you can
1150 add, for example:</p></div>
1153 <pre><code># Always include the following lines for all PXELINUX clients
1154 site-option-space "pxelinux";
1156 if exists dhcp-parameter-request-list {
1157 # Always send the PXELINUX options (specified in hexadecimal)
1158 option dhcp-parameter-request-list = concat(option dhcp-parameter-request-list,d0,d1,d2,d3);
1159 }
1160 # These lines should be customized to your setup
1161 option pxelinux.configfile "configs/common";
1162 option pxelinux.pathprefix "/tftpboot/pxelinux/files/";
1163 option pxelinux.reboottime 30;
1165 </div></div>
1166 <div class="paragraph"><p>Note that the configfile is relative to the pathprefix: this will look
1167 for a config file called /tftpboot/pxelinux/files/configs/common on
1168 the TFTP server.</p></div>
1170 server to send the PXELINUX-specific options, even though they are not
1171 explicitly requested. Since the DHCP request is done before PXELINUX
1174 For example, to use the hexadecimal form of the hardware address as
1175 the configuration file name, you could do something like:</p></div>
1180 if exists dhcp-parameter-request-list {
1181 # Always send the PXELINUX options (specified in hexadecimal)
1182 option dhcp-parameter-request-list = concat(option dhcp-parameter-request-list,d0,d1,d2,d3);
1183 }
1184 option pxelinux.configfile =
1187 </div></div>
1191 </div>
1192 </div>
1193 </div>
1199 <li>
1200 <p>
1201 The error recovery routine doesn’t work quite right. For right now,
1202 it just does a hard reset - seems good enough.
1203 </p>
1204 </li>
1205 <li>
1206 <p>
1207 We should probably call the UDP receive function in the keyboard
1208 entry loop, so that we answer ARP requests.
1209 </p>
1210 </li>
1211 <li>
1212 <p>
1213 Boot sectors/disk images are not supported yet.
1214 </p>
1215 </li>
1216 </ul></div>
1218 list (see syslinux.txt for the address.)</p></div>
1222 varying degrees of severity. Please see:</p></div>
1226 </div></div>
1228 <li>
1229 <p>
1230 for a list of currently known hardware problems, with workarounds
1231 if known.
1232 </p>
1233 </li>
1234 </ol></div>
1236 gPXE project (formerly known as Etherboot) provides an open-source PXE
1237 stack that works with a number of cards, and which can be loaded from
1238 a CD-ROM, USB key, or floppy if desired.</p></div>
1243 </div></div>
1245 <li>
1246 <p>
1247 and ready-to-use ROM or disk images from:
1248 </p>
1252 </div></div>
1253 </li>
1254 </ol></div>
1256 works just barely well enough to load a single file, but doesn’t
1257 handle the more advanced items required by PXELINUX. If so, it is
1258 possible to use the built-in PXE stack to load gPXE, which can then
1259 load PXELINUX. See:</p></div>
1263 </div></div>
1264 </div>
1265 </div>
1266 </div>
1272 <div class="paragraph"><p>PXELINUX does not support MTFTP, and there are no plans of doing so, as
1274 MB) in size. It is of course possible to use MTFTP for the initial
1275 boot, if you have such a setup. MTFTP server setup is beyond the scope
1276 of this document.</p></div>
1277 </div>
1281 rather, if it has not received any input for approximately five
1282 minutes after displaying an error message, it will reset the machine.
1283 This allows an unattended machine to recover in case it had bad enough
1284 luck of trying to boot at the same time the TFTP server goes down.</p></div>
1285 </div>
1286 </div>
1287 </div>
1291 <div class="paragraph"><p><strong>syslinux.cfg</strong>(5), <strong>syslinux-cli</strong>(1), <strong>lilo</strong>(8), <strong>keytab-lilo.pl</strong>(8),
1292 <strong>fdisk</strong>(8), <strong>mkfs</strong>(8), <strong>superformat</strong>(1).</p></div>
1293 </div>
1294 </div>
1299 <strong>SYSLINUX</strong> documentation by H. Peter Anvin <<a href="mailto:hpa@zytor.com">hpa@zytor.com</a>>. The conversion
1300 to an AsciiDoc was made by Gene Cumm <<a href="mailto:gene.cumm@gmail.com">gene.cumm@gmail.com</a>></p></div>
1301 </div>
1302 </div>
1303 </div>
1308 </div>
1309 </div>
1310 </body>
1311 </html>