New -osirrox option sparse= controls extraction into sparse files
This commit is contained in:
@ -50,7 +50,7 @@
|
||||
@c man .\" First parameter, NAME, should be all caps
|
||||
@c man .\" Second parameter, SECTION, should be 1-8, maybe w/ subsection
|
||||
@c man .\" other parameters are allowed: see man(7), man(1)
|
||||
@c man .TH XORRISO 1 "Version 1.5.3, Oct 27, 2020"
|
||||
@c man .TH XORRISO 1 "Version 1.5.3, Nov 02, 2020"
|
||||
@c man .\" Please adjust this date whenever revising the manpage.
|
||||
@c man .\"
|
||||
@c man .\" Some roff macros, for reference:
|
||||
@ -5739,6 +5739,21 @@ MD5 of the copied content gets computed and compared with the recorded MD5.
|
||||
A mismatch causes an error message of severity SORRY.
|
||||
Option @strong{check_md5_force} causes an error message if -md5 is "on"
|
||||
but no MD5 is recorded for the data file.
|
||||
@*
|
||||
Option @strong{sparse=} controls production of sparse files during
|
||||
extraction of files from the ISO filesystem.
|
||||
Default is @strong{sparse=off}.
|
||||
@*
|
||||
A positive number like in @strong{sparse=1m} sets the minimum requirement
|
||||
for the length of a sequence of 0-bytes which shall be represented by a gap.
|
||||
This saves disk space if the disk filesystem supports sparse files.
|
||||
A gap gets created by help of lseek(2) if a sequence of read buffers, which
|
||||
contain only 0-bytes, bears at least the minimum amount of bytes. Expect
|
||||
read buffers to be in the size range of 32k or 64k.
|
||||
@*
|
||||
Command -paste_in creates gaps only if the writing begins at or after the end
|
||||
of the existing disk file. So the sequence of -paste_in commands matters.
|
||||
Command -concat does not create sparse files.
|
||||
@c man .TP
|
||||
@item -extract iso_rr_path disk_path
|
||||
@kindex -extract copies file tree to disk
|
||||
|
Reference in New Issue
Block a user