home *** CD-ROM | disk | FTP | other *** search
- SUM 1.1 by Bill Dimm
-
- USAGE:
- sum [options] file1 [file2]
-
- DESCRIPTION:
-
- Sum generates checksums for a file, and will find the number
- of readable bytes in the file. This information can be stored in a
- chksum file so that the integrity of a file can be determined at a
- later date. This is especially useful when you want to verify that a
- disk crash recovery was successful. A chksum file will be 9 to 13 bytes
- long depending on the number of checksums generated. Sum does
- everything the Unix version does, and more, but the checksums that it
- generates are not intended to be compatible with those generated by Unix.
- Options:
-
- -r Use the alternate checksum method instead of the default.
-
- -b Use both checksum methods.
-
- -s Show the contents of a chksum file (chksum files are compressed)
- The checksum methods to use will be determined from the
- chksum file file1.
-
- -o Output to a chksum file (in addition to the screen). File2
- will be the chksum file.
-
- -v Verify that the checksums (and size) of file1 match those
- stored in the chksum file file2. The checksum methods to use
- will be determined by the contents of file2.
-
- The options -s -o and -v are mutually exclusive, and cannot be
- specified together.
-
- IMPROVEMENTS:
-
- Since version 1.0, sum has been recompiled with Lattice 5.02
- to make it smaller.
-
- EXAMPLES:
-
- Print both chksums for the file sample.doc:
- sum -b df0:sample.doc
-
- Create a chksum file for sample.doc (using both checksum methods):
- sum -o -b df0:sample.doc df1:chksums/sample.doc.chk
-
- Later verify that the file sample.doc file is still in tact:
- sum -v df0:sample.doc df1:chksums/sample.doc.chk
-
- Diskplay contents of chksum file:
- sum -s df1:chksums/sample.doc.chk
-