New option -append_partition, -as mkisofs -append_partition

libisoburn/trunk/xorriso/xorriso.texi

@@ -44,7 +44,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 XORRISO 1 "Oct 15, 2010"
+@c man .TH XORRISO 1 "Oct 18, 2010"
 @c man .\" Please adjust this date whenever revising the manpage.
 @c man .\"
 @c man .\" Some roff macros, for reference:
@@ -714,7 +714,7 @@ inner dashes are interpreted as underscores.
 * Filter::              Filters for data file content
 * Writing::             Writing the result, drive control
 * SetWrite::            Settings for result writing
-* Bootable::            El Torito bootable ISO images
+* Bootable::            Bootable ISO images
 * Jigdo::               Jigdo Template Extraction
 * Charset::             Character sets
 * Exception::           Exception processing
@@ -2677,9 +2677,9 @@ xorriso adds the traditional 300k of padding by default to all images.
 For images which will never get to a CD it is safe to use -padding 0 .
 @end table
 @c man .TP
-@c man .B El Torito bootable ISO images:
+@c man .B Bootable ISO images:
 @node Bootable, Jigdo, SetWrite, Options
-@section El Torito bootable ISO images
+@section Bootable ISO images
 @c man .PP
 Contrary to published specifications many BIOSes will load an El Torito
 record from the first session on media and not from the last one, which
@@ -2696,6 +2696,14 @@ it is advised to patch it
 when a follow-up session gets written. But one should not rely on the
 capability to influence the bootability of the existing sessions, unless one
 can assume overwriteable media.
+@*
+There are booting mechanisms which do not use an El Torito record but rather
+start at the first bytes of the image: PC-BIOS MBR for hard-disk-like devices,
+MIPS Volume Header for old SGI computers, DEC Boot Block for old DECstation.
+@*
+The boot firmware EFI may use programs which are located in a FAT filesystem
+and announced by an MBR partition table entry.
+@*
 @table @asis
 @sp 1
 @c man .TP
@@ -2897,6 +2905,33 @@ Only a single boot file can be declared by mipsel_path=.
 This removes the ban on MBR production.
 @*
 @end table
+@*
+@table @asis
+@sp 1
+@c man .TP
+@item -append_partition partition_number type_code disk_path
+@kindex -append_partition   adds arbitrary file after image end
+@cindex Appended Filesystem Image, -append_partition
+Cause a prepared filesystem image to be appended to the ISO image and to be
+described by a partition table entry in an MBR at the start of the emerging
+ISO image. The partition entry will bear the size of the submitted file
+rounded up to the next multiple of 2048 bytes.
+@*
+Beware of subsequent multi-session runs. The appended partition will get
+overwritten.
+@*
+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
+features, number 2 would be the most natural choice.
+@*
+The type_code may be "FAT12", "FAT16", "Linux",
+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".
+@*
+The disk_path must provide the necessary data bytes at commit time.
+An empty disk_path disables this feature for the given partition number.
+@end table
 @c man .TP
 @c man .B Jigdo Template Extraction:
 @node Jigdo, Charset, Bootable, Options
@@ -4071,6 +4106,8 @@ instead of -G to apply the effect of -boot_image isolinux partition_table=on.
 @minus{}partition_offset number is
 @minus{}boot_image any partition_offset=number.
 @*
+Option @minus{}append_partition is supported.
+@*
 The options of genisoimage Jigdo Template Extraction are recognized and
 performed via xorriso option -jigdo. See the "Alias:" names there for the
 meaning of the genisoimage options.