2 .\" @(#)isoinfo.8 1.7 04/06/01 joerg
4 .\" Modified for cdrkit in 12/2006
7 .if t .ds a \v'-0.55m'\h'0.00n'\z.\h'0.40n'\z.\v'0.55m'\h'-0.40n'a
8 .if t .ds o \v'-0.55m'\h'0.00n'\z.\h'0.45n'\z.\v'0.55m'\h'-0.45n'o
9 .if t .ds u \v'-0.55m'\h'0.00n'\z.\h'0.40n'\z.\v'0.55m'\h'-0.40n'u
10 .if t .ds A \v'-0.77m'\h'0.25n'\z.\h'0.45n'\z.\v'0.77m'\h'-0.70n'A
11 .if t .ds O \v'-0.77m'\h'0.25n'\z.\h'0.45n'\z.\v'0.77m'\h'-0.70n'O
12 .if t .ds U \v'-0.77m'\h'0.30n'\z.\h'0.45n'\z.\v'0.77m'\h'-0.75n'U
19 .TH ISOINFO 1 "04/06/01" "Version 2.0"
21 devdump, isoinfo, isovfy, isodump \- Utility programs for dumping and verifying iso9660
77 is a crude utility to interactively display the contents of device or
79 The initial screen is a display of the first 256 bytes of the first 2048 byte
81 The commands are the same as with
85 is a crude utility to interactively display the contents of iso9660 images
86 in order to verify directory integrity.
87 The initial screen is a display of the first part of the root directory,
88 and the prompt shows you the extent number and offset in the extent.
91 You can use the 'a' and 'b'
92 commands to move backwards and forwards within the image. The 'g' command
93 allows you to goto an arbitrary extent, and the 'f' command specifies
94 a search string to be used. The '+' command searches forward for the next
95 instance of the search string, and the 'q' command exits
102 is a utility to perform directory like listings of iso9660 images.
105 is a utility to verify the integrity of an iso9660 image. Most of the tests
108 were added after bugs were discovered in early versions of
110 It isn't all that clear how useful this is anymore, but it doesn't hurt to
114 The options common to all programs are
115 .BR \-help , \-h , \-version ,
116 .BI i =name, dev =name.
119 program has additional command line options. The options are:
124 print a summary of all options.
127 Print information from the primary volume descriptor (PVD) of the iso9660
128 image. This includes information about Rock Ridge, Joliet extensions
129 and Eltorito boot information
133 generate output as if a 'find . -print' command had been run on the iso9660
134 image. You should not use the
141 Specifies the path of the iso9660 image that we wish to examine.
146 are mutual exclusive.
149 Sets the SCSI target for the drive, see notes above.
150 A typical device specification is
153 If a filename must be provided together with the numerical target
154 specification, the filename is implementation specific.
155 The correct filename in this case can be found in the system specific
156 manuals of the target operating system.
161 support, you need to use the control device (e.g.
163 A correct device specification in this case may be
164 .BI dev= /dev/rcd0.ctl:@
167 On Linux, drives connected to a parallel port adapter are mapped
168 to a virtual SCSI bus. Different adapters are mapped to different
169 targets on this virtual SCSI bus.
173 option is present, the program
174 will try to get the device from the
178 If the argument to the
180 option does not contain the characters ',', '/', '@' or ':',
181 it is interpreted as an label name that may be found in the file
182 /etc/wodim.conf (see FILES section).
188 are mutual exclusive.
191 generate output as if a 'ls -lR' command had been run on the iso9660 image.
192 You should not use the
199 Quick hack to help examine single session disc files that are to be written to
200 a multi-session disc. The sector number specified is the sector number at
201 which the iso9660 image should be written when send to the cd-writer. Not
202 used for the first session on the disc.
205 Print path table information.
208 Extract information from Rock Ridge extensions (if present) for permissions,
209 file names and ownerships.
212 Extract information from Joliet extensions (if present) for file names.
215 Convert Joliet file names (if present) to the supplied charset. See
220 Quick hack to help examine multi-session images that have already been burned
221 to a multi-session disc. The sector number specified is the sector number for
222 the start of the session we wish to display.
225 Extract specified file to stdout.
227 The author of the original sources (1993 .\|.\|. 1998) is
228 Eric Youngdale <ericy@gnu.ai.mit.edu> or <eric@andante.jic.com> is to blame
229 for these shoddy hacks.
230 J\*org Schilling wrote the SCSI transport library and its adaptation layer to
231 the programs and newer parts (starting from 1999) of the utilities, this makes
233 Copyright (C) 1999-2004 J\*org Schilling.
234 Patches to improve general usability would be gladly accepted.
236 This manpage describes the program implementation of
239 as shipped by the cdrkit distribution. See
241 http://alioth.debian.org/projects/debburn/
242 for details. It is a spinoff from the original program distributed in the
243 cdrtools package [1]. However, the cdrtools
244 developers are not involved in the development of this spinoff and therefore
245 shall not be made responsible for any problem caused by it. Do not try to get
246 support for this program by contacting the original author(s).
248 If you have support questions, send them to
251 debburn-devel@lists.alioth.debian.org
254 If you have definitely found a bug, send a mail to this list or to
257 submit@bugs.debian.org
260 writing at least a short description into the Subject and "Package: cdrkit" into the first line of the mail body.
262 The user interface really sucks.
263 .SH FUTURE IMPROVEMENTS
264 These utilities are really quick hacks, which are very useful for debugging
265 problems in genisoimage or in an iso9660 filesystem. In the long run, it would
266 be nice to have a daemon that would NFS export a iso9660 image.
268 The isoinfo program is probably the program that is of the most use to
271 These utilities come with the
273 package, and the primary download site
274 is http://debburn.alioth.debian.org/ and FTP mirrors of distributions.
275 Despite the name, the software is not beta.
280 This may either hold a device identifier that is suitable to the open
281 call of the SCSI transport library or a label in the file /etc/wodim.conf.
286 environment is present, the remote connection will not be created via
288 but by calling the program pointed to by
291 .BR RSH= /usr/bin/ssh
292 to create a secure shell connection.
294 Note that this forces the program
295 to create a pipe to the
297 program and disallows the program
298 to directly access the network socket to the remote server.
299 This makes it impossible to set up performance parameters and slows down
300 the connection compared to a
309 environment is present, the remote SCSI server will not be the program
310 .B /opt/schily/sbin/rscsi
311 but the program pointed to by
313 Note that the remote SCSI server program name will be ignored if you log in
314 using an account that has been created with a remote SCSI server program as
320 Default values can be set for the following options in /etc/wodim.conf.
324 This may either hold a device identifier that is suitable to the open
325 call of the SCSI transport library or a label in the file /etc/wodim.conf
326 that allows to identify a specific drive on the system.
329 is an identifier for a specific drive on the system.
330 Such an identifier may not contain the characters ',', '/', '@' or ':'.
332 Each line that follows a label contains a TAB separated list of items.
333 Currently, four items are recognized: the SCSI ID of the drive, the
334 default speed that should be used for this drive, the default FIFO size
335 that should be used for this drive and drive specific options. The values for
339 may be set to -1 to tell the program to use the global defaults.
340 The value for driveropts may be set to "" if no driveropts are used.
341 A typical line may look this way:
345 yamaha= 1,6,0 -1 -1 burnfree
347 This tells the program
350 is at scsibus 0, target 5, lun 0 and should be used with speed 4 and
352 A second drive may be found at scsibus 1, target 6, lun 0 and uses the
353 default speed and the default FIFO size.
364 [1] Cdrtools 2.01.01a08 from May 2006, http://cdrecord.berlios.de