"Fossies" - the Fresh Open Source Software Archive  

Source code changes of the file "xorriso/xorriso.info" between
libisoburn-1.5.0.tar.gz and libisoburn-1.5.2.tar.gz

About: libisoburn is a frontend for the libraries libburn and libisofs which enables creation and expansion of ISO-9660 filesystems on all media and file types supported by libburn. It implements the API and command interpreter of program xorriso, and installs this program as small dynamically linked binary. xorriso is suitable for incremental data backup and for production of bootable ISO 9660 images. A statically linked version is available as GNU xorriso.

Binary file (standard input) matches
Home  |  About  |  Features  |  All  |  Newest  |  Dox  |  Diffs  |  RSS Feeds  |  Screenshots  |  Comments  |  Imprint  |  Privacy  |  HTTP(S)
xorriso.info  (libisoburn-1.5.0):xorriso.info  (libisoburn-1.5.2)
This is xorriso.info, produced by makeinfo version 5.2 from This is xorriso.info, produced by makeinfo version 5.2 from
xorriso.texi. xorriso.texi.
xorriso - creates, loads, manipulates and writes ISO 9660 filesystem xorriso - creates, loads, manipulates and writes ISO 9660 filesystem
images with Rock Ridge extensions. images with Rock Ridge extensions.
Copyright (C) 2007 - 2017 Thomas Schmitt Copyright (C) 2007 - 2019 Thomas Schmitt
Permission is granted to distrubute this text freely. Permission is granted to distribute this text freely.
INFO-DIR-SECTION Archiving INFO-DIR-SECTION Archiving
START-INFO-DIR-ENTRY START-INFO-DIR-ENTRY
* Xorriso: (xorriso). Burns ISO 9660 on CD, DVD, BD. * Xorriso: (xorriso). Burns ISO 9660 on CD, DVD, BD.
END-INFO-DIR-ENTRY END-INFO-DIR-ENTRY
 
File: xorriso.info, Node: Top, Next: Overview, Up: (dir) File: xorriso.info, Node: Top, Next: Overview, Up: (dir)
GNU xorriso 1.5.0 GNU xorriso 1.5.2
***************** *****************
xorriso - creates, loads, manipulates and writes ISO 9660 filesystem xorriso - creates, loads, manipulates and writes ISO 9660 filesystem
images with Rock Ridge extensions. images with Rock Ridge extensions.
* Menu: * Menu:
* Overview:: Overview * Overview:: Overview
* Model:: Session model * Model:: Session model
* Media:: Media types and states * Media:: Media types and states
* Methods:: Creating, Growing, Modifying, Blind Growing * Methods:: Creating, Growing, Modifying, Blind Growing
skipping to change at line 638 skipping to change at line 638
performed even if there are pending changes. performed even if there are pending changes.
-outdev can be performed without previous -dev or -indev. In that -outdev can be performed without previous -dev or -indev. In that
case an empty ISO image with no changes pending is created. It can case an empty ISO image with no changes pending is created. It can
either be populated by help of -map, -add et.al. or it can be either be populated by help of -map, -add et.al. or it can be
discarded silently if -dev or -indev are performed afterwards. discarded silently if -dev or -indev are performed afterwards.
Special address string "-" means standard output, to which several Special address string "-" means standard output, to which several
restrictions apply. See above paragraph "Libburn drives". restrictions apply. See above paragraph "Libburn drives".
An empty address string "" gives up the current output drive An empty address string "" gives up the current output drive
without acquiring a new one. No writing is possible without an without acquiring a new one. No writing is possible without an
output drive. output drive.
-drive_class "harmless"|"banned"|"caution"|"clear_list" disk_pattern
Add a drive path pattern to one of the safety lists or make those
lists empty. There are three lists defined which get tested in the
following sequence:
If a drive address path matches the "harmless" list then the drive
will be accepted. If it is not a MMC device then the prefix
"stdio:" will be prepended automatically. This list is empty by
default.
Else if the path matches the "banned" list then the drive will not
be accepted by 'xorriso' but rather lead to a FAILURE event. This
list is empty by default.
Else if the path matches the "caution" list and if it is not a MMC
device, then its address must have the prefix "stdio:" or it will
be rejected. This list has by default one entry: "/dev".
If a drive path matches no list then it is considered "harmless".
By default these are all paths which do not begin with directory
"/dev".
A path matches a list if one of its parent paths or itself matches
a list entry. Address prefix "stdio:" or "mmc:" will be ignored
when testing for matches.
By pseudo-class "clear_list" and pseudo-patterns "banned",
"caution", "harmless", or "all", the lists may be made empty.
E.g.: -drive_class clear_list banned
One will normally define the -drive_class lists in one of the
'xorriso' Startup Files.
Note: This is not a security feature but rather a bumper for the
superuser to prevent inadverted mishaps. For reliably blocking
access to a device file you have to deny its rw-permissions in the
filesystem.
-drive_access "exclusive"|"shared":"unrestricted"|"readonly"
Control whether device file locking mechanisms shall be used when
acquiring a drive, and whether status or content of the medium in
the drive may be altered. Useful and most harmless are the setting
"shared:readonly" and the default setting "exclusive:unrestricted".
"exclusive" enables tests and locks when acquiring the drive. It
depends on the operating system which locking mechanisms get
applied, if any. On GNU/Linux it is open(O_EXCL). On FreeBSD it is
flock(LOCK_EX).
"shared" disables the use of these mechanisms to become able to
acquire drives which are mounted, or opened by some process, or
guarded by /dev/pktcdvd*.
"unrestricted" enables all technically appropriate operations on an
acquired drive. "shared:unrestricted" risks to get own burn runs
spoiled by other processes or to vice versa spoil activities of
such processes. So use "exclusive:unrestricted" unless you know
for sure that "shared" is safe.
"readonly" disables operations which might surprise a co-user of
the drive. For -outdev these are formatting, blanking, writing,
ejecting. For -indev this is ejecting. Be aware that even reading
and drive status inquiries can disturb an ongoing burn run on
CD-R[W] and DVD-R[W].
-scsi_dev_family "default"|"sr"|"scd"|"sg" -scsi_dev_family "default"|"sr"|"scd"|"sg"
GNU/Linux specific: GNU/Linux specific:
By default, xorriso tries to map Linux drive addresses to /dev/sr* By default, xorriso tries to map Linux drive addresses to /dev/sr*
before they get opened for operating the drive. This coordinates before they get opened for operating the drive. This coordinates
well with other use cases of optical drives, like mount(8). But well with other use cases of optical drives, like mount(8). But
since year 2010 all /dev/sr* share a global lock which allows only since year 2010 all /dev/sr* share a global lock which allows only
one drive to process an SCSI command while all others have to wait one drive to process an SCSI command while all others have to wait
for its completion. This yields awful throughput if more than one for its completion. This yields awful throughput if more than one
drive is writing or reading simultaneously. The global lock is not drive is writing or reading simultaneously. The global lock is not
applied to device files /dev/sg* and also not if the xorriso drive applied to device files /dev/sg* and also not if the xorriso drive
skipping to change at line 744 skipping to change at line 796
If a track of a CD starts at block 123456 and gets copied to a disk If a track of a CD starts at block 123456 and gets copied to a disk
file where it begins at block 0, then this copy can be loaded with file where it begins at block 0, then this copy can be loaded with
-displacement -123456 -displacement -123456
If an ISO image was written onto a partition with offset of 640000 If an ISO image was written onto a partition with offset of 640000
blocks of 512 bytes, then it can be loaded from the base device by blocks of 512 bytes, then it can be loaded from the base device by
-load sbsector 160000 -displacement 160000 -load sbsector 160000 -displacement 160000
(If the partition start address is not divisible by 4, then you (If the partition start address is not divisible by 4, then you
will have to employ a loop device instead.) will have to employ a loop device instead.)
In both cases, the ISO sessions should be self contained, i.e. not In both cases, the ISO sessions should be self contained, i.e. not
add-on sessions to an ISO image outside their track or partition. add-on sessions to an ISO image outside their track or partition.
-drive_class "harmless"|"banned"|"caution"|"clear_list" disk_pattern
Add a drive path pattern to one of the safety lists or make those
lists empty. There are three lists defined which get tested in the
following sequence:
If a drive address path matches the "harmless" list then the drive
will be accepted. If it is not a MMC device then the prefix
"stdio:" will be prepended automatically. This list is empty by
default.
Else if the path matches the "banned" list then the drive will not
be accepted by 'xorriso' but rather lead to a FAILURE event. This
list is empty by default.
Else if the path matches the "caution" list and if it is not a MMC
device, then its address must have the prefix "stdio:" or it will
be rejected. This list has by default one entry: "/dev".
If a drive path matches no list then it is considered "harmless".
By default these are all paths which do not begin with directory
"/dev".
A path matches a list if one of its parent paths or itself matches
a list entry. Address prefix "stdio:" or "mmc:" will be ignored
when testing for matches.
By pseudo-class "clear_list" and pseudo-patterns "banned",
"caution", "harmless", or "all", the lists may be made empty.
E.g.: -drive_class clear_list banned
One will normally define the -drive_class lists in one of the
'xorriso' Startup Files.
Note: This is not a security feature but rather a bumper for the
superuser to prevent inadverted mishaps. For reliably blocking
access to a device file you have to deny its rw-permissions in the
filesystem.
-read_fs "any"|"norock"|"nojoliet"|"ecma119" -read_fs "any"|"norock"|"nojoliet"|"ecma119"
Specify which kind of filesystem tree to load if present. If the Specify which kind of filesystem tree to load if present. If the
wish cannot be fulfilled, then ECMA-119 names are loaded and wish cannot be fulfilled, then ECMA-119 names are loaded and
converted according to -ecma119_map. converted according to -ecma119_map.
"any" first tries to read Rock Ridge. If not present, Joliet is "any" first tries to read Rock Ridge. If not present, Joliet is
tried. tried.
"norock" does not try Rock Ridge. "norock" does not try Rock Ridge.
"nojoliet" does not try Joliet. "nojoliet" does not try Joliet.
"ecma119" tries neither Rock Ridge nor Joliet. "ecma119" tries neither Rock Ridge nor Joliet.
-assert_volid pattern severity -assert_volid pattern severity
skipping to change at line 856 skipping to change at line 879
ISO images, test ACL during file comparison, and restore ACLs to ISO images, test ACL during file comparison, and restore ACLs to
disk files when extracting them from ISO images. See also commands disk files when extracting them from ISO images. See also commands
-getfacl, -setfacl. -getfacl, -setfacl.
-xattr "on"|"user"|"any"|"off" -xattr "on"|"user"|"any"|"off"
Enable or disable processing of xattr attributes. If enabled, then Enable or disable processing of xattr attributes. If enabled, then
'xorriso' will handle xattr similar to ACL. See also commands 'xorriso' will handle xattr similar to ACL. See also commands
-getfattr, -setfattr and above paragraph about xattr. -getfattr, -setfattr and above paragraph about xattr.
Modes "on" and "user" read and write only attributes from namespace Modes "on" and "user" read and write only attributes from namespace
"user". "user".
Mode "any" processes attributes of all namespaces. This might need Mode "any" processes attributes of all namespaces. This might need
adminstrator privileges, even if the owner of the disk file tries administrator privileges, even if the owner of the disk file tries
to read or write the attributes. to read or write the attributes.
Note that xattr from namespace "isofs." are never read from disk Note that xattr from namespace "isofs." are never read from disk
or restored to disk. Further it is not possible to set them via or restored to disk. Further it is not possible to set them via
xorriso xattr manipulation commands. xorriso xattr manipulation commands.
-md5 "on"|"all"|"off"|"load_check_off" -md5 "on"|"all"|"off"|"load_check_off"
Enable or disable processing of MD5 checksums for the overall Enable or disable processing of MD5 checksums for the overall
session and for each single data file. If enabled then images with session and for each single data file. If enabled then images with
checksum tags get loaded only if the tags of superblock and checksum tags get loaded only if the tags of superblock and
directory tree match properly. The MD5 checksums of data files and directory tree match properly. The MD5 checksums of data files and
whole session get loaded from the image if there are any. whole session get loaded from the image if there are any.
skipping to change at line 915 skipping to change at line 938
neither a Rock Ridge name nor a Joliet name was read from the neither a Rock Ridge name nor a Joliet name was read from the
session. session.
Mode "stripped" is the default. It shows the names as found in the Mode "stripped" is the default. It shows the names as found in the
ISO but removes trailing ";1" or ".;1" if present. ISO but removes trailing ";1" or ".;1" if present.
Mode "unmapped" shows names as found without removing characters. Mode "unmapped" shows names as found without removing characters.
Mode "lowercase" is like "stripped" but also maps uppercase letters Mode "lowercase" is like "stripped" but also maps uppercase letters
to lowercase letters. This is compatible to default GNU/Linux to lowercase letters. This is compatible to default GNU/Linux
mount behavior. mount behavior.
Mode "uppercase" is like "stripped" but maps lowercase letters to Mode "uppercase" is like "stripped" but maps lowercase letters to
uppercase, if any occur despite the prescriptions of ECMA-119. uppercase, if any occur despite the prescriptions of ECMA-119.
-iso_nowtime "dynamic"|timestring
Choose whether to use the current time ("dynamic") or a fixed time
point for timestamps of ISO 9660 nodes without a disk source file
and as default for superblock timestamps.
If a timestring is given, then it is used for such timestamps. For
the formats of timestrings see command *-alter_date*.
-disk_dev_ino "on"|"ino_only"|"off" -disk_dev_ino "on"|"ino_only"|"off"
Enable or disable processing of recorded file identification Enable or disable processing of recorded file identification
numbers (dev_t and ino_t). If enabled they are stored as xattr and numbers (dev_t and ino_t). If enabled they are stored as xattr and
can substantially accelerate file comparison. The root node gets a can substantially accelerate file comparison. The root node gets a
global start timestamp. If during comparison a file with younger global start timestamp. If during comparison a file with younger
timestamps is found in the ISO image, then it is suspected to have timestamps is found in the ISO image, then it is suspected to have
inconsistent content. inconsistent content.
If device numbers and inode numbers of the disk filesystems are If device numbers and inode numbers of the disk filesystems are
persistent and if no irregular alterations of timestamps or system persistent and if no irregular alterations of timestamps or system
clock happen, then potential content changes can be detected clock happen, then potential content changes can be detected
skipping to change at line 1399 skipping to change at line 1428
part files in it. This is necessary if the size of the disk file part files in it. This is necessary if the size of the disk file
exceeds -file_size_limit. Older operating systems can handle files exceeds -file_size_limit. Older operating systems can handle files
in mounted ISO 9660 filesystems only if they are smaller than 2 GiB in mounted ISO 9660 filesystems only if they are smaller than 2 GiB
or in other cases 4 GiB. or in other cases 4 GiB.
Default is 0 which will exclude files larger than -file_size_limit Default is 0 which will exclude files larger than -file_size_limit
by a FAILURE event. A well tested -split_size is 2047m. Sizes by a FAILURE event. A well tested -split_size is 2047m. Sizes
above -file_size_limit are not permissible. above -file_size_limit are not permissible.
While command -split_size is set larger than 0 such a directory While command -split_size is set larger than 0 such a directory
with split file pieces will be recognized and handled like a with split file pieces will be recognized and handled like a
regular file by commands -compare* , -update*, and in overwrite regular file by commands -compare* , -update*, and in overwrite
situations. There are -ossirox parameters "concat_split_on" and situations. There are -osirrox parameters "concat_split_on" and
"concat_split_off" which control the handling when files get "concat_split_off" which control the handling when files get
restored to disk. restored to disk.
In order to be recognizable, the names of the part files have to In order to be recognizable, the names of the part files have to
describe the splitting by 5 numbers: describe the splitting by 5 numbers:
part_number,total_parts,byte_offset,byte_count,disk_file_size part_number,total_parts,byte_offset,byte_count,disk_file_size
which are embedded in the following text form: which are embedded in the following text form:
part_#_of_#_at_#_with_#_of_# part_#_of_#_at_#_with_#_of_#
Scaling characters like "m" or "k" are taken into respect. All Scaling characters like "m" or "k" are taken into respect. All
digits are interpreted as decimal, even if leading zeros are digits are interpreted as decimal, even if leading zeros are
present. present.
skipping to change at line 2732 skipping to change at line 2761
"--interval:"Flags":"Interval":"Zeroizers":"Source "--interval:"Flags":"Interval":"Zeroizers":"Source
The component "--interval" states that this is not a plain disk path but The component "--interval" states that this is not a plain disk path but
rather an interval reader description string. rather an interval reader description string.
The component Flags modifies the further interpretation: The component Flags modifies the further interpretation:
"local_fs" demands to read from a file depicted by the path in Source. "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 "imported_iso" demands to read from the -indev. This works only if
-outdev is not the same as -indev. The Source component is ignored. -outdev is not the same as -indev. The Source component is ignored.
"appended_partition_NNN" with a decimal number NNN works only for "appended_partition_NNN" with a decimal number NNN works only for
-boot_image bootspecs which announce El Torito boot image paths: -boot_image bootspecs which announce El Torito boot image paths:
bin_path=, efi_path=. The number gives the partition number as used bin_path=, efi_path=. The number gives the partition number as used
with the corresponding option -append_partition. with the corresponding command -append_partition.
The component Interval consists of two byte address numbers separated by The component Interval consists of two byte address numbers separated by
a "-" character. E.g. "0-429" means to read bytes 0 to 429. a "-" character. E.g. "0-429" means to read bytes 0 to 429.
The component Zeroizers consists of zero or more comma separated The component Zeroizers consists of zero or more comma separated
strings. They define which part of the read data to zeroize. Byte strings. They define which part of the read data to zeroize. Byte
number 0 means the byte read from the Interval start address. Each number 0 means the byte read from the Interval start address. Each
string may be one of: string may be one of:
"zero_mbrpt" demands to zeroize the MBR partition table if bytes 510 and "zero_mbrpt" demands to zeroize the MBR partition table if bytes 510 and
511 bear the MBR signature 0x55 0xaa. 511 bear the MBR signature 0x55 0xaa.
"zero_gpt" demands to check for a GPT header in bytes 512 to 1023, to "zero_gpt" demands to check for a GPT header in bytes 512 to 1023, to
zeroize it and its partition table blocks. zeroize it and its partition table blocks.
skipping to change at line 2927 skipping to change at line 2956
The partition GUIDs get generated by minimally varying the disk The partition GUIDs get generated by minimally varying the disk
GUID. GUID.
*-boot_image any part_like_isohybrid=on* enables -boot_image *-boot_image any part_like_isohybrid=on* enables -boot_image
isolinux partition_entry= even if no -boot_image isolinux isolinux partition_entry= even if no -boot_image isolinux
system_area= is given. No MBR partition of type 0xee emerges, even system_area= is given. No MBR partition of type 0xee emerges, even
if GPT gets produced. Gaps between GPT and APM partitions will not if GPT gets produced. Gaps between GPT and APM partitions will not
be filled by more partitions. Appended partitions get mentioned in be filled by more partitions. Appended partitions get mentioned in
APM if other APM partitions emerge. APM if other APM partitions emerge.
*-boot_image any iso_mbr_part_type=*number sets the partition type *-boot_image any iso_mbr_part_type=*number sets the partition type
of the MBR partition which represents the ISO or at least protects of the MBR partition which represents the ISO or at least protects
it. Number may be 0x00 to 0xff. The text "default" re-enables the it.
Number may be 0x00 to 0xff. The text "default" re-enables the
default types of the various occasions to create an ISO MBR default types of the various occasions to create an ISO MBR
partition. partition. This is without effect if no such partition emerges by
This is without effect if no such partition emerges by other other settings or if the partition type is prescribed mandatorily
settings or if the partition type is prescribed mandatorily like like 0xee for GPT protective MBR or 0x96 for CHRP.
0xee for GPT protective MBR or 0x96 for CHRP. If instead a type_guid is given by a 32-digit hex string like
a2a0d0ebe5b9334487c068b6b72699c7 or by a structured text like
EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, then it will be used as
partition type if the ISO filesystem appears as partition in GPT.
In MBR, C12A7328-F81F-11D2-BA4B-00A0C93EC93B will be mapped to
0xef. Any other GUID will be mapped to 0x83.
*grub2_mbr=*disk_path works like "any" system_area= with additional *grub2_mbr=*disk_path works like "any" system_area= with additional
patching for modern GRUB MBRs. The content start address of the patching for modern GRUB MBRs. The content start address of the
first boot image is converted to a count of 512 byte blocks, and an first boot image is converted to a count of 512 byte blocks, and an
offset of 4 is added. The result is written as 64 bit offset of 4 is added. The result is written as 64 bit
little-endian number to byte address 0x1b0. little-endian number to byte address 0x1b0.
This feature can be revoked either by grub2_mbr= with empty disk This feature can be revoked either by grub2_mbr= with empty disk
path, or by submitting a disk_path via system_area=. path, or by submitting a disk_path via system_area=.
*partition_table=on* causes a simple partition table to be written *partition_table=on* causes a simple partition table to be written
into bytes 446 to 511 of the System Area. into bytes 446 to 511 of the System Area.
With type "isolinux" it shows a partition that begins at byte 0 and With type "isolinux" it shows a partition that begins at byte 0 and
skipping to change at line 3113 skipping to change at line 3148
will get overwritten. will get overwritten.
Partitions may be appended with boot block type MBR and with SUN Partitions may be appended with boot block type MBR and with SUN
Disk Label. Disk Label.
With MBR: With MBR:
partition_number may be 1 to 4. Number 1 will put the whole ISO partition_number may be 1 to 4. Number 1 will put the whole ISO
image into the unclaimed space before partition 1. So together image into the unclaimed space before partition 1. So together
with most 'xorriso' MBR features, number 2 would be the most with most 'xorriso' MBR features, number 2 would be the most
natural choice. natural choice.
The type_code may be "FAT12", "FAT16", "Linux", or a hexadecimal The type_code may be "FAT12", "FAT16", "Linux", or a hexadecimal
number between 0x00 and 0xff. Not all those numbers will yield number between 0x00 and 0xff. Not all those numbers will yield
usable results. For a list of codes search the Internet for usable results. For a list of MBR partition type codes search the
"Partition Types" or run fdisk command "L". Internet for "Partition Types" or run fdisk command "L".
type_code may also be a type GUID as plain hex string like
a2a0d0ebe5b9334487c068b6b72699c7 or as structured text like
EBD0A0A2-B9E5-4433-87C0-68B6B72699C7. It will be used if the
partition is mentioned in GPT. In MBR,
C12A7328-F81F-11D2-BA4B-00A0C93EC93B will be mapped to 0xef. Any
other GUID will be mapped to 0x83.
If some other command causes the production of GPT, then the If some other command causes the production of GPT, then the
appended partitions will be mentioned there too. appended partitions will be mentioned there too.
The disk_path must provide the necessary data bytes at commit time. The disk_path must provide the necessary data bytes at commit time.
An empty disk_path disables this feature for the given partition An empty disk_path disables this feature for the given partition
number. number.
With SUN Disk Label (selected by -boot_image any sparc_label=): 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 partition_number may be 2 to 8. Number 1 will always be the ISO
image. Partition start addresses are aligned to 320 KiB. The image. Partition start addresses are aligned to 320 KiB. The
type_code does not matter. Submit 0x0. type_code does not matter. Submit 0x0.
Partition image name "." causes the partition to become a copy of Partition image name "." causes the partition to become a copy of
skipping to change at line 3913 skipping to change at line 3954
"unreadable". "unreadable".
"valid" and "invalid" are qualities imported from a sector_map "valid" and "invalid" are qualities imported from a sector_map
file. "tao_end" and "off_track" are intentionally not file. "tao_end" and "off_track" are intentionally not
readable, but not bad either. "partial" are blocks retrieved readable, but not bad either. "partial" are blocks retrieved
from a partially readable chunk. They are supposed to be ok from a partially readable chunk. They are supposed to be ok
but stem from a suspicious neighborhood. but stem from a suspicious neighborhood.
"md5_match" and "md5_mismatch" regions overlap with regions of "md5_match" and "md5_mismatch" regions overlap with regions of
other quality. The former is a strong confirmation for other quality. The former is a strong confirmation for
quality, the latter only tells that one or more blocks of the quality, the latter only tells that one or more blocks of the
region must be wrong. region must be wrong.
By default bad_limit is set higher than md5_mismatch, so that
mismatches are classified as quality class "0" rather than