New -as mkisofs option -appended_gpt_with_gaps
This commit is contained in:
@ -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 01, 2024"
|
||||
.TH XORRISOFS 1 "Version 1.5.7, Nov 17, 2024"
|
||||
.\" Please adjust this date whenever revising the manpage.
|
||||
.\"
|
||||
.\" Some roff macros, for reference:
|
||||
@ -1430,6 +1430,8 @@ of the cylinder size.
|
||||
Beware of subsequent multi\-session runs. The appended partition will get
|
||||
overwritten.
|
||||
.br
|
||||
With \fBMBR\fR:
|
||||
.br
|
||||
partition_number may be 1 to 4. Number 1 will put the whole ISO image into
|
||||
the unclaimed space before partition 1. So together with most xorriso MBR
|
||||
or GPT features, number 2 would be the most natural choice.
|
||||
@ -1452,6 +1454,22 @@ type "Apple_HFS", any other to "Data".
|
||||
If some other command causes the production of GPT, then the appended
|
||||
partitions will be mentioned there too, even if not \-appended_part_as_gpt
|
||||
is given.
|
||||
.br
|
||||
\fBGPT\fR can be forced by option \-appended_part_as_gpt.
|
||||
.br
|
||||
partition_number may be 1 to 8. But other than with MBR partitions it is not
|
||||
guaranteed that the resulting GPT partition will have this number, because
|
||||
it might get occupied by a partition entry which fills a gap in the coverage
|
||||
of the whole emerging image.
|
||||
.br
|
||||
The chance to get the desired partition number is increased much by
|
||||
option \-appended_gpt_with_gaps.
|
||||
.br
|
||||
The type_code may be the same as described with MBR. Given GUIDs are used
|
||||
unchanged. Given MBR partition types get translated. 0xef becomes
|
||||
C12A7328\-F81F\-11D2\-BA4B\-00A0C93EC93B, others become
|
||||
EBD0A0A2\-B9E5\-4433\-87C0\-68B6B72699C7.
|
||||
.br
|
||||
.TP
|
||||
\fB\-appended_part_as_gpt\fR
|
||||
Marks partitions from \-append_partition in GPT rather than in MBR.
|
||||
@ -1479,6 +1497,22 @@ parameter partition_number.
|
||||
By default, appended partitions get marked in APM only if APM is produced
|
||||
because of other options and \-part_like_isohybrid is enabled.
|
||||
.TP
|
||||
\fB\-appended_gpt_with_gaps\fR
|
||||
Possibly leave some parts of the resulting image unclaimed by partitions in
|
||||
the emerging GPT in order to increase he chance to get in GPT the
|
||||
partition numbers given with option \-append_partition.
|
||||
.br
|
||||
The ISO 9660 filesystem gets marked by a GPT partition
|
||||
only if none of the appended partitions has partition number 1,
|
||||
and if no other command causes a partition inside the emerging ISO 9660
|
||||
filesystem, and if \-partition_offset is 16.
|
||||
.br
|
||||
If this option is not given, then gap filling partitions will be inserted
|
||||
so that no part of the emerging image after block 16 is unclaimed by GPT
|
||||
partitions. This happens only if partitions get appended and a valid GPT
|
||||
emerges, e.g. by option \-appended_part_as_gpt.
|
||||
Commands which produce isohybrid\-style invalid GPT disable gap filling.
|
||||
.TP
|
||||
\fB\-efi-boot-part\fR disk_path
|
||||
Copy a file from disk into the emerging ISO image and mark it by a GPT entry as
|
||||
EFI System Partition. EFI boot firmware is supposed to use a FAT filesystem
|
||||
|
Reference in New Issue
Block a user