similar to: [PATCH 3/3] syslinux: support isolinux configuration files

> I'm the developer of manjaroiso, the tool we use to build our install > medias for Manjaro Linux. > During our testings we found out, that syslinux6 won't work on older > hardware. I've a new Lenovo i7 notebook which booted up our images > just fine. Even with syslinux6. On my other PCs I got similar error > messages as Carl got. (snip) > > In

Hello, I wish to recompile only isolinux.bin and nothing else. I made some changes to core/fs/lib/loadconfig.c and now I wish to make (compile) isolinux.bin only. The only way how to do it seems to be "make" in the directory of syslinux sources. But this takes very long and compiles everything. Is there a better way to make only isolinux.bin? Something like "make isolinux"

Actually, as you may have questions with some elements you'll see in the log, and especially: Detected Syslinux version: 6.03/20150819 (from '/EFI/BOOT/isolinux.bin') So I should point out that EFI/grub is actually used by the tails people to chain load EFI/Syslinux (hence the ldlinux.e64, ldlinux.c32 as well as isolinux.bin one also sees in /efi/boot/). As a result, in the

> Their isolinux/isolinux.cfg has > DEFAULT loadconfig > LABEL loadconfig > CONFIG /arch/boot/syslinux/archiso.cfg > The file arch/boot/syslinux/archiso.cfg is readable too. > IIRC, Arch isolinux/isolinux.cfg should say: DEFAULT loadconfig LABEL loadconfig CONFIG /arch/boot/syslinux/archiso.cfg APPEND /arch/ Or it might be using relative paths: DEFAULT

Hello again, * TFTP and DHCP started using: dnsmasq --port=0 \ --no-daemon \ --enable-tftp \ --tftp-root=/run/archiso/bootmnt \ --dhcp-range=192.168.0.2,192.168.0.254,86400 \ --dhcp-boot=/arch/boot/syslinux/gpxelinux.0 \ --dhcp-option-force=209,boot/syslinux/archiso.cfg \ --dhcp-option-force=210,/arch * and for DHCP+HTTP

> Hello Ady & list, > > On Wed, Aug 27, 2014 at 08:17:51AM +0300, Ady wrote: > > > Hello Ady, > > > > > > On Fri, Aug 01, 2014 at 08:35:27PM +0300, Ady wrote: > > > > Goal: To have one USB drive capable of booting UEFI IA32 and UEFI X64 > > > > (with an optional Syslinux menu containing multiple entries). > > > > >

Hello Ady & list, On Wed, Aug 27, 2014 at 08:17:51AM +0300, Ady wrote: > > Hello Ady, > > > > On Fri, Aug 01, 2014 at 08:35:27PM +0300, Ady wrote: > > > Goal: To have one USB drive capable of booting UEFI IA32 and UEFI X64 > > > (with an optional Syslinux menu containing multiple entries). > > > > > > Problem (solved) #1: The default

Hi, Ady: > I am using the ISO image from TAILS as an excuse to "tease" TAILS' devs > and other users of Syslinux. If intrigeri (TAILS developer) "bites". > then users reading this mailing list might learn one thing or two about > Syslinux (6.04-pre1+). :) > 1_ EFI/BOOT/isolinux.bin is probably a mistake (or misunderstanding) > originated in the ISO

-- Re-sent as original may be stuck at awaiting "authorisation" (originally sent before I joined the mailing list) Hi All, It is impossible to boot Linux-based ISOs that use Syslinux 6.02 via CD or DVD on older - non-UEFI - systems. Any attempt to do so will result in the following error message: ISOLINUX 6.02 ETCDisolinux: Disk error 01, AX = 4279, drive FE It is still possible to

On Wed, 12 Jun, at 12:42:01PM, Gerardo Exequiel Pozzi wrote: > make installer > make -C utils > make -C com32 > > then copy all files *.c32 (including ldlinux.c32) and lpxelinux.0 I suspect the above make commands aren't enough to rebuild the necessary files. I just pushed out a 5.11-pre1 with a version of the patch that only changes the internal representation of PATH. Could

On Wed, Aug 27, 2014 at 2:08 AM, Prof. Dipl.-Ing. Klaus Knopper <syslinux at knopper.net> wrote: > Apparently, the rename of ldlinux.e32 to ldlinux.e64 for the 64bit > variant is already in the mainline git, so the only change left for > automatically chosing a different config file is the tiny patch attached > here, which will > > - prepend syslnx64.cfg to the config file

On Tue, 11 Jun, at 03:54:21AM, H. Peter Anvin wrote: > On 06/11/2013 01:03 AM, Matt Fleming wrote: > > On Mon, 10 Jun, at 07:57:50AM, H. Peter Anvin wrote: > >> Either that or make the path a list rather than a string, using the > >> normal word separators when entered on the command line, a bit like the > >> (t)csh does. That is a bigger change but is probably

> Hello Ady, > > On Fri, Aug 01, 2014 at 08:35:27PM +0300, Ady wrote: > > Goal: To have one USB drive capable of booting UEFI IA32 and UEFI X64 > > (with an optional Syslinux menu containing multiple entries). > > > > Problem (solved) #1: The default directory location for both > > syslinux.efi is the same. > > > > Solution #1: Rename each

On 3/8/2016 14:26, Pete Batard via Syslinux wrote: > [...] > But in essence, yes, that's pretty much it. So then some thoughts: 1. Did you mean a truly "merged" file, where the very same file could be used for ISOLINUX and for disk-based Syslinux? Or did you mean "tacked on," where ldlinux.bin would be appended to isolinux.bin so that you could later

On Wed, 12 Jun, at 11:17:44AM, Gerardo Exequiel Pozzi wrote: > Cool thanks!. Now looks better, but still not work. > > For some reason, "ldlinux.c32" is apparently sent but "Failed to load" > by PXELINUX and few seconds later, dnsmasq shows an error message > "failed sending": Argh! The patch was broken. I missed the new core/path.c file. My bad.

On 3/8/2016 07:23, Pete Batard via Syslinux wrote: > [...] the merging of ldlinux.sys and isolinux.bin, which I would very > much like to rally people on this list into seeing as beneficial. [...] My understanding is that isolinux.bin and ldlinux.bin are pretty much twins[1]. If I understand correctly, you'd like the latter to be tacked onto the former because people are too stupid

Hi, i am experiencing strange boot failures after repacking the ISO image archlinux-2013.11.01-dual.iso without isohybrid and EFI: # mount -o loop archlinux-2013.11.01-dual.iso /mnt $ xorriso -as mkisofs \ -o arch_repacked.iso \ -c isolinux/boot.cat \ -b isolinux/isolinux.bin \ -no-emul-boot -boot-load-size 4 -boot-info-table \ -V "ARCH_201311" \

H. Peter Anvin schreef op 9-8-2013 7:37: > Sorry. If you are substituting any files you should substitute them all. I assume it's not possible to store a copy of the LDLINUX.SYS binary at the end or inside of either ISOLINUX.BIN or LDLINUX.C32 then? Then at least it could be extracted, for those distributions not having LDLINUX.SYS / SYSLINUX(64).EXE present on their CD. Having

On 2013.08.10 01:55, H. Peter Anvin wrote: >> I assume it's not possible to store a copy of the LDLINUX.SYS binary at >> the end or inside of either ISOLINUX.BIN > > Not really. ldlinux.sys isn't just an ordinary file, it really needs to > be installed with the Syslinux installer. My application already its own version of the Syslinux installer [1], and simply

Hello, First, this setup works fine without any error in syslinux 4.06 as show below. For convenience, both versions of syslinux 4.06 [#1] and 5.10 [#2] directories (~2MB each) are uploaded ready for test. As said before, this is tested on qemu-1.5.0 + dnsmasq 2.66 in Arch Linux @ 64-bit. If more info is needed, please let me know. Good luck! Relevant directory structure is at