version 1, including all changes.
.
| Rev |
Author |
# |
Line |
| 1 |
JohnMcPherson |
1 |
!!NAME |
| |
|
2 |
devdump, isoinfo, isovfy, isodump - Utility programs for dumping and verifying iso9660 images. |
| |
|
3 |
|
| |
|
4 |
!!SYNOPSIS |
| |
|
5 |
__devdump __ ''isoimage'' |
| |
|
6 |
|
| |
|
7 |
__isodump __ ''isoimage'' |
| |
|
8 |
|
| |
|
9 |
__isoinfo__ ~[ __-d__ ] ~[ __-h__ ] ~[ __-R__ ] ~[ __-J__ ] ~[ __-j__ ''charset'' ] ~[ __-f__ ] ~[ __-l__ ] ~[ __-p__ ] ~[ __-T__ ''sector'' ] ~[ __-N__ ''sector'' ] ~[ __-i__ ''isoimage'' ] ~[ __-x__ ''path'' ] |
| |
|
10 |
|
| |
|
11 |
__isovfy __ ''isoimage'' |
| |
|
12 |
|
| |
|
13 |
!!DESCRIPTION |
| |
|
14 |
__devdump__ is a crude utility to interactively display the contents of device or filesystem images. The initial screen is a display of the first 256 bytes of the first 2048 byte sector. The commands are the same as with __isodump__ . |
| |
|
15 |
|
| |
|
16 |
__isodump__ is a crude utility to interactively display the contents of iso9660 images in order to verify directory integrity. The initial screen is a display of the first part of the root directory, and the prompt shows you the extent number and offset in the extent. |
| |
|
17 |
|
| |
|
18 |
You can use the 'a' and 'b' commands to move backwards and forwards within the image. The 'g' command allows you to goto an arbitrary extent, and the 'f' command specifies a search string to be used. The '+' command searches forward for the next instance of the search string, and the 'q' command exits __devdump__ or __isodump__ . |
| |
|
19 |
|
| |
|
20 |
|
| |
|
21 |
__isoinfo__ is a utility to perform directory like listings of iso9660 images. |
| |
|
22 |
|
| |
|
23 |
__isovfy__ is a utility to verify the integrity of an iso9660 image. Most of the tests in __isovfy__ were added after bugs were discovered in early versions of __mkisofs.__ It isn't all that clear how useful this is anymore, but it doesn't hurt to have this around. |
| |
|
24 |
|
| |
|
25 |
|
| |
|
26 |
!!OPTIONS |
| |
|
27 |
Only the __isoinfo__ program has any command line options. These are: |
| |
|
28 |
;__-h__ : print a summary of all options. |
| |
|
29 |
;__-d__ : Print information from the primary volume descriptor (PVD) of the iso9660 image. This includes information about Rock Ridge and Joliet extensions if present. |
| |
|
30 |
;__-f__ : generate output as if a 'find . -print' command had been run on the iso9660 image. You should not use the __-l__ image with the __-f__ option. |
| |
|
31 |
;__-i iso_image__ : Specifies the path of the iso9660 image that we wish to examine. |
| |
|
32 |
;__-l__ : generate output as if a 'ls -lR' command had been run on the iso9660 image. You should not use the __-f__ image with the __-l__ option. |
| |
|
33 |
;__-N sector__ : Quick hack to help examine single session disc files that are to be written to a multi-session disc. The sector number specified is the sector number at which the iso9660 image should be written when send to the cd-writer. Not used for the first session on the disc. |
| |
|
34 |
;__-p__ : Print path table information. |
| |
|
35 |
;__-R__ : Extract information from Rock Ridge extensions (if present) for permissions, file names and ownerships. |
| |
|
36 |
;__-J__ : Extract information from Joliet extensions (if present) for file names. |
| |
|
37 |
;__-j charset__ : Convert Joliet file names (if present) to the supplied charset. See mkisofs(8) for details. |
| |
|
38 |
;__-T sector__ : Quick hack to help examine multi-session images that have already been burned to a multi-session disc. The sector number specified is the sector number for the start of the session we wish to display. |
| |
|
39 |
;__-x pathname__ : Extract specified file to stdout. |
| |
|
40 |
|
| |
|
41 |
!!AUTHOR |
| |
|
42 |
Eric Youngdale <ericy*gnu.ai.mit.edu> or <eric*andante.jic.com> is to blame for these shoddy hacks. Patches to improve general usability would be gladly accepted. |
| |
|
43 |
|
| |
|
44 |
!!BUGS |
| |
|
45 |
The user interface really sucks. |
| |
|
46 |
|
| |
|
47 |
!!FUTURE IMPROVEMENTS |
| |
|
48 |
These utilities are really quick hacks, which are very useful for debugging problems in mkisofs or in an iso9660 filesystem. In the long run, it would be nice to have a daemon that would NFS export a iso9660 image. |
| |
|
49 |
|
| |
|
50 |
The isoinfo program is probably the program that is of the most use to the general user. |
| |
|
51 |
|
| |
|
52 |
!!AVAILABILITY |
| |
|
53 |
These utilities come with the mkisofs package, and the primary ftp site is tsx-11.mit.edu in /pub/linux/BETA/cdrom/mkisofs and many other mirror sites. Despite the name, the software is not beta. |
| |
|
54 |
|
| |
|
55 |
!!SEE ALSO |
| |
|
56 |
mkisofs(8) |
| |
|
57 |
|
| |
|
58 |
|
| |
|
59 |
|
| |
|
60 |
---- |
| |
|
61 |
!!User Submitted Notes |
| |
|
62 |
|
| |
|
63 |
As the 'bugs' section above says, the interactive interface really sucks. |
| |
|
64 |
|
| |
|
65 |
I've found that the easiest way to examine and get files out of an ISO image is to generate a file listing: |
| |
|
66 |
<verbatim> |
| |
|
67 |
isoinfo -J -f -i image-file.iso > filelist.txt |
| |
|
68 |
</verbatim> |
| |
|
69 |
*-J for Joliet filename extensions -- use -R if you use Rock Ridge filename extensions instead |
| |
|
70 |
* -f for a file listing like the output of find(1) |
| |
|
71 |
and then grab the files you want out of the <tt>filelist.txt</tt>, remembering that isoinfo writes to stdout(3): |
| |
|
72 |
<verbatim> |
| |
|
73 |
isoinfo -J -i image-file.iso -x /file/from/filelist > newfilename |
| |
|
74 |
</verbatim> |
