Changed prescription for safe loading of tray before xorrisofs add-on session

This commit is contained in:
2018-11-11 14:43:43 +01:00
parent ff68bda006
commit b8ee16af4a
9 changed files with 286 additions and 186 deletions

View File

@ -718,15 +718,18 @@ 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 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,
rather than letting xorrecord do this by its own SCSI driver. Many
system CD-ROM drivers do not take notice of xorrecord's activities.
$ dd if=/dev/sr0 count=1 >/dev/null 2>&1
Now get the -msinfo numbers:
Many systems do not take notice of xorrecord's write activities. It is
necessary to force their attention by ejecting and reloading the drive
tray. Therefore above run uses option -eject.
Get the -msinfo numbers (and properly reload the tray if it has a motor)
by:
$ 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 \
-J -graft-points /dir2=./tree2
@ -748,7 +751,18 @@ File: xorrecord.info, Node: ExIsoFly, Next: ExAfio, Prev: ExIsoMulti, Up: Ex
=====================================
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 \
-J -graft-points /dir2=./tree2 \
@ -756,8 +770,8 @@ pipeline without storing the ISO 9660 image as file on hard disk:
-waiti -multi -grow_overwriteable_iso \
-eject padsize=300k -
This is also the main use case of program *xorriso* itself, where
this run would look like:
This is also the main use case of program *xorriso* itself, where the
run would need no system workarounds and simply look like:
$ xorriso -dev /dev/sr0 -joliet on -speed 12 -fs 8m \
-map ./tree2 /dir2 -commit_eject all
@ -1017,13 +1031,13 @@ Node: ExFormat31368
Node: ExDeformat31886
Node: ExIsoSingle32153
Node: ExIsoMulti32437
Node: ExIsoFly34071
Node: ExAfio34742
Node: Files35740
Node: Seealso36296
Node: Bugreport36659
Node: Legal37250
Node: CommandIdx38179
Node: ConceptIdx41669
Node: ExIsoFly34181
Node: ExAfio35373
Node: Files36371
Node: Seealso36927
Node: Bugreport37290
Node: Legal37881
Node: CommandIdx38810
Node: ConceptIdx42300

End Tag Table