search for: image_type_config

...pen() implementations (by filesystem type?) would look for the config file with a relative filename in the old current directory and not the new current directory. Is that a useful or necessary feature? Is Matt Fleming (author of the original code) still lurking on this list to explain? Or could IMAGE_TYPE_CONFIG set the directory before processing the config file. Both menu.c32 and ldlinux.EXT have parse_configs() functions that they send the argc/argv list they receive. Both functions handle multiple arguments as multiple config files to be processed (with either parse_one_config() or parse_main_config(...

...if (status != Countof(filename) - 1) { + fprintf(stderr, "Error constructing --config filename\n"); + status = EXIT_FAILURE; + goto err_filename; + } + + printf("Loading config-file '%s'...\n", filename); + syslinux_run_kernel_image(filename, "", 0, IMAGE_TYPE_CONFIG); + fprintf(stderr, "Failed to load config-file\n"); + status = EXIT_FAILURE; + + err_filename: + + err_config_nic_type: + + out: + + err_usage: + + err_nic_type_info: + + return status; +} + +static int usage(const char *prog) +{ + const char text[] = +"Us...

....000000000 -0600 > +++ b/com32/elflink/ldlinux/execute.c 2015-02-18 18:46:02.193886584 -0700 > @@ -41,6 +41,7 @@ const struct image_types image_boot_type > { "fdimage", IMAGE_TYPE_FDIMAGE }, > { "com32", IMAGE_TYPE_COM32 }, > { "config", IMAGE_TYPE_CONFIG }, > + { "efi", IMAGE_TYPE_EFI }, > { NULL, 0 }, > }; > > @@ -89,6 +90,13 @@ __export void execute(const char *cmdlin > do_sysappend(q); > } > > +#ifdef __FIRMWARE_BIOS__ > + if(type==IMAGE_TYPE_EFI) { > +...

...36,7 +137,8 @@ __export void execute(const char *cmdline, uint32_t type, bool sysappend) /* Restore the console */ ldlinux_console_init(); - ldlinux_enter_command(); + /* Jump back to the main to call ldlinux_enter_command */ + longjmp(__return_to_command_prompt, 1); } else if (type == IMAGE_TYPE_CONFIG) { char *argv[] = { LDLINUX, NULL, NULL }; char *config; diff --git a/com32/elflink/ldlinux/ldlinux.c b/com32/elflink/ldlinux/ldlinux.c index 9b01dd3..0172117 100644 --- a/com32/elflink/ldlinux/ldlinux.c +++ b/com32/elflink/ldlinux/ldlinux.c @@ -31,6 +31,8 @@ static const struct file_ext file...

...ould > look for the config file with a relative filename in the old current > directory and not the new current directory. > > Is that a useful or necessary feature? > > Is Matt Fleming (author of the original code) still lurking on this > list to explain? > > Or could IMAGE_TYPE_CONFIG set the directory before processing the config file. The CONFIG directive first changes the CWD and then it parses the new cfg file; or at least it is supposed to. For network setups, I would humbly suggest avoiding absolute paths, and using [MENU] INCLUDE (instead of CONFIG) whenever possib...

...ecute.c 2014-10-06 10:27:44.000000000 -0600 +++ b/com32/elflink/ldlinux/execute.c 2015-02-18 18:46:02.193886584 -0700 @@ -41,6 +41,7 @@ const struct image_types image_boot_type { "fdimage", IMAGE_TYPE_FDIMAGE }, { "com32", IMAGE_TYPE_COM32 }, { "config", IMAGE_TYPE_CONFIG }, + { "efi", IMAGE_TYPE_EFI }, { NULL, 0 }, }; @@ -89,6 +90,13 @@ __export void execute(const char *cmdlin do_sysappend(q); } +#ifdef __FIRMWARE_BIOS__ + if(type==IMAGE_TYPE_EFI) { + printf("Bios core cannot load efi image %s\n",kernel);...

...ory. > > > > Is that a useful or necessary feature? > > > > Is Matt Fleming (author of the original code) still lurking on this > > list to explain? It is a serious while ago that Matt posted on this ML, so don't wait for an answer from him. > > Or could IMAGE_TYPE_CONFIG set the directory before processing the config file. > > > The CONFIG directive first changes the CWD and then it parses the new > cfg file; or at least it is supposed to. > > For network setups, I would humbly suggest avoiding absolute paths, and > using [MENU] INCLUDE...

...); return 1; } init_structs(); detect_parameters(argc,argv); if (detect_syslinux() == 1) { fprintf(stderr, "No valid bootloader found..\n\n"); show_usage(); return 1; } if (strlen(bootlinux) > 0 ) { syslinux_run_kernel_image(bootlinux, "", 0, IMAGE_TYPE_CONFIG); fprintf(stderr, "config: failed to load '%s' (missing file?).\n\n", bootlinux); show_usage(); return 1; } else if (extlinux_param | isolinux_param | pxelinux_param | syslinux_param) { fprintf(stderr, "No config file specified for the current bootloader.\n\...

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

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

...{ "boot", IMAGE_TYPE_BOOT }, + { "bss", IMAGE_TYPE_BSS }, + { "pxe", IMAGE_TYPE_PXE }, + { "fdimage", IMAGE_TYPE_FDIMAGE }, + { "comboot", IMAGE_TYPE_COMBOOT }, + { "com32", IMAGE_TYPE_COM32 }, + { "config", IMAGE_TYPE_CONFIG }, + { NULL, 0 }, }; extern int create_args_and_load(char *); -void execute(const char *cmdline, enum kernel_type type) +void execute(const char *cmdline, uint32_t type) { - const char *p, *const *pp; const char *kernel, *args; + const char *p; com32sys_t ireg; char *q; @@ -79,22...

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