Mentioned in the man page the increased number of appended GPT partitions in libisofs

xorriso/xorriso.1

@@ -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 XORRISO 1 "Version 1.5.7, Aug 07, 2023"
+.TH XORRISO 1 "Version 1.5.7, May 07, 2024"
 .\" Please adjust this date whenever revising the manpage.
 .\"
 .\" Some roff macros, for reference:
@@ -1394,7 +1394,8 @@ pattern expansion happens. The current \-cdi directory has no influence.
 \fB\-cut_out\fR disk_path byte_offset byte_count iso_rr_path
 Map a byte interval of a regular disk file or of a device file into a regular
 file in the ISO image. The file depicted by disk_path has to support random
-read access.
+read access. A symbolic link will only work if enabled by \-follow "link" or
+"param".
 .br
 Cutting out a byte interval may be necessary if the disk file is larger than
 a single medium, or if it exceeds the traditional limit of 2 GiB \- 1 for old
@@ -1565,7 +1566,7 @@ Keep in mind that there may be alternative paths to the same disk file. The
 exclusion tests are done literally, so that they do not keep files from getting
 into the ISO filesystem by other paths. Accordingly an exclusion does not
 prevent a disk file from being overwritten by file extraction via an
-alternative not excluded path. So the exlusions need to be coordinated with
+alternative not excluded path. So the exclusions need to be coordinated with
 the actual disk_path parameters given with commands.
 .br
 (Do not forget to end the list of disk_paths by "\-\-")
@@ -1585,10 +1586,10 @@ handled as one parameter for \-not_paths or \-not_leaf.
 .TP
 \fB\-follow\fR occasion[:occasion[...]]
 Enable or disable resolution of symbolic links and mountpoints under
-disk_paths. This applies to actions \-add, \-du*x, \-ls*x, \-findx, \-concat,
-and to \-disk_pattern expansion.
+disk_paths. This applies to actions \-add, \-cut_out, \-du*x, \-ls*x, \-findx,
+\-concat, and to \-disk_pattern expansion.
 .br
-There are three kinds of follow decisison to be made:
+There are three main kinds of follow decisison to be made:
 .br
 \fBlink\fR is the hop from a symbolic link to its target file object for the
 purpose of reading. I.e. not for command \-concat.
@@ -1613,7 +1614,7 @@ expansion).
 If enabled then \-ls*x will show the link targets rather than the links
 themselves. \-du*x, \-findx, and \-add will process the link targets but not
 follow links in an eventual directory tree below the targets (unless "link"
-is enabled). 
+is enabled). \-cut_out will process link targets.
 .br
 Occasions can be combined in a colon separated list. All occasions
 mentioned in the list will then lead to a positive follow decision. 
@@ -3633,7 +3634,7 @@ and their designated fate.
 .br
 Examples:
 .br
-Drop unknown El Torito:
+Drop El Torito:
 .br
  \-boot_image any discard
 .br
@@ -3851,6 +3852,7 @@ Use this to discard an MBR which was loaded with the ISO image.
 \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.
+The number of appendable partitions with GPT is 8 rather than 4 with MBR.
 .br
 \fBappended_part_as=mbr\fR is the default. Appended partitions get
 marked in GPT only if GPT is produced because of other settings.
@@ -3858,7 +3860,8 @@ If given explicitly, this clears setting "gpt" and "apm". Nevertheless "apm"
 may be added to "mbr".
 .br
 \fBappended_part_as=apm\fR marks partitions from \-append_partition in APM
-additionally to "mbr" or "gpt".
+additionally to "mbr" or "gpt". The partition number in APM will not be
+influenced by \-append_partition parameter partition_number.
 .br
 By default, appended partitions get marked in APM only if APM is
 produced because of other options together with part_like_isohybrid="on".
@@ -4033,9 +4036,11 @@ of the cylinder size.
 Beware of subsequent multi\-session runs. The appended partition will get
 overwritten.
 .br
-Partitions may be appended with boot block type MBR and with SUN Disk Label.
+Partitions may be appended with partition table types MBR, GPT, and
+SUN Disk Label. Additionally to MBR and GPT it is possible to have them
+marked in APM.
 .br
-With MBR:
+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 \fBxorriso\fR
@@ -4055,11 +4060,30 @@ In APM, 48465300\-0000\-11AA\-AA11\-00306543ECAC will be mapped to partition
 type "Apple_HFS", any other to "Data".
 .br
 If some other command causes the production of GPT, then the appended
-partitions will be mentioned there too. GPT can be forced by
+partitions will be mentioned there too.
+.br
+\fBGPT\fR can be forced by
 .br
  \-boot_image "any" "appended_part_as=gpt"
 .br
-With SUN Disk Label (selected by \-boot_image any sparc_label=):
+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.
+.br
+More important than the desired partition number will be that the resulting
+ISO filesystem is covered gaplessly with GPT table and its partitions and that
+the partitions in the table are sorted by block address. If partition_number is
+higher than the number of preceding partitions, then the appropriate number of
+empty partition entries is inserted to achieve the desired partition_number.
+If the number of preceding partitions is too high, then a NOTE message informs
+about the inability to achieve partition_number and about the actually assigned
+number.
+.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
+\fBSUN Disk Label\fR is chosen by \-boot_image any sparc_label=.
 .br
 partition_number may be 2 to 8. Number 1 will always be the ISO image.
 Partition start addresses are aligned to 320 KiB. The type_code does not
@@ -5167,7 +5191,7 @@ manipulation commands like \-rm or \-find ... \-exec rm before extraction,
 and end the program by \-rollback_end .
 .br
 Excluded disk_path parameters of extraction commands cause SORRY events.
-Implicitely given paths in trees under disk_path parameters are excluded
+Implicitly given paths in trees under disk_path parameters are excluded
 silently.
 .br
 If disk file objects already exist then the settings of \-overwrite and
@@ -6713,7 +6737,7 @@ Thomas Schmitt <scdbackup@gmx.net>
 .br
 for libburnia\-project.org
 .SH COPYRIGHT
-Copyright (c) 2007 \- 2023 Thomas Schmitt
+Copyright (c) 2007 \- 2024 Thomas Schmitt
 .br
 Permission is granted to distribute this text freely. It shall only be
 modified in sync with the technical properties of \fBxorriso\fR.