New -osirrox settings "blocked" and "unblock"

libisoburn/trunk/xorriso/xorriso.texi

@@ -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.2.5, Dec 25, 2012"
+@c man .TH XORRISO 1 "Version 1.2.5, Jan 04, 2013"
 @c man .\" Please adjust this date whenever revising the manpage.
 @c man .\"
 @c man .\" Some roff macros, for reference:
@@ -4592,7 +4592,7 @@ The directory permissions on disk have to allow rwx.
 @table @asis
 @sp 1
 @c man .TP
-@item -osirrox "on"|"device_files"|"off"|"banned"|[:option:...]
+@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
@@ -4600,6 +4600,10 @@ 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".
 @*
+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.
+@*
 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
@@ -5380,6 +5384,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.
 @*
+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.
+@*
 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
@@ -5392,6 +5401,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.
 @*
+Example:
+@*
+  xorriso -launch_frontend "$(which xorriso-tcltk)" -stdio --
+@*
 The frontend program should first send via its standard output:
 @*
   -mark 0 -pkt_output on -msg_op start_sieve - -reassure off