Documentation changes of rev 3480

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 "Oct 18, 2010"
+.TH XORRISO 1 "Nov 05, 2010"
 .\" Please adjust this date whenever revising the manpage.
 .\"
 .\" Some roff macros, for reference:
@@ -2241,7 +2241,8 @@ can assume overwriteable media.
 .br
 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.
+MIPS Volume Header for old SGI computers, DEC Boot Block for old DECstation,
+SUN Disk Label for SPARC machines.
 .br
 The boot firmware EFI may use programs which are located in a FAT filesystem
 and announced by an MBR partition table entry.
@@ -2418,32 +2419,47 @@ partition offset. 0 chooses a default value.
 partition offset. 0 chooses a default value.
 .br
 \fBmips_path=\fRiso_rr_path declares a data file in the image to be a
-MIPS Big Endian boot file. Enable production of a MIPS Big Endian Volume
-Header. This is mutually exclusive with MBR production and mipsel_path=.
+MIPS Big Endian boot file and causes production of a MIPS Big Endian Volume
+Header. This is mutually exclusive with production of other boot blocks
+like MBR.
 It will overwrite the first 512 bytes of any data eventually provided by
 system_area=.
 Up to 15 boot files can be declared by mips_path=.
 .br
 \fBmipsel_path=\fRiso_rr_path declares a data file in the image to be the
-MIPS Little Endian boot file. This is mutually exclusive with MBR production
-and mips_path=. It will overwrite the first 512 bytes of any data eventually
+MIPS Little Endian boot file. This is mutually exclusive with other boot
+blocks.
+It will overwrite the first 512 bytes of any data eventually
 provided by system_area=.
 Only a single boot file can be declared by mipsel_path=.
 .br
-\fBmips_discard\fR revokes any boot file declarations made by mips_path=.
-This removes the ban on MBR production.
+\fBsparc_label=\fRtext causes the production of a SUN Disk Label with the
+given text as ASCII label. This boot block format allows to append images
+for partitions 2 to 8. Partition 1 will always be the ISO image.
+See option -append_partition.
+The first 512 bytes of any data eventually provided
+by system_area= will be overwritten.
+.br
+\fBmips_discard\fR and \fBsparc_discard\fR revoke any boot file
+declarations made by mips_path= or mipsel_path=. They also disable production
+of SUN Disk Label.
+This removes the ban on production of other boot blocks.
 .br
 .br
 .TP
 \fB\-append_partition\fR partition_number type_code disk_path
 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.
+described by a partition table entry in a boot block 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.
 .br
 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.
+.br
+With MBR:
+.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
 features, number 2 would be the most natural choice.
@@ -2455,6 +2471,15 @@ yield usable results. For a list of codes search the Internet for
 .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
+With SUN Disk Label (selected 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
+matter. Submit 0x0.
+.br
+Partition image name "." causes the partition to become a copy of the next
+lower valid one.
 .TP
 .B Jigdo Template Extraction:
 .PP

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 19, 2010"
+@c man .TH XORRISO 1 "Nov 05, 2010"
 @c man .\" Please adjust this date whenever revising the manpage.
 @c man .\"
 @c man .\" Some roff macros, for reference:
@@ -2699,7 +2699,8 @@ 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.
+MIPS Volume Header for old SGI computers, DEC Boot Block for old DECstation,
+SUN Disk Label for SPARC machines.
 @*
 The boot firmware EFI may use programs which are located in a FAT filesystem
 and announced by an MBR partition table entry.
@@ -2889,20 +2890,32 @@ partition offset. 0 chooses a default value.
 @*
 @cindex MIPS boot file, activation
 @strong{mips_path=}iso_rr_path declares a data file in the image to be a
-MIPS Big Endian boot file. Enable production of a MIPS Big Endian Volume
-Header. This is mutually exclusive with MBR production and mipsel_path=.
+MIPS Big Endian boot file and causes production of a MIPS Big Endian Volume
+Header. This is mutually exclusive with production of other boot blocks
+like MBR.
 It will overwrite the first 512 bytes of any data eventually provided by
 system_area=.
 Up to 15 boot files can be declared by mips_path=.
 @*
 @strong{mipsel_path=}iso_rr_path declares a data file in the image to be the
-MIPS Little Endian boot file. This is mutually exclusive with MBR production
-and mips_path=. It will overwrite the first 512 bytes of any data eventually
+MIPS Little Endian boot file. This is mutually exclusive with other boot
+blocks.
+It will overwrite the first 512 bytes of any data eventually
 provided by system_area=.
 Only a single boot file can be declared by mipsel_path=.
 @*
-@strong{mips_discard} revokes any boot file declarations made by mips_path=.
-This removes the ban on MBR production.
+@cindex SUN Disk Label, production
+@strong{sparc_label=}text causes the production of a SUN Disk Label with the
+given text as ASCII label. This boot block format allows to append images
+for partitions 2 to 8. Partition 1 will always be the ISO image.
+See option -append_partition.
+The first 512 bytes of any data eventually provided
+by system_area= will be overwritten.
+@*
+@strong{mips_discard} and @strong{sparc_discard} revoke any boot file
+declarations made by mips_path= or mipsel_path=. They also disable production
+of SUN Disk Label.
+This removes the ban on production of other boot blocks.
 @*
 @end table
 @*
@@ -2913,13 +2926,17 @@ This removes the ban on MBR production.
 @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.
+described by a partition table entry in a boot block 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.
 @*
+Partitions may be appended with boot block type MBR and with SUN Disk Label.
+@*
+With MBR:
+@*
 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.
@@ -2931,6 +2948,16 @@ yield usable results. For a list of codes search the Internet for
 @*
 The disk_path must provide the necessary data bytes at commit time.
 An empty disk_path disables this feature for the given partition number.
+@*
+@cindex SUN SPARC boot images, activation
+With SUN Disk Label (selected by -boot_image any sparc_label=):
+@*
+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
+matter. Submit 0x0.
+@*
+Partition image name "." causes the partition to become a copy of the next
+lower valid one.
 @end table
 @c man .TP
 @c man .B Jigdo Template Extraction: