similar to: [5.11-pre1] SYSAPPEND does not work (IPAPPEND alias works)

Displaying 20 results from an estimated 400 matches similar to: "[5.11-pre1] SYSAPPEND does not work (IPAPPEND alias works)"

2013 Jun 14
2
[5.11-pre1] SYSAPPEND does not work (IPAPPEND alias works)
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.
2013 Jun 23
0
[5.11-pre1] SYSAPPEND does not work (IPAPPEND alias works)
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
2013 Jun 14
0
[5.11-pre1] SYSAPPEND does not work (IPAPPEND alias works)
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. > > ---------------------------------------------------------------------
2013 Feb 01
2
5.01 BOOT_IMAGE= is missing in cmdline but path appears two times
Hello Booting with 4.06 cmdline looks like: # cat /proc/cmdline archisobasedir=arch archisolabel=ARCH_201301 initrd=boot/i686/archiso.img console=ttyS0 BOOT_IMAGE=boot/i686/vmlinuz while using 5.01: # cat /proc/cmdline boot/i686/vmlinuz boot/i686/vmlinuz archisobasedir=arch archisolabel=ARCH_201302 initrd=boot/i686/archiso.img console=ttyS0 And this cause some issues for cmdline parsing, I
2013 Jun 24
2
[bug] Syslinux-5.11-pre2: IPAPPEND/SYSAPPEND inconsistent base
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,
2013 Jun 24
2
[bug] Syslinux-5.11-pre2: IPAPPEND/SYSAPPEND inconsistent base
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:
2013 Jun 24
2
[5.11-pre1] SYSAPPEND does not work (IPAPPEND alias works)
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
2013 Jun 24
0
[bug] Syslinux-5.11-pre2: IPAPPEND/SYSAPPEND inconsistent base
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
2013 Jun 24
0
[5.11-pre1] SYSAPPEND does not work (IPAPPEND alias works)
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
2013 Jun 26
0
[bug] Syslinux-5.11-pre2: IPAPPEND/SYSAPPEND inconsistent base
On Sun, 23 Jun, 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),
2002 Aug 17
1
Pxelinux: File not found during boot, HELP
Hi, I am trying to boot the PXEclient via pxeserver and I am getting an error "file not found", following are me setup in the /tftpboot: /tftpboot: initrd.img linuz pxelinux.0 /tftpboot/pxelinux.cfg default (lower case) in the default file: # This is the default pxelinux config file. LABEL test KERNEL vmlinuz APPEND
2013 Jun 06
7
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
Hello, First, this setup works fine without any error in syslinux 4.06 as show below. For convenience, both versions of syslinux 4.06 [#1] and 5.10 [#2] directories (~2MB each) are uploaded ready for test. As said before, this is tested on qemu-1.5.0 + dnsmasq 2.66 in Arch Linux @ 64-bit. If more info is needed, please let me know. Good luck! Relevant directory structure is at
2005 Jun 03
4
Setting up a Pxe Server with udhcpc?
Hello, I am trying to setup a pxe server, I have a debian box with tftp-hda install, the image in place, and the pxeserver.0 in place. I have a router with udhcpc and I would like to use that as the DHCP server for the pxe server... I have been searching for some sort of document or hint as how to set this up, I could not find anything. Does any one know where a good document on this is located
2014 Nov 05
0
SYSAPPEND not replacing spaces
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
2013 Jun 24
2
[PATCH][git] Fix SYSAPPEND
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
2013 Nov 20
0
[PATCH] Add filesystem UUID to SYSAPPEND for FAT
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
2013 Nov 19
2
[PATCH] Add filesystem UUID to SYSAPPEND for FAT
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
2013 Jun 26
2
[PATCH][git] IPAPPEND: standardize and document
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/ &
2013 Jun 26
0
[PATCH][git] IPAPPEND: standardize and document
On Wed, 26 Jun, at 12:02:46PM, Gene Cumm wrote: > 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
2014 Dec 25
2
Chain-loading from WDS to PXELinux on a different tftp server
Hey guys, We are going with WDS to fire up first to get the benefits of targeted M$ deployments. If you have the "handle unknown computers" off on your M$ Distribution point, then you can still use regular WDS which runs next as a PXE filter (DLL linked into WDS) to fire off anything you want to including PXELinux. The stuff I was talking about before with PXELinux not working in