On 10/11/19 12:42 PM, александр епанешников via arch-releng wrote:
thanks for answers.
One for USB EFI boot, the other for the vintage DVD/CD mode in EFI ("El Torito")
wear i can read about Torito? because now i don't understand fully "how boot segment of archiso built?"
For traditional bios firmware, this is done "magically" by these lines: -eltorito-boot isolinux/isolinux.bin -eltorito-catalog isolinux/boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table and for efi firmware with (at last) -eltorito-alt-boot -e EFI/archiso/efiboot.img -no-emul-boot -isohybrid-gpt-basdat" in mkarchiso this requires more work, because efiboot.img must be prepared this is just a vfat fs inside (done at build.sh)
11.10.2019 17:28, Gerardo Exequiel Pozzi via arch-releng пишет:
On 10/6/19 2:38 PM, Alexandr Epaneshnikov via arch-releng wrote:
hello. since i work on #63166 https://bugs.archlinux.org/task/63166?project=6i have sum questions about archiso project.
As far as I understand, two loaders are used. syslinux for bios and systemd-boot for efi. is it so? and why it is so?
* because systemd-boot does not support non-efi * syslinux may not work on efi (at least it does for few machines I tested). * systemd-boot is the... maybe bring most features to systemd...
i modified syslinux config
https://github.com/alex19EP/talkingarch/raw/accessible-upstreem/configs/rele...
to add another entry with kernel cmdline options. do i need to add another file in configs/releng/efiboot/loader/entries for efi support?
yes
why are archiso-x86_64-cd.conf and archiso-x86_64-usb.conf?
One for USB EFI boot, the other for the vintage DVD/CD mode in EFI ("El Torito")
thanks.