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

Bug fix: -boot_image system_area=/dev/zero preserved system area of loaded ISO

Browse Source
This commit is contained in:
Thomas Schmitt
2024-05-13 12:22:04 +02:00
parent c8fab513c6
commit 4dc5edc565
5 changed files with 121 additions and 104 deletions
Download Patch File Download Diff File Expand all files Collapse all files

31
xorriso/xorriso.1
View File

@ -3767,13 +3767,27 @@ which can be used to boot from USB stick or hard disk.
Other than an El Torito boot image, the file disk_path needs not to be added
to the ISO image.
.br
In multi\-session situations the existing System Area is preserved by default.
In in this case, the special disk_path "." prevents reading of
a disk file but nevertheless causes adjustments in the
loaded system area data. Such adjustments may get ordered by \-boot_image
commands.
.br
Special "system_area=/dev/zero" causes 32k of 0\-bytes.
Use this to e.g. discard partition tables which were loaded with the ISO image.
.br
This setting is the default with the write method of Modifying, when \-indev
and \-outdev are both used and not the same drive. If you indeed need to copy
the unchanged system area from \-indev to \-outdev, use
"system_area=\-\-interval:imported_iso:0s\-15s::" , which was the default in older
versions of xorriso.
.br
\fB\-boot_image isolinux system_area=\fR implies "partition_table=on".
In this case, the disk path should lead to one of the SYSLINUX files
isohdp[fp]x*.bin or to a file which was derived from one of those files.
E.g. to the first 512 bytes from an ISOLINUX isohybrid ISO image.
.br
In this case, El Torito boot images (dir=, bin_path=, efi_path=)
may be augmented by
El Torito boot images (dir=, bin_path=, efi_path=) may then be augmented by
\fBisolinux partition_entry=gpt_basdat\fR
or \fBisolinux partition_entry=gpt_hfsplus\fR,
and by \fBisolinux partition_entry=apm_hfsplus\fR.
@ -3783,12 +3797,6 @@ The first three GPT partitions will also be marked by MBR partitions. The
MBR partition of type 0xEF is what actually is used by EFI firmware for
booting from USB stick.
.br
In multi\-session situations the existing System Area is preserved by default.
In in this case, the special disk_path "." prevents reading of
a disk file but nevertheless causes adjustments in the
loaded system area data. Such adjustments may get ordered by \-boot_image
commands.
.br
\fB\-boot_image any gpt_disk_guid=\fRvalue controls whether an emerging GPT
shall get a randomly generated disk GUID or whether the GUID is supplied by
the user.
@ -3856,9 +3864,6 @@ In this case the existing System Area gets checked whether it bears addresses
and sizes as if it had been processed by "partition_table=on". If so,
then those parameters get updated when the new System Area is written.
.br
Special "system_area=/dev/zero" causes 32k of NUL\-bytes.
Use this to discard an MBR which was loaded with the ISO image.
.br
\fBappended_part_as=gpt\fR marks partitions from \-append_partition
in GPT rather than in MBR. In this case the MBR shows a single partition
of type 0xee which covers the whole output data.
@ -4014,8 +4019,8 @@ DEC Alpha SRM Secondary Bootstrap Loader and causes production of a boot sector
which points to it.
This is mutually exclusive with production of other boot blocks like MBR.
.br
\fBmips_discard\fR, \fBsparc_discard\fR, \fBhppa_discard\fR,
\fBalpha_discard\fR
\fBmips_discard\fR, \fBmipsel_discard\fR, \fBsparc_discard\fR,
\fBhppa_discard\fR, \fBalpha_discard\fR
revoke any boot file declarations made for mips/mipsel, sparc, hppa,
or alpha, respectively.
This removes the ban on production of other boot blocks.