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
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
---
src/iso-info.c | 14 +++---
1 file changed, 11 insertions(+), 3 deletions(-)
diff --git a/src/iso-info.c b/src/iso-info.c
index cfca76f7..8cba3111 100644
--- a/src/iso-info.c
+++ b/src/iso-info.c
@@ -87,6 +87,7 @@ static struct arguments
intno_joliet;
int
---
test/Makefile.am| 10 +++
test/check_eltorito.sh | 57
test/data/eltorito.iso | Bin 0 -> 55296 bytes
test/data/eltorito_file | Bin 0 -> 512 bytes
test/eltorito.right | 12 +
test/no_eltorito.right | 8 ++
6 files ch
---
include/cdio/util.h| 7 +++
lib/driver/libcdio.sym | 2 ++
lib/driver/util.c | 29 +
3 files changed, 38 insertions(+)
diff --git a/include/cdio/util.h b/include/cdio/util.h
index 9cca8f9f..e19fd4ac 100644
--- a/include/cdio/util.h
+++ b/include/cdio
Changes from v2:
* Fix trailing whitespace
* Support big-endian platforms
* Handle images that don't place the expandable image(s) at the end of the
volume.
With this iso-info now produces the expected result on an xorriso generated
test image:
/[boot]/:
- [LSN 20514] 2048 Jan 29 2024 2
Enables the El Torito boot images to be listed and extracted from a virtual
"[BOOT]/" root directory. Limited to 8 maximum images and only for No Emulation.
El Torito support can be enabled or disabled through ISO_EXTENSION_EL_TORITO.
The naming convention of the virtual images follows what 7-zip
