|
|
1.1 ! root 1: .TH cvftest 1 "10 Oct 1998" "dmsdos 0.9.2.0" "dmsdos CVF identification tool" ! 2: .SH NAME ! 3: cvftest \- dmsdos CVF identification tool ! 4: .SH SYNOPSIS ! 5: ! 6: .BI cvftest " filename [-v]" ! 7: ! 8: .SH DESCRIPTION ! 9: .I cvftest ! 10: tries to find out whether the file (or device) ! 11: .I filename ! 12: is a CVF. It does so by reading the first 512 bytes from ! 13: .I filename ! 14: and checking for certain strings. ! 15: ! 16: If ! 17: .I filename ! 18: is just a minus sign (-) the data are read from standard input. ! 19: ! 20: If the switch ! 21: .I -v ! 22: is given the result of the test is printed to standard output including ! 23: a description about what kind of CVF was detected. ! 24: ! 25: .SH RETURN VALUES ! 26: .I cvftest ! 27: returns zero (i.e. true) if ! 28: .I filename ! 29: has been recognized as a CVF. Otherwise it returns 1. A value >1 ! 30: indicates an error (e.g. ! 31: .I filename ! 32: does not exist or cannot be read). ! 33: ! 34: .SH BUGS ! 35: This program is so simple that it could be a shell script. But I'm not a shell ! 36: hacker, so it's C. ! 37: ! 38: The test is not idiot-proof. As it just checks for some magic values, it ! 39: might eventually misidentify other files as CVFs. These cases are supposed ! 40: to be extremely unlikely, though, and have never been reported yet. But if ! 41: you take a look at the source you easily find a way to fool the program :-) ! 42: ! 43: .SH SEE ALSO ! 44: ! 45: Refer to the dmsdos main documentation for further information.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.