Summary ====== I have a recommendation for a minor documentation change regarding 'keeppxe'. I lost some time on this and think that a clarification could save other people time in the future. pxelinux.doc should be tweaked to explicitly say that the "keeppxe" option should be given on the kernel command line through the APPEND statemen Detail ===== pxelinux.doc line 356 says: If the option "keeppxe" is given on the kernel command line, PXELINUX will keep the PXE and UNDI stacks in memory. I interpreted this to mean that 'keeppxe' should go after 'kernel' in my configuration file ... as in: INCORRECT EXAMPLE ----------------- label foo kernel memdisk keeppxe append initrd=/freedos/fd2880.img I then spent a few hours trying to figure out why things were not working. In fact, the 'keeppxe' needs to be added to the kernel command line as part of the 'append' statement, as in: CORRECT EXAMPLE --------------- label foo kernel memdisk append initrd=/freedos/fd2880.img keeppxe As with many things, in hindsight it was obvious. I recommend that pxelinux.doc be amended to explicitly say that the 'keeppxe' parameter gets added to the kernel command line using the APPEND directive ... something like: If the option "keeppxe" is passed to the kernel command line using the APPEND statement, PXELINUX will keep the PXE and UNDI stacks in memory. Miguel
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, Mar 02, 2006 at 09:40:56AM -0500, Miguel wrote:> Summary > ======> > I have a recommendation for a minor documentation change regarding 'keeppxe'. > > I lost some time on this and think that a clarification could save other > people time in the future. > > pxelinux.doc should be tweaked to explicitly say that the "keeppxe" option > should be given on the kernel command line through the APPEND statemen ><snip/>> > I recommend that pxelinux.doc be amended to explicitly say that the > 'keeppxe' parameter gets added to the kernel command line using the APPEND > directive ... something like: > > If the option "keeppxe" is passed to the kernel command line using the > APPEND statement, PXELINUX will keep the PXE and UNDI stacks in memory.Okay, thank you. I have it reworded in this diff --git a/pxelinux.doc b/pxelinux.doc index b863f95..9e41420 100644 - --- a/pxelinux.doc +++ b/pxelinux.doc @@ -354,9 +354,9 @@ Normally, PXELINUX will unload the PXE a the kernel. In special circumstances (for example, when using MEMDISK to boot an operating system with an UNDI network driver) it might be desirable to keep the PXE stack in memory. If the option "keeppxe" - -is given on the kernel command line, PXELINUX will keep the PXE and - -UNDI stacks in memory. (If you don't know what this means, you - -probably don't need it.) +is given on the kernel command line, using the APPEND statement, +PXELINUX will keep the PXE and UNDI stacks in memory. (If you don't know +what this means, you probably don't need it.) ++++ CURRENTLY KNOWN PROBLEMS ++++> MiguelHtH GSt -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFEBxEqOSINbgwa/7sRAmosAKCalGz/mKC0muONVOwUi6IHHD+CmACfcvRl f89R+MgOFqFCFyFmUnUnJ2c=ggv+ -----END PGP SIGNATURE-----
----- Forwarded message from Miguel <mth at mth.com> ----- From: Miguel <mth at mth.com> To: Geert Stappers <stappers at stappers.nl> Subject: Re: [syslinux] keeppxe - documentation recommendation Date: Fri, 3 Mar 2006 08:42:12 -0500 (EST) User-Agent: SquirrelMail/1.4.6 [CVS]-0.cvs20050812.1.fc4> Okay, thank you. I have it reworded in this > diff --git a/pxelinux.doc b/pxelinux.docThank you. Miguel ----- End forwarded message ----- Now it is back on the mailinglist