search for: search_directories

...after ldlinux.c32 is loaded, so ldlinux.c32 should always be in the root? i'm looking for a way to configure this to only search the libs and ldlinux.c32 in ./mods/ to limit the needed GETs to the server, speed things up a bit and have a neat directory structure. i was already found the 'search_directories' static const in load_env32.c, but after changing that to: static const char *search_directories[] = { "/mods", NULL }; it still does these requests: GET /libcom32.c32 GET //libcom32.c32 Any help is appreciated. Rgds, Reni

...same directory under the assumption that the documentation is right and syslinux will look in the same directory as the filename for ldlinux.EXT. The code appears to do that, but what the TFTP server sees is a second request for /efi/syslinux.efi and then ldlinux.e64 searched for in the hard coded search_directories list which doesn't match my network configuration. If I change the DHCP configuration to use pathprefix set to /efi/ then it finds ldlinux.e64 and can find my configfile, but I want to follow the layout recommended in the wiki documentation where I could have all three of bios, e32 and e64 ver...

From: Matt Fleming <matt.fleming at intel.com> The following patch series is available at, git://git.zytor.com/users/mfleming/syslinux.git elflink All patches are against the 'elflink' branch. This series fixes a few serious bugs and some behavioural incompatibilities with the 4.x series. Matt Fleming (19): ldlinux: Initialise 'p' before using it. ldlinux: Parse

Hello Syslinux Team, If I understand correctly (and I should emphasize that condition), the lib*.c32 library modules, when required, are initially searched-for according to the following (fallback) rules: 1_ Search for the relevant lib*.c32 file(s) in the Current Working Directory. 2_ Search for the relevant lib*.c32 file(s) in the directory where ldlinux.c32 is located. Then the lib*.c32

...the assumption that the documentation is > right and syslinux will look in the same directory as the filename for > ldlinux.EXT. The code appears to do that, but what the TFTP server > sees is a second request for /efi/syslinux.efi and then ldlinux.e64 > searched for in the hard coded search_directories list which doesn't > match my network configuration. > > If I change the DHCP configuration to use pathprefix set to /efi/ then > it finds ldlinux.e64 and can find my configfile, but I want to follow > the layout recommended in the wiki documentation where I could have > all...

From: Matt Fleming <matt.fleming at intel.com> The first two patches in this series are fixes for bugs reported by someone in #syslinux. The third makes dmitest.c32 actually wait for user input. If no one has any objections/concerns, I'll pull this into the official elflink branch. Matt Fleming (3): core: Print error message if we don't load ldlinux.c32 Clean up $(GPLLIB) leak

...} /* note to self: do _*NOT*_ use static key word on this function */ -void load_env32(com32sys_t * regs) +void load_env32(com32sys_t * regs __unused) { struct file_info *fp; int fd; char *argv[] = { LDLINUX, NULL }; - char *realname; + char realname[FILENAME_MAX]; static const char *search_directories[] = { "/boot/isolinux", @@ -138,7 +126,6 @@ void load_env32(com32sys_t * regs) }; dprintf("Starting 32 bit elf module subsystem...\n"); - call_constr(); PATH = malloc(strlen(PATH_DEFAULT) + 1); if (!PATH) { diff --git a/core/font.c b/core/font.c index 0eeb90f..1fc...