Published coordination rules for -cut_out, -compare and -update
This commit is contained in:
parent
7c226f7442
commit
9eaa268b26
@ -613,14 +613,13 @@ E.g:
|
||||
.br
|
||||
/file/part_3_of_3_at_4094m_with_2047m_of_5753194821
|
||||
.br
|
||||
-cut_out is not yet coordinated with -compare_r and -update_r.
|
||||
But the names of the part files in this example already follow a
|
||||
future convention by which xorriso will be able to recognize
|
||||
-cut_out is coordinated with -compare* and -update* if the names of the
|
||||
part files follow a convention by which xorriso is able to recognize
|
||||
file parts and process them accordingly:
|
||||
.br
|
||||
A disk file gets mapped to a ISO directory. Its split parts
|
||||
have names which describe the splitting by 5 numbers which are separated
|
||||
by some text:
|
||||
A disk file gets mapped to an ISO directory containing its split parts
|
||||
as regular files. The parts have names which describe the splitting
|
||||
by 5 numbers which are separated by some non-numerical text:
|
||||
.br
|
||||
part_number, total_parts, byte_offset, byte_count, disk_path_size
|
||||
.br
|
||||
@ -631,7 +630,13 @@ even if leading zeros are present.
|
||||
Not all parts have to be present on the same media. But those parts
|
||||
which are present have to sit in the same directory. No other files
|
||||
are allowed in there. Parts have to be disjoint. Their numbers have
|
||||
to be plausible. byte_count must be valid as -cut_out argument.
|
||||
to be plausible. E.g. byte_count must be valid as -cut_out argument
|
||||
and it must be the same with all parts.
|
||||
.br
|
||||
If the disk file grows enough to need new parts then those get added
|
||||
to the directory if it already contains all parts of the old disk file.
|
||||
If not all parts are present, then only those present parts will
|
||||
be updated.
|
||||
.TP
|
||||
\fB\-rm\fR iso_rr_path [***]
|
||||
Delete the given files from the ISO image.
|
||||
@ -1695,7 +1700,7 @@ enter option and arguments :
|
||||
.br
|
||||
enter option and arguments :
|
||||
.br
|
||||
.B \-add /pictures/confidential/work_office /pictures/confidential/work_factory
|
||||
.B \-add /pictures/confidential/office /pictures/confidential/factory
|
||||
.br
|
||||
enter option and arguments :
|
||||
.br
|
||||
@ -1849,7 +1854,7 @@ Always have a blank media ready to perform a full backup in case the update
|
||||
attempt fails. An overview of sessions is given by option -toc.
|
||||
.br
|
||||
\fBBetter do not use your youngest backup for -update_r\fR.
|
||||
Have at least two media which you use alternating. So only older backups
|
||||
Have at least two media which you use alternatingly. So only older backups
|
||||
get endangered by the new write operation, while the newest backup is
|
||||
stored safely on a different media.
|
||||
.br
|
||||
|
Loading…
Reference in New Issue
Block a user