AutoRPM is a program that can do any combination of the following: mirror RPMs from an FTP site, keep installed RPMs consistent with an FTP site or local directory and keep installed RPMs in a cluster or network of systems consistent. It is highly flexible and contains a fully command-line driven interactive install mode (for installing RPMs from the queue or for installing RPMs from your system interactively). It also handles recursive dependencies, multiple versions of the same RPM, the same RPM with multiple architectures, and more. It does some of the same tasks as up2date and AutoUpdate.
Payload Delivery Vehicle (PDV) is a program that builds an executable that contains a complete package (e.g. and RPM, System V package or tar file) and the commands required to install it. When the executable is run it will extract the payload (the package) and then execute another command (such as rpm -i, pkgadd -d etc.). The big advantage to this is that a developer can hand a user a single file to be executed - the end user does not need to know how to extract the package or get it installed.
ImageBackup is a fully automatic incremental backup system for digital pictures. It will create backup CDs, one at a time, until all images have been backed up. You than then run the program regularly and it will keep gathering images until another disc is full. Once a disc is full, it can use AutoScrapbook to create Web-based index files, automatically generate an ISO image, and reset the staging area. Once an image has been stored in a backup ISO image, it will not be backed up again. Any new images, regardless of where they are mixed into your directory structure, will be added to backups when necessary.
newsyslog is a faithful Perl rewrite of the MIT newsyslog utility, with a number of features taken from the FreeBSD and NetBSD variants of newsyslog. It archives log files based on size, date or interval, and can optionally compress archives with gzip or bzip2. Complete documentation is available via "perldoc newsyslog.pl".
fs2svn takes a sequence of archive folders (snapshots or historical backups of a project) and makes a new Subversion repository, preserving their revision history. Each top-level folder creates one revision, which is backdated to its most recent file's modification date. Additions, changes, and deletions between one folder and the next are all recorded in the repository, and the efficient diff-based storage saves disk space over the original full or incremental backups.