1/ TO BUILD
autoreconf && ./configure && make (Linux)
autoheader259 && autoconf259 && ./configure && gmake (FreeBSD)
as root, to get rdup installed.
rdup depends on:
o Gmake for compilation
o Glib to build. Glib is the lowlevel C library of the
GTK project. Configure will check for this.
o Perl for the scripts.
o File::copy module for Perl
o rdup-snap-link depends on GNU cp to create the hardlinked directories
2/ DIFFERENCE WITH RSYNC
While rsync really works well, I wanted to have the ability to gzip
and/or encrypt the backupped files. rsync can not do that. That is why I
wrote rdup, which, with the help of some scripts will do that.
rdup is a utility inspired by rsync and the plan9 way of doing backups.
rdup it self does not backup anything, it only print a list of absolute
filenames to standard output. Auxilary scripts are needed that act on
this list and implement the backup strategy. This way rdup can be kept
lean and mean. Current the (stripped) rdup executable measures 28 KB (on
AMD64) and I don't expect that to increase much.
The manual page explains rdup's options and usage, see rdup(1). For an
introduction into making backups see rdup-backups(1).
The filelist as printed starts with the root of the filedump and then
decends into directories. This way all top level directories can be
created in sequence. If you process the files in the same order no magic
is needed to create directories that otherwise might be missing.
All files in this archive are copyrighted by Miek Gieben, unless stated
otherwise in the file itself.
(c) Miek Gieben, 2005-2008.
GPL, version 3, See the file LICENSE.