commit a8ed769271d099fc3a0dd4e85c867ec512aef97b
parent f08d3792bd0dc9154b8a0e09b339d9d80845b71f
Author: sin <sin@2f30.org>
Date: Thu, 7 Mar 2019 17:20:44 +0000
Rename bak to repo in README
Diffstat:
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/README b/README
@@ -2,15 +2,15 @@ dedup is a simple data deduplication program.
To use dedup you have to first initialize the repository.
- dedup -r ~/bak -i
+ dedup -r ~/repo -i
dedup only handles a single file at a time, so using tar is advised.
For example, to dedup a directory file you can invoke dedup as
follows:
- tar -c ~/dir | dedup -r ~/bak -m "$(date)"
+ tar -c ~/dir | dedup -r ~/repo -m "$(date)"
-This will create .{snapshots,store} files in the ~/bak
+This will create .{snapshots,store} files in the ~/repo
directory. The store file contains all the unique blocks. The
snapshots file contains all the revisions of files that have been
deduplicated. Each revision is identified by its SHA256 hash. The
@@ -18,13 +18,13 @@ cache file is only used to speed up block hash comparison.
To list all known revisions run:
- dedup -r ~/bak -l
+ dedup -r ~/repo -l
You will get a list of hashes. Each hash corresponds to a single file
(in this case, a tar archive).
To extract a file from the deduplicated store run:
- dedup -r ~/bak -e <hash> > dir.tar
+ dedup -r ~/repo -e <hash> > dir.tar
Dedup depends on liblz4 and openssl.
