search for: load_kernel

...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 '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 appreciat...

...inux.c index 85066b1..a23b2f3 100644 --- a/com32/elflink/ldlinux/ldlinux.c +++ b/com32/elflink/ldlinux/ldlinux.c @@ -65,7 +65,7 @@ static int ldlinux_main(int argc, char **argv) /* * Auto boot */ - if (defaultlevel || !noescape) { + if (defaultlevel || noescape) { if (defaultlevel) { load_kernel(); /* Shouldn't return */ } else {

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

...m/?p=syslinux/syslinux.git;a=commit;h=0b3b862ff49ab1b0b5d5af8c15d58e3c4baaf634 > > At this point, syslinux_run_command is using the equivalent of > create_args_and_load(), a function that is *not* negatively affected > by ALLOWOPTIONS. > > The behavior was changed in 2013 to use load_kernel to *add* label support: > http://git.zytor.com/?p=syslinux/syslinux.git;a=commit;h=04f40bc55ed4f39d6c625b017bb16907f7d50c05 > > At this point the 8 or 9 com32 modules I listed earlier stopped working > when ALLOWOPTIONS was set. This is a change from the previous 6 years > of behavi...

Hello, Is there a function to check a bzImage CRC ? If (ImageCRC("/bzImage") == -1) Load_kernel("/BACKUP/bzImage") or what else Thanks Regards Johann

...el. Some kernels are linked with a virtual entry point and without this patch these kernels are unbootable. Hope this helps, Matthew --- a/com32/modules/mboot.c 2009-04-03 09:48:08.000000000 +1000 +++ b/com32/modules/mboot.c 2009-04-03 09:48:16.000000000 +1000 @@ -650,6 +650,13 @@ static size_t load_kernel(struct multibo exit(1); } + /* The real entry point is the actual physical location of the code to jump to. + * This allows kernels with a virtual entry point address to successfully run (if + * their startup code is position-indepe...

...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 '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.) > &...

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

...dlinux.c @@ -124,7 +124,7 @@ static const char *apply_extension(const char *kernel, const char *ext) /* Copy the rest of the command line */ strcpy(k + len + elen, p); - k[len + elen] = '\0'; + k[len + elen + strlen(p)] = '\0'; return k; } @@ -164,6 +164,12 @@ static void load_kernel(const char *command_line) if (!allowimplicit) goto bad_implicit; + /* Insert a null character to ignore any user-specified options */ + if (!allowoptions) { + char *p = (char *)find_command(kernel); + *p = '\0'; + } + type = parse_kernel_type(kernel); if (type == KT_KERNEL) {...

...t int main(int argc __unused, char **argv) const void *adv; const char *cmdline; size_t count = 0; + int retval; ldlinux_console_init(); @@ -333,16 +336,25 @@ __export int main(int argc __unused, char **argv) if (!syslinux_setadv(ADV_BOOTONCE, 0, NULL)) syslinux_adv_write(); - load_kernel(cmdline); /* Shouldn't return */ - ldlinux_enter_command(); - } - - if (!forceprompt && !shift_is_held()) - ldlinux_auto_boot(); + /* + * The corresponding longjmp is located in the execute function + * after a COM32 module has returned. + */ + retval = setjmp(__return_to_comm...

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. --Ian > From: ian at internals.io > To: syslinux at zytor.com > Date: Tue, 29 Apr 2014 13:55:39 -0500 > Subject: [sysl...

...odd. Thank you very much! --Ian > From: ady-sf at hotmail.com > To: syslinux at zytor.com > Date: Wed, 30 Apr 2014 00:14:39 +0300 > Subject: Re: [syslinux] Issues with syslinux_run_command(str) and parameters > > > > 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 s...

...ommit;h=0b3b862ff49ab1b0b5d5af8c15d58e3c4baaf634 > > > > At this point, syslinux_run_command is using the equivalent of > > create_args_and_load(), a function that is *not* negatively affected > > by ALLOWOPTIONS. > > > > The behavior was changed in 2013 to use load_kernel to *add* label support: > > http://git.zytor.com/?p=syslinux/syslinux.git;a=commit;h=04f40bc55ed4f39d6c625b017bb16907f7d50c05 > > > > At this point the 8 or 9 com32 modules I listed earlier stopped working > > when ALLOWOPTIONS was set. This is a change from the previous 6...

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

...does things and Solaris kernels rely on this behaviour. Signed-of-by: Ralf Ertzinger <ralf at skytale.net> --- diff --git a/com32/modules/mboot.c b/com32/modules/mboot.c index ad659d9..2af74c1 100644 --- a/com32/modules/mboot.c +++ b/com32/modules/mboot.c @@ -582,71 +582,11 @@ static size_t load_kernel(struct multiboot_info *mbi, char *cmdline) /* This kernel will do: figure out where all the pieces will live */ - if (mbh->flags & MULTIBOOT_AOUT_KLUDGE) { - - /* Use the offsets in the multiboot header */ -#ifdef DEBUG - printf("Using multiboot...

...; // Global registers for this module @@ -35,33 +38,26 @@ void runsyslinuxcmd(const char *cmd) return; strcpy(bounce, cmd); - REG_AX(inreg) = 0x0003; // Run command - REG_BX(inreg) = OFFS(bounce); - REG_ES(inreg) = SEG(bounce); - __intcall(0x22, &inreg, &outreg); + load_kernel(bounce); } void gototxtmode(void) { - REG_AX(inreg) = 0x0005; - __intcall(0x22, &inreg, &outreg); + syslinux_force_text_mode(); } void syslinux_idle(void) { - REG_AX(inreg) = 0x0013; - __intcall(0x22, &inreg, &outreg); + __idle(); } unsigned int getve...

From: Matt Fleming <matt.fleming at intel.com> Since we can't use __intcall() for EFI, and since we can now have the ELF module code resolve all our symbols at runtime, we should delete as many references to __intcall() as possible and just access the symbols directly. The most interesting patch is the support for weak symbols. We need to be able to reference derivative-specific

...com32 ifcpu.c32 append 64 -- labelX OPT1 -- labelX OPT2 # invoked as is regardless of allowoptions and allowimplicit *Example (prompt) proposed* kernelX OPT # OPT not passed with allowoptions 0 (fully blocked with IMPLICIT 0) labelX OPT # OPT not passed with allowoptions 0 One option is to change load_kernel() with an extra argument to know if the supplied command_line is provided via configuration or from the user. Then applied allowoptions, allowimplicit only if the cmdline is user_supplied (of course adding the support for allowoptions in the label path). For command coming from the boot-once, coul...

From: Sylvain Gault <sylvain.gault at gmail.com> Hello there, I propose 2 patches that fix two possible stack overflows either when running a COM32 module or when loading a new config file. I didn't find a better way to do this than to use the infamous setjmp/longjmp functions to restore the stack to a previous state. This makes the logic a bit more complex, but the behavior is not

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