New -boot_image bootspec "appended_part_as=", new -as mkisofs option -appended_part_as_gpt

libisoburn/trunk/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.3.9, Jan 29, 2015"
+.TH XORRISO 1 "Version 1.3.9, Feb 06, 2015"
 .\" Please adjust this date whenever revising the manpage.
 .\"
 .\" Some roff macros, for reference:
@@ -3126,6 +3126,13 @@ then those parameters get updated when the new System Area is written.
 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.
+.br
+\fBappended_part_as=mbr\fR is the default. Appended partitions get
+marked in GPT only if GPT is produced because of other settings. 
+.br
 \fBchrp_boot_part=on\fR causes a single partition in MBR which covers
 the whole ISO image and has type 0x96. This is not compatible with any
 other feature that produces MBR partition entries. It makes GPT unrecognizable.
@@ -3272,6 +3279,9 @@ or a hexadecimal number between 0x00 and 0xff. Not all those numbers will
 yield usable results. For a list of codes search the Internet for
 "Partition Types" or run fdisk command "L".
 .br
+If some other command causes the production of GPT, then the appended
+partitions will be mentioned there too. 
+.br
 The disk_path must provide the necessary data bytes at commit time.
 An empty disk_path disables this feature for the given partition number.
 .br