Enabled use of libisofs interval reader in xorriso
This commit is contained in:
@ -50,7 +50,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 XORRISOFS 1 "Version 1.3.9, Feb 28, 2015"
|
||||
@c man .TH XORRISOFS 1 "Version 1.3.9, Apr 21, 2015"
|
||||
@c man .\" Please adjust this date whenever revising the manpage.
|
||||
@c man .\"
|
||||
@c man .\" Some roff macros, for reference:
|
||||
@ -1394,6 +1394,64 @@ MBR boot code. All three do not hamper El Torito booting from CDROM.
|
||||
MIPS Big Endian (SGI), MIPS Little Endian (DEC), SUN SPARC, HP-PA, DEC Alpha.
|
||||
Those are mutually not combinable and also not combinable with MBR, GPT,
|
||||
or APM.
|
||||
@c man .PP
|
||||
@sp 1
|
||||
@cindex Interval reader for system area and partitions
|
||||
Several of the following options expect disk paths as input but also accept
|
||||
description strings for the libisofs interval reader, which is able to cut
|
||||
out data from disk files or -indev and to zeroize parts of the content:
|
||||
-G, -generic-boot, @minus{}@minus{}embedded-boot, @minus{}@minus{}grub2-mbr,
|
||||
-isohybrid-mbr, -efi-boot-part, -prep-boot-part, -B, -sparc-boot,
|
||||
-append_partition.
|
||||
@*
|
||||
The description string consists
|
||||
of the following components, separated by colon ':'
|
||||
@*
|
||||
"@minus{}@minus{}interval:"Flags":"Interval":"Zeroizers":"Source
|
||||
@*
|
||||
The component "@minus{}@minus{}interval" states that this is not
|
||||
a plain disk path but rather a interval reader description string.
|
||||
@*
|
||||
The component Flags modifies the further interpretation:
|
||||
@*
|
||||
"local_fs" demands to read from a file depicted by the path in Source.
|
||||
@*
|
||||
"imported_iso" demands to read from the -indev. This works only if -outdev
|
||||
is not the same as -indev. The Source component is ignored.
|
||||
@*
|
||||
The component Interval consists of two byte address numbers separated by a "-" character. E.g. "0-429" means to read bytes 0 to 429.
|
||||
@*
|
||||
The component Zeroizers consists of zero or more comma separated strings.
|
||||
They define which part of the read data to zeroize. Byte number 0 means
|
||||
the byte read from the Interval start address.
|
||||
Each string may be one of:
|
||||
@*
|
||||
"zero_mbrpt" demands to zeroize the MBR partition table if
|
||||
bytes 510 and 511 bear the MBR signature 0x55 0xaa.
|
||||
@*
|
||||
"zero_gpt" demands to check for a GPT header in bytes 512 to 1023,
|
||||
to zeroize it and its partition table blocks.
|
||||
@*
|
||||
"zero_apm" demands to check for an APM block 0 and to zeroize
|
||||
its partition table blocks.
|
||||
@*
|
||||
Start_byte"-"End_byte demands to zeroize the read-in bytes beginning
|
||||
with number Start_byte and ending after End_byte.
|
||||
@*
|
||||
The component Source is the file path with flag "local_fs", and ignored with
|
||||
flag "imported_iso".
|
||||
@*
|
||||
Byte numbers may be scaled by a suffix out of @{k,m,g,t,s,d@} meaning
|
||||
multiplication by @{1024, 1024k, 1024m, 1024g, 2048, 512@}. A scaled value
|
||||
end number depicts the last byte of the scaled range.
|
||||
@*
|
||||
E.g. "0d-0d" is "0-511".
|
||||
@*
|
||||
Examples:
|
||||
@*
|
||||
"local_fs:0-32767:zero_mbrpt,zero_gpt,440-443:/tmp/template.iso"
|
||||
@*
|
||||
"imported_iso:45056d-47103d::"
|
||||
@*
|
||||
@table @asis
|
||||
@sp 1
|
||||
@ -1498,22 +1556,25 @@ So the value defined here is only in effect if a new ISO image gets written.
|
||||
@item -partition_hd_cyl number
|
||||
@kindex -partition_hd_cyl MBR heads per cylinder
|
||||
@cindex MBR, sectors per head, -partition_sec_hd
|
||||
Set the number of heads per cylinder for the partition table.
|
||||
Set the number of heads per cylinder for the MBR partition table.
|
||||
0 chooses a default value. Maximum is 255.
|
||||
@c man .TP
|
||||
@item -partition_sec_hd number
|
||||
@kindex -partition_sec_hd MBR sectors per head
|
||||
@cindex MBR, sectors per head, -partition_sec_hd
|
||||
Set the number of sectors per head for the partition table.
|
||||
Set the number of sectors per head for the MBR partition table.
|
||||
0 chooses a default value. Maximum is 63.
|
||||
@*
|
||||
The product partition_sec_hd * partition_hd_cyl * 512 is the cylinder size.
|
||||
It should be divisible by 2048 in order to allow exact alignment.
|
||||
If it is too small to describe the image size by at most 1024 cylinders,
|
||||
With appended partitions and -appended_part_as_gpt there is no limit for
|
||||
the number of cylinders. Else there may be at most 1024 of them.
|
||||
If the cylinder size is too small to stay below the limit,
|
||||
then appropriate values of partition_hd_cyl are chosen with
|
||||
partition_sec_hd 32 or 63. If the image is larger than 8,422,686,720 bytes,
|
||||
then the cylinder size constraints cannot be fulfilled. They seem not overly
|
||||
important anyway. Flat block addresses in partition tables are good for 1 TiB.
|
||||
then the cylinder size constraints cannot be fulfilled for MBR.
|
||||
They seem not overly important anyway.
|
||||
Flat block addresses in partition tables are good for 1 TiB.
|
||||
@c man .TP
|
||||
@item -partition_cyl_align mode
|
||||
@kindex -partition_cyl_align Image size alignment
|
||||
@ -1521,7 +1582,8 @@ important anyway. Flat block addresses in partition tables are good for 1 TiB.
|
||||
Control image size alignment to an integer number of cylinders.
|
||||
It is prescribed by isohybrid specs and it seems to please program fdisk.
|
||||
Cylinder size must be divisible by 2048.
|
||||
Images larger than 8,323,596,288 bytes cannot be aligned.
|
||||
Images larger than 8,323,596,288 bytes cannot be aligned in MBR partition
|
||||
table.
|
||||
@*
|
||||
Mode "auto" is default. Alignment by padding happens only if
|
||||
option -isohybrid-mbr is given.
|
||||
@ -1534,8 +1596,8 @@ to an aligned size.
|
||||
Mode "off" disables alignment unconditionally.
|
||||
@c man .TP
|
||||
@item -append_partition partition_number type_code disk_path
|
||||
@kindex -append_partition Append MBR partition after image
|
||||
@cindex MBR, append partition, -append_partition
|
||||
@kindex -append_partition Append MBR or GPT partition after image
|
||||
@cindex MBR, GPT, append partition, -append_partition
|
||||
Cause a prepared filesystem image to be appended to the ISO image and to be
|
||||
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
|
||||
@ -1547,15 +1609,17 @@ 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.
|
||||
or GPT 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".
|
||||
This code matters only with MBR, not with GPT.
|
||||
@*
|
||||
If some other command causes the production of GPT, then the appended
|
||||
partitions will be mentioned there too.
|
||||
partitions will be mentioned there too, even if not -appended_part_as_gpt
|
||||
is given.
|
||||
@c man .TP
|
||||
@item -appended_part_as_gpt
|
||||
@kindex -appended_part_as_gpt Appended partitions in GPT
|
||||
|
||||
Reference in New Issue
Block a user