Enabled osirrox of more file types, curbed with device files

xorriso/xorriso.1

@@ -1596,18 +1596,31 @@ pseudo-drives or as log files.
 But its alter ego, osirrox, is able to extract file objects
 from ISO images and to create, overwrite, or delete file objects on disk.
 .TP
-\fB\-osirrox\fR "on"|"off"
+\fB\-osirrox\fR "on"|"device_files"|"off"
 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".
+.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
+operating system. Best is to restore device files only to the same system
+from where they were copied. If not enabled, device files in the ISO image
+are ignored during restore operations.
+.br
+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.
 .TP
 \fB\-cpx\fR iso_rr_path [***] disk_path
-Extract regular files from the ISO image and store them under the address given
-by disk_path. If more then one iso_rr_path is given then disk_path must be
-a directory or non-existent. In the latter case it gets created and the
-extracted files get installed in it with the same leafnames.
+Extract single leaf file objects from the ISO image and store them under
+the address given by disk_path. If more then one iso_rr_path is given then
+disk_path must be a directory or non-existent. In the latter case it gets
+created. The extracted files get installed in it with the same leafnames.
 .br
 Missing directory components in disk_path will get created, if possible.
+Disk file exclusions are in effect. If this is undesired then perform
+-not_mgt "off" first.
 .TP
 .B Command compatibility emulations:
 .PP