|
|
|
|
@ -144,13 +144,13 @@ filesystems.
|
|
|
|
|
one and the modifications.
|
|
|
|
|
See paragraph Creating, Growing, Modifying, Blind Growing below.
|
|
|
|
|
.PP
|
|
|
|
|
\fBxorriso\fR adopts the concept of multi\-session by loading an eventual
|
|
|
|
|
image directory tree, allowing to manipulate it by several actions, and to
|
|
|
|
|
write the new image to the target media.
|
|
|
|
|
\fBxorriso\fR adopts the concept of multi\-session by loading an
|
|
|
|
|
image directory tree if present,
|
|
|
|
|
by allowing to manipulate it by several actions,
|
|
|
|
|
and by writing the new image to the target media.
|
|
|
|
|
.br
|
|
|
|
|
The first session of a \fBxorriso\fR run begins by the definition of
|
|
|
|
|
the input
|
|
|
|
|
drive with the eventual ISO image or by the definition of an output drive.
|
|
|
|
|
the input drive with the ISO image or by the definition of an output drive.
|
|
|
|
|
The session ends by command \-commit which triggers writing. A \-commit is
|
|
|
|
|
done automatically when the program ends regularly.
|
|
|
|
|
.PP
|
|
|
|
|
@ -198,7 +198,7 @@ With used CD\-RW and DVD\-RW it can be achieved by action \-blank "as_needed".
|
|
|
|
|
Overwriteable media are considered blank if they are new or if they have
|
|
|
|
|
been marked as blank by \fBxorriso\fR.
|
|
|
|
|
Action \-blank "as_needed" can be used to do this marking on overwriteable
|
|
|
|
|
media, or to apply eventual mandatory formatting to new media.
|
|
|
|
|
media, or to apply mandatory formatting to new media if necessary.
|
|
|
|
|
.br
|
|
|
|
|
\fBAppendable\fR media accept further sessions. Either they are MMC
|
|
|
|
|
multi\-session media in appendable state, or they are overwriteable media
|
|
|
|
|
@ -237,7 +237,7 @@ and output drive determines which write method will be used.
|
|
|
|
|
They have quite different capabilities and constraints.
|
|
|
|
|
.PP
|
|
|
|
|
The method of \fBgrowing\fR adds new data to the existing media. These
|
|
|
|
|
data comprise of eventual new file content and they override the existing
|
|
|
|
|
data comprise of new file content and they override the existing
|
|
|
|
|
ISO 9660 + Rock Ridge directory tree. It is possible to hide files from
|
|
|
|
|
previous sessions but they still exist on media and with many types of
|
|
|
|
|
optical media it is quite easy to recover them by mounting older sessions.
|
|
|
|
|
@ -413,7 +413,7 @@ It uses this extension if enabled by option
|
|
|
|
|
\fB\-acl\fR.
|
|
|
|
|
.br
|
|
|
|
|
AAIP enhanced images are supposed to be mountable normally, but one cannot
|
|
|
|
|
expect that the mounted filesystem will show and respect the eventual ACLs.
|
|
|
|
|
expect that the mounted filesystem will show and respect the ACLs.
|
|
|
|
|
For now, only \fBxorriso\fR is able to retrieve those ACLs.
|
|
|
|
|
It can bring them into
|
|
|
|
|
effect when files get restored to an ACL enabled file system or it can
|
|
|
|
|
@ -421,8 +421,8 @@ print them in a format suitable for tool setfacl.
|
|
|
|
|
.br
|
|
|
|
|
Files with ACL show as group permissions the setting of entry "mask::" if
|
|
|
|
|
that entry exists. Nevertheless the non\-listed group members get handled
|
|
|
|
|
according to entry "group::". \fBxorriso\fR brings "group::" into effect
|
|
|
|
|
before eventually removing the ACL from a file.
|
|
|
|
|
according to entry "group::". When removing ACL from a file,
|
|
|
|
|
\fBxorriso\fR brings "group::" into effect.
|
|
|
|
|
.PP
|
|
|
|
|
\fBxattr\fR (aka EA)
|
|
|
|
|
are pairs of name and value which can be attached to file objects. AAIP is
|
|
|
|
|
@ -464,14 +464,14 @@ appears among the arguments of such a command.
|
|
|
|
|
.PP
|
|
|
|
|
\fBPattern expansion\fR
|
|
|
|
|
converts a list of pattern words into a list of existing file addresses.
|
|
|
|
|
Eventual unmatched pattern words appear themselves in that result list, though.
|
|
|
|
|
Unmatched pattern words appear themselves in that result list, though.
|
|
|
|
|
.br
|
|
|
|
|
Pattern matching supports the usual shell parser wildcards '*' '?' '[xyz]'
|
|
|
|
|
and respects '/' as separator which may only be matched literally.
|
|
|
|
|
.br
|
|
|
|
|
It is a property of some particular commands and not a general
|
|
|
|
|
feature. It gets controlled by commands \-iso_rr_pattern and \-disk_pattern.
|
|
|
|
|
Commands which eventually use pattern expansion all have variable argument
|
|
|
|
|
Commands which may use pattern expansion all have variable argument
|
|
|
|
|
lists which are marked in this man page by "[***]" rather than "[...]".
|
|
|
|
|
.br
|
|
|
|
|
Some other commands perform pattern matching unconditionally.
|
|
|
|
|
@ -501,10 +501,10 @@ as in $'...' of bash.
|
|
|
|
|
.br
|
|
|
|
|
It is not enabled by default. See option \-backslash_codes.
|
|
|
|
|
.PP
|
|
|
|
|
When the program begins then it first looks for argument \-no_rc. If this is
|
|
|
|
|
When the program starts then it first looks for argument \-no_rc. If this is
|
|
|
|
|
not present then it looks for its startup files and
|
|
|
|
|
eventually reads their content as command input lines. Then it interprets
|
|
|
|
|
the program arguments as commands and parameters and finally it enters
|
|
|
|
|
reads their content as command input lines. Then it interprets
|
|
|
|
|
the program arguments as commands and parameters. Finally it enters
|
|
|
|
|
dialog mode if command \-dialog "on" was executed up to then.
|
|
|
|
|
.PP
|
|
|
|
|
The program ends either by command \-end, or by the end of program arguments
|
|
|
|
|
@ -562,16 +562,20 @@ inner dashes are interpreted as underscores.
|
|
|
|
|
.TP
|
|
|
|
|
.B Aquiring source and target drive:
|
|
|
|
|
.PP
|
|
|
|
|
Before aquiring a drive one will eventually enable options which influence
|
|
|
|
|
the behavior of image loading. See next option group.
|
|
|
|
|
The effect of aquiring a drive may depend on several options in the
|
|
|
|
|
next paragraph "Influencing the behavior of image loading".
|
|
|
|
|
If desired, their enabling commands have to be performed before the
|
|
|
|
|
commands which aquire the drive.
|
|
|
|
|
.TP
|
|
|
|
|
\fB\-dev\fR address
|
|
|
|
|
Set input and output drive to the same address and load an eventual ISO image.
|
|
|
|
|
Set input and output drive to the same address and load an ISO image if it
|
|
|
|
|
is present.
|
|
|
|
|
If there is no ISO image then create a blank one.
|
|
|
|
|
Set the image expansion method to growing.
|
|
|
|
|
.br
|
|
|
|
|
This is only allowed as long as no changes are pending in the currently
|
|
|
|
|
loaded ISO image. Eventually one has to perform \-commit or \-rollback first.
|
|
|
|
|
loaded ISO image. If changes are pending, then one has to perform \-commit
|
|
|
|
|
or \-rollback first.
|
|
|
|
|
.br
|
|
|
|
|
Special address string "\-" means standard output, to which several restrictions
|
|
|
|
|
apply. See above paragraph "Libburn drives".
|
|
|
|
|
@ -580,7 +584,8 @@ An empty address string "" gives up the current device
|
|
|
|
|
without aquiring a new one.
|
|
|
|
|
.TP
|
|
|
|
|
\fB\-indev\fR address
|
|
|
|
|
Set input drive and load an eventual ISO image. If the new input drive differs
|
|
|
|
|
Set input drive and load an ISO image if present.
|
|
|
|
|
If the new input drive differs
|
|
|
|
|
from \-outdev then switch from growing to modifying or to blind growing.
|
|
|
|
|
It depends on the setting of \-grow_blindly which of both gets activated.
|
|
|
|
|
The same rules and restrictions apply as with \-dev.
|
|
|
|
|
@ -651,11 +656,11 @@ setting is valid for \-rollback until next \-dev or \-indev, where it
|
|
|
|
|
will be reset to "auto".
|
|
|
|
|
.TP
|
|
|
|
|
\fB\-displacement\fR [-]lba
|
|
|
|
|
Compensate an eventual displacement of the image versus the start address
|
|
|
|
|
Compensate a displacement of the image versus the start address
|
|
|
|
|
for which the image was prepared. This affects only loading of ISO images
|
|
|
|
|
and reading of their files. The multi\-session method of growing is not allowed
|
|
|
|
|
as long as \-displacement is non\-zero. I.e. \-indev and \-outdev must be
|
|
|
|
|
different. Eventually the displacement is reset to 0 before the drive
|
|
|
|
|
different. The displacement gets reset to 0 before the drive
|
|
|
|
|
gets re\-aquired after writing.
|
|
|
|
|
.br
|
|
|
|
|
Examples:
|
|
|
|
|
@ -690,7 +695,7 @@ 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".
|
|
|
|
|
.br
|
|
|
|
|
A path matches a list if one of its parent paths or itself matches a list
|
|
|
|
|
entry. An eventual address prefix "stdio:" or "mmc:" will be ignored when
|
|
|
|
|
entry. Address prefix "stdio:" or "mmc:" will be ignored when
|
|
|
|
|
testing for matches.
|
|
|
|
|
.br
|
|
|
|
|
By pseudo\-class "clear_list" and pseudo\-patterns "banned", "caution",
|
|
|
|
|
@ -716,16 +721,15 @@ input media and does not discard an already loaded image.
|
|
|
|
|
.TP
|
|
|
|
|
\fB\-in_charset\fR character_set_name
|
|
|
|
|
Set the character set from which to convert file names when loading an
|
|
|
|
|
image. This has eventually to be done before specifying \-dev , \-indev or
|
|
|
|
|
\-rollback. See paragraph "Character sets" for more explanations.
|
|
|
|
|
image. See paragraph "Character sets" for more explanations.
|
|
|
|
|
When loading the written image after \-commit the setting of \-out_charset
|
|
|
|
|
will be copied to \-in_charset.
|
|
|
|
|
.TP
|
|
|
|
|
\fB\-auto_charset\fR "on"|"off"
|
|
|
|
|
Enable or disable recording and interpretation of the output character
|
|
|
|
|
set name in an xattr attribute of the image root directory. If enabled then
|
|
|
|
|
an eventual recorded character set name gets used as input character set
|
|
|
|
|
when reading an image.
|
|
|
|
|
set name in an xattr attribute of the image root directory. If enabled and
|
|
|
|
|
if a recorded character set name is found, then this name will be used as
|
|
|
|
|
namoe of the input character set when reading an image.
|
|
|
|
|
.br
|
|
|
|
|
Note that the default output charset is the local character set of the
|
|
|
|
|
terminal where \fBxorriso\fR runs. Before attributing this local
|
|
|
|
|
@ -740,7 +744,8 @@ In default mode "off", iso_rr files lose their inode numbers at image load
|
|
|
|
|
time. Each iso_rr file object which has no inode number at image generation
|
|
|
|
|
time will get a new unique inode number if \-compliance is set to new_rr.
|
|
|
|
|
.br
|
|
|
|
|
Mode "on" preserves eventual inode numbers from the loaded image.
|
|
|
|
|
Mode "on" preserves inode numbers from the loaded image if such numbers
|
|
|
|
|
were recorded.
|
|
|
|
|
When committing a session it searches for families of iso_rr files
|
|
|
|
|
which stem from the same disk file, have identical content filtering and have
|
|
|
|
|
identical properties. The family members all get the same inode number.
|
|
|
|
|
@ -784,12 +789,12 @@ See also options \-getfattr, \-setfattr and above paragraph about xattr.
|
|
|
|
|
.TP
|
|
|
|
|
\fB\-md5\fR "on"|"all"|"off"|"load_check_off"
|
|
|
|
|
Enable or disable processing of MD5 checksums for the overall session and for
|
|
|
|
|
each single data file. If enabled then images get loaded only if eventual
|
|
|
|
|
checksums tags of superblock and directory tree match properly. The MD5
|
|
|
|
|
each single data file. If enabled then images with checksum tags get loaded
|
|
|
|
|
only if the tags of superblock and directory tree match properly. The MD5
|
|
|
|
|
checksums of data files and whole session get loaded from the image if there
|
|
|
|
|
are any.
|
|
|
|
|
.br
|
|
|
|
|
With options \-compare and \-update the eventually recorded MD5 of a file
|
|
|
|
|
With options \-compare and \-update the recorded MD5 of a file
|
|
|
|
|
will be used to avoid content reading from the image. Only the disk file
|
|
|
|
|
content will be read and compared with that MD5. This can save much time
|
|
|
|
|
if \-disk_dev_ino "on" is not suitable.
|
|
|
|
|
@ -822,7 +827,7 @@ Currently this is a shortcut for: \-hardlinks on \-acl on \-xattr on \-md5 on.
|
|
|
|
|
.TP
|
|
|
|
|
\fB\-disk_dev_ino\fR "on"|"ino_only"|"off"
|
|
|
|
|
Enable or disable processing of recorded file identification numbers
|
|
|
|
|
(dev_t and ino_t). They are eventually stored as xattr and allow
|
|
|
|
|
(dev_t and ino_t). If enabled they are stored as xattr and allow
|
|
|
|
|
to substantially accelerate file comparison. The root node gets a global start
|
|
|
|
|
timestamp. If during comparison a file with younger timestamps is found in the
|
|
|
|
|
ISO image, then it is suspected to have inconsistent content.
|
|
|
|
|
@ -847,7 +852,7 @@ too.
|
|
|
|
|
Read\-only drives do not tell the actual media type but show any media as
|
|
|
|
|
ROM (e.g. as DVD\-ROM). The session history of MMC multi\-session media might
|
|
|
|
|
be truncated to first and last session or even be completely false.
|
|
|
|
|
(The eventual emulated history of overwriteable media is not affected by this.)
|
|
|
|
|
(The emulated history of overwriteable media is not affected by this.)
|
|
|
|
|
.br
|
|
|
|
|
To have in case of failure a chance of getting the session history and
|
|
|
|
|
especially the address of the last session, there is a scan for ISO 9660
|
|
|
|
|
@ -923,8 +928,9 @@ If other file types collide then the setting of command
|
|
|
|
|
decides.
|
|
|
|
|
.br
|
|
|
|
|
Renaming of files has similar collision handling, but directories can only
|
|
|
|
|
be replaced, not merged. Note that \-mv inserts the source objects into an
|
|
|
|
|
eventual existing target directory rather than attempting to replace it.
|
|
|
|
|
be replaced, not merged. Note that if the target directory exists, then \-mv
|
|
|
|
|
inserts the source objects into this directory rather than attempting
|
|
|
|
|
to replace it.
|
|
|
|
|
.PP
|
|
|
|
|
The commands in this section alter the ISO image and not the local filesystem.
|
|
|
|
|
.TP
|
|
|
|
|
@ -947,7 +953,7 @@ Insert the given files or directory trees from filesystem
|
|
|
|
|
into the ISO image.
|
|
|
|
|
.br
|
|
|
|
|
If \-pathspecs is set to "on" then pattern expansion is always disabled and
|
|
|
|
|
character '=' has a special meaning. It eventually separates the ISO image path
|
|
|
|
|
character '=' has a special meaning. It separates the ISO image path
|
|
|
|
|
from the disk path:
|
|
|
|
|
.br
|
|
|
|
|
iso_rr_path=disk_path
|
|
|
|
|
@ -960,15 +966,16 @@ If no '=' is given then the word is used as both, iso_rr_path and disk path.
|
|
|
|
|
If in this case the word does not begin with '/' then \-cdx is prepended to
|
|
|
|
|
the disk_path and \-cd is prepended to the iso_rr_path.
|
|
|
|
|
.br
|
|
|
|
|
If \-pathspecs is set to "off" then eventual \-disk_pattern expansion applies.
|
|
|
|
|
The resulting words are used as both, iso_rr_path and disk path. Eventually
|
|
|
|
|
\-cdx gets prepended to disk_path and \-cd to iso_rr_path.
|
|
|
|
|
If \-pathspecs is set to "off" then \-disk_pattern expansion applies, if enabled.
|
|
|
|
|
The resulting words are used as both, iso_rr_path and disk path. Relative
|
|
|
|
|
path words get prepended the setting of \-cdx to disk_path and the setting
|
|
|
|
|
of \-cd to iso_rr_path.
|
|
|
|
|
.TP
|
|
|
|
|
\fB\-add_plainly\fR mode
|
|
|
|
|
If set to mode "unknown" then any command word that does not begin with "\-" and
|
|
|
|
|
is not recognized as known command will be subject to a virtual \-add command.
|
|
|
|
|
I.e. it will be used as pathspec or as disk_path and added to the image.
|
|
|
|
|
Eventually \-disk_pattern expansion applies to disk_paths.
|
|
|
|
|
If enabled, \-disk_pattern expansion applies to disk_paths.
|
|
|
|
|
.br
|
|
|
|
|
Mode "dashed" is similar to "unknown" but also adds unrecognized command
|
|
|
|
|
words even if they begin with "\-".
|
|
|
|
|
@ -1087,8 +1094,8 @@ other file causes a FAILURE event.
|
|
|
|
|
\fB\-clone\fR iso_rr_path_original iso_rr_path_copy
|
|
|
|
|
Create a copy of the ISO file object iso_rr_path_original with the new
|
|
|
|
|
address iso_rr_path_copy. If the original is a directory then copy all
|
|
|
|
|
files and directories underneath. An eventual boot catalog file gets
|
|
|
|
|
not copied but is silently ignored.
|
|
|
|
|
files and directories underneath. If iso_rr_path_original is a boot catalog
|
|
|
|
|
file, then it gets not copied but is silently ignored.
|
|
|
|
|
.br
|
|
|
|
|
The copied ISO file objects have the same attributes. Copied data files
|
|
|
|
|
refer to the same content source as their originals.
|
|
|
|
|
@ -1099,7 +1106,7 @@ already exists in the ISO tree.
|
|
|
|
|
.TP
|
|
|
|
|
\fB\-cp_clone\fR iso_rr_path_original [***] iso_rr_path_dest
|
|
|
|
|
Create copies of one or more ISO file objects as with command \-clone.
|
|
|
|
|
Eventually merge directories with existing ones, but do not overwrite
|
|
|
|
|
In case of collision merge directories with existing ones, but do not overwrite
|
|
|
|
|
existing ISO file objects.
|
|
|
|
|
.br
|
|
|
|
|
The rules for generating the copy addresses are the same as with
|
|
|
|
|
@ -1124,8 +1131,8 @@ up to 2g \-1 \-\-. Newer ones are good up to 4g \-1 \-\-.
|
|
|
|
|
You need quite a new Linux kernel to read correctly the final bytes
|
|
|
|
|
of a file >= 4g if its size is not aligned to 2048 byte blocks.
|
|
|
|
|
.br
|
|
|
|
|
\fBxorriso\fR's own data read capabilities are not affected by eventual
|
|
|
|
|
operating system size limits. They apply to mounting only. Nevertheless,
|
|
|
|
|
\fBxorriso\fR's own data read capabilities are not affected by
|
|
|
|
|
operating system size limits. Such limits apply to mounting only. Nevertheless,
|
|
|
|
|
the target filesystem of an \-extract must be able to take the file size.
|
|
|
|
|
.TP
|
|
|
|
|
\fB\-not_mgt\fR code[:code[...]]
|
|
|
|
|
@ -1172,7 +1179,7 @@ get reported with \-compare and deleted from the image with \-update.
|
|
|
|
|
\fB\-not_paths\fR disk_path [***]
|
|
|
|
|
Add the given paths to the list of excluded absolute disk paths. If a given
|
|
|
|
|
path is relative, then the current \-cdx is prepended to form an absolute path.
|
|
|
|
|
Eventual pattern matching happens at definition time and not when exclusion
|
|
|
|
|
Pattern matching, if enabled, happens at definition time and not when exclusion
|
|
|
|
|
checks are made.
|
|
|
|
|
.br
|
|
|
|
|
(Do not forget to end the list of disk_paths by "\-\-")
|
|
|
|
|
@ -1255,7 +1262,7 @@ like with program mkisofs \-graft\-points.
|
|
|
|
|
It also disables \-disk_pattern expansion for command \-add.
|
|
|
|
|
.br
|
|
|
|
|
"off" disables pathspecs of the form target=source
|
|
|
|
|
and eventually enables \-disk_pattern expansion.
|
|
|
|
|
and re\-enables \-disk_pattern expansion.
|
|
|
|
|
.TP
|
|
|
|
|
\fB\-overwrite\fR "on"|"nondir"|"off"
|
|
|
|
|
Allow or disallow to overwrite existing files in the
|
|
|
|
|
@ -1387,8 +1394,8 @@ For octal numbers see man 2 stat.
|
|
|
|
|
Like \-chmod but affecting all files below eventual directories.
|
|
|
|
|
.TP
|
|
|
|
|
\fB\-setfacl\fR acl_text iso_rr_path [***]
|
|
|
|
|
Attach the given ACL to the given iso_rr_paths after deleting their eventually
|
|
|
|
|
existing ACLs.
|
|
|
|
|
Attach the given ACL to the given iso_rr_paths. If the files already have
|
|
|
|
|
ACLs, then those get deleted before the new ones get into effect.
|
|
|
|
|
If acl_text is empty, or contains the text "clear" or the text
|
|
|
|
|
"\-\-remove\-all",
|
|
|
|
|
then the existing ACLs will be removed and no new ones will be
|
|
|
|
|
@ -1510,7 +1517,7 @@ Like \-alter_date but affecting all files below eventual directories.
|
|
|
|
|
\fB\-hide\fR hide_state iso_rr_path [***]
|
|
|
|
|
Prevent the names of the given files from showing up in the directory trees
|
|
|
|
|
of ISO 9660 and/or Joliet when the image gets written.
|
|
|
|
|
The eventual data content of such hidden files will be included in the
|
|
|
|
|
The data content of such hidden files will be included in the
|
|
|
|
|
resulting image, even if they do not show up in any directory.
|
|
|
|
|
But you will need own means to find nameless data in the image.
|
|
|
|
|
.br
|
|
|
|
|
@ -1556,7 +1563,7 @@ Can be true only for data files which stem not from the loaded image.
|
|
|
|
|
\fB\-type\fR type_letter :
|
|
|
|
|
Matches files of the given type:
|
|
|
|
|
"block", "char", "dir", "pipe", "file", "link", "socket", "eltorito",
|
|
|
|
|
"Xotic" which eventually matches what is not matched by the other types.
|
|
|
|
|
and "Xotic" which matches what is not matched by the other types.
|
|
|
|
|
.br
|
|
|
|
|
Only the first letter is interpreted. E.g.: \-find / \-type d
|
|
|
|
|
.br
|
|
|
|
|
@ -1639,7 +1646,7 @@ Normal precedence is: \-not, \-or , \-and.
|
|
|
|
|
\fB\-else\fR ... \fB\-endif\fR :
|
|
|
|
|
Enclose one or more sub expressions. If the \-if expression matches, then
|
|
|
|
|
the \-then expression is evaluated as the result of the whole expression
|
|
|
|
|
up to \-endif. Else the next \-elseif expression is evaluated and eventually
|
|
|
|
|
up to \-endif. Else the next \-elseif expression is evaluated and if it matches,
|
|
|
|
|
its \-then expression. Finally in case of no match, the \-else expression
|
|
|
|
|
is evaluated.
|
|
|
|
|
There may be more than one \-elseif. Neither \-else nor \-elseif are mandatory.
|
|
|
|
|
@ -1715,7 +1722,7 @@ removes an eventual marking from action "update_merge".
|
|
|
|
|
.br
|
|
|
|
|
\fBreport_damage\fR
|
|
|
|
|
classifies files whether they hit a data block that is
|
|
|
|
|
marked as damaged. The result is printed together with the eventual address
|
|
|
|
|
marked as damaged. The result is printed together with the address
|
|
|
|
|
of the first damaged byte, the maximum span of damages, file size, and the
|
|
|
|
|
path of the file.
|
|
|
|
|
.br
|
|
|
|
|
@ -1730,25 +1737,25 @@ different extent number in column "xt".
|
|
|
|
|
prints access permissions in ACL text form to the result channel.
|
|
|
|
|
.br
|
|
|
|
|
\fBsetfacl\fR
|
|
|
|
|
attaches ACLs after removing eventually exiting ones. The new
|
|
|
|
|
attaches ACLs after removing existing ones. The new
|
|
|
|
|
ACL is given in text form as defined with option \-setfacl.
|
|
|
|
|
.br
|
|
|
|
|
E.g.: \-exec setfacl u:lisa:rw,u::rw,g::r,o::\-,m::rw \-\-
|
|
|
|
|
.br
|
|
|
|
|
\fBgetfattr\fR
|
|
|
|
|
prints eventual xattr name\-value pairs from user namespace
|
|
|
|
|
prints xattr name\-value pairs from user namespace
|
|
|
|
|
to the result channel.
|
|
|
|
|
.br
|
|
|
|
|
\fBget_any_xattr\fR
|
|
|
|
|
prints eventual xattr name\-value pairs from any namespace
|
|
|
|
|
prints xattr name\-value pairs from any namespace
|
|
|
|
|
except ACL to the result channel. This is mostly for debugging of
|
|
|
|
|
namespace "isofs".
|
|
|
|
|
.br
|
|
|
|
|
\fBget_md5\fR
|
|
|
|
|
prints eventual recorded MD5 sum together with file path.
|
|
|
|
|
prints the MD5 sum, if recorded, together with file path.
|
|
|
|
|
.br
|
|
|
|
|
\fBcheck_md5\fR
|
|
|
|
|
compares eventual recorded MD5 sum with the file content
|
|
|
|
|
compares the MD5 sum, if recorded, with the file content
|
|
|
|
|
and reports if mismatch.
|
|
|
|
|
.br
|
|
|
|
|
E.g.: \-find / \-not \-pending_data \-exec check_md5 FAILURE \-\-
|
|
|
|
|
@ -1845,7 +1852,7 @@ Options are:
|
|
|
|
|
"suffix=..." sets a file name suffix. If it is not empty then it will be
|
|
|
|
|
appended to the file name or removed from it.
|
|
|
|
|
.br
|
|
|
|
|
"remove_suffix" will remove an eventual file name suffix
|
|
|
|
|
"remove_suffix" will remove a file name suffix
|
|
|
|
|
rather than appending it.
|
|
|
|
|
.br
|
|
|
|
|
"if_nonempty" will leave 0\-sized files unfiltered.
|
|
|
|
|
@ -1903,7 +1910,7 @@ with files from the loaded ISO image if the write method of growing is in
|
|
|
|
|
effect (i.e \-indev and \-outdev are identical).
|
|
|
|
|
.br
|
|
|
|
|
The reserved filter name "\-\-remove\-all\-filters" revokes
|
|
|
|
|
filtering. This will revoke eventual suffix renamings as well.
|
|
|
|
|
filtering. This will revoke suffix renamings as well.
|
|
|
|
|
Use "\-\-remove\-all\-filters+" to
|
|
|
|
|
prevent any suffix renaming.
|
|
|
|
|
.TP
|
|
|
|
|
@ -1919,8 +1926,8 @@ Discard the manipulated ISO image and reload it from \-indev.
|
|
|
|
|
(Use \-rollback_end if immediate program end is desired.)
|
|
|
|
|
.TP
|
|
|
|
|
\fB\-commit\fR
|
|
|
|
|
Perform the write operation. Afterwards eventually make the
|
|
|
|
|
\-outdev the new \-dev and load the image from there.
|
|
|
|
|
Perform the write operation. Afterwards, if \-outdev is readable, make it
|
|
|
|
|
the new \-dev and load the image from there.
|
|
|
|
|
Switch to growing mode.
|
|
|
|
|
(A subsequent \-outdev will activate modification mode or blind growing.)
|
|
|
|
|
\-commit is performed automatically at end of program if there
|
|
|
|
|
@ -1954,7 +1961,7 @@ Note: It is not possible yet to effectively eject disk files.
|
|
|
|
|
\fB\-commit_eject\fR "in"|"out"|"all"|"none"
|
|
|
|
|
Combined \-commit and \-eject. When writing has finished do not make
|
|
|
|
|
\-outdev the new \-dev, and load no ISO image. Rather eject
|
|
|
|
|
\-indev and/or \-outdev. Eventually give up any non\-ejected drive.
|
|
|
|
|
\-indev and/or \-outdev. Give up any non\-ejected drive.
|
|
|
|
|
.TP
|
|
|
|
|
\fB\-blank\fR mode
|
|
|
|
|
Make media ready for writing from scratch (if not \-dummy is activated).
|
|
|
|
|
@ -2401,7 +2408,7 @@ because they appear to inadverted readers as one single session.
|
|
|
|
|
But with multi\-session media CD\-R[W], DVD\-R[W], DVD+R, it implies that the
|
|
|
|
|
whole bootable system has to reside already in the first session and that
|
|
|
|
|
the last session still has to bear all files which the booted system expects
|
|
|
|
|
after eventually mounting the ISO image.
|
|
|
|
|
after mounting the ISO image.
|
|
|
|
|
.br
|
|
|
|
|
If a boot image from ISOLINUX or GRUB is known to be present on media then
|
|
|
|
|
it is advised to patch it
|
|
|
|
|
@ -2422,7 +2429,7 @@ and announced by an MBR partition table entry.
|
|
|
|
|
.br
|
|
|
|
|
"discard"|"keep"|"patch"|"show_status"|bootspec|"next"
|
|
|
|
|
.br
|
|
|
|
|
Define the handling of an eventual set of El Torito boot images which
|
|
|
|
|
Define the handling of a set of El Torito boot images which
|
|
|
|
|
has been read from an existing ISO image or define how to make a prepared
|
|
|
|
|
boot image file set bootable. Such file sets get produced by ISOLINUX or GRUB.
|
|
|
|
|
.br
|
|
|
|
|
@ -2461,8 +2468,8 @@ For ISOLINUX : \-boot_image "isolinux" "patch"
|
|
|
|
|
and their designated fate.
|
|
|
|
|
.br
|
|
|
|
|
|
|
|
|
|
A \fBbootspec\fR is a word of the form name=value and is used to describe
|
|
|
|
|
the parameters of a boot image by an El Torito record and eventually a MBR.
|
|
|
|
|
A \fBbootspec\fR is a word of the form name=valuei. It is used to describe
|
|
|
|
|
the parameters of a boot image by an El Torito record or a MBR.
|
|
|
|
|
The names "dir", "bin_path", "efi_path" lead to El Torito bootable images.
|
|
|
|
|
Name "system_area" activates a given file as MBR.
|
|
|
|
|
.br
|
|
|
|
|
@ -2530,8 +2537,7 @@ They get attributed to the boot image entry in the catalog.
|
|
|
|
|
.br
|
|
|
|
|
\fBnext\fR ends the definition of a boot image and starts a new one.
|
|
|
|
|
Any following \-bootimage bootspecs will affect the new image.
|
|
|
|
|
The first "next" discards eventually loaded boot images and their
|
|
|
|
|
catalog.
|
|
|
|
|
The first "next" discards loaded boot images and their catalog.
|
|
|
|
|
.br
|
|
|
|
|
\fBdiscard\fR gives up an existing boot catalog and its boot images.
|
|
|
|
|
.br
|
|
|
|
|
@ -2570,7 +2576,7 @@ and sizes as if it had been processed by "partition_table=on". If so,
|
|
|
|
|
then those parameters get updated when the new System Area is written.
|
|
|
|
|
.br
|
|
|
|
|
Special "system_area=/dev/zero" causes 32k of NUL\-bytes.
|
|
|
|
|
Use this to discard an MBR which eventually was loaded with the ISO image.
|
|
|
|
|
Use this to discard an MBR which was loaded with the ISO image.
|
|
|
|
|
.br
|
|
|
|
|
\fBpartition_offset=\fR2kb_block_adr causes a partition table with a single
|
|
|
|
|
partition that begins at the given block address. This is counted in 2048 byte
|
|
|
|
|
@ -2610,23 +2616,20 @@ Mode "off" disables alignment for any type.
|
|
|
|
|
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=.
|
|
|
|
|
It will overwrite the first 512 bytes of any data 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 other boot
|
|
|
|
|
blocks.
|
|
|
|
|
It will overwrite the first 512 bytes of any data eventually
|
|
|
|
|
provided by system_area=.
|
|
|
|
|
It will overwrite the first 512 bytes of any data provided by system_area=.
|
|
|
|
|
Only a single boot file can be declared by mipsel_path=.
|
|
|
|
|
.br
|
|
|
|
|
\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.
|
|
|
|
|
The first 512 bytes of any data 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
|
|
|
|
|
@ -2694,14 +2697,14 @@ symbolic file address
|
|
|
|
|
The file address in an .md5 line has to bear the same basename as the
|
|
|
|
|
disk_path of the file which it shall match. The directory path of
|
|
|
|
|
the file address is decisive for To=From mapping, not for file recognition.
|
|
|
|
|
After eventual To=From mapping, the file address gets written into the .jigdo
|
|
|
|
|
After To=From mapping, the file address gets written into the .jigdo
|
|
|
|
|
file. Jigdo restore tools will convert these addresses into really
|
|
|
|
|
reachable data source addresses from which they can read.
|
|
|
|
|
.br
|
|
|
|
|
If the list of jigdo parameters is not empty, then \fBxorriso\fR will
|
|
|
|
|
refuse to
|
|
|
|
|
write to non\-blank targets, it will disable multi\-session emulation, and
|
|
|
|
|
eventual padding will be counted as part of the ISO image.
|
|
|
|
|
padding will be counted as part of the ISO image.
|
|
|
|
|
.br
|
|
|
|
|
.TP
|
|
|
|
|
\fB\-jigdo\fR parameter_name value
|
|
|
|
|
@ -2917,11 +2920,11 @@ signals (e.g. from program "kill" or from keys Ctrl+C) or on signals
|
|
|
|
|
caused by severe program errors.
|
|
|
|
|
.br
|
|
|
|
|
Mode "on" is the default. It uses the signal handler of libburn which produces
|
|
|
|
|
ugly messages but puts much effort in releasing eventually used optical drives
|
|
|
|
|
ugly messages but puts much effort in releasing optical drives
|
|
|
|
|
before \fBxorriso\fR ends.
|
|
|
|
|
.br
|
|
|
|
|
Mode "off" as first \-signal_handling among the start arguments prevents all
|
|
|
|
|
own signal precautions of \fBxorriso\fR. Eventually inherited signal
|
|
|
|
|
own signal precautions of \fBxorriso\fR. Inherited signal
|
|
|
|
|
handler settings stay as they are.
|
|
|
|
|
.br
|
|
|
|
|
It works like "sig_dfl" if given after other signal handling was already
|
|
|
|
|
@ -3039,7 +3042,7 @@ their libburn standard device files.
|
|
|
|
|
.br
|
|
|
|
|
This is only possible when no ISO image changes are pending.
|
|
|
|
|
After this option was executed, there is no drive current
|
|
|
|
|
and no image loaded. Eventually one has to aquire a drive again.
|
|
|
|
|
and no image loaded.
|
|
|
|
|
.br
|
|
|
|
|
In order to be visible, a device has to offer rw\-permissions
|
|
|
|
|
with its libburn standard device file. Thus it might be only the
|
|
|
|
|
@ -3063,7 +3066,7 @@ with only one or two sessions on it. The last of these sessions is supposed
|
|
|
|
|
to be the most recent real session then.
|
|
|
|
|
.br
|
|
|
|
|
Some read\-only drives and media show no usable session history at all.
|
|
|
|
|
Eventually option \-rom_toc_scan might help.
|
|
|
|
|
Option \-rom_toc_scan might help.
|
|
|
|
|
.TP
|
|
|
|
|
\fB\-mount_cmd\fR drive entity id path
|
|
|
|
|
Emit an appropriate command line for mounting the ISO session
|
|
|
|
|
@ -3304,9 +3307,10 @@ composed from disk_path by replacing disk_prefix by iso_rr_prefix.
|
|
|
|
|
\fB\-show_stream\fR iso_rr_path [***]
|
|
|
|
|
Display the content stream chain of data files in the ISO image. The chain
|
|
|
|
|
consists of the iso_rr_name and one or more streams, separated by " < " marks.
|
|
|
|
|
A stream consists of one or more texts eventually in ''\-quotation marks,
|
|
|
|
|
eventually separated by ":" characters. The first text describes the stream
|
|
|
|
|
type, the following ones describe its individual properties.
|
|
|
|
|
A stream description consists of one or more texts, separated by ":"
|
|
|
|
|
characters.
|
|
|
|
|
The first text tells the stream type, the following ones, if ever, describe its
|
|
|
|
|
individual properties.
|
|
|
|
|
Frequently used types are:
|
|
|
|
|
.br
|
|
|
|
|
disk:'disk_path' for local filesystem objects.
|
|
|
|
|
@ -3342,7 +3346,7 @@ sessions. These checksums are reachable only via indev and a loaded image.
|
|
|
|
|
They work independently of the media type and can detect transmission errors.
|
|
|
|
|
.TP
|
|
|
|
|
\fB\-check_media\fR [option [option ...]] --
|
|
|
|
|
Try to read data blocks from the indev drive, eventually copy them to a
|
|
|
|
|
Try to read data blocks from the indev drive, optionally copy them to a
|
|
|
|
|
disk file, and finally report about the encountered quality. Several options
|
|
|
|
|
may be used to modify the default behavior.
|
|
|
|
|
.br
|
|
|
|
|
@ -3360,12 +3364,12 @@ allowed to be unreadable (e.g. gaps between tracks).
|
|
|
|
|
Alternatively it is possible to report damaged files rather than blocks.
|
|
|
|
|
.br
|
|
|
|
|
If \-md5 is "on" then the default mode what=tracks looks out for libisofs
|
|
|
|
|
checksum tags for the ISO session data and eventually checks them
|
|
|
|
|
checksum tags for the ISO session data and checks them
|
|
|
|
|
against the checksums computed from the data stream.
|
|
|
|
|
.TP
|
|
|
|
|
\fB\-check_media_defaults\fR [option [option ...]] --
|
|
|
|
|
Preset options for runs of \-check_media, \-extract_cut and best_effort
|
|
|
|
|
file extraction. Eventual options given with \-check_media will override the
|
|
|
|
|
file extraction. Options given with \-check_media will override the
|
|
|
|
|
preset options. \-extract_cut will override some options automatically.
|
|
|
|
|
.br
|
|
|
|
|
An option consists of a keyword, a "=" character, and a value. Options
|
|
|
|
|
@ -3448,13 +3452,13 @@ recorded MD5 checksums. Severity "ALL" disables this event.
|
|
|
|
|
tries to read the file given by disk_path as
|
|
|
|
|
sector bitmap and to store such a map file after the scan run.
|
|
|
|
|
The bitmap tells which blocks have been read successfully in previous runs.
|
|
|
|
|
It allows to do several scans on the same media, eventually with intermediate
|
|
|
|
|
It allows to do several scans on the same media, even with intermediate
|
|
|
|
|
eject, in order to collect readable blocks whenever the drive is lucky enough
|
|
|
|
|
to produce them. The stored file contains a human readable TOC of tracks
|
|
|
|
|
and their start block addresses, followed by binary bitmap data.
|
|
|
|
|
.br
|
|
|
|
|
\fBmap_with_volid="on"\fR
|
|
|
|
|
examines tracks whether they are ISO images and eventually
|
|
|
|
|
examines tracks whether they are ISO images and
|
|
|
|
|
prints their volume ids into the human readable TOC of sector_map=.
|
|
|
|
|
.br
|
|
|
|
|
\fBpatch_lba0="on"\fR
|
|
|
|
|
@ -3669,7 +3673,7 @@ of mkisofs emulation in the context of a \fBxorriso\fR run.
|
|
|
|
|
.br
|
|
|
|
|
Other than with the "cdrecord" personality there is no automatic \-commit at
|
|
|
|
|
the end of a "mkisofs" option list. Verbosity settings \-v (= "UPDATE") and
|
|
|
|
|
\-quiet (= "SORRY") persist. The output file, eventually chosen with \-o,
|
|
|
|
|
\-quiet (= "SORRY") persist. The output file
|
|
|
|
|
persists until things happen like \-commit, \-rollback, \-dev, or end of
|
|
|
|
|
\fBxorriso\fR.
|
|
|
|
|
\-pacifier gets set to "mkisofs" if files are added to the image.
|
|
|
|
|
@ -3694,7 +3698,7 @@ standard output.
|
|
|
|
|
\-print\-size inhibits automatic image production at program end. This ban is
|
|
|
|
|
lifted only if the pending image changes get discarded.
|
|
|
|
|
.br
|
|
|
|
|
Eventual padding is counted as part of the ISO image if not option \-\-emul\-toc
|
|
|
|
|
Padding is counted as part of the ISO image if not option \-\-emul\-toc
|
|
|
|
|
is given.
|
|
|
|
|
.br
|
|
|
|
|
If no \-iso\-level is given, then level 1 is chosen when the first file or
|
|
|
|
|
@ -3793,7 +3797,7 @@ The scope is only a single data track per session to be written
|
|
|
|
|
to blank, overwriteable, or appendable media. The media gets closed if
|
|
|
|
|
closing is applicable and not option \-multi is present.
|
|
|
|
|
.br
|
|
|
|
|
An eventually acquired input drive is given up.
|
|
|
|
|
If an input drive was aquired, then it is given up.
|
|
|
|
|
This is only allowed if no image changes are pending.
|
|
|
|
|
.br
|
|
|
|
|
dev= must be given as \fBxorriso\fR device address. Addresses like 0,0,0
|
|
|
|
|
@ -3816,7 +3820,7 @@ are aliases for "cdrecord".
|
|
|
|
|
If \fBxorriso\fR is started with one of the leafnames "xorrecord",
|
|
|
|
|
"cdrskin", "cdrecord", or "wodim", then it automatically prepends \-as "cdrskin"
|
|
|
|
|
to the command line arguments. I.e. all arguments will be interpreted cdrecord
|
|
|
|
|
style until "\-\-" is encountered and an eventual commit happens.
|
|
|
|
|
style until "\-\-" is encountered.
|
|
|
|
|
From then on, options are interpreted as \fBxorriso\fR options.
|
|
|
|
|
.br
|
|
|
|
|
\-\-no_rc as first argument of such a program start
|
|
|
|
|
@ -3870,8 +3874,7 @@ Program scdbackup_verify will recognize and verify tag resp. record.
|
|
|
|
|
\fB\-no_rc\fR
|
|
|
|
|
.br
|
|
|
|
|
Only if used as first command line argument this option
|
|
|
|
|
prevents reading and interpretation of eventual startup
|
|
|
|
|
files. See section FILES below.
|
|
|
|
|
prevents reading and interpretation of startup files. See section FILES below.
|
|
|
|
|
.TP
|
|
|
|
|
\fB\-options_from_file\fR fileaddress
|
|
|
|
|
Read quoted input from fileaddress and execute it like dialog lines.
|
|
|
|
|
@ -4018,7 +4021,7 @@ Only "\-scsi_log" with dash "\-" is recognized that way.
|
|
|
|
|
.TP
|
|
|
|
|
\fB\-end\fR
|
|
|
|
|
.br
|
|
|
|
|
End program after writing eventually pending changes.
|
|
|
|
|
End program after writing pending changes.
|
|
|
|
|
.TP
|
|
|
|
|
\fB\-rollback_end\fR
|
|
|
|
|
Discard pending changes. End program immediately.
|
|
|
|
|
@ -4026,7 +4029,7 @@ Discard pending changes. End program immediately.
|
|
|
|
|
\fB#\fR any text
|
|
|
|
|
Only in dialog or file execution mode, and only as first
|
|
|
|
|
non\-whitespace in line:
|
|
|
|
|
Do not execute the line but eventually store it in history.
|
|
|
|
|
Do not execute the line but store it in readline history.
|
|
|
|
|
.TP
|
|
|
|
|
.B Support for frontend programs via stdin and stdout:
|
|
|
|
|
.TP
|
|
|
|
|
@ -4279,7 +4282,7 @@ set ISO\-8859\-1 but that the readers expected UTF\-8. Now a new session with
|
|
|
|
|
the same files gets added with converted file names.
|
|
|
|
|
In order to avoid any weaknesses of the local character set, this command
|
|
|
|
|
pretends that it uses already the final target set UTF\-8.
|
|
|
|
|
Therefore strange file names may appear in eventual messages which
|
|
|
|
|
Therefore strange file names may appear in messages, which
|
|
|
|
|
will be made terminal\-safe by option \-backslash_codes.
|
|
|
|
|
.br
|
|
|
|
|
$ xorriso \-in_charset ISO\-8859\-1 \-local_charset UTF\-8 \\
|
|
|
|
|
@ -4539,7 +4542,7 @@ $ xorriso \-outdev /dev/sr0 \-toc
|
|
|
|
|
.br
|
|
|
|
|
Then load the desired session and copy the file trees to disk.
|
|
|
|
|
Enable restoring of ACL, xattr and hard links.
|
|
|
|
|
Avoid to eventually create /home/thomas/restored without rwx\-permission.
|
|
|
|
|
Avoid to create /home/thomas/restored without rwx\-permission.
|
|
|
|
|
.br
|
|
|
|
|
$ xorriso \-for_backup \\
|
|
|
|
|
.br
|
|
|
|
|
@ -4570,7 +4573,7 @@ $ xorriso \-abort_on NEVER \-indev /dev/sr0 \\
|
|
|
|
|
.br
|
|
|
|
|
data_to="$HOME"/dvd_copy sector_map="$HOME"/dvd_copy.map \-\-
|
|
|
|
|
.br
|
|
|
|
|
This can be repeated several times, eventually with \-eject or with other
|
|
|
|
|
This can be repeated several times, if necessary with \-eject or with other
|
|
|
|
|
\-indev drives. See the human readable part of "$HOME"/dvd_copy.map for
|
|
|
|
|
addresses which can be used on "$HOME"/dvd_copy with mount option \-o sbsector=
|
|
|
|
|
resp. \-s.
|
|
|
|
|
|
