libburnia/libisoburn
2
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Clarified that El Torito images for EFI always get their own size as load size

Browse Source
This commit is contained in:
Thomas Schmitt
2024-12-20 17:37:29 +01:00
parent 362a17c571
commit 23f28b97e5
6 changed files with 96 additions and 90 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
xorriso/xorrisofs.texi
View File

@ -50,7 +50,7 @@
@c man .\" First parameter, NAME, should be all caps
@c man .\" Second parameter, SECTION, should be 1-8, maybe w/ subsection
@c man .\" other parameters are allowed: see man(7), man(1)
@c man .TH XORRISOFS 1 "Version 1.5.7, Nov 17, 2024"
@c man .TH XORRISOFS 1 "Version 1.5.7, Dec 20, 2024"
@c man .\" Please adjust this date whenever revising the manpage.
@c man .\"
@c man .\" Some roff macros, for reference:
@ -1486,10 +1486,12 @@ Nevertheless the default setting of mkisofs is to use the full size of the
boot image rounded up to a multiple of 4 512-byte blocks. This default
may be explicitly enforced by the word "full" instead of a number.
@*
EFI boot images usually get set the number of blocks occupied
EFI boot images always get set the number of blocks occupied
by the boot image file.
@*
El Torito cannot represent load sizes higher than 65535.
EFI images which exceed the maximum size get size 0 or 1, which means
"up to the end of the device" according to the UEFI specification.
@c man .TP
@item -hard-disk-boot
@kindex -hard-disk-boot El Torito boot image emulation