search for: sysappends

...dlinux/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; com32/menu/readconfig.c } else if ((ep = looking_at(p, "ipappend")) || (ep = looking_at(p, "sysappend"))) { if (ld.label) ld.ipappend = atoi(skipspace(ep)); else ipappend = atoi(skipspace(ep)); -- -Gene

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.

..., + .fs_uuid = NULL, }; diff --git a/core/include/core.h b/core/include/core.h index 127ac65..4af037e 100644 --- a/core/include/core.h +++ b/core/include/core.h @@ -81,6 +81,7 @@ extern void print_sysappend(void); extern const char *sysappend_strings[SYSAPPEND_MAX]; extern uint32_t SysAppends; extern void sysappend_set_uuid(const uint8_t *uuid); +extern void sysappend_set_fs_uuid(void); void __cdecl core_intcall(uint8_t, const com32sys_t *, com32sys_t *); void __cdecl core_farcall(uint32_t, const com32sys_t *, com32sys_t *); diff --git a/core/include/fs.h b/core/include/fs.h index...

...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; >> >> com32/menu/readconfig.c >> } else if ((ep = looking_at(p, "ipappend")) || (ep = >> looking_at(p, "sysappend"))) { >> if (ld.label) >> ld.ipappend = atoi(skipspace(ep)); >> else &...

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, 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:copy_and_mangle() prevent proper replacement of spaces by

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

On 06/13/2013 11:06 PM, Gerardo Exequiel 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

...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; > > com32/menu/readconfig.c > } else if ((ep = looking_at(p, "ipappend")) || (ep = > looking_at(p, "sysappend"))) { > if (ld.label) > ld.ipappend = atoi(skipspace(ep)); > else > ipappend...

The following 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

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

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

...| > >> (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 regression in the 5.x code. It appears as though the 4.x parser treated the ipappend string as decimal. Peter, does this look incorrect to you too? The com32/menu code gets this right. -- Matt Fleming, Intel Open Source Technology Center

On Sun, Jun 23, 2013 at 8:24 PM, Gene Cumm <gene.cumm at gmail.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

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

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

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

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

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