similar to: Bug/limitation: allowoptions (for label), implicit (for automated)

My summary: reviewing ALLOWOPTIONS found reasons for further reviewing 'ALLOWOPTIONS' Op 2014-07-12 om 04:35 schreef Ady: > > > I have some questions about "ALLOWOPTIONS 0". > > > > [quote] > > ALLOWOPTIONS flag_val > > If flag_val is 0, the user is not allowed to specify any arguments on > > the kernel command line. The only

I have some questions about "ALLOWOPTIONS 0". [quote] ALLOWOPTIONS flag_val If flag_val is 0, the user is not allowed to specify any arguments on the kernel command line. The only options recognized are those specified in an APPEND) statement. The default is 1. [/quote] My understanding of the behavior of "ALLOWOPTIONS 0" is that unless I type-in a command that is exactly

Yes, MENU HIDE would work as well, but still requires additional entries for each case (possible entries for pxe, syslinux, isolinux, cpu architectures, PCI devices, lua scripting scenarios, etc.) By blocking modules, I meant that as long as I disable user editing of menu commands via ALLOWOPTIONS 0, I cannot use any of the following com32 modules without creating duplicate LABEL entries for each

Good day, If I set allowoptions to 0 to hide editing menu entries and then select to run lua.c32 from menu , run_command() from inside the script it seems to invoke kernel/com32 modules without any parameter. For example pxechn.c32 will never be happy no matter what the command line is. But if you set allowoptions to 1 everything starts to work as expected, except the menu itself.

I did confirm earlier that this does work, and combined with a MENU HIDDEN to hide it from the 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

Peter, Paulo reported some problems with his config files under ISOLINUX and PXELINUX - basically TIMEOUT and TOTALTIMEOUT were broken. The patches I've pushed to the elflink branch fix this and also fix parsing of the ALLOWOPTIONS config directive. The following changes since commit d5e02fb16a11bfdbce1e90a39e6cb5f2ad925389: get_key: Valid key values are positive (2012-04-17 11:25:53

> I have some questions about "ALLOWOPTIONS 0". > > [quote] > ALLOWOPTIONS flag_val > If flag_val is 0, the user is not allowed to specify any arguments on > the kernel command line. The only options recognized are those > specified in an APPEND) statement. The default is 1. > [/quote] > > My understanding of the behavior of "ALLOWOPTIONS 0"

> I didn't see any further communication here; would anyone be > against my submitting/proposing a patch for this? Contributions are always welcome. > > I can see two possible approaches. One approach would be to > isolate the restriction on user commands away from > syslinux_run_command / load_kernel. > > Another would perhaps be to add support for a

This implements the label completion on tab key idea. It does introduce "labelcompl" as new config keyword. The default value is 0 so it does not change current behaviour. If you press tab with an empty command line it will display all labels. If the command line contains any characters it will display the matching labels. This patch is only intended for testing since i didn't check

>> >> >From the perspective of a final user, breaking the prior behavior of >> directives needs to have very clear advantages. > > Reviewing the commit history, I would say that the prior behavior is currently broken. > > The ALLOWOPTIONS feature was added in 2004: >

Apologies for how that formatted. Also on pastebin: http://pastebin.com/EXSq75yX --Ian > From: ian at internals.io > To: ady-sf at hotmail.com; syslinux at zytor.com > Date: Tue, 29 Apr 2014 19:09:09 -0500 > Subject: Re: [syslinux] Issues with syslinux_run_command(str) and parameters > > I don't think that's it, but fair enough, try this sample config: >

Hi, I have tried several different line options, but I cannot seem to get the pxe master password option to work? I have basically tried all combinations of: DEFAULT local PROMPT 0 ALLOWOPTIONS 1 TIMEOUT 500 MENU TITLE sometitle MENU MASTER PASSWD somepassword But just can't seem to get the menu to prompt for a password. version I have is pxe 3.31 Thanks for any help

I didn't see any further communication here; would anyone be against my submitting/proposing a patch for this? I can see two possible approaches. One approach would be to isolate the restriction on user commands away from syslinux_run_command / load_kernel. Another would perhaps be to add support for a 'NOTAB' or 'NOTABTOEDIT' option. There already exists a NOESCAPE

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

Dear all, As you can see from the attachment I'm using R to automatically annotate peptide fragmentation mass spectra, which are represented by impulse plots. I'd like to poll you on approaches of how to deal as generally as possible with the two biggest annotation issues I run into: 1) very close annotated masses (impulses) with similar y-axis dimensions - resulting in overlapping labels

<..trying again after changing outgoing e-mail options to avoid bad headers...> I'm trying to use syslinux 3.08-pre11 on a Gateway E4000 with the (sample) config file below, and the ramdisk images fail to boot if selected as a menu option, but do boot if I press ESC and type the command line manually. The two options are for the same floppy image, but the first is compressed, the

Dear all, I have a function that predicts DV based on one predictor pred: pred<-c(0,3000000,7800000,15600000,23400000,131200000) DV<-c(0,500,1000,1400,1700,1900) ## I define Function 1 that computes the predicted value based on pred values and parameters a and b: calc_DV_pred <- function(a,b) { DV_pred <- rep(0,(length(pred))) for(i in 1:length(DV_pred)){ DV_pred[i] <- a *

Hi, I'm facing some problems with pxelinux. I have ingetrated it into WDS server. I want to use Network boot all way possible. I want to add Hiren boot disk and NT password editor tools. Is this possible? Currently my network boot includes WDS, Linux install, Win98 Startup disk and ghost 11.5 wPS-DOS. My conf file as follows(*) Also in hyperv virtual machines(x64) pxelinux.com displays

Op 2014-05-05 om 23:20 schreef Ady: > > > I didn't see any further communication here; would anyone be > > against my submitting/proposing a patch for this? > > Contributions are always welcome. > > > > > I can see two possible approaches. One approach would be to > > isolate the restriction on user commands away from > > syslinux_run_command /

Hello, i've got a problem with boot pxe on pc, all my pc works fine except in a room where all the same pc doesnt works : my configuration (dhcp tftp etc...) works fine also here is a part of my tftpboot directory ghost/ memdisk menu.c32 pxelinux.0 pxelinux.cfg/ ./ghost: ghost288.IMA ghost_geii_101.IMA ghost_MM.IMA ghost_MM.IMA.old ./pxelinux.cfg: default here is a part of my default