Restructure, and rewrite substantial partsHEADmasterdevel

A notable problem (to me) with the former version was, that upon simple
movements in the source file tree, these would in general cause
duplicated data in the backup forest.  This problem has been resolved
by essentially tracking file movements, using hard links.

Also, the code has been divided into several different files, extranous
code removed, the organization of remote code execution simplified.

In the process of simplification, all parts requiring direct interaction
of the user with the program have been replaced.  In most cases, this
means that the program now just terminates with an error instead of
allowing the user to confirm deletion of an unexpected (remnant) file.
This may be considered a drawback, but actually these interactive
options were anyways suboptimal solutions in most cases - where they
occured, which was due to remnant files of aborted or failed former
backups.

In general, there have been a lot of changes.  Which are not thoroughly
documented here.  Since there is often no strong relation to the old
code, this is not deemed necessary, as the in-code documentation is
expected to be of sufficient help.

Also, there has been added a little general documentation in the README
and particularly the NOTES file.

It is to be noted that this new version is far from sophisticated.  It
has been tested with and is in use for real data, however lacks a lot of
convenience.  In particular, if a backup fails unexpectedly, the next
backup will in the very most cases loudly fail without manual
intervention.  Also, the program is not able to continue the growth of a
backup tree built with former versions of this program, by itself.  This
can however be arranged by hand.

0 files changed, 0 insertions, 0 deletions