Bug fix: -as mkisofs -no-emul-boot without -boot-load-size defaulted to size 4

This commit is contained in:
2016-11-13 11:13:33 +01:00
parent 76ac0d87a8
commit 8adbb1de7e
13 changed files with 194 additions and 129 deletions

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.4.7, Sep 16, 2016"
@c man .TH XORRISOFS 1 "Version 1.4.7, Nov 09, 2016"
@c man .\" Please adjust this date whenever revising the manpage.
@c man .\"
@c man .\" Some roff macros, for reference:
@ -1270,7 +1270,7 @@ the ISO image.
The content of the boot image files is not in the scope of El Torito.
@*
xorriso composes the boot catalog according to the boot image
files given and structured by options -b, -e, -el-torito-alt-boot,
files given and structured by options -b, -e, -eltorito-alt-boot,
and @minus{}@minus{}efi-boot. Often it contains only one entry.
@*
Normally the boot images are data files inside the ISO filesystem. By
@ -1339,12 +1339,17 @@ Perform -eltorito-alt-boot, option -e with the given
iso_rr_path, -no-emul-boot, and again -eltorito-alt-boot. This gesture is
used for achieving EFI-bootability of the GRUB2 rescue CD.
@c man .TP
@item -boot-load-size number
@item -boot-load-size number|"full"
@kindex -boot-load-size El Torito boot image load size
@cindex Bootability, boot image load size, -boot-load-size
Set the number of 512-byte blocks to be loaded at boot time
from the boot image in the current catalog entry.
@*
Non-emulating BIOS bootimages usually need a load size of 4.
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 explicitely enforced by the word "full" instead of a number.
@*
EFI boot images usually get set the number of blocks occupied
by the boot image file.
@*