Updated information about reproducibility and Linux kernel sr lock

xorriso/xorriso.1

@@ -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.5.7, Dec 19, 2024"
+.TH XORRISO 1 "Version 1.5.7, Apr 24, 2025"
 .\" Please adjust this date whenever revising the manpage.
 .\"
 .\" Some roff macros, for reference:
@@ -315,7 +315,7 @@ the path of their block device or of their generic character device. E.g.
 By default xorriso will try to map the given address to /dev/hd* and /dev/sr*.
 The command \-scsi_dev_family can redirect the mapping from sr to scd or sg.
 The latter does not suffer from the concurrency problems which plagued /dev/sr
-of Linux kernels since version 3 up to 5.5. But it does not yield the same
+of Linux kernels since version 2.6 up to 5.5. But it does not yield the same
 addresses which are used by mount(8) or by open(2) for read(2).
 .br
 On FreeBSD the device files have names like
@@ -789,17 +789,17 @@ GNU/Linux specific:
 .br
 By default, xorriso tries to map Linux drive addresses to /dev/sr* before
 they get opened for operating the drive. This coordinates well with
-other use cases of optical drives, like mount(8). But since year 2010
-all /dev/sr* share a global lock which allows only one drive to process
-an SCSI command while all others have to wait for its completion.
-This yields awful throughput if more than one drive is writing or reading
+other use cases of optical drives, like mount(8). But between year 2010 and
+2020 all /dev/sr* shared a global lock which allowed only one drive to process
+an SCSI command while all others had to wait for its completion.
+This yieldied awful throughput if more than one drive was writing or reading
 simultaneously.
-The global lock is not applied to device files /dev/sg* and also not if
+The global lock was never applied to device files /dev/sg* and also not if
 the xorriso drive address is prepended by "stdio:".
 .br
-So for simultaneous burn runs on modern GNU/Linux it is advisable to perform
-\-scsi_dev_family "sg" before any \-dev, \-indev, or \-outdev. The drive addresses
-may then well be given as /dev/sr* but will nevertheless get used as
+So for simultaneous burn runs on GNU/Linux 2.6 to 5.5 it is advisable to
+perform \-scsi_dev_family "sg" before any \-dev, \-indev, or \-outdev. The drive
+addresses may then well be given as /dev/sr*, but will nevertheless get used as
 the matching /dev/sg*.
 .br
 If you decide so, consider to put the command into a global startup file like
@@ -7163,7 +7163,20 @@ then it is used as time value to set the default of
 "volume_date_uuid", \-volume_date "all_file_dates" to "set_to_mtime",
 and \-iso_nowtime to "=$SOURCE_DATE_EPOCH".
 .br
-Startup files and program options can override the effect of SOURCE_DATE_EPOCH.
+Startup files and program commands can override the effect of
+SOURCE_DATE_EPOCH.
+.br
+Be aware that by default xorriso puts its version information into the
+Preparer Id field of the ISO 9660 Primary Volume Descriptor. This may be
+desired in order to clearly define which xorriso version has to be used for
+reproduction. But it may also be undesired because a wider range of xorriso
+versions shall not be excluded from an attempt of reproduction.
+.br
+Use command \-preparer_id with a text other than "@xorriso@" if you want to
+override the default at first production time. This command may also be used
+to explicitly set the preparer id as found in an ISO 9660 filesystem which
+shall be reproduced by a different version of xorriso. The id can be inquired
+by command \-pvd_info.
 .br
 .SS
 .SH SEE ALSO
@@ -7223,7 +7236,7 @@ Thomas Schmitt <scdbackup@gmx.net>
 .br
 for libburnia\-project.org
 .SH COPYRIGHT
-Copyright (c) 2007 \- 2024 Thomas Schmitt
+Copyright (c) 2007 \- 2025 Thomas Schmitt
 .br
 Permission is granted to distribute this text freely. It shall only be
 modified in sync with the technical properties of \fBxorriso\fR.