search for: noescape

(I apologise if this has already been reported - the archive isn't very searchable.) At present the NOESCAPE keyword seems rather useless, because a boot prompt is offered whenever attempts to load a boot image is interrupted using <Ctrl>C. Intuitively, I would expect "NOESCAPE 1" to lock this down also, and that {sys,pxe,iso.ext}linux would simply fall through to the impicit or expli...

I have just pushed out SYSLINUX 3.10-pre11. This version hopefully should fix Curtis' bug (display file garbage) as well as the NOESCAPE problem. Curtis, Alex and Paul, could you try this version out, please? -hpa

...The directive you are referring to is "ALLOWOPTIONS 0" (no "ED"), which prevents users from editing commands. In other words, the user can only execute LABELs "as-is". Yet, I doubt this is the (only) problem. My guess is that you are using another directive, "NOESCAPE 1", which, when combined with additional directives ("PROMPT 0" and/or "UI"), prevents the possibility of "forcing" the "boot:" prompt (with either SHIFT / ALT / CAPS LOCK / NUM LOCK) at boot time. In practice, "NOESCAPE 1" forces either th...

Hello, Could anyone kindly explain to me why the 'g()' in the following function cannot have tail call optimization? > void f(int* x); > void g(); > void h(int v) { > f(&v); > g(); > } > A while ago I was taught that tail call optimization cannot apply if local variables needs to be kept alive, but 'g()' doesn't seem to require anything to be

...ferring to is "ALLOWOPTIONS 0" (no "ED"), > which prevents users from editing commands. In other words, the user > can only execute LABELs "as-is". Yet, I doubt this is the (only) > problem. > > My guess is that you are using another directive, "NOESCAPE 1", > which, when combined with additional directives ("PROMPT 0" and/or > "UI"), prevents the possibility of "forcing" the "boot:" prompt (with > either SHIFT / ALT / CAPS LOCK / NUM LOCK) at boot time. > > In practice, "NOESCAPE...

...OPTIONS 0" (no "ED"), > > which prevents users from editing commands. In other words, the user > > can only execute LABELs "as-is". Yet, I doubt this is the (only) > > problem. > > > > My guess is that you are using another directive, "NOESCAPE 1", > > which, when combined with additional directives ("PROMPT 0" and/or > > "UI"), prevents the possibility of "forcing" the "boot:" prompt (with > > either SHIFT / ALT / CAPS LOCK / NUM LOCK) at boot time. > > > > In...

> 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

...1-27-g3d39943/core/keywords =================================================================== --- syslinux-3.71-27-g3d39943.orig/core/keywords 2008-08-31 22:45:26.000000000 +0200 +++ syslinux-3.71-27-g3d39943/core/keywords 2008-08-31 22:45:28.000000000 +0200 @@ -30,6 +30,7 @@ ontimeout onerror noescape +labelcompl f0 f1 f2 Index: syslinux-3.71-27-g3d39943/core/keywords.inc =================================================================== --- syslinux-3.71-27-g3d39943.orig/core/keywords.inc 2008-08-31 22:45:26.000000000 +0200 +++ syslinux-3.71-27-g3d39943/core/keywords.inc 2008-08-31 22:45:28...

Hi, I am trying the simple menu passswd in syslinux 3.11, and it seems that if I set the timeout option, the menu passwd is ignored. For example: ----------- default menu.c32 timeout 70 prompt 0 noescape 1 MENU MARGIN 5 MENU MASTER PASSWD $4$x$03NXHMe7QS0Ukxlkyh684LkWdqY$ label local MENU DEFAULT # MENU HIDE MENU LABEL Local operating system (if available) MENU PASSWD localboot 0 label memtest # MENU DEFAULT # MENU HIDE MENU LABEL Memory test using Memtest86+ MENU PASSWD kerne...

...Merge remote-tracking branch 'mfleming/for-hpa/elflink/fix-compiler-warnings' into elflink (2011-03-16 12:53:58 -0700) are available in the git repository at: git://git.zytor.com/users/mfleming/syslinux.git for-hpa/elflink/ldlinux Matt Fleming (1): ldlinux: Perform auto-boot if NOESCAPE set in config file com32/elflink/ldlinux/ldlinux.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/com32/elflink/ldlinux/ldlinux.c b/com32/elflink/ldlinux/ldlinux.c index 85066b1..a23b2f3 100644 --- a/com32/elflink/ldlinux/ldlinux.c +++ b/com32/elflink/ldlinux/ldlinux.c...

Talin, how about having the front-end generate an llvm.safe.point () intrinsic call at the desired safe points, and having the addresses of the GC roots (at that point, can vary from call to call) be the parameters (with noescape attribute) to the intrinsic, IIUC currently the GC roots are tagged, and all analysis and transform optimizations have to special case these tagged objects, but if instead their addresses were taken at the safe points no special casing would have to be done -- all analysis and transform op...

...; > 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 setting, so > the remaining piece would be restricting tab. (And perhaps holding > shift to get to the console.. Hmm.) > > I would appreciate any suggestions :) > > Thank you,--Ian > >From the perspective of a final user, breaking the prior behavior of directives nee...

...ul 19, 2011, at 10:06 AM, Peter Lawrence wrote: > Talin, > how about having the front-end generate an llvm.safe.point() intrinsic call at > the desired safe points, and having the addresses of the GC roots (at that point, > can vary from call to call) be the parameters (with noescape attribute) to the intrinsic, > > IIUC currently the GC roots are tagged, and all analysis and transform optimizations > have to special case these tagged objects, but if instead their addresses were taken at > the safe points no special casing would have to be done -- all analysis and...

...4) pxelinux.com displays nothing when booted on legacy network adapter. I'm looking forward for your ideas. Thanks. Okan Bostan Istanbul technical University okan.bostan at itu.edu.tr (*)---------------------------------------- DEFAULT vesamenu.c32 PROMPT 0 NOESCAPE 0 ALLOWOPTIONS 0 # Timeout in units of 1/10 s TIMEOUT 300 MENU WIDTH 40 MENU MARGIN 0 MENU ROWS 12 MENU TIMEOUTROW 14 MENU HSHIFT 3 MENU VSHIFT 7 MENU COLOR BORDER 30;44 #00000000 #00000000 none MENU COLOR TABMSG 1;36;44 #00000000 #00000000 none MENU COLOR TITLE 1;36;44...

...ne... this is pretty annoying. How likely is it that you want to pass a real newline character to PCRE directly? If it's anyhow possible to pass everything between " and " directly to PCRE without expanding it internally in R, please add this to a future version (as an option like noescape=TRUE perhaps?)! I would love to use R instead of Perl for working with regex, without having to do two levels of escape all the time. Thanks, John

From: Matt Fleming <matt.fleming at intel.com> Here are the patches that I've got queued up based on the very helpful feedback I received from people testing Syslinux 5.00-pre9. Unless anyone has any concerns these will make it into Syslinux 5.00-pre10. Matt Fleming (9): pxe: Don't call open_config() from the pxe core ldlinux: Print a warning if no config file is found

.... * New API call to do "localboot". * New API call to query features. * New API call to run kernel image, a lower-level call than "run command". See comboot.doc. * Fix for bug in EBIOS code discovered by Arwin Vosselman. * NOESCAPE security fix. * Comments are now recognized even without a space following #. * Fix incorrect handling of mixes of entries with and without MENU PASSWD. * The idle API call now harmlessly returns failure if it is a no-op. That way the caller can dec...

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

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

On Mon, Jul 18, 2011 at 11:00 AM, Peter Lawrence <peterl95124 at sbcglobal.net>wrote: > Talin, > do you identify safe-points in the current or proposed llvm > scheme, and if so how, > or are they implicit as being at all call sites (which begs the question > what about leaves > in the call tree, how does GC get started at all in that case). > > The LLVM