search for: whichsys

I wrote a new module "whichsys.c32" which detemines which command to execute, based on the Syslinux bootloader variant. In the near future it should/can be replaced by a lua script. But for people who want small binaries: whichsys.c32 is +/- eighty times smaller than lua.c32, atm. Usage: whichsys.c32 [-iso- command]...

With the latest 6.03pre I'm seeing an issue where no parameters are passed to the image executed via syslinux_run_command(). An example of this is whichsys.c32, which uses this. E.g., using an example from the wiki page - whichsys.c32 -iso- chain.c32 hd0 -sys- chain.c32 hd1 swap - results in a loop back to the isolinux menu as chain.c32 receives no parameters. Similarly, using -iso- memdisk initrd=/myimage.ima displays a memdisk error saying no No ram...

...eak. This is also broken at the boot: console prompt. Any commands executed at the boot: prompt also lose all parameters. > > > With the latest 6.03pre I'm seeing an issue where no parameters are passed to the image executed via syslinux_run_command(). > > An example of this is whichsys.c32, which uses this. E.g., using an example from the wiki page - whichsys.c32 -iso- chain.c32 hd0 -sys- chain.c32 hd1 swap - results in a loop back to the isolinux menu as chain.c32 receives no parameters. Similarly, using -iso- memdisk initrd=/myimage.ima displays a memdisk error saying no No ram...

...spot on, and I should have tested that scenario! I narrowed the issue down to a line in my config: ALLOWEDOPTIONS 0 The comment next to it in my config indicates this was added to disallow users dropping to the console with Escape or Tab, a restriction I would like to keep. BUT, when this is set whichsys fails to function in the manner I described. And similarly if I end up at the console prompt for any other reason and try to run something, no parameters make it through). Is this expected? Seems a bit odd. Thank you very much! --Ian > From: ady-sf at hotmail.com > To: syslinux at zytor.co...

> Pushed. Thank you for digging so deeply on this. > Gene, For the c32 modules to be able to use the keeppxe option, and considering that the issue in v.5.+ is that 'IS_PXELINUX' is/was dead code, is there any chance that the code in: com32/modules/whichsys.c would help? I mean, as a different way of detecting the Syslinux variant. In fact, the original idea of having the code in whichsys.c librarized is probably still relevant. TIA, Ady.

...zytor.com > Date: Tue, 29 Apr 2014 13:55:39 -0500 > Subject: [syslinux] Issues with syslinux_run_command(str) and parameters > > With the latest 6.03pre I'm seeing an issue where no parameters are passed to the image executed via syslinux_run_command(). > An example of this is whichsys.c32, which uses this. E.g., using an example from the wiki page - whichsys.c32 -iso- chain.c32 hd0 -sys- chain.c32 hd1 swap - results in a loop back to the isolinux menu as chain.c32 receives no parameters. Similarly, using -iso- memdisk initrd=/myimage.ima displays a memdisk error saying no No ram...

...he visible menu it is a possible solution. I originally assumed that this was due to that going down a different code path and did not mention it, apologies. The scale of my menu makes doubling/tripling menu entries less ideal, though. Do we consider it intended functionality that modules such as whichsys will not work under ALLOWOPTIONS 0? A strict reading of the wiki would allow for this, as the subsequently loaded module does not have parameters in an append label: http://www.syslinux.org/wiki/index.php/SYSLINUX#ALLOWOPTIONS_flag_val Naturally given my situation here, I think it would be ideal i...

...e: [syslinux] Issues with syslinux_run_command(str) and parameters > > I don't think that's it, but fair enough, try this sample config: > ************************************************# Test File: isolinux.cfg > default vesamenu.c32 > ALLOWOPTIONS 0 > LABEL Test kernel whichsys.c32 append -iso- memdisk initrd=fdboot.img -sys- initrd=fdboot.img > MENU END************************************************ > > I am using binaries from 6.03-pre11 from kernel.org. I used vesamenu.c32 and fdboot.img (FreeDOS) for the example but they are not required. > Accepting tha...

...ny of the following com32 modules without creating duplicate LABEL entries for each possible scenario. All of these modules use syslinux_run_cmd() so parameters on the command line will not be received: - gfxboot.c32- cmd.c32- lua.c32- ethersel.c32- ifcpu.c32- ifcpu64.c32- ifmemdsk.c32- ifplop.c32- whichsys.c32- rosh.c32 This doesn't feel like an intended restriction of ALLOWOPTIONS 0. --Ian > From: ady-sf at hotmail.com > To: syslinux at zytor.com > Date: Wed, 30 Apr 2014 05:06:55 +0300 > Subject: Re: [syslinux] Issues with syslinux_run_command(str) and parameters > > >...

...> I narrowed the issue down to a line in my config: > > > ALLOWEDOPTIONS 0 > > > The comment next to it in my config indicates this was added to > disallow users dropping to the console with Escape or Tab, a > restriction I would like to keep. BUT, when this is set whichsys > fails to function in the manner I described. And similarly if I end > up at the console prompt for any other reason and try to run > something, no parameters make it through). > > > Is this expected? Seems a bit odd.? > > Thank you very much! > > --Ian The di...

...itest.c32 elf.c32 linux.c32 reboot.c32 pmload.c32 \ > - meminfo.c32 sdi.c32 sanboot.c32 ifcpu64.c32 vesainfo.c32 \ > - kbdmap.c32 cmd.c32 vpdtest.c32 host.c32 ls.c32 gpxecmd.c32 \ > - ifcpu.c32 cpuid.c32 cat.c32 pwd.c32 ifplop.c32 zzjson.c32 \ > - whichsys.c32 prdhcp.c32 pxechn.c32 kontron_wdt.c32 ifmemdsk.c32 \ > - hexdump.c32 poweroff.c32 cptime.c32 debug.c32 > +# BIOS-specific modules > +MOD_BIOS = disk.c32 elf.c32 ethersel.c32 gpxecmd.c32 ifmemdsk.c32 ifplop.c32 \ > + kbdmap.c32 kontron_wdt.c32 pcitest.c32 pmload.c3...

I don't think that's it, but fair enough, try this sample config: ************************************************# Test File: isolinux.cfg default vesamenu.c32 ALLOWOPTIONS 0 LABEL Test kernel whichsys.c32 append -iso- memdisk initrd=fdboot.img -sys- initrd=fdboot.img MENU END************************************************ I am using binaries from 6.03-pre11 from kernel.org. I used vesamenu.c32 and fdboot.img (FreeDOS) for the example but they are not required. Accepting that this is a silly us...

...the following com32 modules without creating duplicate LABEL entries for each possible scenario. All of these modules use syslinux_run_cmd() so parameters on the command line will not be received: > - gfxboot.c32- cmd.c32- lua.c32- ethersel.c32- ifcpu.c32- ifcpu64.c32- ifmemdsk.c32- ifplop.c32- whichsys.c32- rosh.c32 > > > This doesn't feel like an intended restriction of ALLOWOPTIONS 0. > > --Ian > > > From: ady-sf at hotmail.com > > To: syslinux at zytor.com > > Date: Wed, 30 Apr 2014 05:06:55 +0300 > > Subject: Re: [syslinux] Issues with syslinu...

.../Makefile @@ -24,7 +24,8 @@ MODULES = config.c32 ethersel.c32 dmitest.c32 cpuidtest.c32 \ meminfo.c32 sdi.c32 sanboot.c32 ifcpu64.c32 vesainfo.c32 \ kbdmap.c32 cmd.c32 vpdtest.c32 host.c32 ls.c32 gpxecmd.c32 \ ifcpu.c32 cpuid.c32 cat.c32 pwd.c32 ifplop.c32 zzjson.c32 \ - whichsys.c32 prdhcp.c32 pxechn.c32 kontron_wdt.c32 ifmemdsk.c32 + whichsys.c32 prdhcp.c32 pxechn.c32 kontron_wdt.c32 ifmemdsk.c32 \ + nictype.c32 TESTFILES = diff --git a/com32/modules/nictype.c b/com32/modules/nictype.c new file mode 100644 index 0000000..b2a1c2a --- /dev/null +++ b/com32/modul...

...4,7 +24,7 @@ MODULES = config.c32 ethersel.c32 dmitest.c32 cpuidtest.c32 \ meminfo.c32 sdi.c32 sanboot.c32 ifcpu64.c32 vesainfo.c32 \ kbdmap.c32 cmd.c32 vpdtest.c32 host.c32 ls.c32 gpxecmd.c32 \ ifcpu.c32 cpuid.c32 cat.c32 pwd.c32 ifplop.c32 zzjson.c32 \ - whichsys.c32 pxechn.c32 + whichsys.c32 pxechn.c32 pxedump.c32 TESTFILES = diff --git a/com32/modules/pxedump.c b/com32/modules/pxedump.c new file mode 100644 index 0000000..478eba8 --- /dev/null +++ b/com32/modules/pxedump.c @@ -0,0 +1,241 @@ +/* -------------------------------------------------...

On Sun, Mar 05, 2017 at 05:39:42PM -0500, Gene Cumm wrote: > Adam, how about https://github.com/geneC/syslinux/compare/keeppxe ? I > changed to using strstr() and a uint16_t (to match the called > function) Hi Gene, Looks fine. Thanks. -- Adam

.... I > originally assumed that this was due to that going down a different > code path and did not mention it, apologies.?The scale of my menu > makes doubling/tripling menu entries less ideal, though.? > > > Do we consider it intended functionality that modules such as > whichsys will not work under ALLOWOPTIONS 0? A strict reading of the > wiki would allow for this, as the subsequently loaded module does not > have parameters in an append > label:?http://www.syslinux.org/wiki/index.php/SYSLINUX#ALLOWOPTIONS_fl > ag_val > > > Naturally given my sit...

.../Makefile @@ -24,7 +24,8 @@ MODULES = config.c32 ethersel.c32 dmitest.c32 cpuidtest.c32 \ meminfo.c32 sdi.c32 sanboot.c32 ifcpu64.c32 vesainfo.c32 \ kbdmap.c32 cmd.c32 vpdtest.c32 host.c32 ls.c32 gpxecmd.c32 \ ifcpu.c32 cpuid.c32 cat.c32 pwd.c32 ifplop.c32 zzjson.c32 \ - whichsys.c32 prdhcp.c32 pxechn.c32 kontron_wdt.c32 ifmemdsk.c32 + whichsys.c32 prdhcp.c32 pxechn.c32 kontron_wdt.c32 ifmemdsk.c32 \ + hexdump.c32 TESTFILES = diff --git a/com32/modules/hexdump.c b/com32/modules/hexdump.c new file mode 100644 index 0000000..bc2c70d --- /dev/null +++ b/com32/modul...

...6: (As you can see there are no errors at all) ** for TFTP only: dnsmasq-tftp: sent /run/archiso/bootmnt/arch/boot/syslinux/gpxelinux.0 to 192.168.0.90 dnsmasq-tftp: sent /run/archiso/bootmnt/arch/boot/syslinux/archiso.cfg to 192.168.0.90 dnsmasq-tftp: sent /run/archiso/bootmnt/arch/boot/syslinux/whichsys.c32 to 192.168.0.90 dnsmasq-tftp: sent /run/archiso/bootmnt/arch/boot/syslinux/archiso_pxe_choose.cfg to 192.168.0.90 dnsmasq-tftp: sent /run/archiso/bootmnt/arch/boot/syslinux/ifcpu64.c32 to 192.168.0.90 dnsmasq-tftp: sent /run/archiso/bootmnt/arch/boot/syslinux/archiso_pxe_32_inc.cfg to 192.168.0...

Hi I have a scenario where I need to test for whether I have booted via a syslinux ISO image in init-premount as opposed to (say) PXE boot. Is there any variable that I can test for this? thanks vk