Avoided the use of the term 'eventual' for the meaning 'if applicable'.
This commit is contained in:
parent
dfccac8ba7
commit
75a626d4d4
@ -2,8 +2,11 @@ SVN trunk (to become libisoburn-1.1.0.pl00.tar.gz)
|
||||
===============================================================================
|
||||
* Bug fix: -mount_opts shared worked only with -osirrox o_excl_off
|
||||
* Bug fix: xorriso command -add_plainly "any" did not add all files to the image
|
||||
* New option -signal_handling
|
||||
* Bug fix: The attempt to blank already blank DVD-RW was not gracefully blocked
|
||||
* Bug fix (libisofs): -as mkisofs -isohybrid-mbr without -no-pad
|
||||
was not cylinder aligned
|
||||
* New option -signal_handling
|
||||
* New option -close_damaged
|
||||
|
||||
|
||||
libisoburn-1.0.8.pl00.tar.gz Thu Apr 14 2011
|
||||
|
||||
@ -163,7 +163,7 @@ your desired drive, then consider to kill it.
|
||||
If you cannot get rid of the automounter that easily, try whether it helps
|
||||
to always load the drive tray manually before starting a write run of
|
||||
xorriso. Wait until the drive light is off.
|
||||
Better try to unmount an eventually mounted media before a write run.
|
||||
Better try to unmount a mounted media before a write run.
|
||||
|
||||
|
||||
Besides true optical drives, libisoburn can also address disk files as input or
|
||||
|
||||
@ -128,7 +128,7 @@ address 16*2048 and to let start partition 1 at this address. The second
|
||||
superblock leads to a second directory tree which takes into account the
|
||||
address difference between partition 1 and the base device. So the image
|
||||
gets mountable via both devices and reserves 32 kB for boot manager software
|
||||
where it eventually can manipulate and augment the MBR.
|
||||
where it may manipulate and augment the MBR.
|
||||
(See [http://libburnia-project.org/wiki/PartitionOffset Partition Offset Wiki]
|
||||
for examples.)
|
||||
|
||||
|
||||
@ -10,7 +10,7 @@ via the partition device file. E.g. on GNU/Linux: /dev/sdb and /dev/sdb1.
|
||||
This is achieved by two distinct sets of meta-data which refer to the same
|
||||
file content.
|
||||
|
||||
The dual-mount feature supports Rock Ridge and eventually Joliet too.
|
||||
The dual-mount feature supports Rock Ridge and Joliet too.
|
||||
It is capable of multi-session.
|
||||
|
||||
Currently only offset 32 kB seems to make sense. Smaller offsets are prohibited
|
||||
@ -176,8 +176,8 @@ E.g. by 402 kB to 2 MB.
|
||||
Open questions:
|
||||
|
||||
- Shall the partition of an isohybrid image be marked bootable ?
|
||||
Currently xorriso keeps the 0x80 mark of an eventually imported MBR
|
||||
resp. the 0x80 mark which xorriso eventually sets by its own MBR
|
||||
Currently xorriso keeps the 0x80 mark of an imported MBR
|
||||
resp. the 0x80 mark which xorriso sets by its own MBR
|
||||
preparations.
|
||||
- If not to be marked bootable:
|
||||
What equipment would the partition need to justify having the mark ?
|
||||
|
||||
@ -166,7 +166,7 @@ your desired drive, then consider to kill it.
|
||||
If you cannot get rid of the automounter that easily, try whether it helps
|
||||
to always load the drive tray manually before starting a write run of
|
||||
xorriso. Wait until the drive light is off.
|
||||
Better try to unmount an eventually mounted media before a write run.
|
||||
Better try to unmount a mounted media before a write run.
|
||||
|
||||
|
||||
Besides true optical drives, xorriso can also address disk files as input or
|
||||
@ -237,7 +237,7 @@ any file but rather tell the MD5 of a certain range of data blocks.
|
||||
The superblock checksum tag is written after the ECMA-119 volume descriptors.
|
||||
The tree checksum tag is written after the ECMA-119 directory entries.
|
||||
The session checksum tag is written after all payload including the checksum
|
||||
array. (Then follows eventual padding.)
|
||||
array. (Then follows padding.)
|
||||
|
||||
The tags are single lines of printable text, padded by 0 bytes. They have
|
||||
the following format:
|
||||
@ -254,7 +254,7 @@ Tag_id distinguishes the following tag types
|
||||
|
||||
A relocated superblock may appear at LBA 0 of an image which was produced for
|
||||
being stored in a disk file or on overwriteable media (e.g. DVD+RW, BD-RE).
|
||||
xorriso records the first session at LBA 32. An eventual follow-up session
|
||||
xorriso records the first session at LBA 32. A follow-up session
|
||||
begins at the next block address which is divisible by 32 and higher than the
|
||||
address of the previous session's end tag. Normally no session starts after the
|
||||
address given by relocated superblock parameter session_start=.
|
||||
|
||||
@ -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.
|
||||
|
||||
@ -231,7 +231,7 @@ int Xorriso_destroy(struct XorrisO **xorriso, int flag);
|
||||
/* --------------------- Command Interpreters ------------------- */
|
||||
|
||||
|
||||
/* This special interpreter is eventually called between Xorriso_new() and
|
||||
/* This special interpreter may be called between Xorriso_new() and
|
||||
Xorriso_startup_libraries(). It interprets certain commands which shall
|
||||
get into effect before the libraries get initialized:
|
||||
-abort_on , -report_about , -return_with , -list_delimiter ,
|
||||
@ -273,7 +273,7 @@ int Xorriso_prescan_args(struct XorrisO *xorriso, int argc, char **argv,
|
||||
int Xorriso_read_rc(struct XorrisO *xorriso, int flag);
|
||||
|
||||
|
||||
/* Check whether program arguments shall be backslash decoded and eventually
|
||||
/* Check whether program arguments shall be backslash decoded. If so, then
|
||||
replace *argv by a new argument vector. The old one will not be freed
|
||||
by this call. If it is dynamic memory then you need to keep a copy of
|
||||
the pointer and free it yourself after this call.
|
||||
@ -333,7 +333,8 @@ int Xorriso_interpreter(struct XorrisO *xorriso,
|
||||
int Xorriso_execute_option(struct XorrisO *xorriso, char *line, int flag);
|
||||
|
||||
|
||||
/* Enter xorriso command line dialog mode, eventually using libreadline.
|
||||
/* Enter xorriso command line dialog mode, using libreadline if configured
|
||||
at build time and not disabled at run time.
|
||||
This call returns immediately if not option -dialog "on" was performed
|
||||
before.
|
||||
@param xorriso The context object in which to perform the commands.
|
||||
@ -848,7 +849,7 @@ int Xorriso_option_external_filter(struct XorrisO *xorriso,
|
||||
/* Options -extract , -extract_single */
|
||||
/* @param flag bit0=do not report the restored item
|
||||
bit1=do not reset pacifier, no final pacifier message
|
||||
bit5= -extract_single: eventually do not insert directory tree
|
||||
bit5= -extract_single: do not insert directory tree
|
||||
*/
|
||||
int Xorriso_option_extract(struct XorrisO *xorriso, char *disk_path,
|
||||
char *iso_path, int flag);
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -242,13 +242,13 @@ one and the modifications.
|
||||
See paragraph Creating, Growing, Modifying, Blind Growing below.
|
||||
@c man .PP
|
||||
@sp 1
|
||||
@command{xorriso} 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.
|
||||
@command{xorriso} 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.
|
||||
@c man .br
|
||||
The first session of a @command{xorriso} 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.
|
||||
@c man .PP
|
||||
@ -305,7 +305,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 @command{xorriso}.
|
||||
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.
|
||||
@*
|
||||
@sp 1
|
||||
@cindex Appendable media, _definition
|
||||
@ -354,7 +354,7 @@ They have quite different capabilities and constraints.
|
||||
@sp 1
|
||||
@cindex Growing, _definition
|
||||
The method of @strong{growing} 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.
|
||||
@ -551,7 +551,7 @@ It uses this extension if enabled by option
|
||||
@strong{-acl}.
|
||||
@*
|
||||
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 @command{xorriso} 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
|
||||
@ -559,8 +559,8 @@ print them in a format suitable for tool setfacl.
|
||||
@*
|
||||
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::". @command{xorriso} brings "group::" into effect
|
||||
before eventually removing the ACL from a file.
|
||||
according to entry "group::". When removing ACL from a file,
|
||||
@command{xorriso} brings "group::" into effect.
|
||||
@c man .PP
|
||||
@sp 1
|
||||
@cindex xattr, _definiton
|
||||
@ -610,14 +610,14 @@ appears among the arguments of such a command.
|
||||
@cindex Pattern expansion, _definition
|
||||
@strong{Pattern expansion}
|
||||
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.
|
||||
@*
|
||||
Pattern matching supports the usual shell parser wildcards '*' '?' '[xyz]'
|
||||
and respects '/' as separator which may only be matched literally.
|
||||
@*
|
||||
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 "[...]".
|
||||
@*
|
||||
Some other commands perform pattern matching unconditionally.
|
||||
@ -652,10 +652,10 @@ as in $'...' of bash.
|
||||
It is not enabled by default. See option -backslash_codes.
|
||||
@c man .PP
|
||||
@sp 1
|
||||
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.
|
||||
@c man .PP
|
||||
@sp 1
|
||||
@ -748,20 +748,24 @@ inner dashes are interpreted as underscores.
|
||||
@section Aquiring source and target drive
|
||||
@c man .B Aquiring source and target drive:
|
||||
@c man .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.
|
||||
@table @asis
|
||||
@sp 1
|
||||
@c man .TP
|
||||
@item -dev address
|
||||
@kindex -dev aquires one drive for input and output
|
||||
@cindex Drive, for input and output, -dev
|
||||
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.
|
||||
@*
|
||||
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.
|
||||
@*
|
||||
Special address string "-" means standard output, to which several restrictions
|
||||
apply. See above paragraph "Libburn drives".
|
||||
@ -772,7 +776,8 @@ without aquiring a new one.
|
||||
@item -indev address
|
||||
@kindex -indev aquires a drive for input
|
||||
@cindex Drive, for input, -indev
|
||||
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.
|
||||
@ -856,11 +861,11 @@ will be reset to "auto".
|
||||
@item -displacement [-]lba
|
||||
@kindex -displacement compensate altered image start address
|
||||
@cindex Session, altered start address, -displacement
|
||||
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.
|
||||
@*
|
||||
Examples:
|
||||
@ -897,7 +902,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".
|
||||
@*
|
||||
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.
|
||||
@*
|
||||
By pseudo-class "clear_list" and pseudo-patterns "banned", "caution",
|
||||
@ -927,8 +932,7 @@ input media and does not discard an already loaded image.
|
||||
@kindex -in_charset sets input character set
|
||||
@cindex Character Set, for input, -in_charset
|
||||
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.
|
||||
@c man .TP
|
||||
@ -936,9 +940,9 @@ will be copied to -in_charset.
|
||||
@kindex -auto_charset learns character set from image
|
||||
@cindex Character set, learn from image, -auto_charset
|
||||
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.
|
||||
@*
|
||||
Note that the default output charset is the local character set of the
|
||||
terminal where @command{xorriso} runs. Before attributing this local
|
||||
@ -955,7 +959,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.
|
||||
@*
|
||||
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.
|
||||
@ -1005,12 +1010,12 @@ See also options -getfattr, -setfattr and above paragraph about xattr.
|
||||
@kindex -md5 controls handling of MD5 sums
|
||||
@cindex MD5, control handling, -md5
|
||||
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.
|
||||
@*
|
||||
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.
|
||||
@ -1047,7 +1052,7 @@ Currently this is a shortcut for: -hardlinks on -acl on -xattr on -md5 on.
|
||||
@kindex -disk_dev_ino fast incremental backup
|
||||
@cindex Backup, enable fast incremental, -disk_dev_ino
|
||||
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.
|
||||
@ -1074,7 +1079,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.)
|
||||
@*
|
||||
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
|
||||
@ -1163,8 +1168,9 @@ If other file types collide then the setting of command
|
||||
decides.
|
||||
@*
|
||||
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.
|
||||
@c man .PP
|
||||
@sp 1
|
||||
The commands in this section alter the ISO image and not the local filesystem.
|
||||
@ -1194,7 +1200,7 @@ Insert the given files or directory trees from filesystem
|
||||
into the ISO image.
|
||||
@*
|
||||
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:
|
||||
@*
|
||||
iso_rr_path=disk_path
|
||||
@ -1207,9 +1213,10 @@ 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.
|
||||
@*
|
||||
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.
|
||||
@c man .TP
|
||||
@item -add_plainly mode
|
||||
@kindex -add_plainly inserts one or more paths
|
||||
@ -1217,7 +1224,7 @@ The resulting words are used as both, iso_rr_path and disk path. Eventually
|
||||
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.
|
||||
@*
|
||||
Mode "dashed" is similar to "unknown" but also adds unrecognized command
|
||||
words even if they begin with "-".
|
||||
@ -1360,8 +1367,8 @@ other file causes a FAILURE event.
|
||||
@cindex Directory, copy, -clone
|
||||
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.
|
||||
@*
|
||||
The copied ISO file objects have the same attributes. Copied data files
|
||||
refer to the same content source as their originals.
|
||||
@ -1374,7 +1381,7 @@ already exists in the ISO tree.
|
||||
@kindex -cp_clone copies ISO directory tree
|
||||
@cindex Directories, copy, -cp_clone
|
||||
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.
|
||||
@*
|
||||
The rules for generating the copy addresses are the same as with
|
||||
@ -1405,8 +1412,8 @@ up to 2g -1 @minus{}@minus{}. Newer ones are good up to 4g -1 @minus{}@minus{}.
|
||||
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.
|
||||
@*
|
||||
@command{xorriso}'s own data read capabilities are not affected by eventual
|
||||
operating system size limits. They apply to mounting only. Nevertheless,
|
||||
@command{xorriso}'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.
|
||||
@c man .TP
|
||||
@item -not_mgt code[:code[...]]
|
||||
@ -1457,7 +1464,7 @@ get reported with -compare and deleted from the image with -update.
|
||||
@cindex Insert, file exclusion absolute, -not_paths
|
||||
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.
|
||||
@*
|
||||
(Do not forget to end the list of disk_paths by "@minus{}@minus{}")
|
||||
@ -1552,7 +1559,7 @@ like with program mkisofs -graft-points.
|
||||
It also disables -disk_pattern expansion for command -add.
|
||||
@*
|
||||
"off" disables pathspecs of the form target=source
|
||||
and eventually enables -disk_pattern expansion.
|
||||
and re-enables -disk_pattern expansion.
|
||||
@c man .TP
|
||||
@item -overwrite "on"|"nondir"|"off"
|
||||
@kindex -overwrite enables overwriting in ISO
|
||||
@ -1718,8 +1725,8 @@ Like -chmod but affecting all files below eventual directories.
|
||||
@item -setfacl acl_text iso_rr_path [***]
|
||||
@kindex -setfacl sets ACL in ISO image
|
||||
@cindex ACL, set in ISO image, -setfacl
|
||||
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
|
||||
"@minus{}@minus{}remove-all",
|
||||
then the existing ACLs will be removed and no new ones will be
|
||||
@ -1857,7 +1864,7 @@ Like -alter_date but affecting all files below eventual directories.
|
||||
@cindex hidden, set in ISO image, -hide
|
||||
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.
|
||||
@*
|
||||
@ -1911,7 +1918,7 @@ Can be true only for data files which stem not from the loaded image.
|
||||
@item -type 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.
|
||||
@*
|
||||
Only the first letter is interpreted. E.g.: -find / -type d
|
||||
@*
|
||||
@ -1997,10 +2004,10 @@ Normal precedence is: -not, -or , -and.
|
||||
@c man \fB\-if\fR ... \fB\-then\fR\ ... \fB\-elseif\fR ... \fB\-then\fR ...
|
||||
@c man \fB\-else\fR ... \fB\-endif\fR :
|
||||
@c man-ignore-lines 1
|
||||
@item -if ... -then\ ... -elseif ... -then ... -else ... -endif :
|
||||
@item -if ... -then ... -elseif ... -then ... -else ... -endif :
|
||||
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.
|
||||
@ -2088,7 +2095,7 @@ removes an eventual marking from action "update_merge".
|
||||
@*
|
||||
@item report_damage
|
||||
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.
|
||||
@*
|
||||
@ -2103,25 +2110,25 @@ different extent number in column "xt".
|
||||
prints access permissions in ACL text form to the result channel.
|
||||
@*
|
||||
@item setfacl
|
||||
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.
|
||||
@*
|
||||
E.g.: -exec setfacl u:lisa:rw,u::rw,g::r,o::@minus{},m::rw @minus{}@minus{}
|
||||
@*
|
||||
@item getfattr
|
||||
prints eventual xattr name-value pairs from user namespace
|
||||
prints xattr name-value pairs from user namespace
|
||||
to the result channel.
|
||||
@*
|
||||
@item get_any_xattr
|
||||
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".
|
||||
@*
|
||||
@item get_md5
|
||||
prints eventual recorded MD5 sum together with file path.
|
||||
prints the MD5 sum, if recorded, together with file path.
|
||||
@*
|
||||
@item check_md5
|
||||
compares eventual recorded MD5 sum with the file content
|
||||
compares the MD5 sum, if recorded, with the file content
|
||||
and reports if mismatch.
|
||||
@*
|
||||
E.g.: -find / -not -pending_data -exec check_md5 FAILURE @minus{}@minus{}
|
||||
@ -2228,7 +2235,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.
|
||||
@*
|
||||
"remove_suffix" will remove an eventual file name suffix
|
||||
"remove_suffix" will remove a file name suffix
|
||||
rather than appending it.
|
||||
@*
|
||||
"if_nonempty" will leave 0-sized files unfiltered.
|
||||
@ -2292,7 +2299,7 @@ with files from the loaded ISO image if the write method of growing is in
|
||||
effect (i.e -indev and -outdev are identical).
|
||||
@*
|
||||
The reserved filter name "@minus{}@minus{}remove-all-filters" revokes
|
||||
filtering. This will revoke eventual suffix renamings as well.
|
||||
filtering. This will revoke suffix renamings as well.
|
||||
Use "@minus{}@minus{}remove-all-filters+" to
|
||||
prevent any suffix renaming.
|
||||
@c man .TP
|
||||
@ -2319,8 +2326,8 @@ Discard the manipulated ISO image and reload it from -indev.
|
||||
@item -commit
|
||||
@kindex -commit writes pending ISO image
|
||||
@cindex Write, pending ISO image, -commit
|
||||
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
|
||||
@ -2358,7 +2365,7 @@ Note: It is not possible yet to effectively eject disk files.
|
||||
@cindex Drive, write and eject, -commit_eject
|
||||
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.
|
||||
@c man .TP
|
||||
@item -blank mode
|
||||
@kindex -blank erases media
|
||||
@ -2871,7 +2878,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.
|
||||
@*
|
||||
If a boot image from ISOLINUX or GRUB is known to be present on media then
|
||||
it is advised to patch it
|
||||
@ -2898,7 +2905,7 @@ and announced by an MBR partition table entry.
|
||||
"discard"|"keep"|"patch"|"show_status"|bootspec|"next"
|
||||
@*
|
||||
@sp 1
|
||||
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.
|
||||
@*
|
||||
@ -2939,8 +2946,8 @@ and their designated fate.
|
||||
@*
|
||||
@sp 1
|
||||
|
||||
A @strong{bootspec} 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 @strong{bootspec} 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.
|
||||
@*
|
||||
@ -3008,8 +3015,7 @@ They get attributed to the boot image entry in the catalog.
|
||||
@*
|
||||
@strong{next} 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.
|
||||
@*
|
||||
@strong{discard} gives up an existing boot catalog and its boot images.
|
||||
@*
|
||||
@ -3051,7 +3057,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.
|
||||
@*
|
||||
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.
|
||||
@*
|
||||
@cindex Partition offset, _definiton
|
||||
@strong{partition_offset=}2kb_block_adr causes a partition table with a single
|
||||
@ -3095,15 +3101,13 @@ 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=.
|
||||
@*
|
||||
@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 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=.
|
||||
@*
|
||||
@cindex SUN Disk Label, production
|
||||
@ -3111,8 +3115,7 @@ Only a single boot file can be declared by mipsel_path=.
|
||||
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.
|
||||
@*
|
||||
@strong{mips_discard} and @strong{sparc_discard} revoke any boot file
|
||||
declarations made by mips_path= or mipsel_path=. They also disable production
|
||||
@ -3190,14 +3193,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.
|
||||
@*
|
||||
If the list of jigdo parameters is not empty, then @command{xorriso} 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.
|
||||
@*
|
||||
@table @asis
|
||||
@sp 1
|
||||
@ -3440,11 +3443,11 @@ signals (e.g. from program "kill" or from keys Ctrl+C) or on signals
|
||||
caused by severe program errors.
|
||||
@*
|
||||
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 @command{xorriso} ends.
|
||||
@*
|
||||
Mode "off" as first -signal_handling among the start arguments prevents all
|
||||
own signal precautions of @command{xorriso}. Eventually inherited signal
|
||||
own signal precautions of @command{xorriso}. Inherited signal
|
||||
handler settings stay as they are.
|
||||
@*
|
||||
It works like "sig_dfl" if given after other signal handling was already
|
||||
@ -3582,7 +3585,7 @@ their libburn standard device files.
|
||||
@*
|
||||
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.
|
||||
@*
|
||||
In order to be visible, a device has to offer rw-permissions
|
||||
with its libburn standard device file. Thus it might be only the
|
||||
@ -3608,7 +3611,7 @@ with only one or two sessions on it. The last of these sessions is supposed
|
||||
to be the most recent real session then.
|
||||
@*
|
||||
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.
|
||||
@c man .TP
|
||||
@item -mount_cmd drive entity id path
|
||||
@kindex -mount_cmd composes mount command line
|
||||
@ -3918,9 +3921,10 @@ composed from disk_path by replacing disk_prefix by iso_rr_prefix.
|
||||
@cindex Filter, show chain, -show_stream
|
||||
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:
|
||||
@*
|
||||
disk:'disk_path' for local filesystem objects.
|
||||
@ -3966,7 +3970,7 @@ They work independently of the media type and can detect transmission errors.
|
||||
@kindex -check_media reads media block by block
|
||||
@cindex Verify, check blocks, -check_media
|
||||
@cindex Recovery, retrieve blocks, -check_media
|
||||
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.
|
||||
@*
|
||||
@ -3984,14 +3988,14 @@ allowed to be unreadable (e.g. gaps between tracks).
|
||||
Alternatively it is possible to report damaged files rather than blocks.
|
||||
@*
|
||||
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.
|
||||
@c man .TP
|
||||
@item -check_media_defaults [option [option ...]] @minus{}@minus{}
|
||||
@kindex -check_media_defaults sets -check_media options
|
||||
@cindex Verify, preset -check_media, -check_media_defaults
|
||||
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.
|
||||
@*
|
||||
An option consists of a keyword, a "=" character, and a value. Options
|
||||
@ -4076,13 +4080,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.
|
||||
@*
|
||||
@item map_with_volid="on"
|
||||
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=.
|
||||
@*
|
||||
@item patch_lba0="on"
|
||||
@ -4339,7 +4343,7 @@ of mkisofs emulation in the context of a @command{xorriso} run.
|
||||
@*
|
||||
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
|
||||
@command{xorriso}.
|
||||
-pacifier gets set to "mkisofs" if files are added to the image.
|
||||
@ -4364,7 +4368,7 @@ standard output.
|
||||
-print-size inhibits automatic image production at program end. This ban is
|
||||
lifted only if the pending image changes get discarded.
|
||||
@*
|
||||
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.
|
||||
@*
|
||||
If no -iso-level is given, then level 1 is chosen when the first file or
|
||||
@ -4467,7 +4471,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.
|
||||
@*
|
||||
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.
|
||||
@*
|
||||
dev= must be given as @command{xorriso} device address. Addresses like 0,0,0
|
||||
@ -4490,7 +4494,7 @@ are aliases for "cdrecord".
|
||||
If @command{xorriso} 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 "@minus{}@minus{}" is encountered and an eventual commit happens.
|
||||
style until "@minus{}@minus{}" is encountered.
|
||||
From then on, options are interpreted as @command{xorriso} options.
|
||||
@*
|
||||
@minus{}@minus{}no_rc as first argument of such a program start
|
||||
@ -4556,8 +4560,7 @@ Program scdbackup_verify will recognize and verify tag resp. record.
|
||||
@cindex Process, disable startup files, -no_rc
|
||||
@*
|
||||
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.
|
||||
@c man .TP
|
||||
@item -options_from_file fileaddress
|
||||
@kindex -options_from_file reads commands from file
|
||||
@ -4740,7 +4743,7 @@ Only "-scsi_log" with dash "-" is recognized that way.
|
||||
@cindex Process, end program and write, -end
|
||||
@cindex Program, end and write, -end
|
||||
@*
|
||||
End program after writing eventually pending changes.
|
||||
End program after writing pending changes.
|
||||
@c man .TP
|
||||
@item -rollback_end
|
||||
@kindex -rollback_end ends program without writing
|
||||
@ -4753,7 +4756,7 @@ Discard pending changes. End program immediately.
|
||||
@cindex Comment, #
|
||||
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.
|
||||
@end table
|
||||
@c man .TP
|
||||
@c man .B Support for frontend programs via stdin and stdout:
|
||||
@ -5092,7 +5095,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.
|
||||
@*
|
||||
@sp 1
|
||||
@ -5425,7 +5428,7 @@ $ xorriso -outdev /dev/sr0 -toc
|
||||
@sp 1
|
||||
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.
|
||||
@*
|
||||
@sp 1
|
||||
$ xorriso -for_backup \
|
||||
@ -5462,7 +5465,7 @@ $ xorriso -abort_on NEVER -indev /dev/sr0 \
|
||||
data_to="$HOME"/dvd_copy sector_map="$HOME"/dvd_copy.map @minus{}@minus{}
|
||||
@*
|
||||
@sp 1
|
||||
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.
|
||||
|
||||
@ -78,13 +78,13 @@ but rather not with CD, DVD-R, DVD+R, BD-R.
|
||||
<H3>Optional supporting software:</H2>
|
||||
<DL>
|
||||
<DT>libreadline and libreadline-dev</DT>
|
||||
<DD>eventually make dialog more convenient.</DD>
|
||||
<DD>make dialog more convenient.</DD>
|
||||
<DT>libacl and libacl-devel</DT>
|
||||
<DD>eventually allow on GNU/Linux to get and set ACLs.</DD>
|
||||
<DD>allow on GNU/Linux to get and set ACLs.</DD>
|
||||
<DT>zlib and zlib-devel</DT>
|
||||
<DD>eventually allow zisofs, gzip compression, and Jigdo file production.</DD>
|
||||
<DD>allow zisofs, gzip compression, and Jigdo file production.</DD>
|
||||
<DT>libbz2 and libbz2-devel</DT>
|
||||
<DD>eventually allow bzip2 compression of Jigdo template files.</DD>
|
||||
<DD>allow bzip2 compression of Jigdo template files.</DD>
|
||||
</DL>
|
||||
</P>
|
||||
|
||||
@ -185,7 +185,7 @@ may accept pathspecs of form target=source as known from program mkisofs.</DT>
|
||||
<DD>$<KBD> xorriso -indev /dev/sr0 -du / -- -toc 2>&1 | less</KBD></DD>
|
||||
|
||||
<DT>Make re-usable media writable again, delete any ISO 9660 image,
|
||||
eventually prepare yet unused BD-RE:</DT>
|
||||
prepare yet unused BD-RE:</DT>
|
||||
<DD>$<KBD> xorriso -outdev /dev/sr0 -blank as_needed -eject all</KBD></DD>
|
||||
|
||||
<DT>
|
||||
@ -261,7 +261,7 @@ Important: -indev and -outdev have to be different drives.
|
||||
arguments have to be given in one single line. Backslash may be used to mark
|
||||
a line as incomplete so it gets continued by the next input line.
|
||||
<BR>
|
||||
Command -end stops the program run. It will write eventually pending changes
|
||||
Command -end stops the program run. It will write pending changes
|
||||
to media, if that has not already been done by a previous -commit.</DT>
|
||||
<DD>$<KBD> xorriso -dialog on</KBD></DD>
|
||||
<DD><KBD>enter option and arguments :</KBD></DD>
|
||||
@ -455,7 +455,7 @@ This can bring effective read performance near to the raw media reading speed.
|
||||
(detached GPG signature for verification by
|
||||
<KBD>gpg --verify xorriso-1.0.8.tar.gz.sig xorriso-1.0.8.tar.gz</KBD>
|
||||
<BR>
|
||||
after eventual <KBD>gpg --keyserver keys.gnupg.net --recv-keys ABC0A854</KBD>).
|
||||
after <KBD>gpg --keyserver keys.gnupg.net --recv-keys ABC0A854</KBD>).
|
||||
</DD>
|
||||
<DD>
|
||||
Also on <A HREF="http://www.gnu.org/prep/ftp.html">
|
||||
@ -585,6 +585,9 @@ xorriso command -add_plainly "any" did not add all files to the image
|
||||
<LI>
|
||||
The attempt to blank already blanked DVD-RW was not gracefully blocked
|
||||
</LI>
|
||||
<LI>
|
||||
-as mkisofs -isohybrid-mbr without -no-pad was not cylinder aligned
|
||||
</LI>
|
||||
<!--
|
||||
<LI>- none yet -</LI>
|
||||
-->
|
||||
@ -593,6 +596,7 @@ The attempt to blank already blanked DVD-RW was not gracefully blocked
|
||||
<DD>Enhancements towards stable version 1.0.8:
|
||||
<UL>
|
||||
<LI>New option -signal_handling</LI>
|
||||
<LI>New option -close_damaged</LI>
|
||||
<!--
|
||||
<LI>- none yet -</LI>
|
||||
-->
|
||||
|
||||
@ -1 +1 @@
|
||||
#define Xorriso_timestamP "2011.06.07.144548"
|
||||
#define Xorriso_timestamP "2011.06.17.143813"
|
||||
|
||||
@ -270,7 +270,8 @@ The default for \-root is "/".
|
||||
Enable incremental insertion of files into the loaded image.
|
||||
The effective target and source addresses of given pathspecs get compared
|
||||
whether the target already exists in the ISO image and is still identical
|
||||
to the source on disk. Metadata in the ISO image will eventually get adjusted.
|
||||
to the source on disk. Metadata in the ISO image will get adjusted, if they
|
||||
differ from those on disk.
|
||||
New files and files with changed content will get newly added.
|
||||
Target files which do not exist in any of the according pathspec sources
|
||||
will get removed from the ISO directory tree.
|
||||
@ -301,7 +302,7 @@ device number after each reboot, then this comparison will see all
|
||||
files as changed and thus prevent any incremental size saving.
|
||||
.TP
|
||||
\fB--old-root-no-md5\fR
|
||||
Disable recording and eventual use of MD5 checksums for data file content.
|
||||
Disable recording and use of MD5 checksums for data file content.
|
||||
If neither checksums and nor disk inode numbers are recorded, then
|
||||
option \-old\-root will have to read ISO image file content when comparing
|
||||
it with disk file content.
|
||||
@ -512,7 +513,7 @@ restore them when extracting files from the ISO image.
|
||||
.br
|
||||
Enable recording of MD5 checksums for the overall ISO image and for each
|
||||
single data file in the image. xorriso can check the content of an ISO
|
||||
image with these sums and eventually raise alert on mismatch.
|
||||
image with these sums and raise alert on mismatch.
|
||||
See man xorriso, options \-check_media, check_md5_r.
|
||||
xorriso can print recorded MD5 checksums. E.g. by:
|
||||
.br
|
||||
@ -558,7 +559,7 @@ excluded from the Joliet tree.
|
||||
\fB\-hide\fR disk_path_pattern
|
||||
Make files invisible in the directory tree of ISO 9660 and Rock Ridge,
|
||||
if their disk_path matches the given shell parser pattern.
|
||||
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
|
||||
@ -733,7 +734,7 @@ that points to an EFI image.
|
||||
Consider to use \-\-efi\-boot rather than \-e.
|
||||
.TP
|
||||
\fB--efi-boot\fR iso_rr_path
|
||||
Perform eventual necessary \-eltorito\-alt\-boot, option \-e with the given
|
||||
Perform \-eltorito\-alt\-boot, option \-e with the given
|
||||
iso_rr_path, and again \-eltorito\-alt\-boot. This gesture is
|
||||
used for achieving EFI\-bootability of the GRUB2 rescue CD.
|
||||
.TP
|
||||
@ -880,15 +881,14 @@ Declare a data file in the image to be a
|
||||
MIPS Big Endian boot file and cause 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 \-G.
|
||||
It will overwrite the first 512 bytes of any data provided by \-G.
|
||||
Up to 15 boot files can be declared by multiple \-mips\-boot options.
|
||||
.TP
|
||||
\fB\-mipsel-boot\fR iso_rr_path
|
||||
Declare 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 \-G.
|
||||
It will overwrite the first 512 bytes of any data provided by \-G.
|
||||
Only a single boot file can be declared by \-mipsel\-boot.
|
||||
.TP
|
||||
\fB\-B\fR disk_path[,disk_path ...]
|
||||
@ -968,11 +968,11 @@ 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 eventual padding will be
|
||||
If the list of jigdo parameters is not empty, then padding will be
|
||||
counted as part of the ISO image.
|
||||
.br
|
||||
.TP
|
||||
@ -1042,8 +1042,7 @@ add 150 (= 300 KiB) to the resulting number.
|
||||
.TP
|
||||
\fB--no_rc\fR
|
||||
Only if used as first 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\-help\fR
|
||||
.br
|
||||
@ -1408,7 +1407,7 @@ Become superuser and copy the image to the unpartitioned base device file
|
||||
of the USB stick. On GNU/Linux this is e.g. /dev/sdb, not /dev/sdb1.
|
||||
.br
|
||||
CAUTION:
|
||||
This will overwrite any eventual partitioning on the USB stick and make
|
||||
This will overwrite any partitioning on the USB stick and make
|
||||
remaining data unaccessible.
|
||||
.br
|
||||
So first make sure you got the correct address of the intended device.
|
||||
|
||||
@ -289,10 +289,10 @@ File: xorrisofs.info, Node: SetInsert, Next: SetProduct, Prev: Loading, Up:
|
||||
effective target and source addresses of given pathspecs get
|
||||
compared whether the target already exists in the ISO image and is
|
||||
still identical to the source on disk. Metadata in the ISO image
|
||||
will eventually get adjusted. New files and files with changed
|
||||
content will get newly added. Target files which do not exist in
|
||||
any of the according pathspec sources will get removed from the
|
||||
ISO directory tree.
|
||||
will get adjusted, if they differ from those on disk. New files
|
||||
and files with changed content will get newly added. Target files
|
||||
which do not exist in any of the according pathspec sources will
|
||||
get removed from the ISO directory tree.
|
||||
If the effective setting of -root differs from the iso_rr_path
|
||||
given with -old-root, then the files underneath the -old-root
|
||||
directory get cloned underneath the -root directory. Cloning
|
||||
@ -320,10 +320,10 @@ File: xorrisofs.info, Node: SetInsert, Next: SetProduct, Prev: Loading, Up:
|
||||
size saving.
|
||||
|
||||
--old-root-no-md5
|
||||
Disable recording and eventual use of MD5 checksums for data file
|
||||
content. If neither checksums and nor disk inode numbers are
|
||||
recorded, then option -old-root will have to read ISO image file
|
||||
content when comparing it with disk file content.
|
||||
Disable recording and use of MD5 checksums for data file content.
|
||||
If neither checksums and nor disk inode numbers are recorded, then
|
||||
option -old-root will have to read ISO image file content when
|
||||
comparing it with disk file content.
|
||||
|
||||
|
||||
File: xorrisofs.info, Node: SetProduct, Next: SetCompl, Prev: SetInsert, Up: Options
|
||||
@ -524,8 +524,8 @@ File: xorrisofs.info, Node: SetExtras, Next: SetHide, Prev: SetCompl, Up: Op
|
||||
--md5
|
||||
Enable recording of MD5 checksums for the overall ISO image and
|
||||
for each single data file in the image. xorriso can check the
|
||||
content of an ISO image with these sums and eventually raise alert
|
||||
on mismatch. See man xorriso, options -check_media, check_md5_r.
|
||||
content of an ISO image with these sums and raise alert on
|
||||
mismatch. See man xorriso, options -check_media, check_md5_r.
|
||||
xorriso can print recorded MD5 checksums. E.g. by:
|
||||
-find / -exec get_md5
|
||||
|
||||
@ -571,8 +571,8 @@ File: xorrisofs.info, Node: SetHide, Next: ImageId, Prev: SetExtras, Up: Opt
|
||||
-hide disk_path_pattern
|
||||
Make files invisible in the directory tree of ISO 9660 and Rock
|
||||
Ridge, if their disk_path matches the given shell parser pattern.
|
||||
The eventual data content of such hidden files will be included in
|
||||
the resulting image, even if they do not show up in any directory.
|
||||
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.
|
||||
This command does not apply to the boot catalog.
|
||||
|
||||
@ -736,9 +736,9 @@ Sytem Area.
|
||||
--efi-boot rather than -e.
|
||||
|
||||
--efi-boot iso_rr_path
|
||||
Perform eventual necessary -eltorito-alt-boot, option -e with the
|
||||
given iso_rr_path, and again -eltorito-alt-boot. This gesture is
|
||||
used for achieving EFI-bootability of the GRUB2 rescue CD.
|
||||
Perform -eltorito-alt-boot, option -e with the given iso_rr_path,
|
||||
and again -eltorito-alt-boot. This gesture is used for achieving
|
||||
EFI-bootability of the GRUB2 rescue CD.
|
||||
|
||||
-boot-load-size number
|
||||
Set the number of 512-byte blocks for boot images which emulate a
|
||||
@ -882,15 +882,14 @@ not combinable and also not combinable with MBR.
|
||||
Declare a data file in the image to be a MIPS Big Endian boot file
|
||||
and cause 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 -G. Up to 15 boot files can be declared by multiple
|
||||
-mips-boot options.
|
||||
It will overwrite the first 512 bytes of any data provided by -G.
|
||||
Up to 15 boot files can be declared by multiple -mips-boot options.
|
||||
|
||||
-mipsel-boot iso_rr_path
|
||||
Declare 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
|
||||
-G. Only a single boot file can be declared by -mipsel-boot.
|
||||
overwrite the first 512 bytes of any data provided by -G. Only a
|
||||
single boot file can be declared by -mipsel-boot.
|
||||
|
||||
-B disk_path[,disk_path ...]
|
||||
Cause one or more data files on disk to be written after the end
|
||||
@ -965,11 +964,11 @@ blanks, 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 file. Jigdo restore tools will convert these addresses into
|
||||
really reachable data source addresses from which they can read.
|
||||
If the list of jigdo parameters is not empty, then eventual padding
|
||||
will be counted as part of the ISO image.
|
||||
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.
|
||||
If the list of jigdo parameters is not empty, then padding will be
|
||||
counted as part of the ISO image.
|
||||
|
||||
-jigdo-jigdo disk_path
|
||||
Set the disk_path for the .jigdo file with the checksums and
|
||||
@ -1042,7 +1041,7 @@ File: xorrisofs.info, Node: Miscellaneous, Next: ExSimple, Prev: Jigdo, Up:
|
||||
|
||||
--no_rc
|
||||
Only if used as first argument this option prevents reading and
|
||||
interpretation of eventual startup files. See section FILES below.
|
||||
interpretation of startup files. See section FILES below.
|
||||
|
||||
-help
|
||||
List supported options to stderr. Original mkisofs options bear
|
||||
@ -1363,8 +1362,8 @@ $ xorrisofs -o output.iso \
|
||||
Become superuser and copy the image to the unpartitioned base device
|
||||
file of the USB stick. On GNU/Linux this is e.g. /dev/sdb, not
|
||||
/dev/sdb1.
|
||||
CAUTION: This will overwrite any eventual partitioning on the USB stick
|
||||
and make remaining data unaccessible.
|
||||
CAUTION: This will overwrite any partitioning on the USB stick and make
|
||||
remaining data unaccessible.
|
||||
So first make sure you got the correct address of the intended device.
|
||||
E.g. by reading 100 MiB data from it and watching it blinking:
|
||||
|
||||
@ -1526,7 +1525,7 @@ File: xorrisofs.info, Node: CommandIdx, Next: ConceptIdx, Prev: Legal, Up: T
|
||||
(line 86)
|
||||
* -appid set Application Id: ImageId. (line 46)
|
||||
* -b El Torito PC-BIOS boot image: Bootable. (line 32)
|
||||
* -B SUN SPARC boot images: SystemArea. (line 117)
|
||||
* -B SUN SPARC boot images: SystemArea. (line 116)
|
||||
* -biblio set Biblio File path: ImageId. (line 72)
|
||||
* -boot-info-table Patch El Torito boot image: Bootable. (line 80)
|
||||
* -boot-load-size El Torito boot image load size: Bootable. (line 63)
|
||||
@ -1592,7 +1591,7 @@ File: xorrisofs.info, Node: CommandIdx, Next: ConceptIdx, Prev: Legal, Up: T
|
||||
(line 64)
|
||||
* -md5-list set path of readable .md5: Jigdo. (line 73)
|
||||
* -mips-boot MIPS Big Endian boot image: SystemArea. (line 103)
|
||||
* -mipsel-boot MIPS Little Endian boot image: SystemArea. (line 111)
|
||||
* -mipsel-boot MIPS Little Endian boot image: SystemArea. (line 110)
|
||||
* -N omit version number in ISO file names: SetCompl. (line 67)
|
||||
* -no-emul-boot El Torito boot image emulation: Bootable. (line 72)
|
||||
* -no-pad do not add zeros to ISO tree: SetProduct. (line 76)
|
||||
@ -1629,8 +1628,8 @@ File: xorrisofs.info, Node: CommandIdx, Next: ConceptIdx, Prev: Legal, Up: T
|
||||
(line 21)
|
||||
* -rock Rock Ridge (is always enabled): SetExtras. (line 12)
|
||||
* -root redirect ISO root directory: SetInsert. (line 64)
|
||||
* -sparc-boot SUN SPARC boot images: SystemArea. (line 129)
|
||||
* -sparc-label SUN Disk Label text: SystemArea. (line 132)
|
||||
* -sparc-boot SUN SPARC boot images: SystemArea. (line 128)
|
||||
* -sparc-label SUN Disk Label text: SystemArea. (line 131)
|
||||
* -sysid set System Id: ImageId. (line 49)
|
||||
* -transparent-compression enable recognition of zisofs files: SetInsert.
|
||||
(line 61)
|
||||
@ -1674,10 +1673,10 @@ File: xorrisofs.info, Node: ConceptIdx, Prev: CommandIdx, Up: Top
|
||||
(line 80)
|
||||
* Bootability, control, --efi-boot: Bootable. (line 58)
|
||||
* Bootability, control, -b, -eltorito-boot: Bootable. (line 32)
|
||||
* Bootability, control, -B, -sparc-boot: SystemArea. (line 117)
|
||||
* Bootability, control, -B, -sparc-boot: SystemArea. (line 116)
|
||||
* Bootability, control, -e: Bootable. (line 50)
|
||||
* Bootability, control, -mips-boot: SystemArea. (line 103)
|
||||
* Bootability, control, -mipsel-boot: SystemArea. (line 111)
|
||||
* Bootability, control, -mipsel-boot: SystemArea. (line 110)
|
||||
* Bootability, fill System Area e.g. by MBR, -G, --embedded-boot, -generic-boot: SystemArea.
|
||||
(line 17)
|
||||
* Bootability, install ISOLINUX isohybrid MBR, -isohybrid-mbr: SystemArea.
|
||||
@ -1687,7 +1686,7 @@ File: xorrisofs.info, Node: ConceptIdx, Prev: CommandIdx, Up: Top
|
||||
(line 72)
|
||||
* Bootability, patch System Area partition table, --protective-msdos-label: SystemArea.
|
||||
(line 41)
|
||||
* Bootability, SUN Disk Label text, -sparc-label: SystemArea. (line 132)
|
||||
* Bootability, SUN Disk Label text, -sparc-label: SystemArea. (line 131)
|
||||
* Bugs, reporting: Bugreport. (line 6)
|
||||
* Character Set, for disk file names, -input-charset: Charset.
|
||||
(line 17)
|
||||
@ -1808,29 +1807,29 @@ Node: Xorriso4990
|
||||
Node: Options6129
|
||||
Node: Loading6846
|
||||
Node: SetInsert9140
|
||||
Node: SetProduct13542
|
||||
Node: SetCompl17249
|
||||
Node: SetExtras19568
|
||||
Node: SetHide22442
|
||||
Node: ImageId23450
|
||||
Node: Bootable26954
|
||||
Node: SystemArea31038
|
||||
Node: Charset37400
|
||||
Node: Jigdo38425
|
||||
Node: Miscellaneous42710
|
||||
Node: Examples43883
|
||||
Node: ExSimple44369
|
||||
Node: ExGraft44848
|
||||
Node: ExMkisofs46095
|
||||
Node: ExGrowisofs47346
|
||||
Node: ExIncBackup48518
|
||||
Node: ExIncBckAcc51567
|
||||
Node: ExBootable53242
|
||||
Node: Files55343
|
||||
Node: Seealso56417
|
||||
Node: Bugreport56936
|
||||
Node: Legal57517
|
||||
Node: CommandIdx58325
|
||||
Node: ConceptIdx69658
|
||||
Node: SetProduct13556
|
||||
Node: SetCompl17263
|
||||
Node: SetExtras19582
|
||||
Node: SetHide22445
|
||||
Node: ImageId23444
|
||||
Node: Bootable26948
|
||||
Node: SystemArea31013
|
||||
Node: Charset37347
|
||||
Node: Jigdo38372
|
||||
Node: Miscellaneous42639
|
||||
Node: Examples43803
|
||||
Node: ExSimple44289
|
||||
Node: ExGraft44768
|
||||
Node: ExMkisofs46015
|
||||
Node: ExGrowisofs47266
|
||||
Node: ExIncBackup48438
|
||||
Node: ExIncBckAcc51487
|
||||
Node: ExBootable53162
|
||||
Node: Files55254
|
||||
Node: Seealso56328
|
||||
Node: Bugreport56847
|
||||
Node: Legal57428
|
||||
Node: CommandIdx58236
|
||||
Node: ConceptIdx69569
|
||||
|
||||
End Tag Table
|
||||
|
||||
@ -430,7 +430,8 @@ The default for -root is "/".
|
||||
Enable incremental insertion of files into the loaded image.
|
||||
The effective target and source addresses of given pathspecs get compared
|
||||
whether the target already exists in the ISO image and is still identical
|
||||
to the source on disk. Metadata in the ISO image will eventually get adjusted.
|
||||
to the source on disk. Metadata in the ISO image will get adjusted, if they
|
||||
differ from those on disk.
|
||||
New files and files with changed content will get newly added.
|
||||
Target files which do not exist in any of the according pathspec sources
|
||||
will get removed from the ISO directory tree.
|
||||
@ -467,7 +468,7 @@ files as changed and thus prevent any incremental size saving.
|
||||
@item @minus{}@minus{}old-root-no-md5
|
||||
@kindex @minus{}@minus{}old-root-no-md5 disable MD5 with -old-root
|
||||
@cindex Incremental insertion, disable MD5, @minus{}@minus{}old-root-no-md5
|
||||
Disable recording and eventual use of MD5 checksums for data file content.
|
||||
Disable recording and use of MD5 checksums for data file content.
|
||||
If neither checksums and nor disk inode numbers are recorded, then
|
||||
option -old-root will have to read ISO image file content when comparing
|
||||
it with disk file content.
|
||||
@ -751,7 +752,7 @@ restore them when extracting files from the ISO image.
|
||||
@*
|
||||
Enable recording of MD5 checksums for the overall ISO image and for each
|
||||
single data file in the image. xorriso can check the content of an ISO
|
||||
image with these sums and eventually raise alert on mismatch.
|
||||
image with these sums and raise alert on mismatch.
|
||||
See man xorriso, options -check_media, check_md5_r.
|
||||
xorriso can print recorded MD5 checksums. E.g. by:
|
||||
@*
|
||||
@ -813,7 +814,7 @@ excluded from the Joliet tree.
|
||||
@cindex Hiding, from ISO and Rock Ridge, -hide
|
||||
Make files invisible in the directory tree of ISO 9660 and Rock Ridge,
|
||||
if their disk_path matches the given shell parser pattern.
|
||||
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.
|
||||
@*
|
||||
@ -1040,7 +1041,7 @@ Consider to use @minus{}@minus{}efi-boot rather than -e.
|
||||
@item @minus{}@minus{}efi-boot iso_rr_path
|
||||
@kindex @minus{}@minus{}efi-boot El Torito EFI boot image
|
||||
@cindex Bootability, control, @minus{}@minus{}efi-boot
|
||||
Perform eventual necessary -eltorito-alt-boot, option -e with the given
|
||||
Perform -eltorito-alt-boot, option -e with the given
|
||||
iso_rr_path, and again -eltorito-alt-boot. This gesture is
|
||||
used for achieving EFI-bootability of the GRUB2 rescue CD.
|
||||
@c man .TP
|
||||
@ -1227,7 +1228,7 @@ Declare a data file in the image to be a
|
||||
MIPS Big Endian boot file and cause 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 -G.
|
||||
It will overwrite the first 512 bytes of any data provided by -G.
|
||||
Up to 15 boot files can be declared by multiple -mips-boot options.
|
||||
@c man .TP
|
||||
@item -mipsel-boot iso_rr_path
|
||||
@ -1236,8 +1237,7 @@ Up to 15 boot files can be declared by multiple -mips-boot options.
|
||||
Declare 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 -G.
|
||||
It will overwrite the first 512 bytes of any data provided by -G.
|
||||
Only a single boot file can be declared by -mipsel-boot.
|
||||
@c man .TP
|
||||
@item -B disk_path[,disk_path ...]
|
||||
@ -1339,11 +1339,11 @@ 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.
|
||||
@*
|
||||
If the list of jigdo parameters is not empty, then eventual padding will be
|
||||
If the list of jigdo parameters is not empty, then padding will be
|
||||
counted as part of the ISO image.
|
||||
@*
|
||||
@table @asis
|
||||
@ -1444,8 +1444,7 @@ add 150 (= 300 KiB) to the resulting number.
|
||||
@kindex @minus{}@minus{}no_rc do not execute startup files
|
||||
@cindex Startup files, suppress, @minus{}@minus{}no_rc
|
||||
Only if used as first 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.
|
||||
@c man .TP
|
||||
@item -help
|
||||
@kindex -help list supported options
|
||||
@ -1898,7 +1897,7 @@ Become superuser and copy the image to the unpartitioned base device file
|
||||
of the USB stick. On GNU/Linux this is e.g. /dev/sdb, not /dev/sdb1.
|
||||
@*
|
||||
CAUTION:
|
||||
This will overwrite any eventual partitioning on the USB stick and make
|
||||
This will overwrite any partitioning on the USB stick and make
|
||||
remaining data unaccessible.
|
||||
@*
|
||||
So first make sure you got the correct address of the intended device.
|
||||
|
||||
Loading…
Reference in New Issue
Block a user