diff options
| -rw-r--r-- | doc/todo/Use_bitcoin-mining_ASICs_for_hashing__63__.mdwn | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/todo/Use_bitcoin-mining_ASICs_for_hashing__63__.mdwn b/doc/todo/Use_bitcoin-mining_ASICs_for_hashing__63__.mdwn index 76c8796a3..076f3ce4a 100644 --- a/doc/todo/Use_bitcoin-mining_ASICs_for_hashing__63__.mdwn +++ b/doc/todo/Use_bitcoin-mining_ASICs_for_hashing__63__.mdwn @@ -8,3 +8,9 @@ I got the idea, because I have two RaspberryPis here: - another one runs 2 old-ish ASIC miners. They are just barely "profitable" right now, so in a few months they will be obsolete Both devices to some kind of `SHA256`. I have a feeling this is either extremely easy or extremely complicated to do… :) + +> git-annex uses binaries such as `sha256sum` for hashing large files (large is +> currently hardcoded as bigger than 1MB). If you insert a binary with the same +> interface as `sha256sum` into your `$PATH`, git-annex will automatically use +> it. If you want to use ASIC hashing even for small files, you need to tweak +> `Backend/Hash.hs`. --[[HelmutGrohne]] |