Hi, [ouch, it take me a year? thank you all for this very interesting thread that I'm going to finish reading now.] Pete Batard via Syslinux:> I'll skip the EFI part of tails (that uses grub/EFI) to talk only > about the BIOS/Syslinux part.JFTR Tails uses GRUB only for 32-bit UEFI. We use syslinux for BIOS and 64-bit UEFI.> So, one thing Rufus will need to do is find a "replacement" part, that serves the > same purpose as 'isolinux.bin', but that is compatible with USB-HDD boot. And as far > as I know, the only replacement we can use here is 'ldlinux.sys', which, since we > cannot get it from the ISO, we have to get from somewhere else.The Tails ISO includes utils/{linux/syslinux,win32/syslinux.exe}, that can be used to install a ldlinux.sys that exactly matches the included *.c32 modules. We use the former (utils/linux/syslinux) in Tails Installer when it's run from Tails, and Universal USB Installer uses the latter on Windows. Cheers, -- intrigeri
Hi, intrigeri wrote:> JFTR Tails uses GRUB only for 32-bit UEFI. We use syslinux for BIOS > and 64-bit UEFI.In an ISO that shall boot from DVD ? Please give me an download URL. I just downloaded http://dl.amnesia.boum.org/tails/stable/tails-i386-2.11/tails-i386-2.11.iso which has as volume id: 'TAILS 2.11 - 20170306'. It does not bear any boot starting points for EFI. Neither for DVD nor for HDD. Knoppix 8.0 (distributed with german Linux Magazin issue 04/17) tries to handle EFI by SYSLINUX equipment. I could not yet make a test with real EFI and real DVD. But qemu+OVMF aborts when trying to boot via -cdrom (-hda works fine). https://lists.debian.org/debian-knoppix/2017/04/msg00000.html A problem with general discussion of its EFI equiment is that Knoppix 8.0 is not yet available for download. Have a nice day :) Thomas
Hi, Thomas Schmitt via Syslinux:> intrigeri wrote: >> JFTR Tails uses GRUB only for 32-bit UEFI. We use syslinux for BIOS >> and 64-bit UEFI.> In an ISO that shall boot from DVD ?Tails supports UEFI boot *only* when installed to USB "properly" (either with Tails Installer or Universal USB Installer), i.e. the content of the ISO is extracted to a FAT filesystem. OTOH the isohybrid "dd" installation method, and DVD boot, don't support UEFI so far: in the context of the Tails installation user story, these installation/boot methods are only meant to be used as an intermediary step, and only recommended when installing from OSX (for which we could not find any graphical USB installer that satisfied our needs back when we looked, but perhaps we missed something).> Please give me an download URL.Looks like you've found it already:> I just downloaded > http://dl.amnesia.boum.org/tails/stable/tails-i386-2.11/tails-i386-2.11.iso > which has as volume id: 'TAILS 2.11 - 20170306'. > It does not bear any boot starting points for EFI. Neither for DVD nor > for HDD.Correct.> Knoppix 8.0 (distributed with german Linux Magazin issue 04/17) tries > to handle EFI by SYSLINUX equipment. > I could not yet make a test with real EFI and real DVD. But qemu+OVMF > aborts when trying to boot via -cdrom (-hda works fine). > https://lists.debian.org/debian-knoppix/2017/04/msg00000.html> A problem with general discussion of its EFI equiment is that Knoppix 8.0 > is not yet available for download.Thanks for the info.> Have a nice day :)You too :) Cheers, -- intrigeri
On 2017.04.12 08:29, intrigeri via Syslinux wrote:> The Tails ISO includes utils/{linux/syslinux,win32/syslinux.exe}, that > can be used to install a ldlinux.sys that exactly matches the included > *.c32 modules.That's all very well, but I hope you realize that you are asking for ISO -> USB converting applications to figure out whether distros have a syslinux installer that will apply to the underlying OS, and if so, where it is (being mindful that blindly looking for the first "syslinux.exe" out there might very well yield an ARM executable for Windows RT, so it's not that simple) Saying that there's a "syslinux.exe" somewhere on the ISO is fine if the ISO -> USB conversion process is going to be done manually by a human person. But for an automated application, that has to deal with a myriad of ditsros (and not just tails), not so much... For the purpose of efficiency and size, and because we cannot rely on distros providing a syslinux.exe (which is the exception rather than the norm), Rufus provides it's own integrated Syslinux installer, and it would make very little sense to add an alternate installation path for distros that happen to provide syslinux.exe (as it would then become a support nightmare). Besides the initial point, which is that whatever ISO -> USB conversion application "needs to find a replacement part, that serves the same purpose as 'isolinux.bin', but that is compatible with USB-HDD boot" still stands. Whether that comes from an existing syslinux.exe on the ISO or from elsewhere doesn't change much, as it's not a part we can obtain from the bootloaders that are installed on the ISO, and it must be obtained from somewhere else. Regards, /Pete PS: Resurrecting old discussion is better avoided, as I literally have no idea what the original point was.