> This should all be part of isohybrid now, but I have a vague recollection that one of the patches I sent upstream hadn't been merged yet - I'll check that.
Thanks!
> If you need it to be writeable then it's probably not worth most of this complexity, since it's mostly there in order to support booting off CD. Just generate a VFAT filesystem with an EFI bootloader under /EFI/BOOT and use syslinux to make it bootable on BIOS systems.
The Apple partition map and the El Torito image don't matter, sure, but the GPT/MBR hybrid image would still matter, right? Do systems require anything else besides that to reliably boot the same USB disk via either EFI or BIOS?
> Using separate bootloaders is basically a requirement. We're using isolinux for the BIOS side and grub for the EFI side. Long-run, we can probably consolidate on grub2 for all of it.
I had GRUB2 in mind, yes. :) Ideally, though, I'd love to see a single GRUB2 image that knows how to handle booting via either EFI or BIOS, rather than two separate GRUB2 images each with their own separate set of modules (since GRUB2 modules only work with the GRUB2 image they built against, and since the modules curently choose BIOS or EFI at compile time as well).
Power management, mobile and firmware developer on Linux. Security developer at Aurora. Ex-biologist. mjg59 on Twitter. Content here should not be interpreted as the opinion of my employer. Also on Mastodon.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
no subject
Date: 2012-05-02 02:39 pm (UTC)Thanks!
> If you need it to be writeable then it's probably not worth most of this complexity, since it's mostly there in order to support booting off CD. Just generate a VFAT filesystem with an EFI bootloader under /EFI/BOOT and use syslinux to make it bootable on BIOS systems.
The Apple partition map and the El Torito image don't matter, sure, but the GPT/MBR hybrid image would still matter, right? Do systems require anything else besides that to reliably boot the same USB disk via either EFI or BIOS?
> Using separate bootloaders is basically a requirement. We're using isolinux for the BIOS side and grub for the EFI side. Long-run, we can probably consolidate on grub2 for all of it.
I had GRUB2 in mind, yes. :) Ideally, though, I'd love to see a single GRUB2 image that knows how to handle booting via either EFI or BIOS, rather than two separate GRUB2 images each with their own separate set of modules (since GRUB2 modules only work with the GRUB2 image they built against, and since the modules curently choose BIOS or EFI at compile time as well).