1XORRECORD(1) General Commands Manual XORRECORD(1)
2
6 xorrecord - Emulation of CD/DVD/BD program cdrecord by program xorriso
7
9 xorrecord [ options ] dev=device [track_source]
10
12 xorrecord writes preformatted data to CD, DVD, and BD media.
13 It understands some options of program cdrecord from cdrtools by Joerg
15 Schilling. Its implementation is part of program xorriso which shares
16 no source code with cdrtools, but rather makes use of libburn for
17 communicating with the drive.
18 Another, more complete cdrecord emulator is program cdrskin which uses
19 the same burn functions as xorrecord.
20 MMC, Session, Track, Media types:
22 MMC is a standard out of the SCSI family which defines the interaction
23 between computers and optical drives. Since more than a decade all CD,
24 DVD, or BD recorders obey this standard regardless by what bus cabling
25 they are attached to the computer. libburn relies on this standard
26 compliance and on the capability of the operating system to perform
27 SCSI transactions over the particular bus cabling.
28 A Session is a data region on an optical disc which usually gets
29 written in a single sweep. It contains at least one Track which is a
30 contiguous string of readable blocks. xorrecord produces a single
31 session with a single data track which consists of blocks with 2048
32 bytes each. It chooses the write mode automatically according to media
33 type, medium state, and option -multi.
34 On CD media there are other track types, like audio, and particular
35 write modes like TAO and SAO. CD and DVD- media can put more than one
36 track into a session. Some of these features can be addressed by
37 program cdrskin.
38 MMC describes several recordable media types which roughly form two
39 families.
40 Sequentially recordable media are CD-R, CD-RW, DVD-R, DVD-R DL, DVD-RW,
41 DVD+R, DVD+R DL, BD-R. Except DVD-R DL they can store more than one
42 session if there is still unwritten space and if the previous session
43 was written with option -multi. CD-RW and DVD-RW can be blanked in
44 order to be re-usable from scratch.
45 Overwritable media are DVD-RAM, DVD+RW, formatted DVD-RW, BD-RE. They
46 offer a single session with a single track for random access writing.
47 There is no need to blank overwritable media before re-use.
48 DVD-RW media are sold in sequentially recordable state but can be
49 formatted once to become overwritable. See options
50 blank=format_overwrite and blank=deformat.
51 If ISO 9660 filesystems are to be stored on overwritable media, then it
52 is possible to emulate multiple sessions, by using option
53 --grow_overriteable_iso. In this case, the need for blanking before
54 re-use is emulated too.
55 Drive preparation and addressing:
57 The drives, CD, DVD, or BD burners, are accessed via file addresses
58 which are specific to libburn and the operating system. Those addresses
59 get listed by a run of xorrecord --devices or xorriso -device_links.
60 On GNU/Linux and FreeBSD, the user needs rw-permission for the device
61 file. On Solaris, the user needs r-permission and privilege
62 "sys_devices", which is usually gained by running xorrecord via command
63 pfexec.
64 These permissions resp. privileges are needed already for listing a
65 drive. So it might be necessary to get the overview as superuser resp.
66 via pfexec.
67 xorrecord does not perform cdrecord option -scanbus and does not accept
68 the addresses of form Bus,Target,Lun which are told by -scanbus. If
69 support for these addresses is necessary, consider to use program
70 cdrskin.
71 It is possible to let xorrecord work on emulated drives. Their
72 addresses begin by prefix "stdio:" followed by a file address. The
73 emulated media behavior depends on the file type. See man xorriso for
74 details.
75 If standard output is chosen as emulated drive, then all program result
76 texts, which usually appear on standard output, will get redirected to
77 standard error.
78 Relation to program xorriso:
80 xorrecord is actually a command mode of program xorriso, which gets
81 entered either by xorriso command "-as cdrecord" or by starting the
82 program by one of the names "xorrecord", "cdrecord", "wodim", or
83 "cdrskin".
84 This command mode can be left by argument "--" which leads to generic
85 xorriso command mode. See man xorriso for its description. Other than
86 in xorriso command mode, the sequence of the cdrecord emulation options
87 does not matter. All pending actions get performed in a fixed sequence
88 before the program run ends resp. before cdrecord emulation ends.
89
92 Addressing the drive:
93 --devices
95 Print the list of accessible CD, DVD, or BD drives to standard
96 output. Drives might be inaccessible if the user lacks of
97 permissions to use them or if the drive is in use by another
98 program.
99 Each accessible drive is shown by a line like:
100 0 -dev '/dev/sr0' rwrw-- : 'TSSTcorp' 'CDDVDW SH-S203B'
101 The libburn address of this drive is '/dev/sr0'. 'TSSTcorp' is
102 the name of the vendor (in this case: Toshiba Samsung Storage
103 Technologies Corporation), 'CDDVDW SH-S203B' is the model name
104 (in this case: a DVD burner).
105 dev=drive_address
107 Set the libburn address of the drive to be used.
108 E.g. on GNU/Linux: dev=/dev/sr0
109 E.g. on FreeBSD: dev=/dev/cd0
110 E.g. on Solaris: dev=/dev/rdsk/c2t2d0s2
111 See also above "Drive preparation and addressing".
112 The medium in the drive should not be mounted or be otherwise in
113 use.
114 Inquiring drive and media:
116 -inq Print to standard output: vendor, model name, and firmware
118 revision of the drive.
119 -checkdrive
121 Print unconditionally that the drive supports burnfree, SAO, and
122 TAO. Also print the output of option -inq.
123 -atip Print the output of -checkdrive, the most capable profile of the
125 medium in the drive, the list of profiles which are supported by
126 the drive, whether it is erasable (i.e. can be blanked), the
127 media manufacturer, and the medium product name.
128 Profiles are usage models, which are often tied to a particular
129 media type (e.g. CD-RW), but may also apply to a family of
130 media. E.g. profile CD-ROM applies to all CD media which contain
131 data.
132 -toc Print a table of content of the medium in the drive. The output
134 is not compatible to cdrecord option -toc, but rather the one of
135 xorriso command -toc. It lists the address, vendor, model name,
136 and firmware revision of the drive.
137 About the medium it tells product name and manufacturer, whether
138 there is already content written, and if so, whether the medium
139 is closed or appendable. Appendable media can take another
140 session. The amount of readable and writable data is told. If
141 there are sessions, then their start block address and size is
142 reported. If a session contains an ISO 9660 filesystem, then
143 its Volume Id is reported. If the medium is writable, then the
144 next writable block address is reported.
145 If not option --grow_overriteable_iso is given or no ISO 9660
146 file system is present on the medium, then overwritable media
147 are reported as being blank. This is due to the fact that they
148 can be written from scratch without further preparation, and
149 that MMC does not distinguish between data written by the most
150 previous burn run and older data which have not been overwritten
151 by that burn run. Consequently, these media are reported with 0
152 readable blocks, although all their writable blocks normally are
153 readable, too.
154 -msinfo
156 Print the argument text for option -C of programs mkisofs,
157 genisoimage, or xorrisofs. It consists of two numbers separated
158 by a comma.
159 The first number tells the first block of the first track of the
160 last recorded session. This is also the address used by default
161 when operating systems mount a medium with e.g. ISO 9660
162 filesystem.
163 The second number tells the next writable address, where
164 xorrecord will begin to write the next session.
165 This option is only valid for written, appendable media. In all
166 other cases it will yield no output text but will abort the
167 program with non-zero exit value.
168 Settings for the burn run:
170 A burn run requires exactly one track source address argument, which
172 tells from where to read the data wich shall be put into the upcomming
173 session. The medium state must be either blank or appendable.
174 Track source may be "-" for standard input or the address of a readable
175 file of any type except directories. Nearly all media types accept a
176 track source with unpredictable byte count, like standard input or
177 named pipes. Nevertheless, DVD-R DL and DVD-RW blanked by mode
178 deformat_quickest demand exact in-advance reservation of the track
179 size, so that they either need to be read from a source of predictable
180 length, or need to be accompanied by option tsize= or by option
181 -isosize.
182 Several options expect a size value as argument. A number with a
183 trailing letter "b" or without a trailing letter is a plain byte count.
184 Other trailing letters cause multiplication of the given number by a
185 scaling factor:
186 "k" or "K" = 1024 , "m" or "M" = 1024k , "g" or "G" = 1024m , "s" or
187 "S" = 2048
188 E.g. tsize=234567s means a size of 234567 * 2048 = 480393216 bytes.
189 blank=mode
191 Blank a CD-RW or DVD-RW to make it re-usable from scratch.
192 Format a DVD-RW, DVD+RW, DVD-RAM, BD-R, or BD-RE if not yet
193 formatted.
194 This operation normally makes any recorded data on the medium
195 unreadable. It is combinable with burning in the same run of
196 xorrecord, or it may be performed without a track source,
197 leaving the medium empty.
198 The mode given with blank= selects the particular behavior:
199 as_needed
201 Try to make the media ready for writing from scratch. If
202 it needs formatting, then format it. If it is not blank,
203 then try to apply blank=fast. It is a reason to abort if
204 the medium cannot assume thoroughly writeable state, e.g.
205 if it is a non-blank write-once.
206 This leaves unformatted DVD-RW in unformatted blank
207 state. To format DVD-RW use blank=format_overwrite. Blank
208 unformatted BD-R stay unformatted.
209 (Note: blank=as_needed is not an original cdrecord
210 option.)
211 all
213 Blank an entire CD-RW or an unformatted DVD-RW.
214 fast
216 Minimally blank an entire CD-RW or blank an unformatted
217 DVD-RW.
218 deformat
220 Like blank=all but with the additional ability to blank
221 overwriteable DVD-RW. This will destroy their formatting
222 and make them sequentially recordable.
223 (Note: blank=deformat is not an original cdrecord
224 options)
225 deformat_quickest
227 Like blank=deformat but blanking DVD-RW only minimally.
228 This is faster than full blanking but yields media
229 incapable of writing tracks of unpredicatable size.
230 Multi-session will not be possible either.
231 (Note: blank=deformat_quickest is not an original
232 cdrecord option.)
233 format_overwrite
235 Format a DVD-RW to "Restricted Overwrite". The user
236 should bring some patience.
237 Format unformatted DVD+RW, BD-RE or blank BD-R to their
238 default size. It is not mandatory to do this with DVD+RW
239 and BD-RE media, because they will get formatted
240 automatically on the first write attempt.
241 BD-R media may be written in unformatted state. This
242 keeps disabled the replacement of bad blocks and enables
243 full nominal write speed. Once BD-R media are written,
244 they cannot be formatted any more.
245 For re-formatting already formatted media or for
246 formatting with non-default size, use program xorriso
247 with command -format.
248 (Note: blank=format_overwrite is not an original cdrecord
249 options)
250 -multi This option keeps CD, unformatted DVD-R[W], DVD+R, or BD-R
252 appendable after the current session has been written. Without
253 it the disc gets closed and may not be written any more -
254 unless it is a -RW and gets blanked, which causes loss of its
255 content.
256 This option cannot be applied to DVD-R DL and DVD-RW which were
257 blanked by type deformat_quickest.
258 In order to have all filesystem content accessible, the eventual
259 ISO-9660 filesystem of a follow-up session needs to be prepared
260 in a special way by the filesystem formatter program. mkisofs,
261 genisoimage, and xorrisofs expect particular info about the
262 situation which can be retrieved by xorrecord option -msinfo.
263 With overwriteable DVD or BD media, -multi cannot mark the end
264 of the session. So when adding a new session, this end has to
265 be determined from the payload. Currently only ISO-9660
266 filesystems can be used that way. See option
267 --grow_overwriteable_iso.
268 -dummy Try to perform the drive operations without actually affecting
270 the inserted media. There is no warranty that this will work
271 with a particular combination of drive and media. Blanking is
272 prevented reliably, though. To avoid inadverted real burning,
273 -dummy refuses burn runs on anything but CD-R[W], DVD-R[W], or
274 emulated stdio-drives.
275 -waiti Wait until input data is available at stdin or EOF occurs at
277 stdin. Only then begin to access any drives.
278 One should use this if xorrisofs is working at the end of a pipe
279 where the feeder process reads from the drive before it starts
280 writing its output into xorrisofs. Example:
281 xorrisofs ... -C 0,12800 -M /dev/sr0 ... | \
282 xorrecord dev=/dev/sr0 ... -waiti -
283 This option works even if standard input is not the track
284 source. If no process is piping in, then the Enter key of your
285 terminal will act as trigger for xorrecord. Note that this input
286 line will not be consumed by cdrskin if standard input is not
287 the track source. It will end up as shell command, usually.
288 tsize=size
290 Announce the exact size of the track source. This is necessary
291 with DVD-R DL media and with quickest blanked DVD-RW, if the
292 size cannot be determined in advance from the track source. E.g.
293 if it is standard input or a named pipe.
294 If the track source does not deliver the predicted amount of
295 bytes, the remainder of the track is padded with zeros. This is
296 not considered an error. If on the other hand the track source
297 delivers more than the announced bytes then the track on media
298 gets truncated to the predicted size and xorrecord exits with
299 non-zero value.
300 -isosize
302 Try to obtain the track size from the content of the track
303 source. This works only if the track source bears an ISO 9660
304 filesystem. Any other track source content will cause the burn
305 run to abort.
306 If the track source is not a regular file or block device, then
307 this option will work only if the program's fifo size is at
308 least 64k. See option fs=.
309 padsize=size
311 Add the given amount of trailing zeros to the upcomming track.
312 This feature can be disabled by size 0. Default is 300 kB in
313 order to work around a problem with GNU/Linux which often fails
314 to read the last few blocks of a CD track which was written in
315 write mode TAO. TAO is used by xorrecord if the track size
316 cannot be predicted or if the CD medium is not blank but
317 appendable.
318 -nopad The same as padsize=0.
320 -pad The same as padsize=15s. This was once sufficient with older
322 GNU/Linux kernels. Meanwhile one should at least use
323 padsize=128k, if not padsize=300k.
324 -data Explicitely announce that the track source shall be recorded as
326 data track, and not as audio track. This option has no effect
327 with xorrecord, because there is no support for other track
328 formats anyway.
329 fs=size
331 Set the size of the program fifo buffer to the given value
332 rather than the default of 4m.
333 The fifo buffers a temporary surplus of track source data in
334 order to provide the drive with a steady stream during times of
335 temporary lack of track source supply.
336 Other than cdrecord, xorrecord enables drive buffer underrun
337 protection by default and does not wait with writing until the
338 fifo is full for a first time. On very old CD drives and slow
339 computers, this might cause aborted burn runs. In this case,
340 consider to use program cdrskin for CD burning. DVD and BD
341 drives tolerate buffer underrun without problems.
342 The larger the fifo, the longer periods of poor source supply
343 can be compensated. But a large fifo can deprive the operating
344 system of read cache for better filesystem performance.
345 speed=value
347 Set the write speed. Default is 0 = maximum speed. Speed can be
348 given in media type dependent x-speed numbers or as a desired
349 throughput per second in MMC compliant kB (= 1000) or MB (= 1000
350 kB). Media x-speed factor can be set explicity by appending "c"
351 for CD, "d" for DVD, "b" for BD. "x" is optional.
352 Example speeds:
353 706k = 706kB/s = 4c = 4xCD
354 5540k = 5540kB/s = 4d = 4xDVD
355 If there is no hint about the speed unit attached, then the
356 medium in the drive will decide. Default unit is CD, 1x =
357 176,400 raw bytes/second. With DVD, 1x = 1,385,000
358 bytes/second. With BD, 1x = 4,495,625 bytes/second.
359 MMC drives usually activate their own idea of speed and take the
360 speed value given by the burn program only as a hint for their
361 own decision.
362 -eject Eject the drive tray after alll other work is done.
364 Program version and verbosity:
366 -version
368 Print to standard output a line beginning by
369 "Cdrecord 2.01-Emulation Copyright"
370 and further lines which report the version of xorriso and its
371 supporting libraries. They also state the license under which
372 the program is provided, and disclaim any warranty, to the
373 extent permitted by law.
374 -v Increase program verbosity by one level. There are four
376 verbosity levels from nearly silent to debugging verbosity. The
377 both highest levels can be enabled by repeated -v or by -vv
378 resp. -vvv.
379 -V Log SCSI commands and drive replies to standard error. This
381 might be of interest if xorrecord and a particular drive or
382 medium do not cooperate as expected, or if you just want to know
383 how libburn interacts with the drive. To understand this
384 extremely verbous log, one needs to read SCSI specs SPC, SBC,
385 and MMC.
386 Please do not add such a log to a bug report on the first hand,
387 unless you want to point out a particular deviation from said
388 specs, or if you get asked for this log by a maintainer of
389 xorrecord who feels in charge for your bug report.
390 -help Print a sparse list of program options to standard error and
392 declare not to be cdrecord.
393 Options not compatible to cdrecord:
395 --no_rc
397 Only if used as first command line argument this option prevents
398 reading and interpretation of startup files. See section FILES
399 below.
400 --grow_overwriteable_iso
402 Enable emulation of multi-session writing on overwriteable media
403 which contain an ISO 9660 filesystem. This emulation is learned
404 from growisofs -M but adapted to the usage model of
405 xorrecord -msinfo
406 xorrisofs -C -M | xorrecord -waiti -multi -
407 for sequential media.
408 --grow_overwriteable_iso does not hamper the use of true
409 multi-session media. I.e. it is possible to use the same
410 xorrecord options with both kinds of media and to achieve
411 similar results if ISO 9660 filesystem images are to be written.
412 This option implies option -isosize and therefore demands that
413 the track source is a ISO 9660 filesystem image.
414 With overwriteable media and no option blank=fast|all present it
415 expands an eventual ISO 9660 filesystem on media. It is assumed
416 that this image's inner size description points to the end of
417 the valuable data. Overwriteable media with a recognizable ISO
418 9660 size will be regarded as appendable rather than as blank.
419 I.e. options -msinfo and -toc will work. -toc will always show
420 a single session with its size increasing with every added ISO
421 9660 image.
422 stream_recording="on"|"off"|number
424 Mode "on" requests that compliance to the desired speed setting
425 is preferred over management of write errors. With DVD-RAM and
426 BD this can bring effective write speed near to the nominal
427 write speed of the media. But it will also disable the
428 automatic use of replacement blocks if write errors occur. It
429 might as well be disliked or ignored by the drive.
430 If a number is given, then error management stays enabled for
431 all byte addresses below that number. Any number below 16s is
432 the same as "off".
433 dvd_obs="default"|"32k"|"64k"
435 Linux specific: Set the number of bytes to be transmitted with
436 each write operation to DVD or BD media. Tracks get padded up to
437 the next multiple of this write size. A number of 64 KB may
438 improve throughput with bus systems which show latency problems.
439 The default depends on media type, option stream_recording=, and
440 on compile time options.
441 write_start_address=value
443 Set the block address on overwritable media where to start
444 writing the track. With DVD+RW, DVD-RAM or BD-RE, byte_offset
445 must be aligned to 2 kiB blocks, but better is 32 kiB on DVD and
446 64 kiB on BD. With formatted DVD-RW 32 kiB alignment is
447 mandatory.
448 Other media are not suitable for this option.
449 stdio_sync="on"|"off"|number
451 Set the number of bytes after which to force output to emulated
452 stdio: drives. This forcing keeps the memory from being clogged
453 with lots of pending data for slow devices. Default "on" is the
454 same as "16m". Forced output can be disabled by "off".
455
457 Overview of examples:
458 Get an overview of drives and their addresses
459 Get info about a particular drive or loaded media
460 Prepare CD-RW or DVD-RW for re-use, BD-R for bad block handling
461 Format DVD-RW to avoid need for blanking before re-use
462 De-format DVD-RW to make it capable of multi-session again
463 Write a single ISO 9660 filesystem image
464 Write multiple ISO 9660 sessions
465 Write ISO 9660 session on-the-fly
466 Write compressed afio archive on-the-fly
467 Get an overview of drives and their addresses:
469 $ xorrecord --devices
470 Get info about a particular drive and loaded media:
472 $ xorrecord dev=/dev/sr0 -atip -toc --grow_overwriteable_iso
473 Prepare CD-RW or DVD-RW for re-use:
475 $ xorrecord -v dev=/dev/sr0 blank=as_needed -eject
476 Format DVD-RW to avoid need for blanking before re-use:
478 $ xorrecord -v dev=/dev/sr0 blank=format_overwrite -eject
479 This command may also be used to format BD-R media before first use, in
480 order to enable handling of write errors. Several hundred MB of spare
481 blocks will be reserved and write runs on such media will perform with
482 less than half nominal speed.
483 De-format DVD-RW to make it capable of multi-session again:
485 $ xorrecord -v dev=/dev/sr0 blank=deformat
486 Write a single ISO 9660 filesystem image:
488 $ xorrecord -v dev=/dev/sr0 speed=12 fs=8m \
489 blank=as_needed -eject padsize=300k my_image.iso
490 Write multiple ISO 9660 sessions:
492 This is possible with all media except minimally blanked DVD-RW and
493 DVD-R DL, which cannot do multi-session.
494 The first session is written like in the previous example, except that
495 option -multi is used. It will contain the files of hard disk directory
496 ./tree1 under the ISO 9660 directory /dir1:
497 $ xorrisofs -o image_1.iso -J -graft-points /dir1=./tree1
498 $ xorrecord -v dev=/dev/sr0 speed=12 fs=8m \
499 -multi --grow_overwritable_iso \
500 blank=as_needed -eject padsize=300k image_1.iso
501 For the second session xorrisofs needs to know the -msinfo numbers of
502 the medium. Further it will read data from the medium by using the
503 system's read-only CD-ROM driver.
504 It is advised to load the tray manually or via dd by the CD-ROM driver,
505 rather than letting xorrecord do this by its own SCSI driver. Many
506 system CD-ROM drivers do not take notice of xorrecord's activities.
507 $ dd if=/dev/sr0 count=1 >/dev/null 2>&1
508 Now get the -msinfo numbers:
509 $ m=$(xorrecord dev=/dev/sr0 -msinfo)
510 and use them with xorrisofs to add ./tree2 to the image as /dir2:
511 $ xorrisofs -M /dev/sr0 -C $m -o image_2.iso \
512 -J -graft-points /dir2=./tree2
513 Now burn the new session onto the same medium. This time without
514 blanking:
515 $ xorrecord -v dev=/dev/sr0 speed=12 fs=8m \
516 -multi --grow_overwritable_iso \
517 -eject padsize=300k image_2.iso
518 Operating systems which mount this medium will read the superblock of
519 the second session and show both directories /dir1 and /dir2.
520 Write ISO 9660 session on-the-fly:
522 It is possible to combine the run of xorrisofs and xorrecord in a
523 pipeline without storing the ISO 9660 image as file on hard disk:
524 $ xorrisofs -M /dev/sr0 -C $m \
525 -J -graft-points /dir2=./tree2 \
526 | xorrecord -v dev=/dev/sr0 speed=12 fs=8m \
527 -waiti -multi --grow_overwritable_iso \
528 -eject padsize=300k -
529 This is also the main use case of program xorriso itself, where this
530 run would look like:
531 $ xorriso -dev /dev/sr0 -joliet on -speed 12 -fs 8m \
532 -map ./tree2 /dir2 -commit_eject all
533 Write compressed afio archive on-the-fly:
535 This is possible with all media except minimally blanked DVD-RW and
536 DVD-R DL. Since the compressed output stream is of very variable
537 speed, a larger fifo is advised. Nevertheless, this example is not
538 suitable for very old CD drives which have no underrun protection and
539 thus would abort the burn run on temporary data shortage.
540 $ find . | afio -oZ - | \
541 xorrecord -v dev=/dev/sr0 speed=12 fs=64m \
542 -multi padsize=300k -
543 afio archives do not contain references to absolute data block
544 addresses. So they need no special precautions for multi-session. One
545 may get the session start addresses by option -toc, and then use dd
546 option skip= to begin reading at one of those addresses. E.g. for
547 listing its content:
548 $ dd if=/dev/sr0 bs=2048 skip=64046 | afio -tvZ -
549 afio will know when the end of the archive is reached.
550
552 Startup files:
553 If not --no_rc is given as the first argument then xorrecord attempts
554 on startup to read and execute lines from the following files:
555 /etc/default/xorriso
556 /etc/opt/xorriso/rc
557 /etc/xorriso/xorriso.conf
558 $HOME/.xorrisorc
559 The files are read in the sequence given here, but none of them is
560 required to exist. The lines are not interpreted as xorrecord options
561 but as generic xorriso commands. See man xorriso.
562
564 For generic xorriso command mode
565 xorriso(1)
566 Formatting track sources for xorrecord:
568 xorrisofs(1), mkisofs(8), genisoimage(8), afio(1), star(1)
569 Other programs which burn sessions to optical media
571 growisofs(1), cdrecord(1), wodim(1), cdrskin(1)
572
574 To report bugs, request help, or suggest enhancements for xorriso,
575 please send electronic mail to the public list <bug-xorriso@gnu.org>.
576 If more privacy is desired, mail to <scdbackup@gmx.net>.
577 Please describe what you expect xorriso to do, the program arguments
578 resp. commands by which you tried to achieve it, the messages of
579 xorriso, and the undesirable outcome of your program run.
580 Expect to get asked more questions before solutions can be proposed.
581
583 Thomas Schmitt <scdbackup@gmx.net>
584 for libburnia-project.org
585
587 Copyright (c) 2011 Thomas Schmitt
588 Permission is granted to distribute this text freely. It shall only be
589 modified in sync with the technical properties of xorriso. If you make
590 use of the license to derive modified versions of xorriso then you are
591 entitled to modify this text under that same license.
592
594 xorriso is in part based on work by Vreixo Formoso who provides
595 libisofs together with Mario Danic who also leads the libburnia team.
596 Thanks to Andy Polyakov who invented emulated growing, to Derek Foreman
597 and Ben Jansens who once founded libburn.
598 Compliments towards Joerg Schilling whose cdrtools served me for ten
599 years.
600 Version 1.1.8, Nov 20, 2011 XORRECORD(1)