"Fossies" - the Fresh Open Source Software Archive  

Source code changes of the file "xorriso/xorrecord.info" 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.

Binary file (standard input) matches
Home  |  About  |  Features  |  All  |  Newest  |  Dox  |  Diffs  |  RSS Feeds  |  Screenshots  |  Comments  |  Imprint  |  Privacy  |  HTTP(S)
xorrecord.info  (libisoburn-1.5.0):xorrecord.info  (libisoburn-1.5.2)
This is xorrecord.info, produced by makeinfo version 5.2 from This is xorrecord.info, produced by makeinfo version 5.2 from
xorrecord.texi. xorrecord.texi.
xorrecord - Emulation of CD/DVD/BD program cdrecord by program xorriso xorrecord - Emulation of CD/DVD/BD program cdrecord by program xorriso
Copyright (C) 2011 - 2018 Thomas Schmitt Copyright (C) 2011 - 2019 Thomas Schmitt
Permission is granted to distrubute this text freely. Permission is granted to distribute this text freely.
INFO-DIR-SECTION Archiving INFO-DIR-SECTION Archiving
START-INFO-DIR-ENTRY START-INFO-DIR-ENTRY
* Xorrecord: (xorrecord). Emulates CD/DVD/BD program cdrecord * Xorrecord: (xorrecord). Emulates CD/DVD/BD program cdrecord
END-INFO-DIR-ENTRY END-INFO-DIR-ENTRY
 
File: xorrecord.info, Node: Top, Next: Overview, Up: (dir) File: xorrecord.info, Node: Top, Next: Overview, Up: (dir)
xorrecord 1.5.0 xorrecord 1.5.2
*************** ***************
xorrecord - Emulation of CD/DVD/BD program cdrecord by program xorriso xorrecord - Emulation of CD/DVD/BD program cdrecord by program xorriso
* Menu: * Menu:
* Overview:: Overview * Overview:: Overview
* Standards:: MMC, Session, Track, Media types * Standards:: MMC, Session, Track, Media types
* Drive:: Drive preparation and addressing * Drive:: Drive preparation and addressing
* Xorriso:: Relation to program xorriso * Xorriso:: Relation to program xorriso
* Options:: Options * Options:: Options
skipping to change at line 474 skipping to change at line 474
permitted by law. permitted by law.
Afterwards end emulation without performing any drive operation. Afterwards end emulation without performing any drive operation.
-v -v
Increase program verbosity by one level. There are four verbosity Increase program verbosity by one level. There are four verbosity
levels from nearly silent to debugging verbosity. The both highest levels from nearly silent to debugging verbosity. The both highest
levels can be enabled by repeated -v or by -vv or by -vvv. levels can be enabled by repeated -v or by -vv or by -vvv.
-V -V
Log SCSI commands and drive replies to standard error. This might Log SCSI commands and drive replies to standard error. This might
be of interest if *xorrecord* and a particular drive or medium do be of interest if *xorrecord* and a particular drive or medium do
not cooperate as expected, or if you just want to know how libburn not cooperate as expected, or if you just want to know how libburn
interacts with the drive. To understand this extremely verbous interacts with the drive. To understand this extremely verbose
log, one needs to read SCSI specs SPC, SBC, and MMC. log, one needs to read SCSI specs SPC, SBC, and MMC.
Please do not add such a log to a bug report on the first hand, Please do not add such a log to a bug report on the first hand,
unless you want to point out a particular deviation from said unless you want to point out a particular deviation from said
specs, or if you get asked for this log by a maintainer of specs, or if you get asked for 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 -help
Print a sparse list of program options to standard error and Print a sparse list of program options to standard error and
declare not to be cdrecord. declare not to be cdrecord.
Afterwards end emulation without performing any drive operation. Afterwards end emulation without performing any drive operation.
 
File: xorrecord.info, Node: NonCdrecord, Next: ExDevices, Prev: Verbous, Up: Options File: xorrecord.info, Node: NonCdrecord, Next: ExDevices, Prev: Verbous, Up: Options
5.5 Options not compatible to cdrecord 5.5 Options not compatible to cdrecord
====================================== ======================================
--no_rc --no_rc
Only if used as first command line argument this option prevents Only if used as first command line argument this option prevents
reading and interpretation of startup files. See section FILES reading and interpretation of startup files. See section FILES
below. below.
--drive_not_exclusive
This option disables the use of device file locking mechanisms 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
mounted, or opened by some other process, or guarded by
/dev/pktcdvd*. Make sure that other users 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/sr* By default, cdrskin tries to map Linux drive addresses to /dev/sr*
before they get opened for operating the drive. This coordinates before they get opened for operating the drive. This coordinates
well with other use cases of optical drives, like mount(8). But 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 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 one drive to process an SCSI command while all others have to wait
for its completion. This yields awful throughput if more than one for its completion. This yields awful throughput if more than one
drive is writing or reading simultaneously. drive is writing or reading simultaneously.
The global lock is not applied to device files /dev/sg* and also The global lock is not applied to device files /dev/sg* and also
skipping to change at line 706 skipping to change at line 714
./tree1 under the ISO 9660 directory /dir1: ./tree1 under the ISO 9660 directory /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 For the second session xorrisofs needs to know the -msinfo numbers of
the medium. Further it will read data from the medium by using the the medium. Further it will read data from the medium by using the
system's read-only CD-ROM driver. 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 is
rather than letting xorrecord do this by its own SCSI driver. Many necessary to force their attention by ejecting and reloading the drive
system CD-ROM drivers do not take notice of xorrecord's activities. tray. Therefore above run uses option -eject.
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
loading:
$ 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 Now burn the new session onto the same medium. This time without
blanking: 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
skipping to change at line 736 skipping to change at line 747
Operating systems which mount this medium will read the superblock of Operating systems which mount this medium will read the superblock of
the second session and show both directories /dir1 and /dir2. the second session and show both directories /dir1 and /dir2.
 
File: xorrecord.info, Node: ExIsoFly, Next: ExAfio, Prev: ExIsoMulti, Up: Ex amples File: xorrecord.info, Node: ExIsoFly, Next: ExAfio, Prev: ExIsoMulti, Up: Ex amples
6.8 Write ISO 9660 session on-the-fly 6.8 Write ISO 9660 session on-the-fly
===================================== =====================================
It is possible to combine the run of *xorrisofs* and 'xorrecord' in a It is possible to combine the run of *xorrisofs* and 'xorrecord' in a
pipeline without storing the ISO 9660 image as file on hard disk: pipeline without storing the ISO 9660 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 is also the main use case of program *xorriso* itself, where the
this run 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
 
File: xorrecord.info, Node: ExAfio, Prev: ExIsoFly, Up: Examples File: xorrecord.info, Node: ExAfio, Prev: ExIsoFly, Up: Examples
6.9 Write compressed afio archive on-the-fly 6.9 Write compressed afio archive on-the-fly
============================================ ============================================