Bump lvmsync protocol version and update receiver

cc6ad8b changed the lvmsync protocol from expressing offsets in chunks
to bytes, but the protocol version and receiver code weren't updated,
resulting in incorrectly applied diffs. This patch updates the receiver
to correctly handle the new protocol, and also increases the protocol
version so as not to confuse older clients.
Fix missing handshake in snapback files
Escape hyphens in VG name, too [Closes: GH#25]
Guard wait_thr for Ruby 1.8 compatibility [Closes: GH#30]
Merge pull request #28 from deriamis/vgcfgbackup

Variables vary even more than you might think...
Merge pull request #14 from AnchorCat/bump-lvmsync-protocol

Bump lvmsync protocol version and update receiver
Merge branch 'popen3-ruby1.9-fix' of git://github.com/AnchorCat/lvmsync

Conflicts:
	lib/lvm/vg_config.rb

(MP: A much better fix for the 1.8 incompatibilities I hacked around in
bf42ee8)
#
# It looks like you may be committing a merge.
# If this is not correct, please remove the file
#	.git/MERGE_HEAD
# and try again.

# Please enter the commit message for your changes. Lines starting
# with '#' will be ignored, and an empty message aborts the commit.
# On branch master
# Your branch is up-to-date with 'github/master'.
#
# All conflicts fixed but you are still merging.
#
# Changes to be committed:
#	modified:   lib/lvm/vg_config.rb
#
Merge pull request #26 from Informatic/master

Fix missing handshake in snapback files
Stylistic fix
Variables can contain plus and period too, apparently [Closes: GH#20]
Fix up test suite
Don't rely on having lvmsync in the path on local invocations
Fix htonq to actually be network byte order
Fix the block maps for data ranges

The existing code uses the underlying data blocks as keys, and the
origin blocks as values, which is backwards. This is done correctly
above for the single mapping case, so this bug only affects range
mappings.
Run git release on release, too
Merge branch 'master' of https://github.com/mpalmer/lvmsync