libburnia/libisoburn
2
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

New -osirrox option check_md5_on|_off|_force

Browse Source
This commit is contained in:
Thomas Schmitt
2020-01-02 18:50:59 +01:00
parent 71b61339e9
commit 3466f2300a
9 changed files with 265 additions and 167 deletions
Download Patch File Download Diff File Expand all files Collapse all files

66
xorriso/xorriso.texi
View File

@ -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, Dec 23, 2019"
@c man .TH XORRISO 1 "Version 1.5.3, Jan 02, 2020"
@c man .\" Please adjust this date whenever revising the manpage.
@c man .\"
@c man .\" Some roff macros, for reference:
@ -1238,6 +1238,9 @@ 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.
@*
Commands which copy whole data files from ISO to hard disk will verify the
copied data stream by the recorded MD5, if -osirrox "check_md5_on" is set.
@*
At image generation time they are computed for each file which gets its data
written into the new session. The checksums of files which have their data
in older sessions get copied into the new session. Superblock, tree and whole
@ -5510,16 +5513,16 @@ The directory permissions on disk have to allow rwx.
@item -osirrox setting[:option:...]
@kindex -osirrox enables ISO-to-disk copying
@cindex Restore, enable ISO-to-disk, -osirrox
Setting "off" disables disk filesystem manipulations. This is the default
unless the program was started with leafname "osirrox". Elsewise
the capability to restore files can be enabled explicitly by -osirrox "on".
It can be irrevocably disabled by -osirrox "banned".
Setting @strong{off} disables disk filesystem manipulations. This is the default
unless the program was started with leafname @strong{osirrox}. Elsewise the
capability to restore files can be enabled explicitly by -osirrox @strong{on}.
It can be irrevocably disabled by -osirrox @strong{banned}.
@*
The setting "blocked" is like "off". But it can only be revoked by
setting "unblock", which elsewise is like "on". This can be used to curb
command scripts which might use "on" undesiredly.
The setting @strong{blocked} is like @strong{off}. But it can only be revoked
by setting @strong{unblock}, which elsewise is like @strong{on}. This can be
used to curb command scripts which might use @strong{on} undesiredly.
@*
To enable restoring of special files by "device_files" is potentially
To enable restoring of special files by @strong{device_files} is potentially
dangerous.
The meaning of the number st_rdev (see man 2 stat) depends much on the
operating system. Best is to restore device files only to the same system
@ -5530,34 +5533,43 @@ Due to a bug of previous versions, device files from previous sessions might
have been altered to major=0, minor=1. So this combination does not get
restored.
@*
Option "concat_split_on" is default. It enables restoring of split file
Option @strong{concat_split_on} is default. It enables restoring of split file
directories as data files if the directory contains a complete collection
of -cut_out part files. With option "concat_split_off" such directories are
handled like any other ISO image directory.
of -cut_out part files. With option @strong{concat_split_off} such directories
are handled like any other ISO image directory.
@*
Option "auto_chmod_off" is default. If "auto_chmod_on" is set then access
restrictions for disk directories get circumvented if those directories
are owned by the effective user who runs @command{xorriso}. This happens
by temporarily granting rwx permission to the owner.
Option @strong{auto_chmod_off} is default. If @strong{auto_chmod_on} is set
then access restrictions for disk directories get circumvented if those
directories are owned by the effective user who runs @command{xorriso}.
This happens by temporarily granting rwx permission to the owner.
@*
Option "sort_lba_on" may improve read performance with optical drives. It
can restore large numbers of hard links without exhausting
Option @strong{sort_lba_on} may improve read performance with optical drives.
It can restore large numbers of hard links without exhausting
-temp_mem_limit. It does not preserve directory mtime and it needs
-osirrox option auto_chmod_on in order to extract directories which offer no
write permission. Default is "sort_lba_off".
write permission. Default is @strong{sort_lba_off}.
@*
Option "o_excl_on" is the default unless the program was started with leafname
"osirrox". On GNU/Linux it tries to avoid using drives which are mounted or in
use by other libburn programs.
Option "o_excl_off" on GNU/Linux enables access to such drives by the
Option @strong{o_excl_on} is the default unless the program was started with
leafname "osirrox". On GNU/Linux it tries to avoid using drives which are
mounted or in use by other libburn programs.
Option @strong{o_excl_off} on GNU/Linux enables access to such drives by the
equivalent of -drive_access "shared:readonly". I.e. drives which
get acquired while "o_excl_off" will refuse to get blanked, formatted,
get acquired while @strong{o_excl_off} will refuse to get blanked, formatted,
written, or ejected. But be aware that even harmless inquiries can spoil
ongoing burns of CD-R[W] and DVD-R[W].
@*
Option "strict_acl_off" is default. It tolerates on FreeBSD the presence of
directory "default" ACLs in the ISO image. With "strict_acl_on" these
GNU/Linux ACLs cause on FreeBSD a FAILURE event during restore with -acl "on".
Option @strong{strict_acl_off} is default. It tolerates on FreeBSD the presence
of directory "default" ACLs in the ISO image.
With @strong{strict_acl_on} these GNU/Linux ACLs cause on FreeBSD a FAILURE
event during restore with -acl "on".
@*
Option @strong{check_md5_off} disables MD5 checking during copy to disk.
The default option @strong{check_md5_on} enables it if -md5 is "on". If a data
file with recorded MD5 is copied as a whole to the disk filesystem, then the
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.
@c man .TP
@item -extract iso_rr_path disk_path
@kindex -extract copies file tree to disk