1ISOINFO(1)                  General Commands Manual                 ISOINFO(1)
2
3
4

NAME

6       devdump,  isoinfo,  isovfy,  isodump - Utility programs for dumping and
7       verifying iso9660 images.
8

SYNOPSIS

10       devdump isoimage
11
12       isodump isoimage
13
14       isoinfo [ -d ] [ -h ] [ -R ] [ -J ] [ -j charset ] [ -f ] [ -l ] [ -p ]
15       [ -T sector ] [ -N sector ] [ -i isoimage ] [ -x path ]
16
17       isovfy isoimage
18

DESCRIPTION

20       devdump  is  a  crude  utility to interactively display the contents of
21       device or filesystem images.  The initial screen is a  display  of  the
22       first  256  bytes  of the first 2048 byte sector.  The commands are the
23       same as with isodump.
24
25       isodump is a crude utility to interactively  display  the  contents  of
26       iso9660  images  in  order  to verify directory integrity.  The initial
27       screen is a display of the first part of the root  directory,  and  the
28       prompt shows you the extent number and offset in the extent.
29
30              You  can use the 'a' and 'b' commands to move backwards and for‐
31              wards within the image. The 'g' command allows you  to  goto  an
32              arbitrary  extent, and the 'f' command specifies a search string
33              to be used. The  '+'  command  searches  forward  for  the  next
34              instance of the search string, and the 'q' command exits devdump
35              or isodump.
36
37       isoinfo is a utility to perform  directory  like  listings  of  iso9660
38       images.
39
40       isovfy  is  a utility to verify the integrity of an iso9660 image. Most
41       of the tests in isovfy were added after bugs were discovered  in  early
42       versions  of  genisoimage.   It isn't all that clear how useful this is
43       anymore, but it doesn't hurt to have this around.
44
45

OPTIONS

47       The   options   common   to   all   programs   are   -help,-h,-version,
48       i=name,dev=name.   The  isoinfo  program  has  additional  command line
49       options. The options are:
50
51       -help
52
53       -h     print a summary of all options.
54
55       -d     Print information from the primary volume  descriptor  (PVD)  of
56              the  iso9660  image. This includes information about Rock Ridge,
57              Joliet extensions and Eltorito boot information if present.
58
59       -f     generate output as if a 'find . -print' command had been run  on
60              the  iso9660  image. You should not use the -l image with the -f
61              option.
62
63       -i iso_image
64              Specifies the path of the iso9660 image that we wish to examine.
65              The options -i and dev=target are mutual exclusive.
66
67       dev=target
68              Sets  the SCSI target for the drive, see notes above.  A typical
69              device specification is dev=6,0 .  If a filename  must  be  pro‐
70              vided  together  with  the  numerical  target specification, the
71              filename is implementation specific.  The  correct  filename  in
72              this  case  can  be  found in the system specific manuals of the
73              target operating system.  On a FreeBSD system without  CAM  sup‐
74              port,  you need to use the control device (e.g.  /dev/rcd0.ctl).
75              A  correct  device   specification   in   this   case   may   be
76              dev=/dev/rcd0.ctl:@ .
77
78              On Linux, drives connected to a parallel port adapter are mapped
79              to a virtual SCSI bus. Different adapters are mapped to  differ‐
80              ent targets on this virtual SCSI bus.
81
82              If  no  dev  option  is present, the program will try to get the
83              device from the CDR_DEVICE environment.
84
85              If the argument to the dev= option does not contain the  charac‐
86              ters  ',',  '/',  '@' or ':', it is interpreted as an label name
87              that may be found in the file /etc/wodim.conf  (see  FILES  sec‐
88              tion).
89
90              The options -i and dev=target are mutual exclusive.
91
92       -l     generate  output  as  if  a 'ls -lR' command had been run on the
93              iso9660 image.  You should not use the  -f  image  with  the  -l
94              option.
95
96       -N sector
97              Quick hack to help examine single session disc files that are to
98              be written to a multi-session disc. The sector number  specified
99              is  the sector number at which the iso9660 image should be writ‐
100              ten when send to the cd-writer. Not used for the  first  session
101              on the disc.
102
103       -p     Print path table information.
104
105       -R     Extract  information from Rock Ridge extensions (if present) for
106              permissions, file names and ownerships.
107
108       -J     Extract information from Joliet extensions (if present) for file
109              names.
110
111       -j charset
112              Convert  Joliet file names (if present) to the supplied charset.
113              See genisoimage(8) for details.
114
115       -T sector
116              Quick hack  to  help  examine  multi-session  images  that  have
117              already  been  burned to a multi-session disc. The sector number
118              specified is the sector number for the start of the  session  we
119              wish to display.
120
121       -x pathname
122              Extract specified file to stdout.
123

AUTHOR

125       The  author  of  the original sources (1993 ... 1998) is Eric Youngdale
126       <ericy@gnu.ai.mit.edu> or <eric@andante.jic.com> is to blame for  these
127       shoddy hacks.  Joerg Schilling wrote the SCSI transport library and its
128       adaptation layer to the programs and newer parts (starting  from  1999)
129       of  the  utilities,  this  makes  them  Copyright  (C)  1999-2004 Joerg
130       Schilling.  Patches  to  improve  general  usability  would  be  gladly
131       accepted.
132
133       This manpage describes the program implementation of isoinfo as shipped
134       by the cdrkit distribution. See  http://alioth.debian.org/projects/deb
135       burn/  for  details. It is a spinoff from the original program distrib‐
136       uted in the cdrtools package [1]. However, the cdrtools developers  are
137       not involved in the development of this spinoff and therefore shall not
138       be made responsible for any problem caused by it. Do  not  try  to  get
139       support for this program by contacting the original author(s).
140
141       If you have support questions, send them to
142
143       debburn-devel@lists.alioth.debian.org
144
145       If you have definitely found a bug, send a mail to this list or to
146
147       submit@bugs.debian.org
148
149       writing  at  least  a  short description into the Subject and "Package:
150       cdrkit" into the first line of the mail body.
151

BUGS

153       The user interface really sucks.
154

FUTURE IMPROVEMENTS

156       These utilities are really quick  hacks,  which  are  very  useful  for
157       debugging  problems  in genisoimage or in an iso9660 filesystem. In the
158       long run, it would be nice to have a daemon that  would  NFS  export  a
159       iso9660 image.
160
161       The  isoinfo program is probably the program that is of the most use to
162       the general user.
163

AVAILABILITY

165       These utilities come with the cdrkit package, and the primary  download
166       site  is http://debburn.alioth.debian.org/ and FTP mirrors of distribu‐
167       tions.  Despite the name, the software is not beta.
168
169

ENVIRONMENT

171       CDR_DEVICE
172              This may either hold a device identifier that is suitable to the
173              open  call  of the SCSI transport library or a label in the file
174              /etc/wodim.conf.
175
176       RSH    If the RSH environment is present, the  remote  connection  will
177              not be created via rcmd(3) but by calling the program pointed to
178              by RSH.  Use e.g.  RSH=/usr/bin/ssh to  create  a  secure  shell
179              connection.
180
181              Note that this forces the program to create a pipe to the rsh(1)
182              program and disallows the program to directly access the network
183              socket to the remote server.  This makes it impossible to set up
184              performance parameters and slows down the connection compared to
185              a root initiated rcmd(3) connection.
186
187       RSCSI  If the RSCSI environment is present, the remote SCSI server will
188              not  be  the  program  /opt/schily/sbin/rscsi  but  the  program
189              pointed  to  by RSCSI.  Note that the remote SCSI server program
190              name will be ignored if you log in using  an  account  that  has
191              been created with a remote SCSI server program as login shell.
192
193

FILES

195       /etc/wodim.conf
196              Default   values  can  be  set  for  the  following  options  in
197              /etc/wodim.conf.
198
199              CDR_DEVICE
200                     This may either hold a device identifier that is suitable
201                     to the open call of the SCSI transport library or a label
202                     in the file /etc/wodim.conf that  allows  to  identify  a
203                     specific drive on the system.
204
205              Any other label
206                     is  an  identifier  for  a  specific drive on the system.
207                     Such an identifier may not contain  the  characters  ',',
208                     '/', '@' or ':'.
209
210                     Each  line  that follows a label contains a TAB separated
211                     list of items.  Currently, four items are recognized: the
212                     SCSI  ID  of  the drive, the default speed that should be
213                     used for this drive, the default FIFO size that should be
214                     used  for this drive and drive specific options. The val‐
215                     ues for speed and fifosize may be set to -1 to  tell  the
216                     program  to  use  the  global  defaults.   The  value for
217                     driveropts may be set to "" if no driveropts are used.  A
218                     typical line may look this way:
219
220                     teac1= 0,5,0   4    8m   ""
221
222                     yamaha= 1,6,0  -1   -1   burnfree
223
224                     This  tells  the  program  that a drive named teac1 is at
225                     scsibus 0, target 5, lun 0 and should be used with  speed
226                     4  and  a FIFO size of 8 MB.  A second drive may be found
227                     at scsibus 1, target 6, lun 0 and uses the default  speed
228                     and the default FIFO size.
229

SEE ALSO

231       genisoimage(1), wodim(1), readcd(1), ssh(1).
232

SOURCES

234       [1] Cdrtools 2.01.01a08 from May 2006, http://cdrecord.berlios.de
235
236
237
238
239Version 2.0                        04/06/01                         ISOINFO(1)
Impressum