On 2024.01.30 08:49, Thomas Schmitt via Libcdio-devel wrote:
The specs do not prescribe a particular sequence of boot images or their
position within the overall body of an ISO 9660 filesystem.
The specs do not prescribe that an image should contain extra garbage.
It is implied.
You can of c
Hi,
Pete Batard wrote:
> If you are
> going to set a EFI partition to a size of 0 or 1, then the image will occupy
> all sectors from the LSN to the end of the volume.
I understand that this was specified as a last resort because
- UEFI did not want to invent a new competitor to El Torito,
- the
Hi all,
So... we have a problem:
On 2024.01.29 15:04, Thomas Schmitt via Libcdio-devel wrote:
Pete Batard wrote:
I'll just add that I didn't formally test this, since I haven't had a chance
to locate an ISO with a > 32MB El-Torito image yet.
You can build yourself one:
- Get legacy PC-BIOS
Hi,
Pete Batard wrote:
> I'll just add that I didn't formally test this, since I haven't had a chance
> to locate an ISO with a > 32MB El-Torito image yet.
You can build yourself one:
- Get legacy PC-BIOS boot image isolinux.bin from e.g. a Debian netinst
ISO:
xorriso -osirrox on -indev d
I'll just add that I didn't formally test this, since I haven't had a
chance to locate an ISO with a > 32MB El-Torito image yet.
I did however validate, with the test El-Torito image, that if you
remove the "(max_lsn - p_iso->boot_img[k].lsn) >= 0x4000" condition, you
got the warning in iso-in
