+ The tests should pass. If they don't pass for you, stop here and
+ send an email to bup-list@googlegroups.com. Though if there are
+ symbolic links along the current working directory path, the tests
+ may fail. Running something like this before "make test" should
+ sidestep the problem:
+
+ cd "$(/bin/pwd)"
+
+ - You can install bup via "make install", and override the default
+ destination with DESTDIR and PREFIX.
+
+ Files are normally installed to "$DESTDIR/$PREFIX" where DESTDIR is
+ empty by default, and PREFIX is set to /usr. So if you wanted to
+ install bup to /opt/bup, you might do something like this:
+
+ make install DESTDIR=/opt/bup PREFIX=''
+
+ - The Python executable that bup will use is chosen by ./configure,
+ which will search for a reasonable version unless PYTHON is set in
+ the environment, in which case, bup will use that path. You can
+ see which Python executable was chosen by looking at the
+ configure output, or examining cmd/python-cmd.sh, and you can
+ change the selection by re-running ./configure.
+
+From binary packages
+--------------------
+
+Binary packages of bup are known to be built for the following OSes:
+
+ - Debian:
+ http://packages.debian.org/search?searchon=names&keywords=bup
+ - Ubuntu:
+ http://packages.ubuntu.com/search?searchon=names&keywords=bup
+ - pkgsrc (NetBSD, Dragonfly, and others)
+ http://pkgsrc.se/sysutils/bup
+ http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/sysutils/bup/
+ - Arch Linux:
+ https://www.archlinux.org/packages/?sort=&q=bup
+ - Fedora:
+ https://apps.fedoraproject.org/packages/bup
+
+
+Using bup
+---------
+
+ - Get help for any bup command:
+
+ bup help
+ bup help init
+ bup help index
+ bup help save
+ bup help restore
+ ...
+
+ - Initialize the default BUP_DIR (~/.bup):
+
+ bup init
+
+ - Make a local backup (-v or -vv will increase the verbosity):
+
+ bup index /etc
+ bup save -n local-etc /etc
+
+ - Restore a local backup to ./dest:
+
+ bup restore -C ./dest local-etc/latest/etc
+ ls -l dest/etc
+
+ - Look at how much disk space your backup took:
+
+ du -s ~/.bup
+
+ - Make another backup (which should be mostly identical to the last one;
+ notice that you don't have to *specify* that this backup is incremental,
+ it just saves space automatically):
+
+ bup index /etc
+ bup save -n local-etc /etc
+
+ - Look how little extra space your second backup used (on top of the first):
+
+ du -s ~/.bup
+
+ - Get a list of your previous backups:
+
+ bup ls local-etc
+
+ - Restore your first backup again:
+
+ bup restore -C ./dest-2 local-etc/2013-11-23-11195/etc
+
+ - Make a backup to a remote server which must already have the 'bup' command
+ somewhere in its PATH (see /etc/profile, etc/environment, ~/.profile, or
+ ~/.bashrc), and be accessible via ssh.
+ Make sure to replace SERVERNAME with the actual hostname of your server:
+
+ bup init -r SERVERNAME:path/to/remote-bup-dir
+ bup index /etc
+ bup save -r SERVERNAME:path/to/remote-bup-dir -n local-etc /etc
+
+ - Restore a backup from a remote server. (FAIL: unfortunately,
+ unlike "bup join", "bup restore" does not yet support remote
+ restores. See both "bup join" and "Things that are stupid" below.)
+
+ - Defend your backups from death rays (OK fine, more likely from the
+ occasional bad disk block). This writes parity information
+ (currently via par2) for all of the existing data so that bup may
+ be able to recover from some amount of repository corruption:
+
+ bup fsck -g
+
+ - Use split/join instead of index/save/restore. Try making a local
+ backup using tar: