Displaying 3 results from an estimated 3 matches for "syslinux_configfile".
Did you mean:
syslinux_config_file
2017 Apr 12
1
Improving TAILS, WAS: Module Versioning
...12440
> However, I do not see "ldlinux.e32" in the list provided by Pete, so
> perhaps TAILS' devs. have decided to just use grub.efi (and no
> chainloading)?
Exactly. I didn't manage to chainload 32-bit syslinux EFI from GRUB,
and I didn't bother since GRUB's syslinux_configfile works fine for us.
> 3_ When building the ISO image, the script(s) should rather move
> everything from the "isolinux" directory to a "syslinux" directory. The
> same goes to the cfg file name, as isolinux.bin can use "syslinux.cfg"
> just fine. Then th...
2016 Mar 07
4
Module Versioning
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
2017 Apr 12
0
Module Versioning
...understanding going on here.
There are three cases for Tails, let me show you what's used in each case:
* BIOS: isolinux/, business as usual
* 64-bit UEFI: EFI/BOOT/bootx64.efi, which is syslinux
* 32-bit UEFI: EFI/BOOT/bootia32.efi, which is GRUB that loads the
syslinux config with the syslinux_configfile directive; we do that
due to the fact that the we can put only one set of *.c32 modules
and syslinux configuration, for one single architecture, in
EFI/BOOT; I'll look into commit 7d9c9ec ("Add architecture-specific
config name to search") later as this might allow us to d...