Changed prescription for safe loading of tray before xorrisofs add-on session
This commit is contained in:
@ -50,7 +50,7 @@
|
||||
@c man .\" First parameter, NAME, should be all caps
|
||||
@c man .\" Second parameter, SECTION, should be 1-8, maybe w/ subsection
|
||||
@c man .\" other parameters are allowed: see man(7), man(1)
|
||||
@c man .TH XORRECORD 1 "Version 1.5.1, Oct 08, 2018"
|
||||
@c man .TH XORRECORD 1 "Version 1.5.1, Nov 11, 2018"
|
||||
@c man .\" Please adjust this date whenever revising the manpage.
|
||||
@c man .\"
|
||||
@c man .\" Some roff macros, for reference:
|
||||
@ -998,20 +998,21 @@ 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.
|
||||
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.
|
||||
@*
|
||||
@sp 1
|
||||
$ dd if=/dev/sr0 count=1 >/dev/null 2>&1
|
||||
@*
|
||||
Now get the -msinfo numbers:
|
||||
Get the -msinfo numbers (and properly reload the tray if it has a motor) by:
|
||||
@*
|
||||
$ m=$(xorrecord dev=/dev/sr0 -msinfo)
|
||||
@*
|
||||
@sp 1
|
||||
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
|
||||
@*
|
||||
@sp 1
|
||||
Use the numbers with xorrisofs to add ./tree2 to the image as /dir2:
|
||||
@*
|
||||
@sp 1
|
||||
$ xorrisofs -M /dev/sr0 -C $m -o image_2.iso \
|
||||
@ -1036,7 +1037,21 @@ of the second session and show both directories /dir1 and /dir2.
|
||||
@node ExIsoFly, ExAfio, ExIsoMulti, Examples
|
||||
@section Write ISO 9660 session on-the-fly
|
||||
It is possible to combine the run of @strong{xorrisofs} and @command{xorrecord}
|
||||
in a pipeline without storing the ISO 9660 image as file on hard disk:
|
||||
in a 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.
|
||||
@*
|
||||
@sp 1
|
||||
$ m=$(xorrecord dev=/dev/sr0 -msinfo)
|
||||
@*
|
||||
@sp 1
|
||||
$ dd if=/dev/sr0 count=1 >/dev/null 2>&1
|
||||
@*
|
||||
@sp 1
|
||||
$ xorrisofs -M /dev/sr0 -C $m \
|
||||
@ -1051,7 +1066,7 @@ in a pipeline without storing the ISO 9660 image as file on hard disk:
|
||||
@*
|
||||
@sp 1
|
||||
This is also the main use case of program @strong{xorriso} itself,
|
||||
where this run would look like:
|
||||
where the run would need no system workarounds and simply look like:
|
||||
@*
|
||||
@sp 1
|
||||
$ xorriso -dev /dev/sr0 -joliet on -speed 12 -fs 8m \
|
||||
|
Reference in New Issue
Block a user