"Fossies" - the Fresh Open Source Software Archive  

Source code changes of the file "xorriso/xorrecord.1" between
libisoburn-1.5.0.tar.gz and libisoburn-1.5.2.tar.gz

About: libisoburn is a frontend for the libraries libburn and libisofs which enables creation and expansion of ISO-9660 filesystems on all media and file types supported by libburn. It implements the API and command interpreter of program xorriso, and installs this program as small dynamically linked binary. xorriso is suitable for incremental data backup and for production of bootable ISO 9660 images. A statically linked version is available as GNU xorriso.

xorrecord.1  (libisoburn-1.5.0)	:	xorrecord.1  (libisoburn-1.5.2)
skipping to change at line 322		skipping to change at line 322
and further lines which report the version of xorriso and its supp orting libraries. They also		and further lines which report the version of xorriso and its supp orting libraries. They also
state the license under which the program is provided, and discla im any warranty, to the extent		state the license under which the program is provided, and discla im any warranty, to the extent
permitted by law.		permitted by law.
Afterwards end emulation without performing any drive operation.		Afterwards end emulation without performing any drive operation.
-v Increase program verbosity by one level. There are four verbosity levels from nearly silent to		-v Increase program verbosity by one level. There are four verbosity levels from nearly silent to
debugging verbosity. The both highest levels can be enabled by rep eated -v or by -vv or by -vvv.		debugging verbosity. The both highest levels can be enabled by rep eated -v or by -vv or by -vvv.
-V Log SCSI commands and drive replies to standard error. This mig ht be of interest if xorrecord		-V Log SCSI commands and drive replies to standard error. This mig ht be of interest if xorrecord
and a particular drive or medium do not cooperate as expected, or if you just want to know how		and a particular drive or medium do not cooperate as expected, or if you just want to know how
libburn interacts with the drive. To understand this extremely verbous log, one needs to read		libburn interacts with the drive. To understand this extremely verbose log, one needs to read
SCSI specs SPC, SBC, and MMC.		SCSI specs SPC, SBC, and MMC.
Please do not add such a log to a bug report on the first hand, un less you want to point out a		Please do not add such a log to a bug report on the first hand, un less you want to point out a
particular deviation from said specs, or if you get asked f or this log by a maintainer of		particular deviation from said specs, or if you get asked f or this log by a maintainer of
xorrecord who feels in charge for your bug report.		xorrecord who feels in charge for your bug report.
-help Print a sparse list of program options to standard error and decla re not to be cdrecord.		-help Print a sparse list of program options to standard error and decla re not to be cdrecord.
Afterwards end emulation without performing any drive operation.		Afterwards end emulation without performing any drive operation.
Options not compatible to cdrecord:		Options not compatible to cdrecord:
--no_rc		--no_rc
Only if used as first command line argument this option prevents r eading and interpretation of		Only if used as first command line argument this option prevents r eading and interpretation of
startup files. See section FILES below.		startup files. See section FILES below.
		--drive_not_exclusive
		This option disables the use of device file locking mechanism
		s when acquiring the drive. On
		GNU/Linux the locking is done by open(O_EXCL), on FreeBSD by flock
		(LOCK_EX).
		Be aware that it can cause problems if you use a drive which is mo
		unted, or opened by some other
		process, or guarded by /dev/pktcdvd*. Make sure that other u
		sers of the drive do not cause
		drive activities while a xorrecord burn run is going on.
drive_scsi_dev_family=sr|scd|sg|default		drive_scsi_dev_family=sr|scd|sg|default
GNU/Linux specific:		GNU/Linux specific:
By default, cdrskin tries to map Linux drive addresses to /dev/		By default, cdrskin tries to map Linux drive addresses to /dev/sr*
sr* before they get opened for		before they get opened for
operating the drive. This coordinates well with other use cas		operating the drive. This coordinates well with other use
es of optical drives, like		cases of optical drives, like
mount(8). But since year 2010 all /dev/sr* share a global lock		mount(8). But since year 2010 all /dev/sr* share a global lock whi
which allows only one drive to		ch allows only one drive to
process an SCSI command while all others have to wait for its com		process an SCSI command while all others have to wait for its
pletion. This yields awful		completion. This yields awful
throughput if more than one drive is writing or reading simultaneo usly.		throughput if more than one drive is writing or reading simultaneo usly.
The global lock is not applied to device files /dev/sg* and		The global lock is not applied to device files /dev/sg* and also
also not with the system calls		not with the system calls
read(2), write(2). But ioctl(SG_IO) is affected, which is needed t		read(2), write(2). But ioctl(SG_IO) is affected, which is neede
o perform the SCSI commands		d to perform the SCSI commands
for optical burning.		for optical burning.
So for simultaneous burn runs on modern GNU/Linux it is advisable to use		So for simultaneous burn runs on modern GNU/Linux it is advisable to use
drive_scsi_dev_family="sg". The drive addresses may then well be given as /dev/sr* but will		drive_scsi_dev_family="sg". The drive addresses may then well be given as /dev/sr* but will
nevertheless get used as /dev/sg*.		nevertheless get used as /dev/sg*.
--grow_overwriteable_iso		--grow_overwriteable_iso
Enable emulation of multi-session writing on overwriteable m edia which contain an ISO 9660		Enable emulation of multi-session writing on overwriteable media which contain an ISO 9660
filesystem. This emulation is learned from growisofs -M but adapte d to the usage model of		filesystem. This emulation is learned from growisofs -M but adapte d to the usage model of
xorrecord -msinfo		xorrecord -msinfo
xorrisofs -C -M | xorrecord -waiti -multi -		xorrisofs -C -M | xorrecord -waiti -multi -
for sequential media.		for sequential media.
--grow_overwriteable_iso does not hamper the use of true multi-		--grow_overwriteable_iso does not hamper the use of true mu
session media. I.e. it is		lti-session media. I.e. it is
possible to use the same xorrecord options with both kinds o		possible to use the same xorrecord options with both kinds of me
f media and to achieve similar		dia and to achieve similar
results if ISO 9660 filesystem images are to be written. This opt		results if ISO 9660 filesystem images are to be written. This
ion implies option -isosize		option implies option -isosize
and therefore demands that the track source is a ISO 9660 filesyst em image.		and therefore demands that the track source is a ISO 9660 filesyst em image.
With overwriteable media and no option blank=fast|all present i t expands an eventual ISO 9660		With overwriteable media and no option blank=fast|all present it e xpands an eventual ISO 9660
filesystem on media. It is assumed that this image's inner size de scription points to the end of		filesystem on media. It is assumed that this image's inner size de scription points to the end of
the valuable data. Overwriteable media with a recognizable ISO 9660 size will be regarded as		the valuable data. Overwriteable media with a recognizable ISO 96 60 size will be regarded as
appendable rather than as blank. I.e. options -msinfo and -toc wil l work. -toc will always show		appendable rather than as blank. I.e. options -msinfo and -toc wil l work. -toc will always show
a single session with its size increasing with every added ISO 966 0 image.		a single session with its size increasing with every added ISO 966 0 image.
--multi_if_possible		--multi_if_possible
Apply option -multi if the medium is suitable. Not suitable are D VD-R DL and DVD-RW, which were		Apply option -multi if the medium is suitable. Not suitable are DV D-R DL and DVD-RW, which were
blanked with mode "deformat_quickest".		blanked with mode "deformat_quickest".
Not all drives correctly recognize such fast-blanked DVD-RW which		Not all drives correctly recognize such fast-blanked DVD-RW whic
need "on". If there is well		h need "on". If there is well
founded suspicion that a burn run failed due to -multi, the		founded suspicion that a burn run failed due to -multi, then th
n this causes a re-try without		is causes a re-try without
-multi.		-multi.
stream_recording="on"|"off"|number		stream_recording="on"|"off"|number
Mode "on" requests that compliance to the desired speed setting is preferred over management of		Mode "on" requests that compliance to the desired speed setting i s preferred over management of
write errors. With DVD-RAM and BD this can bring effective write s peed near to the nominal write		write errors. With DVD-RAM and BD this can bring effective write s peed near to the nominal write
speed of the media. But it will also disable the automatic use of replacement blocks if write		speed of the media. But it will also disable the automatic use of replacement blocks if write
errors occur. It might as well be disliked or ignored by the drive .		errors occur. It might as well be disliked or ignored by the drive .
If a number is given, then error management stays enabled for all byte addresses below that		If a number is given, then error management stays enabled for all byte addresses below that
number. Any number below 16s is the same as "off".		number. Any number below 16s is the same as "off".
dvd_obs="default"|"32k"|"64k"		dvd_obs="default"|"32k"|"64k"
Linux specific: Set the number of bytes to be transmitted with eac h write operation to DVD or BD		Linux specific: Set the number of bytes to be transmitted with eac h write operation to DVD or BD
media. Tracks get padded up to the next multiple of this wri		media. Tracks get padded up to the next multiple of this write siz
te size. A number of 64 KB may		e. A number of 64 KB may
improve throughput with bus systems which show latency problems. T		improve throughput with bus systems which show latency problems
he default depends on media		. The default depends on media
type, option stream_recording=, and on compile time options.		type, option stream_recording=, and on compile time options.
modesty_on_drive=parameter[:parameters]		modesty_on_drive=parameter[:parameters]
Control whether the drive buffer shall be kept from getting comp		Control whether the drive buffer shall be kept from getting comple
letely filled. Parameter "on"		tely filled. Parameter "on"
(or "1") keeps the program from trying to write to the burner dri		(or "1") keeps the program from trying to write to the burne
ve while its buffer is in		r drive while its buffer is in
danger to be filled over a given limit. If this filling is excee		danger to be filled over a given limit. If this filling is exceed
ded then the program will wait		ed then the program will wait
until the filling reaches a given low percentage value.		until the filling reaches a given low percentage value.
This can ease the load on operating system and drive controller an d thus help with achieving		This can ease the load on operating system and drive controlle r and thus help with achieving
better input bandwidth if disk and burner are not on independent c ontrollers (like hda and hdb).		better input bandwidth if disk and burner are not on independent c ontrollers (like hda and hdb).
It may also help with simultaneous burns on different burners with		It may also help with simultaneous burns on different burners wi
Linux kernels like 3.16, if		th Linux kernels like 3.16, if
one has reason not to fix the problem by drive_scsi_dev_fam		one has reason not to fix the problem by drive_scsi_dev_family="
ily="sg". On the other hand it		sg". On the other hand it
increases the risk of buffer underflow and thus reduced write spee d.		increases the risk of buffer underflow and thus reduced write spee d.
Some burners are not suitable because they report buffer fill with granularity too coarse in		Some burners are not suitable because they report buffer fill with granularity too coarse in
size or time, or expect their buffer to be filled to the top befor e they go to full speed.		size or time, or expect their buffer to be filled to the top befor e they go to full speed.
Parameters "off" or "0" disable this feature.		Parameters "off" or "0" disable this feature.
The threshold for beginning to wait is given by paramete		The threshold for beginning to wait is given by parameter
r "max_percent=". Parameter		"max_percent=". Parameter
"min_percent=" defines the threshold for resuming transmission. P		"min_percent=" defines the threshold for resuming transmission.
ercentages are permissible in		Percentages are permissible in
the range of 25 to 100. Numbers in this range without a pre		the range of 25 to 100. Numbers in this range without a prepend
pended name are interpreted as		ed name are interpreted as
"on:min_percent=".		"on:min_percent=".
E.g.: modesty_on_drive=75		E.g.: modesty_on_drive=75
The optimal values depend on the buffer behavior of the drive.		The optimal values depend on the buffer behavior of the drive.
Parameter "timeout_sec=" defines after which time of unsuccessful waiting the modesty shall be		Parameter "timeout_sec=" defines after which time of unsuccessfu l waiting the modesty shall be
disabled because it does not work.		disabled because it does not work.
Parameter "min_usec=" defines the initial sleeping period in micr		Parameter "min_usec=" defines the initial sleeping period in micro
oseconds. If the drive buffer		seconds. If the drive buffer
appears to be too full for sending more data, the program will wai		appears to be too full for sending more data, the program will w
t the given time and inquire		ait the given time and inquire
the buffer fill state again. If repeated inquiry shows not eno		the buffer fill state again. If repeated inquiry shows not enough
ugh free space, the sleep time		free space, the sleep time
will slowly be increased to what parameter "max_usec=" defines.		will slowly be increased to what parameter "max_usec=" defines.
Parameters, which are not mentioned with a modesty_on_drive= optio n, stay unchanged. Default		Parameters, which are not mentioned with a modesty_on_drive= op tion, stay unchanged. Default
is:		is:
modesty_on_drive=off:min_percent=90:max_percent=95:		modesty_on_drive=off:min_percent=90:max_percent=95:
timeout_sec=120:min_usec=5000:max_usec=25000		timeout_sec=120:min_usec=5000:max_usec=25000
use_immed_bit="on"|"off"|"default"		use_immed_bit="on"|"off"|"default"
Control whether several long lasting SCSI commands shall be exec		Control whether several long lasting SCSI commands shall be execut
uted with the Immed bit, which		ed with the Immed bit, which
makes the commands end early while the drive operation is still go		makes the commands end early while the drive operation is still g
ing on. xorriso then inquires		oing on. xorriso then inquires
progress indication until the drive reports to be ready again.		progress indication until the drive reports to be ready again. If
If this feature is turned off,		this feature is turned off,
then blanking and formatting will show no progress indication.		then blanking and formatting will show no progress indication.
It may depend on the operating system whether -use_immed_bit is se t to "off" by default.		It may depend on the operating system whether -use_immed_bit is se t to "off" by default.
write_start_address=value		write_start_address=value
Set the block address on overwritable media where to start writin		Set the block address on overwritable media where to start wr
g the track. With DVD+RW,		iting the track. With DVD+RW,
DVD-RAM or BD-RE, byte_offset must be aligned to 2 kiB blocks, b		DVD-RAM or BD-RE, byte_offset must be aligned to 2 kiB blocks, but
ut better is 32 kiB on DVD and		better is 32 kiB on DVD and
64 kiB on BD. With formatted DVD-RW 32 kiB alignment is mandatory .		64 kiB on BD. With formatted DVD-RW 32 kiB alignment is mandatory .
Other media are not suitable for this option.		Other media are not suitable for this option.
stdio_sync="on"|"off"|number		stdio_sync="on"|"off"|number
Set the number of bytes after which to force output to emulated s		Set the number of bytes after which to force output to emulate
tdio: drives. This forcing		d stdio: drives. This forcing
keeps the memory from being clogged with lots of pending data for		keeps the memory from being clogged with lots of pending data for
slow devices. Default "on" is		slow devices. Default "on" is
the same as "16m". Forced output can be disabled by "off".		the same as "16m". Forced output can be disabled by "off".
EXAMPLES		EXAMPLES
Overview of examples:		Overview of examples:
Get an overview of drives and their addresses		Get an overview of drives and their addresses
Get info about a particular drive or loaded media		Get info about a particular drive or loaded media
Prepare CD-RW or DVD-RW for re-use, BD-R for bad block handling		Prepare CD-RW or DVD-RW for re-use, BD-R for bad block handling
Format DVD-RW to avoid need for blanking before re-use		Format DVD-RW to avoid need for blanking before re-use
De-format DVD-RW to make it capable of multi-session again		De-format DVD-RW to make it capable of multi-session again
Write a single ISO 9660 filesystem image		Write a single ISO 9660 filesystem image
skipping to change at line 459		skipping to change at line 466
$ xorrecord --devices		$ xorrecord --devices
Get info about a particular drive and loaded media:		Get info about a particular drive and loaded media:
$ xorrecord dev=/dev/sr0 -atip -toc --grow_overwriteable_iso		$ xorrecord dev=/dev/sr0 -atip -toc --grow_overwriteable_iso
Prepare CD-RW or DVD-RW for re-use:		Prepare CD-RW or DVD-RW for re-use:
$ xorrecord -v dev=/dev/sr0 blank=as_needed -eject		$ xorrecord -v dev=/dev/sr0 blank=as_needed -eject
Format DVD-RW to avoid need for blanking before re-use:		Format DVD-RW to avoid need for blanking before re-use:
$ xorrecord -v dev=/dev/sr0 blank=format_overwrite -eject		$ xorrecord -v dev=/dev/sr0 blank=format_overwrite -eject
This command may also be used to format BD-R media before first use, in o		This command may also be used to format BD-R media before first use,
rder to enable handling of		in order to enable handling of
write errors. Several hundred MB of spare blocks will be reserved and		write errors. Several hundred MB of spare blocks will be reserved and wri
write runs on such media will		te runs on such media will
perform with less than half nominal speed.		perform with less than half nominal speed.
De-format DVD-RW to make it capable of multi-session again:		De-format DVD-RW to make it capable of multi-session again:
$ xorrecord -v dev=/dev/sr0 blank=deformat		$ xorrecord -v dev=/dev/sr0 blank=deformat
Write a single ISO 9660 filesystem image:		Write a single ISO 9660 filesystem image:
$ xorrecord -v dev=/dev/sr0 speed=12 fs=8m \		$ xorrecord -v dev=/dev/sr0 speed=12 fs=8m \
blank=as_needed -eject padsize=300k my_image.iso		blank=as_needed -eject padsize=300k my_image.iso
Write multiple ISO 9660 sessions:		Write multiple ISO 9660 sessions:
This is possible with all media except minimally blanked DVD-RW and DVD-R DL, which cannot do		This is possible with all media except minimally blanked DVD-RW and DVD-R DL, which cannot do
multi-session.		multi-session.
The first session is written like in the previous example, except that option -multi is used. It will		The first session is written like in the previous example, except that op tion -multi is used. It will
contain the files of hard disk directory ./tree1 under the ISO 9660 direc tory /dir1:		contain the files of hard disk directory ./tree1 under the ISO 9660 direc tory /dir1:
$ xorrisofs -o image_1.iso -J -graft-points /dir1=./tree1		$ xorrisofs -o image_1.iso -J -graft-points /dir1=./tree1
$ xorrecord -v dev=/dev/sr0 speed=12 fs=8m \		$ xorrecord -v dev=/dev/sr0 speed=12 fs=8m \
-multi --grow_overwriteable_iso \		-multi --grow_overwriteable_iso \
blank=as_needed -eject padsize=300k image_1.iso		blank=as_needed -eject padsize=300k image_1.iso
For the second session xorrisofs needs to know the -msinfo numbers of the medium. Further it will read		For the second session xorrisofs needs to know the -msinfo numbers of th e medium. Further it will read
data from the medium by using the system's read-only CD-ROM driver.		data from the medium by using the system's read-only CD-ROM driver.
It is advised to load the tray manually or via dd by the CD-ROM driver,		Many systems do not take notice of xorrecord's write activities. It i
rather than letting xorrecord		s necessary to force their
do this by its own SCSI driver. Many system CD-ROM drivers do not		attention by ejecting and reloading the drive tray. Therefore above run
take notice of xorrecord's		uses option -eject.
activities.		Get the -msinfo numbers (and properly reload the tray if it has a motor)
$ dd if=/dev/sr0 count=1 >/dev/null 2>&1		by:
Now get the -msinfo numbers:
$ m=$(xorrecord dev=/dev/sr0 -msinfo)		$ m=$(xorrecord dev=/dev/sr0 -msinfo)
and use them with xorrisofs to add ./tree2 to the image as /dir2:		Offer a victim to any problem caused by obtrusive demons after tray loadi
		ng:
		$ dd if=/dev/sr0 count=1 >/dev/null 2>&1
		Use the numbers with xorrisofs to add ./tree2 to the image as /dir2:
$ xorrisofs -M /dev/sr0 -C $m -o image_2.iso \		$ xorrisofs -M /dev/sr0 -C $m -o image_2.iso \
-J -graft-points /dir2=./tree2		-J -graft-points /dir2=./tree2
Now burn the new session onto the same medium. This time without blanking :		Now burn the new session onto the same medium. This time without blanking :
$ xorrecord -v dev=/dev/sr0 speed=12 fs=8m \		$ xorrecord -v dev=/dev/sr0 speed=12 fs=8m \
-multi --grow_overwriteable_iso \		-multi --grow_overwriteable_iso \
-eject padsize=300k image_2.iso		-eject padsize=300k image_2.iso
Operating systems which mount this medium will read the superblock of th e second session and show both		Operating systems which mount this medium will read the superblock of th e second session and show both
directories /dir1 and /dir2.		directories /dir1 and /dir2.
Write ISO 9660 session on-the-fly:		Write ISO 9660 session on-the-fly:
It is possible to combine the run of xorrisofs and xorrecord in a pipelin e without storing the ISO 9660		It is possible to combine the run of xorrisofs and xorrecord in a pipelin e without storing the ISO 9660
image as file on hard disk:		image as file on hard disk.
		The piped run is more vulnerable to the problem that some systems
		have not enough patience with
		automatic tray loading and that demons may interfere with a first CD-ROM
		driver read attempt from a
		freshly loaded medium. It is advised to load the tray manually or via a
		separate run of xorriso with a
		subsequent run of dd.
		Again, xorriso has the patience and dd is a dispensable victim for demons
		.
		$ m=$(xorrecord dev=/dev/sr0 -msinfo)
		$ dd if=/dev/sr0 count=1 >/dev/null 2>&1
$ xorrisofs -M /dev/sr0 -C $m \		$ xorrisofs -M /dev/sr0 -C $m \
-J -graft-points /dir2=./tree2 \		-J -graft-points /dir2=./tree2 \
| xorrecord -v dev=/dev/sr0 speed=12 fs=8m \		| xorrecord -v dev=/dev/sr0 speed=12 fs=8m \
-waiti -multi --grow_overwriteable_iso \		-waiti -multi --grow_overwriteable_iso \
-eject padsize=300k -		-eject padsize=300k -
This is also the main use case of program xorriso itself, where this run		This is also the main use case of program xorriso itself, where the
would look like:		run would need no system
		workarounds and simply look like:
$ xorriso -dev /dev/sr0 -joliet on -speed 12 -fs 8m \		$ xorriso -dev /dev/sr0 -joliet on -speed 12 -fs 8m \
-map ./tree2 /dir2 -commit_eject all		-map ./tree2 /dir2 -commit_eject all
Write compressed afio archive on-the-fly:		Write compressed afio archive on-the-fly:
This is possible with all media except minimally blanked DVD-RW and D VD-R DL. Since the compressed		This is possible with all media except minimally blanked DVD-RW and D VD-R DL. Since the compressed
output stream is of very variable speed, a larger fifo is advised. Nevert heless, this example is not		output stream is of very variable speed, a larger fifo is advised. Nevert heless, this example is not
suitable for very old CD drives which have no underrun protection and th us would abort the burn run on		suitable for very old CD drives which have no underrun protection and th us would abort the burn run on
temporary data shortage.		temporary data shortage.
$ find . | afio -oZ - | \		$ find . | afio -oZ - | \
xorrecord -v dev=/dev/sr0 speed=12 fs=64m \		xorrecord -v dev=/dev/sr0 speed=12 fs=64m \
skipping to change at line 556		skipping to change at line 571
public list <bug-xorriso@gnu.org>. If more privacy is desired, mail to < scdbackup@gmx.net>.		public list <bug-xorriso@gnu.org>. If more privacy is desired, mail to < scdbackup@gmx.net>.
Please describe what you expect xorriso to do, the program arguments o r dialog commands by which you		Please describe what you expect xorriso to do, the program arguments o r dialog commands by which you
tried to achieve it, the messages of xorriso, and the undesirable outcome of your program run.		tried to achieve it, the messages of xorriso, and the undesirable outcome of your program run.
Expect to get asked more questions before solutions can be proposed.		Expect to get asked more questions before solutions can be proposed.
AUTHOR		AUTHOR
Thomas Schmitt <scdbackup@gmx.net>		Thomas Schmitt <scdbackup@gmx.net>
for libburnia-project.org		for libburnia-project.org
COPYRIGHT		COPYRIGHT
Copyright (c) 2011 - 2018 Thomas Schmitt		Copyright (c) 2011 - 2019 Thomas Schmitt
Permission is granted to distribute this text freely. It shall only be modified in sync with the		Permission is granted to distribute this text freely. It shall only be modified in sync with the
technical properties of xorriso. If you make use of the license to deriv e modified versions of xorriso		technical properties of xorriso. If you make use of the license to deriv e modified versions of xorriso
then you are entitled to modify this text under that same license.		then you are entitled to modify this text under that same license.
CREDITS		CREDITS
xorriso is in part based on work by Vreixo Formoso who provides libisofs together with Mario Danic who		xorriso is in part based on work by Vreixo Formoso who provides libisofs together with Mario Danic who
also leads the libburnia team. Thanks to Andy Polyakov who invented emul ated growing, to Derek Foreman		also leads the libburnia team. Thanks to Andy Polyakov who invented emul ated growing, to Derek Foreman
and Ben Jansens who once founded libburn.		and Ben Jansens who once founded libburn.
Compliments towards Joerg Schilling whose cdrtools served me for ten year s.		Compliments towards Joerg Schilling whose cdrtools served me for ten year s.
Version 1.5.0, Sep 15, 2018 XORRECORD(1)		Version 1.5.2, Oct 26, 2019 XORRECORD(1)
End of changes. 36 change blocks.
94 lines changed or deleted		119 lines changed or added

---