search for: allowedopt

> > Thanks Ady, you were 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...

...******************************** 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 use of whichsys.c32, running the same thing in both cases, it does illustrate the issue. When ALLOWEDOPTIONS is set to 0, memdisk errors "No ramdisk image specified!" as it does not receive the additional parameter. If you comment out ALLOWEDOPTIONS 0, then memdisk loads the image without any trouble. Similarly, if I use a config that only has the ALLOWOPTIONS 0 line (no vesamenu, etc.), &qu...

...***************** > > 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 use of whichsys.c32, running the same thing in both cases, it does illustrate the issue. When ALLOWEDOPTIONS is set to 0, memdisk errors "No ramdisk image specified!" as it does not receive the additional parameter. If you comment out ALLOWEDOPTIONS 0, then memdisk loads the image without any trouble. > Similarly, if I use a config that only has the ALLOWOPTIONS 0 line (no vesamenu, etc.)...

> More context to this: syslinux_run_command calls into load_kernel(), and somewhere behind load_kernel things break. 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

Thanks Ady, you were 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 o...