A common problem is that one has files around that we must absolutely
get rid off. For example checked out version that are safely stored
in archived, family fotos triply back-upped on DVD's , test files
that clog up backups. I once hacked directory with bikini contest
models. A series with a young model doesn't show up on the website.
She was 17 at the time, so it was deleted, but I have this series.
The last photo was naughty, it showed a nipple! CHILDPORN!
If a secret service found this photo, all my computers would be
confiscated and later returned by judge's orders to me, three
years later, with apologies. We cannot have that.

My proposal is to have a database with <file length, checksum).
If you discover that the scanned file is no good after two weeks
of lingering you do

helhol janwolkers.tiff

From time to time we run 'helhol --clean ' to get rid of all files everywhere.

Finesse are to be added.
Equate checked out files without version mark to a file with no
version mark.
helhol all files of all versions from the RCS archive to the database,
helhol RCS

helhol nokia_old.tar

The CRC polynomial could be secret. In this way nor the names, nor the
crc leaves a clue what file are originally deleted.
For a 64 bit polynomial expect a 1 in 10^9 clash for files that are
the same size.

What would you think?
A first version would be easy, specially if you have a B-tree package that stores on disk.

Groetjes Albert
--
Don't praise the day before the evening. One swallow doesn't make spring.
You must not say "hey" before you have crossed the bridge. Don't sell the
hide of the bear until you shot it. Better one bird in the hand than ten in
the air. First gain is a cat purring. - the Wise from Antrim -

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)