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.1
View File

@ -9,7 +9,7 @@
.\" First parameter, NAME, should be all caps
.\" Second parameter, SECTION, should be 1-8, maybe w/ subsection
.\" other parameters are allowed: see man(7), man(1)
.TH XORRISOFS 1 "Version 1.5.7, Nov 17, 2024"
.TH XORRISOFS 1 "Version 1.5.7, Dec 20, 2024"
.\" Please adjust this date whenever revising the manpage.
.\"
.\" Some roff macros, for reference:
@ -1112,10 +1112,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.
.br
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.
.br
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.
.TP
\fB\-hard-disk-boot\fR
Mark the boot image in the current catalog entry as emulated hard disk.