libburnia/libisoburn
2
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

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

Browse Source
This commit is contained in:
Thomas Schmitt
2018-11-11 14:43:43 +01:00
parent ff68bda006
commit b8ee16af4a
9 changed files with 286 additions and 186 deletions
Download Patch File Download Diff File Expand all files Collapse all files

35
xorriso/xorrecord.1
View File

@ -9,7 +9,7 @@
.\" First parameter, NAME, should be all caps
.\" Second parameter, SECTION, should be 1-8, maybe w/ subsection
.\" other parameters are allowed: see man(7), man(1)
.TH XORRECORD 1 "Version 1.5.1, Oct 08, 2018"
.TH XORRECORD 1 "Version 1.5.1, Nov 11, 2018"
.\" Please adjust this date whenever revising the manpage.
.\"
.\" Some roff macros, for reference:
@ -736,18 +736,19 @@ 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.
.br
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.
.br
$ dd if=/dev/sr0 count=1 >/dev/null 2>&1
.br
Now get the \-msinfo numbers:
Get the \-msinfo numbers (and properly reload the tray if it has a motor) by:
.br
$ m=$(xorrecord dev=/dev/sr0 \-msinfo)
.br
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:
.br
$ dd if=/dev/sr0 count=1 >/dev/null 2>&1
.br
Use the numbers with xorrisofs to add ./tree2 to the image as /dir2:
.br
$ xorrisofs \-M /dev/sr0 \-C $m \-o image_2.iso \\
.br
@ -766,7 +767,19 @@ of the second session and show both directories /dir1 and /dir2.
.SS
.B Write ISO 9660 session on-the-fly:
It is possible to combine the run of \fBxorrisofs\fR and \fBxorrecord\fR
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.
.br
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.
.br
Again, xorriso has the patience and dd is a dispensable victim for demons.
.br
$ m=$(xorrecord dev=/dev/sr0 \-msinfo)
.br
$ dd if=/dev/sr0 count=1 >/dev/null 2>&1
.br
$ xorrisofs \-M /dev/sr0 \-C $m \\
.br
@ -779,7 +792,7 @@ in a pipeline without storing the ISO 9660 image as file on hard disk:
\-eject padsize=300k \-
.br
This is also the main use case of program \fBxorriso\fR itself,
where this run would look like:
where the run would need no system workarounds and simply look like:
.br
$ xorriso \-dev /dev/sr0 \-joliet on \-speed 12 \-fs 8m \\
.br