ISODUMP
Section: Linux User's Manual (1)
Updated: 2008-01-30
Index
Return to Main Contents
NAME
isodump - extract iso9660 image from device or file
SYNOPSIS
isodump
[-ahHpvVx]
[infile [outfile]]
DESCRIPTION
Isodump
extracts an iso9660 image from
infile
(defaults to
/dev/cdrom)
to
outfile
(defaults to
stdout)
where the size of the image is taken from the image itself
(its primary descriptor block).
As usual, dashes indicate standard in- and output.
If
infile
refers to a CDROM you may read the first (data-) track only.
This is due to the fact that
isodump
is based on read(2) calls only. Use
cddaread(1)
for ripping tracks #>1 off a cd.
Isodump
also allows for conversion of images generated by other
programs such as CloneCD and Nero which do not produce valid iso9660 images
(loop device mountable images). The input format is detected
automatically. However, since XA and NRG images cannot be detected by
reading the first block only, for these images the
-x
and
-n
flag must be specified, respectively. But relax - you are told about it.
OPTIONS
- -a
-
extract all data available (read until EOF)
- -h
-
display help on stdout and
exit successfully
- -H
-
write 80 hash marks on stderr
- -n
-
assume NRG image input (skip first 150 blocks)
- -p
-
don't pad image (if it's too small)
- -v
-
increase verbosity level on stderr
- -V
-
display version and compilation info on stdout and
exit successfully
- -x
-
assume XA image input (set block offset to 24)
RETURN VALUE
On success, 0 is returned. On error, a value >0 is returned.
ERRORS
- 1
-
image has been padded to required size
- 2
-
a program bug has seen the light
- 3
-
program exited due to a read error
- 4
-
image is broken or of unknown type
- 5
-
the error is different from those explained above
HINTS
Isodump
tries to create images of correct size (taken from the primary descriptor
block). If it encounters an unexpected
EOF,
by default the stream is filled up with zeroes, it's
padded.
(Assumption: The image size is already known, i.e. the
primary descriptor block has been read.) However,
isodump
does not correct an
read error
because the reason remains unknown. - Am I reading from CDROM,
harddisk or stdin??
Thus, if you have a broken CDROM and you really want to pad the image,
you must run
isodump
twice, one instance for the dump and another for padding:
isodump -vvH
|
isodump
>
image_file
AUTHOR
Steffen Solyga <solyga@absinth.net>
SEE ALSO
isoinfo(1),
cddaread(1),
disksize(1),
mkisofs(8)
Index
- NAME
-
- SYNOPSIS
-
- DESCRIPTION
-
- OPTIONS
-
- RETURN VALUE
-
- ERRORS
-
- HINTS
-
- AUTHOR
-
- SEE ALSO
-
This document was created by
man2html,
using the manual pages.
Time: 13:09:19 GMT, July 30, 2010