similar to: Baking Cookies

Hmm... well adding the __export stopped the "undefined symbol" error from showing up when I add "SENDCOOKIES" in the config, however I'm still not seeing any cookies being sent to my webserver. Any ideas on how to further debug? (if you want to send me the debug compile options privately that's okay too) -----Original Message----- From: H. Peter Anvin [mailto:hpa at

FYI -- Did some more digging. These two changes lets SENDCOOKIES behavior work as desired/intended. --- syslinux-6.02/com32/include/syslinux/pxe_api.h 2013-10-13 13:59:03.000000000 -0400 +++ syslinux-6.02-changed/com32/include/syslinux/pxe_api.h 2013-11-21 17:00:57.379519000 -0500 @@ -589,7 +589,7 @@ void __weak unload_pxe(uint16_t flags); uint32_t __weak dns_resolv(const char *);

On 11/20/2013 01:11 PM, Santillanes, Russel wrote: > I think my oven is broken, but maybe I have the recipe wrong. > > I've been trying to utilize the lwIP stack and dmi information to avoid iPXE use. I can do a SYSAPPEND 0x00080 and it shows up in /proc/cmdline after booting the kernel, but tcpdump is not revealing the cookies as described during HTTP calls in the documentation.

The following is the current change-log for Syslinux 6.03. The final stable version might include additional items. Before the final release, it would be helpful to receive feedback about: _ Any item that should be added or eliminated. _ Any item that should be edited in any way (rewording, technical details...). _ Any item that should not be included. _ Any credit that should be added /

The following changes since commit 02c28ea889fde01c857f004d257cb69015ce69a2: Matt Fleming (1): NEWS: Mention noteworthy changes in 5.10 are available in the git repository at: git://github.com/geneC/syslinux.git doc-for-mfleming Gene Cumm (12): Fix SERIAL directive in docs doc/syslinux.txt: grammar txt/syslinux.cfg.txt: Add SYSAPPEND txt/syslinux.cfg.txt: Add

Hi everyone, I have released Syslinux 6.03. It is by and large identical to 6.03-pre20. I would like to do a short cycle for 6.04, because 64-bit support for ext4 has come up as a very high priority. Therefore I do not want to stuff too many things into the 6.04 release but hold them for 6.05. Thanks to Ady for most of the changelog. Changes in 6.03: * chain: Fix chainloading on 6.02

OK, 6.01 is now out. The main intention of this release was to fix the terrible bug in Syslinux 6.00 which made it impossible to boot kernels from BIOS. This resulted in a way shorter than usual release cycle, and it does mean that there are some bugs that have been reported that haven't yet been fixed. Shortlog appended below. Thanks to everyone who helped test things out. --- Gene Cumm

Hi, Adam Williamson > I think it would be better if someone else confirms there's actually > something to fix. There was indeed the shortcomming that byte values 128 to 255 were treated as whitespace and mapped to "_" resp. "". This would affect non-ASCII characters of UTF-8 or old ISO-8859. But the reason why gcc 5 made a difference to gcc 4.9 is not found yet.

The following is a first attempt to list the current change log for Syslinux 6.03. The final stable version, whenever it will be released, might include additional items. I would appreciate feedback regarding: _ Any item that should be added. _ Any item that should be edited in any way. _ Any item that should not be included. _ Any credit that should be added or corrected. _ Any wrong or

Filesystem UUID shows the partition we boot kernel from. The kernel parameter has format like FSUUID=DA1A-0B2E. The SYSAPPEND bit is 0x40000. Now the FAT only supports FSUUID. The patch is based on 67aaaeeb228. Signed-off-by: Serj Kalichev <serj.kalichev at gmail.com> --- com32/include/syslinux/sysappend.h | 1 + core/fs/btrfs/btrfs.c | 3 ++- core/fs/ext2/ext2.c

core and the simple menu do not interpret the IPAPPEND/SYSAPPEND directives in the same way. Which is the proper way? Either way, this should be clarified in the documentation. com32/elflink/ldlinux/readconfig.c: } else if ((ep = looking_at(p, "ipappend")) || (ep = looking_at(p, "sysappend"))) { uint32_t s = strtoul(skipspace(ep), NULL,

With the release of 6.03 on October 6th. but page still shows latest as 2013-10-13 : Syslinux 6.02 released. http://www.syslinux.org/wiki/index.php/The_Syslinux_Project On 6 Oct 2014 at 9:35, H. Peter Anvin wrote: Date sent: Mon, 06 Oct 2014 09:35:19 -0700 From: "H. Peter Anvin" <hpa at zytor.com> To: For discussion of Syslinux and tftp-hpa

On Sun, Jun 23, 2013 at 11:09 PM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Sun, Jun 23, 2013 at 11:06 PM, Gene Cumm <gene.cumm at gmail.com> wrote: >> core and the simple menu do not interpret the IPAPPEND/SYSAPPEND >> directives in the same way. Which is the proper way? Either way, >> this should be clarified in the documentation. > > To be clear:

> Let me know what kind of info would be useful for debugging the > mboot issue, and I will collect it all. Also, EFI is still somewhat > new to me, so I don't know how to find the UEFI firmware revision > or UEFI extension agents. I'll see if it's in the server manual, > but if you have an idea how one typically finds those, I'd appreciate > any pointers. >

On 06/13/2013 10:15 PM, Gene Cumm wrote: > On Thu, Jun 13, 2013 at 8:08 PM, Gerardo Exequiel Pozzi > <vmlinuz386 at yahoo.com.ar> wrote: >> Hello >> >> While testing PXE booting, I decided to change IPAPPEND to the new >> SYSAPPEND and does not work: nothing is appended to command line. >> >> I tested using menu.c32 and vesamenu.c32, same issue.

On Sun, Jun 23, 2013 at 3:16 PM, Gerardo Exequiel Pozzi <vmlinuz386 at yahoo.com.ar> wrote: > I guess the bug is here (com32/menu/readconfig.c) > > 910 } else if (looking_at(p, "ipappend") || looking_at(p, > "sysappend")) { > 911 if (ld.label) > 912 ld.ipappend = atoi(skipspace(p + 8)); > 913

Hello While testing PXE booting, I decided to change IPAPPEND to the new SYSAPPEND and does not work: nothing is appended to command line. I tested using menu.c32 and vesamenu.c32, same issue. --------------------------------------------------------------------- SERIAL 0 38400 UI boot/syslinux/vesamenu.c32 LABEL arch64_nbd MENU LABEL Boot Arch Linux (x86_64) (NBD) LINUX boot/x86_64/vmlinuz

The following changes since commit 4ff8fcac8e7b5046987dee15592ab510ab343aa8: Matt Fleming (1): Merge branch 'menu-ipappend-1-for-mfleming' of git://github.com/geneC/syslinux into elflink are available in the git repository at: git://github.com/geneC/syslinux.git ipappend-fix-for-mfleming Gene Cumm (2): core & menu: fix IPAPPEND/SYSAPPEND conversion doc/ &

Hi, poma wrote: > - "unsigned char c;" does not solve the problem > > - "c >= 0 && c <= ' '" solves the problem for the current git What the ... ?!? My proposal of "(c >= 0 ... )" was only made to avoid the need for a type change of variable "c". Both proposals should be equivalent ... on the first morning glimpse they

To remind you once again. ISOLINUX >= 6.00 built with GCC >= 5.0.0 causes a broken boot. This relates specifically to the use of the vesamenu.c32, menu.c32 works without problemos. This "code" is already in 6.03, therefore this is not a fix for it! Revert "SYSAPPEND: Fix space stripping" This reverts commit 3106dcd http://repo.or.cz/w/syslinux.git/commit/3106dcd Fixes