add a benchmark for our hash function

Fix docker $ipfs_data mount path in README

blocks: Don't re-Put blocks we already have

Commit 1192be19 tried to do this, but
had a simple mistake. Functions returning `bool, error` pretty much
never return `true, anError`, so that branch was never taken.

Also fix the partial sentence in the

core/commands: pin ls: display types by default

If you want to get only the hashes (i.e. the previous behaviour), you can use
the `--quiet` flag.

let wantlist command show other peers wantlists

only warn about io.EOF from mux.ReaderHeaders (fixes #1143)

This patch update fixes various issues, in particular:
- windows support (0.3.0 had broken it)
- commandline parses spaces correctly.

* much improved commandline parsing by @AtnNn
* improved dockerfile by @luzifer
* add cmd cleanup by @wking
* fix flatfs windows support by @tv42 and @gatesvp
* test case improvements by @chriscool
* ipns resolution timeout bug fix by @whyrusleeping
* new cluster tests with iptb by @whyrusleeping
* fix log callstack printing bug by @whyrusleeping
* document bash completiong by @dylanPowers

Improve command line parsing

Improve Dockerfile

core/commands/add: Change add() to only accept a single reader

Fix flatfs on Windows

refactored ipns records to point to paths

Also changed the ipns dns resolution to use the "dnslink" format

Fix iptb tests

License: MIT
Signed-off-by: Christian Couder <chriscool@tuxfamily.org>

License: MIT
Signed-off-by: Christian Couder <chriscool@tuxfamily.org>

fixes #1108

Mention correct key size in help for init

Add timeout to ipns resolution at startup

* Added VOLUME to enable users to keep a state of the repo outside the container
* Added ipfs user to let ipfs run as a normal user and not as root
* Set IPFS_PATH to push IPFS to use the exposed dir
* Improved start script to be more verbose about errors

I'm so sick of this absolute crap. It goes wrong all the time.
I want to get off godeps soon. But for now, let's **please**
setup a test on travis that exercises all sorts of godep things
to avoid merging anything that will break.

Maybe we can fail the build if any library is NOT vendored.

Catch up with core/commands/add.go.

The change to an array of readers comes from e096060b
(refactor(core/commands2/add) split loop, 2014-11-06), where it's used
to setup readers for each path in the argument list.  However, since
6faeee83 (cmds2/add: temp fix for -r. horrible hack, 2014-11-11) the
argument looping moved outside of add() and into Run(), so we can drop
the multiple-reader support from add().

Adding a file can create multiple nodes (e.g. the splitter can chunk
the file into several blocks), but:

1. we were only appending a single node per reader to our returned
   list, and
2. we are only using the final node in that returned list,

so this commit also adjusts add() to return a single node reference
instead on an array of nodes.