search for: ldlinux

...from 192.168.103.41 filename efi64/syslinux.efi Oct 7 01:16:10 foreman in.tftpd[43905]: tftp: client does not accept options Oct 7 01:16:10 foreman in.tftpd[43906]: RRQ from 192.168.103.41 filename efi64/syslinux.efi Oct 7 01:16:10 foreman in.tftpd[43907]: RRQ from 192.168.103.41 filename efi64/ldlinux.e64 Oct 7 01:16:10 foreman in.tftpd[43908]: RRQ from 192.168.103.41 filename efi64/ldlinux.e64 Oct 7 01:16:11 foreman in.tftpd[43909]: RRQ from 192.168.103.41 filename efi64/ldlinux.e64 Oct 7 01:16:11 foreman in.tftpd[43940]: RRQ from 192.168.103.41 filename efi64/ldlinux.e64 Oct 7 01:16:12 for...

Thanks for the response, Gene. Much appreciated. I didn't get all of it; mind if I follow on below? ldlinux.sys is ldlinux.bin without the VBR (Volume Boot Record) code. > Makes sense. > > 1. Where is the code that goes in the VBR or Block Group 0 padding? > > diskboot.inc. > which appears to be included in diskstart.inc. I will have to dig in and see how this all gets compiled (poi...

A proposal for changing the LDLINUX.SYS layout and flow: The current situation ("old style"): ldlinux.bin's physical layout: - VBR - 512 bytes of padding (never lands in memory) - ldlinux.sys, which is: - Sect1 code (494 bytes, leaving enough room for at least one extent, as planned) - Extent po...

Calc the size of ldlinux.sys from ldlinux.bin, and check if it exceeds the limit. ldlinux.sys must fit between the bootsector and two copies of ADV whose size may vary. Thus, the size of ldlinux.sys (limit) can be at most: 65536 - 2 * ADV_SIZE - 512. Certain file systems (such as BTRFS and UFS2) will rely on ldlinux.sys b...

...> > how this all gets compiled (pointers always appreciated :-) ). > > Yes. > Is the build process documented? Or am I just going to have to plod through the makefiles? > As Ady said, embedded within the syslinux/extlinux installer. > Got it. And I did a byte comparison of ldlinux.bin/ldlinux.sys. Identical except for the first 1024 bytes. First 512 are the VBR, as you described, next 512 are all zeros (I assume for using with ext?). > Actually, mildly more complex but similar. Setup some basics, the > first sector of ldlinux.sys, execute it. > > The first sec...

...of Syslinux operation which could be fairly easily improved. quoting from the official documentation: Since version 5.00, when a SYSLINUX or EXTLINUX installer is used, the relevant boot sector will be modified and two files will be added to the "installation directory": the ldlinux.sys boot loader file, and an auxiliary ldlinux.c32 file. Note that these two files are not necessary so as to execute the installers; they are already embedded in the installers themselves. http://www.syslinux.org/wiki/index.php?title=Library_modules#All_Syslinux_variants_need_an_addit...

...hanges since commit 8c576f1fe03e34879921311f46613a35c6530000: 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/...

...ntel.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 ldlinux: Fix logic if no DEFAULT or UI directive is found ldlinux: get_key() requires raw access to user input com32: Include .init_array section in .ctors in linker script CLI: Fix command history traversal win: Fix installing to a directory...

...6.03-pre16 BIOS: lpxelinux.0: as per pre14 6.03-pre17 BIOS: lpxelinux.0: boots OK TFTP & HTTP ---------------- 6.03-pre11 EFI32: boots OK TFTP & HTTP 6.03-pre12 EFI32: fails - gets stuck in a loop downloading files - differs each boot 6.03-pre13 EFI32: fails - downloads /pxelinux.c32 & /ldlinux.c32 - then continually retries to download ldlinux.e32 6.03-pre14 EFI32: fails - downloads /pxelinux.c32 & /ldlinux.e32 - also then tries to download /syslinux/ldlinux.e32, /boot/isolinux/ldlinux.e32, and /syslinux/ldlinux.e32 - then boot fails 6.03-pre15 EFI32: fails as per pre14 6.03-pre16 EF...

Hi, These patches fix some compiler warnings in ldlinux and elflink. I've tried to split the patches out so that they only change one file or one type of problem at once. So, if they do inadvertently introduce any bugs it should at least be easy to bisect to a smallish commit. The following changes since commit 9ded45991b4fc83b40af963feb773ddca258...

...m trying to setup a PXE server for two Debian releases (stretch and buster) using their respective network boot images (netboot.tar.gz), which I extracted into subdirectories of the TFTP server's root directory: ??? ??? debian ??? ??? ??? buster ??? ??? ??? ??? debian-installer ??? ??? ??? ??? ldlinux.c32 -> debian-installer/i386/boot-screens/ldlinux.c32 ??? ??? ??? ??? pxelinux.0 -> debian-installer/i386/pxelinux.0 ??? ??? ??? ??? pxelinux.cfg -> debian-installer/i386/pxelinux.cfg ??? ??? ??? ??? version.info ??? ??? ??? stretch ??? ??????? ??? debian-installer ??? ??????? ??? ldlinux....

I am trying to build an RPM starting from the TAR archive. The relevant error is: make[1]: Entering directory `/tmp1/Software/rpmbuild/BUILD/syslinux-5.00/libinstaller' perl bin2c.pl syslinux_bootsect < ../core/ldlinux.bss > bootsect_bin.c perl bin2c.pl syslinux_ldlinux 512 < ../core/ldlinux.sys > ldlinux_bin.c perl bin2c.pl syslinux_mbr < ../mbr/mbr.bin > mbr_bin.c perl bin2c.pl syslinux_gptmbr < ../mbr/gptmbr.bin > gptmbr_bin.c make[1]: *** No rule to make target `../com32/elflink/ldlinux/...

...tual FAT filesystem and partition table. Nothing is ever written to a file, and it must run without anything needing to be root, loop mounting etc. Running "syslinux --install <something>" is a non-starter. So I've looked at how syslinux works and I see that it adds the files LDLINUX.SYS and LDLINUX.C32 to the FAT filesystem -- I can easily emulate this bit in the plugin since we are already creating a full FAT32 filesystem on the fly. However the problem is that syslinux also creates a boot sector [ie. core/bios/diskboot.inc in the syslinux source] and I suppose it must encod...

From: Raphael S. Carvalho <raphael.scarv at gmail.com> v2: Extract ADV_SIZE automatically from libinstaller/setadv.h. Calc the size of ldlinux.sys from ldlinux.bin, and check if it exceeds the limit. ldlinux.sys must fit between the bootsector and two copies of ADV whose size may vary. Thus, the size of ldlinux.sys can be at most: 65536 - 2 * ADV_SIZE - 512 (limit). Certain file systems (such as BTRFS and UFS2) will rely on ldlinux.sys b...

...could be fairly easily improved. > > quoting from the official documentation: > > Since version 5.00, when a SYSLINUX or EXTLINUX installer is used, > the relevant boot sector will be modified and two files will be > added to the "installation directory": the ldlinux.sys boot loader > file, and an auxiliary ldlinux.c32 file. Note that these two files > are not necessary so as to execute the installers; they are already > embedded in the installers themselves. > > http://www.syslinux.org/wiki/index.php?title=Library_modules#All_Syslinu...

From: Matt Fleming <matt.fleming at linux.intel.com> This is a series of patches that, * shrink the core by moving things into an ldlinux ELF module * begin wiring up some of the C versions of various functions The core now only contains essential code and loads the ldlinux module to do everything else, like providing a command line interface and loading kernels. The config file parsing and kernel load are now done entirely in C. T...

...cking 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/cmdline Matt Fleming (2): elflink, cli: TAB key now displays labels ldlinux, cli: Add support for F-keys com32/elflink/ldlinux/cli.c | 21 +++++++++ com32/elflink/ldlinux/config.h | 2 + com32/elflink/ldlinux/ldlinux.c | 2 +- com32/elflink/ldlinux/readconfig.c | 84 ++++++++++++++++++++++++++++++++++++ com32/elflink/modules/menu.h | 2 +...

From: Sylvain Gault <sylvain.gault at gmail.com> When a COM32 module exits, the functions never return and a new call to ldlinux_enter_command is made. This could fill the stack and overflow on some data present in memory. This patch use setjmp/longjmp to return to the main function and restart from there when a COM32 module exits. Signed-off-by: Sylvain Gault <sylvain.gault at gmail.com> --- com32/elflink/ldlinux/e...

> On May 25, 2014 3:39 AM, "Geert Stappers" <stappers at stappers.nl> wrote: > > > > > > While going throug old posts found: > > > > Op 2013-08-31 om 17:01 schreef Raphael S.Carvalho: > > > Calc the size of ldlinux.sys from ldlinux.bin, and check if it exceeds > the limit. > > > ldlinux.sys must fit between the bootsector and two copies of ADV whose > size may vary. > > > Thus, the size of ldlinux.sys (limit) can be at most: 65536 - 2 * > ADV_SIZE - 512. > > > > > &gt...

...always appreciated :-) ). >> >> Yes. > > Is the build process documented? Or am I just going to have to plod through > the makefiles? I don't think so. >> As Ady said, embedded within the syslinux/extlinux installer. > > Got it. And I did a byte comparison of ldlinux.bin/ldlinux.sys. Identical > except for the first 1024 bytes. First 512 are the VBR, as you described, > next 512 are all zeros (I assume for using with ext?). I believe so. >> Actually, mildly more complex but similar. Setup some basics, the >> first sector of ldlinux.sys, exe...