Gave up the unusual parameter sequences of -extract and -paste_in
This commit is contained in:
@ -1644,6 +1644,24 @@ of -cut_out part files.
|
||||
With option "concat_split_off" such directories are
|
||||
handled like any other ISO image directory.
|
||||
.TP
|
||||
\fB\-extract\fR iso_rr_path disk_path
|
||||
Restore the file objects at and underneath iso_rr_path to their corresponding
|
||||
addresses at and underneath disk_path.
|
||||
This is the inverse of -map or -update_r.
|
||||
.br
|
||||
If iso_rr_path is a directory and disk_path is an existing directory then
|
||||
both trees will be merged. Directory attributes get extracted only if the disk
|
||||
directory is newly created by the restore operation.
|
||||
Disk files get removed only if they are to be replaced
|
||||
by file objects from the ISO image.
|
||||
.br
|
||||
As many attributes as possible are copied together with restored
|
||||
file objects.
|
||||
.TP
|
||||
\fB\-extract_single\fR iso_rr_path disk_path
|
||||
Like -extract, but if iso_rr_path is a directory then its sub tree gets not
|
||||
restored.
|
||||
.TP
|
||||
\fB\-cpx\fR iso_rr_path [***] disk_path
|
||||
Extract single leaf file objects from the ISO image and store them under
|
||||
the address given by disk_path. If more then one iso_rr_path is given then
|
||||
@ -1664,39 +1682,18 @@ ownership and group as in ISO image.
|
||||
Like -cpx but also extracting whole directory trees from the ISO image.
|
||||
.br
|
||||
The resulting disk paths are determined as with shell command cp -r :
|
||||
If disk_path is an existing directory then the trees will be inserted
|
||||
If disk_path is an existing directory then the trees will be inserted or merged
|
||||
underneath this directory and will keep their leaf names. The ISO directory "/"
|
||||
has no leaf name and thus gets mapped directly to disk_path.
|
||||
.br
|
||||
If directories do already exist under disk_path then their content
|
||||
eventually gets merged with the content of restored directories
|
||||
of the same name. Directory attributes get extracted only if the disk
|
||||
directory is newly created by the restore operation.
|
||||
Disk files get removed only if they are to be replaced
|
||||
by file objects from the ISO image.
|
||||
.TP
|
||||
\fB\-cp_rax\fR iso_rr_path [***] disk_path
|
||||
Like -cp_rx but restoring mtime, atime as in ISO image and trying to set
|
||||
ownership and group as in ISO image.
|
||||
.PP
|
||||
The following restore operations are inverse mappings of data manipulation
|
||||
commands which have the same parameters. I.e. the disk_path stays the first
|
||||
argument although the operation copies data from ISO image to disk.
|
||||
.TP
|
||||
\fB\-extract\fR disk_path iso_rr_path
|
||||
Restore the file objects underneath iso_rr_path to their corresponding
|
||||
addresses underneath disk_path. Attributes get restored as with cp_rax.
|
||||
This is the inverse mapping of options -map or -update_r with the same
|
||||
arguments.
|
||||
.TP
|
||||
\fB\-extract_single\fR disk_path iso_rr_path
|
||||
Like -extract, but if iso_rr_path is a directory then its sub tree gets not
|
||||
restored.
|
||||
.TP
|
||||
\fB\-paste_in\fR disk_path byte_offset byte_count iso_rr_path
|
||||
Read the content of a ISO data file iso_rr_path and write it into a data
|
||||
file on disk beginning at the byte_offset. Write at most byte_count bytes.
|
||||
This is the inverse mapping of option -cut_out with the same arguments.
|
||||
\fB\-paste_in\fR iso_rr_path disk_path byte_offset byte_count
|
||||
Read the content of a ISO data file and write it into a data file on disk
|
||||
beginning at the byte_offset. Write at most byte_count bytes.
|
||||
This is the inverse of option -cut_out.
|
||||
.TP
|
||||
.B Command compatibility emulations:
|
||||
.PP
|
||||
@ -2143,17 +2140,20 @@ on media and if the expected changes are much smaller than the full backup.
|
||||
An update run will probably save no time but last longer than a full backup.
|
||||
Another good reason may be given if read speed is much higher than write speed.
|
||||
.br
|
||||
With \fBmount\fR option \fB"sbsector="\fR it is possible to access the session
|
||||
trees which represent the older backup versions. Multi-session media and
|
||||
most overwriteable media written by xorriso can tell
|
||||
the sbsector by xorriso option -toc.
|
||||
.br
|
||||
With \fBmount\fR option \fB"sbsector="\fR it is possible to access the session
|
||||
trees which represent the older backup versions. With CD media, Linux mount
|
||||
accepts session numbers directly by its option "session=".
|
||||
.br
|
||||
Multi-session media and most overwriteable media written by xorriso can tell
|
||||
the sbsector of a session by xorriso option -toc.
|
||||
Another way to keep track of incremental sessions is to
|
||||
set before writing a suitable path for xorriso option -session_log where
|
||||
the sbsector number gets recorded as the second word in each line.
|
||||
.br
|
||||
With CD media, Linux mount accepts session numbers directly by its option
|
||||
"session=".
|
||||
Independently of mount there is xorriso option \fB-osirrox on\fR which enables
|
||||
the builtin restore commands -extract, -cpx and others. They operate on the
|
||||
session eventually selected by option \fB-load\fR.
|
||||
.br
|
||||
\fBDo not write more than about 50 sessions\fR to one multi-session media.
|
||||
Theoretical limits are higher but in practice the media deteriorate more early.
|
||||
|
Reference in New Issue
Block a user