This directory contains the "backup" program (in Perl) and some
associated "helper" programs/scripts (generally in Perl and/or shell).

They're not (yet) written for general distribution (I still consider
them Alpha/Beta code - though they're quite "good enough" that I use
them on a fairly regular basis for the quite important task of handing
most of my routine backups of my laptop).  Some of the Alpha/Beta
characteristics - except for "helper" programs, pretty much all of the
configuration stuff for the backup program is in the script itself
(ought to go in a separate file, but I haven't yet decided where -
probably something like /usr/local/etc/<program_name>.conf ... and
"backup" is probably yet a bit too generic a name for the program).
There are also things in the script that are highly specific to my
system (e.g.  pathnames for the program and helper scripts and certain
specific hardware) that would need to have much more suitable defaults
for more general distribution.

They are generally best viewed with tabstops set every 4 characters (e.g. vi
:se tabstop=4

It's been a while (since 2003-09-25) since I made any particularly
substantial changes to the backup program itself:

RCS file: RCS/backup,v
Working file: backup
head: 1.23
branch:
locks: strict
access list:
symbolic names:
keyword substitution: kv
total revisions: 23;	selected revisions: 23
description:
backup program
----------------------------
revision 1.23
date: 2004/07/12 02:23:22;  author: michael;  state: Exp;  lines: +5 -5
corrections/tweaks
----------------------------
revision 1.22
date: 2004/07/12 01:34:40;  author: michael;  state: Exp;  lines: +31 -24
enhanced indexing and added backup of additional filesystem types
----------------------------
revision 1.21
date: 2004/03/25 04:52:29;  author: michael;  state: Exp;  lines: +1 -1
corrected comment typo
----------------------------
revision 1.20
date: 2003/09/25 06:40:35;  author: michael;  state: Exp;  lines: +65 -53

Apologies in advance if it's not the most beautiful code in the world
(especially the Perl code - which also hasn't been peer reviewed by
anyone yet).  I do tend to, however, write pretty good solid code (e.g.
pretty well checking return codes, errors, logic of all the things that
may happen, and hopefully pretty well covering all scenarios so
hopefully the program pretty much always does something reasonable, even
if something unreasonable or relatively unexpected occurs, including
also pretty well avoiding security errors).
