FreeCalypso > hg > freecalypso-sw
comparison ffstools/Usage @ 251:63cd64625597
ffstools/Usage write-up done
author | Michael Spacefalcon <msokolov@ivan.Harhan.ORG> |
---|---|
date | Sat, 01 Feb 2014 21:47:52 +0000 |
parents | 3d88461d8284 |
children |
comparison
equal
deleted
inserted
replaced
250:3d88461d8284 | 251:63cd64625597 |
---|---|
47 | 47 |
48 The next argument after the FFS organization for tiffs (or after the image | 48 The next argument after the FFS organization for tiffs (or after the image |
49 filename for mokoffs/pirffs) is the command (or operation) to be performed. | 49 filename for mokoffs/pirffs) is the command (or operation) to be performed. |
50 The following tiffs commands are currently available: | 50 The following tiffs commands are currently available: |
51 | 51 |
52 General information commands | |
53 ============================ | |
54 | |
55 These commands display general or summary information about the FFS image: | |
56 | |
57 tiffs <...> blkhdr | |
58 | |
59 This command displays the basic information contained in the header of each | |
60 flash erase block comprising the FFS image. | |
61 | |
62 tiffs <...> fsinfo | |
63 | |
64 This command displays some general information about the file system. | |
65 | |
52 Standard listing/extraction commands | 66 Standard listing/extraction commands |
53 ==================================== | 67 ==================================== |
54 | 68 |
55 These commands list or extract the normally-visible content of the FFS, i.e., | 69 These commands list or extract the normally-visible content of the FFS, i.e., |
56 the content which is visible when the FFS is "mounted" normally, and which the | 70 the content which is visible when the FFS is "mounted" normally, and which the |
57 FFS promises to preserve - as opposed to deleted or overwritten content. | 71 FFS promises to preserve - as opposed to deleted or overwritten content. |
58 | 72 |
59 ls [-v[v]] [pathname...] | 73 tiffs <...> ls [-v[v]] [pathname...] |
60 | 74 |
61 Tiffs ls without additional arguments yields a listing of the complete FFS | 75 Tiffs ls without additional arguments yields a listing of the complete FFS |
62 directory tree, akin to tar tv. Example output fragment: | 76 directory tree, akin to tar tv. Example output fragment: |
63 | 77 |
64 fr 4096 /.journal | 78 fr 4096 /.journal |
80 data chunk, relative to the beginning of the FFS image. | 94 data chunk, relative to the beginning of the FFS image. |
81 | 95 |
82 Tiffs ls with a pathname argument yields information about the specified FFS | 96 Tiffs ls with a pathname argument yields information about the specified FFS |
83 object; -v and -vv options act as already described, but are arguably more | 97 object; -v and -vv options act as already described, but are arguably more |
84 useful when listing single files. | 98 useful when listing single files. |
99 | |
100 tiffs <...> cat [-v|-h] pathname | |
101 | |
102 Just like the standard Unix cat(1) command, but cat'ing files from the FFS image | |
103 under study. The non-standard -h option means hex dump - it is handy because | |
104 almost all files in TI's GSM device FFS are binary, rather than ASCII. | |
105 | |
106 tiffs <...> xtr dest-dir | |
107 | |
108 This command extracts the complete content of the FFS into your ordinary Unix | |
109 file system. The sole argument is the local directory into which the root of | |
110 the GSM device FFS should be extracted. | |
111 | |
112 Forensic analysis commands | |
113 ========================== | |
114 | |
115 Unlike the "standard" listing/extraction commands which present TIFFS as a | |
116 "normal" Unix file system, using the "forensic" commands effectively requires | |
117 that the operator understands how TIFFS works, in particular, what an inode is | |
118 in TIFFS. | |
119 | |
120 tiffs <...> lsino [-v[v]] | |
121 | |
122 This command lists the FFS inode array from first to last; this listing order | |
123 will normally correspond to the forward chronological order of object creation. | |
124 -v and -vv options add verbosity. | |
125 | |
126 '.' in the object type column means segment, '~' means a deleted object. The | |
127 lsino command only lists the inode array, and does not try to recover the | |
128 original type of deleted/overwritten objects from the journal or other clues. | |
129 The program attempts to recover the pathname of each inode, but because such | |
130 reverse mapping from inodes to pathnames is not an operation which TIFFS was | |
131 properly designed to support, and the pathname recovery algorithm in this TIFFS | |
132 IVA tool is made as generic as possible (doesn't look at the object types), the | |
133 lsino listing will occasionally include some bogus pathnames. Once again, it | |
134 is expected that the operator knows what s/he is doing when using these forensic | |
135 commands. | |
136 | |
137 tiffs <...> lsino [-v[v]] [-f] ino... | |
138 | |
139 This command works just like ls with an explicit pathname argument, but takes | |
140 one or more inode numbers instead. The -f option matters only if the requested | |
141 inode is in the deleted/overwritten state; it tells the lsino command to assume | |
142 that the object is/was the head inode of a file; -vf and -vvf combinations are | |
143 particularly useful. | |
144 | |
145 tiffs <...> catino [-v|-h] ino | |
146 | |
147 Just like regular cat, but takes an inode number instead of a pathname. Can be | |
148 used to cat the old content of deleted or overwritten files. |