blog: Update linux binary tarball shasums

I just accidentally the binary release.
blog: v0.11.0 release
zlib: allow passing options to convenience methods
deps: upgrade libuv to c43e851
src: fix Persistent<> deprecation warning

Pass the Isolate to Persistent<Function>::New(). Fixes the following
warning:

  ../../src/node.cc: In function ‘v8::Handle<v8::Value>
  node::UsingDomains(const v8::Arguments&)’:
  ../../src/node.cc:921: warning: ‘New’ is deprecated
  declared at ../../deps/v8/include/v8.h:4438)
crypto: Pass options to ctor calls
lint: add isolate, remove semicolon
build: allow building with dtrace on osx
dtrace: pass more arguments to probes

OSX and other DTrace implementations don't support dereferencing
structs in probes. To accomodate that pass members from the struct as
arguments so that DTrace is useful on those systems.
dtrace: actually use the _handle.fd value

When using the DTrace/systemtap subsystems it would be helpful to
actually have an fd associated with the requests and responses.
dtrace: check if _handle property is set

Check that _handle is an object before trying to read its `fd`
property, avoids bogus values.
repl: isSyntaxError() catches "strict mode" errors

Closes #5178.
repl: use more readable RegExp syntax for spaces

This is just a cosmetic change really, nothing major.
buffer: change output of Buffer.prototype.toJSON()

Expand the JSON representation of Buffer to include type information
so that it can be deserialized in JSON.parse() without context.

Fixes #5110.
Fixes #5143.
querystring: Removing unnecessary binding

Binding of `http_parser` in querystring isn't used anywhere and should
be removed.
doc: typo fixes
etw: update prototypes to match dtrace provider

The DTrace probes were updated to accomodate platforms that can't
handle structs, update the prototypes for ETW but it's not necessary
to do anything with the new arguments as it's redundant information.
Ensure BAD domain example actually uses domain
tls: Destroy socket when encrypted side closes

The v0.8 Stream.pipe() method automatically destroyed the destination
stream whenever the src stream closed.  However, this caused a lot of
problems, and was removed by popular demand.  (Many userland modules
still have a no-op destroy() method just because of this.) It was also
very hazardous because this would be done even if { end: false } was
passed in the pipe options.

In v0.10, we decided that the 'close' event and destroy() method are
application-specific, and pipe() doesn't automatically call destroy().
However, TLS actually depended (silently) on this behavior.  So, in this
case, we should just go ahead and destroy the thing when close happens.

Closes #5145
test: test intended code-paths

The tests did not agree with the test comments. Tests first and second
were both testing the !state.reading case. Now second tests the
state.reading && state.length case.

Fixes joyent/node#5183