Debian Codegraph @

upstream/opensuse-tumbleweed/man8/isoinfo.8

raw
1 .\"
2 .\" @(#)isoinfo.8 1.17 18/05/24 joerg
3 .\"
4 .\" -*- nroff -*-
5 .if t .ds a \v'-0.55m'\h'0.00n'\z.\h'0.40n'\z.\v'0.55m'\h'-0.40n'a
6 .if t .ds o \v'-0.55m'\h'0.00n'\z.\h'0.45n'\z.\v'0.55m'\h'-0.45n'o
7 .if t .ds u \v'-0.55m'\h'0.00n'\z.\h'0.40n'\z.\v'0.55m'\h'-0.40n'u
8 .if t .ds A \v'-0.77m'\h'0.25n'\z.\h'0.45n'\z.\v'0.77m'\h'-0.70n'A
9 .if t .ds O \v'-0.77m'\h'0.25n'\z.\h'0.45n'\z.\v'0.77m'\h'-0.70n'O
10 .if t .ds U \v'-0.77m'\h'0.30n'\z.\h'0.45n'\z.\v'0.77m'\h'-0.75n'U
11 .if t .ds s \\(*b
12 .if t .ds S SS
13 .if n .ds a ae
14 .if n .ds o oe
15 .if n .ds u ue
16 .if n .ds s sz
17 .TH ISOINFO 8 "2022/10/06" "Version 3.02"
18 .SH NAME
19 devdump, isoinfo, isovfy, isodump \- Utility programs for dumping and verifying iso9660
20 images.
21 .SH SYNOPSIS
22 .B devdump
23 .I isoimage
24 .PP
25 .B isodump
26 .I isoimage
27 .PP
28 .B isoinfo
29 [
30 .I options
31 ]
32 [
33 .B\-find
34 [
35 .I find expression
36 ]]
37 .PP
38 .B isovfy
39 .I isoimage
40 .SH DESCRIPTION
41 .B devdump
42 is a crude utility to interactively display the contents of device or
43 filesystem images.
44 The initial screen is a display of the first 256 bytes of the first 2048 byte
45 sector.
46 The commands are the same as with
47 .BR isodump .
48 .PP
49 .B isodump
50 is a crude utility to interactively display the contents of iso9660 images
51 in order to verify directory integrity.
52 The initial screen is a display of the first part of the root directory,
53 and the prompt shows you the extent number and offset in the extent.
54 .RS
55 .PP
56 You can use the 'a' and 'b'
57 commands to move backwards and forwards within the image. The 'g' command
58 allows you to goto an arbitrary extent, and the 'f' command specifies
59 a search string to be used. The '+' command searches forward for the next
60 instance of the search string, and the 'q' command exits
61 .B devdump
62 or
63 .BR isodump .
64 .RE
65 .PP
66 .B isoinfo
67 is a utility to perform directory like listings of iso9660 images.
68 .PP
69 .B isovfy
70 is a utility to verify the integrity of an iso9660 image. Most of the tests
71 in
72 .B isovfy
73 were added after bugs were discovered in early versions of
74 .B mkisofs.
75 It isn't all that clear how useful this is anymore, but it doesn't hurt to
76 have this around.
77
78 .SH OPTIONS
79 The options common to all programs are
80 .BR \-help , \-h , \-version ,
81 .BI i =name, dev =name.
82 The
83 .B isoinfo
84 program has additional command line options. The options are:
85 .TP
86 .B \-help
87 .TP
88 .B \-h
89 print a summary of all options.
90 .TP
91 .B \-d
92 Print information from the primary volume descriptor (PVD) of the iso9660
93 image. This includes information about Rock Ridge, Joliet extensions
94 and Eltorito boot information
95 if present.
96 .TP
97 .B \-f
98 generate output as if a 'find . -print' command had been run on the iso9660
99 image. You should not use the
100 .B -l
101 image with the
102 .B -f
103 option.
104 The same output is created by calling
105 .I isoinfo
106 with
107 .B \-find \-print
108 .TP
109 .BI \-find " find expression"
110 This option acts a separator. If it is used, all
111 .B isoinfo
112 options must be to the left of the
113 .B \-find
114 option. To the right of the
115 .B \-find
116 option, mkisofs accepts the find command line syntax only.
117 If the find expression includes a
118 .B \-print
119 or
120 .B \-ls
121 promary, the
122 .B \-l to
123 .B isoinfo
124 is ignored.
125 If the find expression evaluates as true, the selected action (e.g.
126 list the ISO-9660 directory) is performed.
127 .TP
128 .B \-i iso_image
129 Specifies the path of the iso9660 image that we wish to examine.
130 The options
131 .B \-i
132 and
133 .BI dev= target
134 are mutual exclusive.
135 .TP
136 .BI \-ignore\-error
137 Ignore errors.
138 The commands
139 by default aborts on several errors, such as read errors. With this option in effect,
140 the commands try to continue.
141 Use with care.
142 .TP
143 .BI dev= target
144 Sets the SCSI target for the drive, see notes above.
145 A typical device specification is
146 .BI dev= 6,0
147 \&.
148 If a filename must be provided together with the numerical target
149 specification, the filename is implementation specific.
150 The correct filename in this case can be found in the system specific
151 manuals of the target operating system.
152 On a
153 .I FreeBSD
154 system without
155 .I CAM
156 support, you need to use the control device (e.g.
157 .IR /dev/rcd0.ctl ).
158 A correct device specification in this case may be
159 .BI dev= /dev/rcd0.ctl:@
160 \&.
161 .sp
162 On Linux, drives connected to a parallel port adapter are mapped
163 to a virtual SCSI bus. Different adapters are mapped to different
164 targets on this virtual SCSI bus.
165 .sp
166 If no
167 .I dev
168 option is present, the program
169 will try to get the device from the
170 .B CDR_DEVICE
171 environment.
172 .sp
173 If the argument to the
174 .B dev=
175 option does not contain the characters ',', '/', '@' or ':',
176 it is interpreted as an label name that may be found in the file
177 /etc/default/cdrecord (see FILES section).
178 .sp
179 The options
180 .B \-i
181 and
182 .BI dev= target
183 are mutual exclusive.
184 .TP
185 .B \-debug
186 Print additional debug information. This enables e.g. printing
187 of all directory entries if a file has more than one directory entry
188 and printing of more information from the primary volume descriptor.
189 .sp
190 In debug mode, Rock Ridge information is parsed with
191 .B \-R
192 even if it is not standard compliant.
193 .TP
194 .B \-l
195 generate output as if a 'ls -lR' command had been run on the iso9660 image.
196 You should not use the
197 .B -f
198 image with the
199 .B -l
200 option.
201 .sp
202 The numbers in square brackets are the starting sector number as decimal
203 number (based on 2048 bytes per sector) and the iso9660 directory flags
204 as hexadecimal number as follows:
205 .RS
206 .TP
207 .B 0x00
208 A plain file (not really a flag).
209 .TP
210 .B 0x01
211 Hide the file name from directory listings.
212 .TP
213 .B 0x02
214 A directory.
215 .TP
216 .B 0x04
217 An associated file (e.g. an Apple resource fork).
218 .TP
219 .B 0x08
220 Record format in extended attributes is used.
221 .TP
222 .B 0x10
223 No read/execute permission in extended attributes.
224 .TP
225 .B 0x20
226 reserved
227 .TP
228 .B 0x40
229 reserved
230 .TP
231 .B 0x80
232 Not the final entry of a multi extent file.
233 .RE
234 .TP
235 .B \-N sector
236 Quick hack to help examine single session disc files that are to be written to
237 a multi-session disc. The sector number specified is the sector number at
238 which the iso9660 image should be written when send to the cd-writer. Not
239 used for the first session on the disc.
240 .TP
241 .B \-p
242 Print path table information.
243 .TP
244 .B \-R
245 Extract information from Rock Ridge extensions (if present) for permissions,
246 file names and ownerships.
247 .TP
248 .B \-s
249 Print file size info in multiples of sector size (2048 bytes).
250 .TP
251 .B \-J
252 Extract information from Joliet extensions (if present) for file names.
253 .TP
254 .B \-j charset
255 Convert Joliet file names (if present) to the supplied charset. See
256 .BR mkisofs (8)
257 for details.
258 .TP
259 .B \-T sector
260 Quick hack to help examine multi-session images that have already been burned
261 to a multi-session disc. The sector number specified is the sector number for
262 the start of the session we wish to display.
263 .TP
264 .B \-X
265 Extract files from the image and put them into the filesystem.
266 If the
267 .B \-find
268 option is not used, all files are extracted.
269 .sp
270 The
271 .B isoinfo
272 program supports to extract all files, even multi extent
273 files (files > 4 GB).
274 .sp
275 Before extracting files using the
276 .B \-X
277 option, it is recommended to change the current directory
278 to an empty directory in order to prevent to clobber existing files.
279 .TP
280 .B \-x pathname
281 Extract specified file to stdout.
282 The
283 .B pathname
284 needs to start with a slash ('/') and in case of iso9660 names, must match
285 the full pathname of the file including the version number (usually ';1').
286 If the option
287 .B \-R
288 has been specified and the filesystem carries Rock Ridge attributes, the
289 .B pathname
290 must match the full Rock Ridge pathname of the file.
291
292 .SH ENVIRONMENT
293 .TP
294 .B CDR_DEVICE
295 This may either hold a device identifier that is suitable to the open
296 call of the SCSI transport library or a label in the file /etc/default/cdrecord.
297 .TP
298 .B RSH
299 If the
300 .B RSH
301 environment is present, the remote connection will not be created via
302 .BR rcmd (3)
303 but by calling the program pointed to by
304 .BR RSH .
305 Use e.g.
306 .BR RSH= /usr/bin/ssh
307 to create a secure shell connection.
308 .sp
309 Note that this forces the program
310 to create a pipe to the
311 .B rsh(1)
312 program and disallows the program
313 to directly access the network socket to the remote server.
314 This makes it impossible to set up performance parameters and slows down
315 the connection compared to a
316 .B root
317 initiated
318 .B rcmd(3)
319 connection.
320 .TP
321 .B RSCSI
322 If the
323 .B RSCSI
324 environment is present, the remote SCSI server will not be the program
325 .B /opt/schily/sbin/rscsi
326 but the program pointed to by
327 .BR RSCSI .
328 Note that the remote SCSI server program name will be ignored if you log in
329 using an account that has been created with a remote SCSI server program as
330 login shell.
331
332 .SH FILES
333 .TP
334 /etc/default/cdrecord
335 Default values can be set for the following options in /etc/default/cdrecord.
336 .RS
337 .TP
338 CDR_DEVICE
339 This may either hold a device identifier that is suitable to the open
340 call of the SCSI transport library or a label in the file /etc/default/cdrecord
341 that allows one to identify a specific drive on the system.
342 .TP
343 Any other label
344 is an identifier for a specific drive on the system.
345 Such an identifier may not contain the characters ',', '/', '@' or ':'.
346 .sp
347 Each line that follows a label contains a TAB separated list of items.
348 Currently, four items are recognized: the SCSI ID of the drive, the
349 default speed that should be used for this drive, the default FIFO size
350 that should be used for this drive and drive specific options. The values for
351 .I speed
352 and
353 .I fifosize
354 may be set to -1 to tell the program to use the global defaults.
355 The value for driveropts may be set to "" if no driveropts are used.
356 A typical line may look this way:
357 .sp
358 teac1= 0,5,0 4 8m ""
359 .sp
360 yamaha= 1,6,0 -1 -1 burnfree
361 .sp
362 This tells the program
363 that a drive named
364 .I teac1
365 is at scsibus 0, target 5, lun 0 and should be used with speed 4 and
366 a FIFO size of 8 MB.
367 A second drive may be found at scsibus 1, target 6, lun 0 and uses the
368 default speed and the default FIFO size.
369 .RE
370
371 .SH SEE ALSO
372 .BR mkisofs (8),
373 .BR cdrecord (1),
374 .BR readcd (1),
375 .BR scg (4),
376 .BR rcmd (3),
377 .BR ssh (1).
378
379 .SH BUGS
380 The user interface really sucks.
381
382 .SH AUTHOR
383 The author of the original sources (1993 .\|.\|. 1998) is
384 Eric Youngdale <[email protected]> or <[email protected]> is to blame
385 for these shoddy hacks.
386 .LP
387 J\*org Schilling wrote the SCSI transport library and its adaptation layer to
388 the programs and newer parts (starting from 1999) of the utilities, this makes
389 them
390 Copyright (C) 1999-2018 J\*org Schilling.
391 Patches to improve general usability would be gladly accepted.
392 .SH FUTURE IMPROVEMENTS
393 These utilities are really quick hacks, which are very useful for debugging
394 problems in mkisofs or in an iso9660 filesystem. In the long run, it would
395 be nice to have a daemon that would NFS export a iso9660 image.
396 .PP
397 The isoinfo program is probably the program that is of the most use to
398 the general user.
399
400 .SH "SOURCE DOWNLOAD"
401 The source code for
402 .BR devdump ,
403 .BR isodump ,
404 .BR isoinfo
405 and
406 .B isovfy
407 is included in the
408 .B schilytools
409 project and may be retrieved from the
410 .B schilytools
411 project at Codeberg at:
412 .LP
413 .B
414 https://codeberg.org/schilytools/schilytools/
415 .LP
416 The download directory is:
417 .LP
418 .B
419 https://codeberg.org/schilytools/schilytools/releases
420
421 .SH "INTERFACE STABILITY"
422 The interfaces provided by
423 .B readcd
424 are designed for long term stability.
425 As
426 .B readcd
427 depends on interfaces provided by the underlying operating system,
428 the stability of the interfaces offered by
429 .B readcd
430 depends on the interface stability of the OS interfaces.
431 Modified interfaces in the OS may enforce modified interfaces
432 in
433 .BR readcd .