search for: sysappend

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...

...fect 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 question why poma's observations are not reproducible for you needs an answer, too. Your observations could match e.g. a trailing garbage byte which gcc 5 causes in SYSAPPEND strings and which gets dropped by the now functional whitespace converter. Hopefully some byte in the range of 1 to 31. poma's observations would be explainable if on his system a byte in the range of 128 to 255 in one of the SYSAPPEND strings has to survive. (But why did "unsigned char c...

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 | 1 + core/fs/fat/f...

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: core treats the value as always hexidecimal while simple > menu treats it as decimal unless a 0x prefix is present. Correction: simple menu...

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. >> >> --------------------------------------------------------------------- >> SERIAL 0 38400 >> UI boot/syslinux/vesamenu.c32 >> >> &g...

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 else > 914 ipappend = atoi(skipspace(p + 8)); > > since the length of "sysappend" (9) differs from "ipappend"...

Hello, The description of SYSAPPEND for the DMI information states that the spaces are replaced by underscores, but this replacement does not occur in 6.03. There's small bug present in triplicata in com32/elflink/ldlinux/readconfig.c:copy_sysappend_string(), com32/menu/readconfig.c:copy_sysappend_string(), and core/sysappend.c:c...

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/...

...Pozzi wrote: > 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. >>> >>> --------------------------------------------------------------------- >>> SERIAL 0 38400 >>> UI boot/syslinux/vesamenu....

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: core treats the value as always hexidecimal while simple menu treats it as decimal unless a 0x prefix is present. > com32/elflink/ldlinux/readconfig.c: >...

...wing changes since commit 022cdd1d56512e8759e8374c10a7420201db93c0: Matt Fleming (1): cli: don't disable linewrap when redrawing the cmdline are available in the git repository at: git://github.com/geneC/syslinux.git menu-ipappend-1-for-mfleming Gene Cumm (1): menu.c32: Fix SYSAPPEND com32/menu/readconfig.c | 8 +++++--- 1 files changed, 5 insertions(+), 3 deletions(-)

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. Trying the magic "SENDCOOKIES" parameter outside of an inline SYSAPPEND call just gives me an "Error: An undefined symbol...

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. > > --------------------------------------------------------------------- > SERIAL 0 38400 > UI boot/syslinux/vesamenu.c32 > > > LABEL arch64_nbd > MENU LA...

...n, at 11:21:45PM, Gene Cumm wrote: > Correction: simple menu always does decimal (as should be expected). > > >> com32/elflink/ldlinux/readconfig.c: > >> } else if ((ep = looking_at(p, "ipappend")) || > >> (ep = looking_at(p, "sysappend"))) { > >> uint32_t s = strtoul(skipspace(ep), NULL, 16); > >> if (ld.label) > >> ld.ipappend = s; > >> else > >> SysAppends = s; This looks incorrect to me, and is likely a regre...

...mail.com> wrote: > 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 else >> 914 ipappend = atoi(skipspace(p + 8)); >> >> since the length of "sysappend" (9) differs f...

...rwan Velu has updated the hdt code recently, some of it for DMI. For these updates to be effective, it needs to be re-built from current git HEAD together with the core module, the library modules and the bootloader. Whether it would then work correctly (under UEFI), I do not know. _ Using the SYSAPPEND directive in the Syslinux configuration file (hint: then check the resulting generated Syslinux cookie for the relevant client system, or run 'cat /proc/cmdline' in the booted system). If the server boots with Syslinux, this method would apply to it too. A possible SYSAPPEND statement...

....com/show_bug.cgi?id=1234653#c9 4.9.2-5.fc22. I got about the same one. Debian 4.9.2-10. Anybody can give me hints how to install gcc 5 as alternative compiler on a Debian 8.1 ? (I am still learning about my new system.) To poma: There must be a character between 128 and 255 (-128 to -1) in the SYSAPPEND strings which needs the "c >= 0" term to survive. Any idea what it could be in the light of the list in com32/include/syslinux/sysappend.h ? To all: Any idea how to inspect those strings while booting or while an operating system is up ? Have a nice day :) Thomas

...b510ab343aa8: 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/ & txt/: Document IPAPPEND/SYSAPPEND format com32/elflink/ldlinux/readconfig.c | 2 +- com32/menu/readconfig.c | 2 +- doc/syslinux.txt | 3 ++- txt/syslinux.cfg.txt | 4 +++- 4 files changed, 7 insertions(+), 4 delet...

On 11/19/2013 04:30 AM, Serj Kalichev wrote: > 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> Nice. It would be good to get a patch for ext2 for this as well (the UUID of an ext2/3/4 filesystem is stored in the superblock, so...

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 broken boot via vesamenu.c32 for the current git - 5186539 2015-06-27 version 6.04 2015 built with gcc version 5.1.1 --- com32/elflink/ldlinux/readconfig.c | 2 +- com32/menu/readconfig.c...