cfv is a utility to both test and create .sfv (Simple File Verify), .csv, .crc, .md5(sfv style), md5sum, BSD md5, sha1sum, and .torrent checksum verification files. It also includes test-only support for .par and .par2 files. These files are commonly used to ensure the correct retrieval or storage of data.
nget is a commandline NNTP file grabber. It automatically pieces together multipart postings for easy retrieval, even substituting parts from multiple servers and newsgroups. It handles disconnects gracefully, resuming after the last part successfully downloaded, and caching of header data for quick access. It automatically downloads only as many par/par2 files as needed.
python-fchksum is a module used to find checksums of files (or stdin). It supports md5, crc32, cksum, bsd-style sum, and sysv-style sum. The advantage of using fchksum over the Python md5 and zlib(.crc32) modules is both ease of use and speed. You only need to tell it the filename, and the work is done by C code.
ssh-multiadd adds multiple ssh keys to the ssh authentication agent. These may use the same passphrase. When run without arguments, it adds $HOME/.ssh/identity and $HOME/.ssh/id_dsa. Alternative file names can be given on the command line or in the configuration file. It uses ssh-askpass if necessary. Unlike ssh-add, if any of the keys use the same passphrase, you will only need to enter each unique passphrase once, and keys that are already added will not be prompted for again.
pyprof is a wrapper around python's profile module for easily profiling python scripts without having to specify the whole path to them if they are in $PATH. It has command line arg and rc file configurable behaviors. If pyprof_auto is used, any python code can be profiled merely by setting the $PYPROF environment variable.
This program examines the current buffer and determines the indent style in use, then sets vim tabstop/shiftwidth/etc to work correctly with that style, and creates a syntax match to highlight any indentation in the file that does not match the selected style. It can be set up to auto-detect when opening files.
GVidChanger-minimal (gvidm) is a GTK app to quickly and easily change video resolutions in X. Running it will pop up a list of available modes; upon choosing a mode or cancelling, it exits. If you are running dual or multi-head displays, it will give you a list of screens so you can select the appropriate one. You can also specify on the command line a mode to switch to immediately, or a list of modes to choose from.
cvs-importer automates the task of importing all past versions of an existing project into CVS or Subversion, including automatically removing generated files, creating .cvsignore files/svn:ignore properties, and tagging each version. Thus, you can gain some of the advantages of scm for the older versions that weren't actually developed in cvs/svn, by having all the changes in the history.
> % Python is already included on
> % distros.
> I've never seen python installed on
> any machines that *I* use.
I'm not talking about whatever minimalistic stuff you have on your machines, but the average install.
> Really? So reading byte by byte and
> calling CRC32 functions on that is
> &quot;not slower&quot; than for example,
> mmap()'ing the file and running CRC32 on
> the entire file? Oh, did I mention we
> are using Python here?
I know you love trolling timecop, but if you would just look, you would see that in fact it does not read byte by byte.
It either: a) uses the fchksum C module to get crc for the entire file in one call, b) mmaps the file and uses zlib C module to get crc of entire file in one call, or c) if neither mmap or fchksum is available (maybe some weird arch without mmap) it will read in 64K chunks and crc them. So yes, it is in fact not slower _at all_.
> Python? Get real. Nobody used Python
> for anything other than random hacks or
> things that nobody will ever want to
And C is just _so_ much more maintainable.. riiiight.
> Hello, I remember seeing at least 3
> other SFV-related projects on
> sourceforge/freshmeat and none of them
> used python. What the hell, now warez
> kiddies must install python to get
> their checksums done?
Python is already included on most/all distros.
> And I just wonder the performance of
> checksumming a 650mb iso with
> something written in a VB-like
> interpreted language.
If you had spent 5 seconds to check
instead of just "wondering" (aka
trolling), you would have found out that
the checksumming is done in C modules
that are called by cfv.
> Let's pick the right language for the
> job, eh?
Say, how many of those "at least 3
other" projects included support for
csv, md5, or par files? Zero? Maybe I
did pick the right language for the job,