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

New -osirrox settings "blocked" and "unblock"

Browse Source
This commit is contained in:
Thomas Schmitt
2013-01-04 19:00:14 +00:00
parent 343b12b190
commit d8a8ba5e05
8 changed files with 114 additions and 63 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
libisoburn/trunk/xorriso/xorriso.1
View File

@ -9,7 +9,7 @@
.\" First parameter, NAME, should be all caps
.\" Second parameter, SECTION, should be 1-8, maybe w/ subsection
.\" other parameters are allowed: see man(7), man(1)
.TH XORRISO 1 "Version 1.2.5, Dec 25, 2012"
.TH XORRISO 1 "Version 1.2.5, Jan 04, 2013"
.\" Please adjust this date whenever revising the manpage.
.\"
.\" Some roff macros, for reference:
@ -3911,12 +3911,16 @@ of \-overwrite "nondir". I.e. directories cannot be deleted.
Access permissions of files in the ISO image do not restrict restoring.
The directory permissions on disk have to allow rwx.
.TP
\fB\-osirrox\fR "on"|"device_files"|"off"|"banned"|[:option:...]
\fB\-osirrox\fR setting[:option:...]
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".
.br
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.
.br
To enable restoring of special files by "device_files" is potentially
dangerous.
The meaning of the number st_rdev (see man 2 stat) depends much on the
@ -4592,6 +4596,11 @@ Sorted from low to high severity.
Start the program that is given as first parameter. Submit the other
parameters as program arguments. Enable xorriso dialog mode.
.br
Two nameless pipe objects are created. xorriso standard input gets
connected to the standard output of the started program.
xorriso standard output and standard error get connected to the
standard input of that program.
.br
xorriso will abort when the started program ends or if it cannot
be started at all. In both cases it will return a non\-zero exit value.
The exit value will be zero if the frontend sends \-end or \-rollback_end
@ -4604,6 +4613,10 @@ The program name will not be searched in the $PATH directories.
To make this clear, it must contain at least one /\-character.
Best is an absolute path.
.br
Example:
.br
xorriso \-launch_frontend "$(which xorriso\-tcltk)" \-stdio \-\-
.br
The frontend program should first send via its standard output:
.br
\-mark 0 \-pkt_output on \-msg_op start_sieve \- \-reassure off