0.5.8.1
-------
  *) A serious bug pointed out by Guzovsky, Eduard <EGuzovsky@crossbeamsys.com>
     fixed. All the credits should go to him.
     Since the "epoch_log" uses the same memory as the transfer_log and 
     it's elements are bigger than the elements of the transfer_log. 
     Memory corruption is a likely result of this.

0.5.8
-----
A lot of new features: (This release should be named 0.6)
  *) codecleanup of the on-the-fly counters
  *) drbdsetup is not splitted into a disk and a net part / syntax changed
  *) syncer rewritten. Now a lot faster but currently only woking with
     4K based file systems. (mkfs -b 4096)
  *) Meta-data management implemented. => DRBD is now able to select
     the node with the up-to-date data to become primary after a cluster 
     restart.
  *) datadisk / drbd scripts rewritten two times :) Now they are in
     perl and we have a new configuration file named /etc/drbd.conf

0.5.7
-----
Bugfix release:
  *) Fixed the bh_count > 0 bug.
  *) Fixed the multiple-timeouts-bug.
  *) Fixed a bug when working with a fs with a blocksize other than 4096
  *) Applied the patch from Juri Haberland against the datadisk script.

0.5.6
-----
No updates to the mirroring core. (It seems to be stable)
A lot of updates to the "user interface"
  *) Better log-messages and better messages of drbdsetup.
  *) Fixed a few crashes of drbdsetup/ioctl interface.
  *) It is not longer possible to use an already mounted partition.
  *) It's possible to unconfigure a drbd device now.
  *) Fixed the "infinite error messages" when a wrong disk size was given.
A better datadisk script (Thomas Mangin contributed this, thanks)
Some work on the protocol:
  *) Cleanup
  *) Added automatic reconnect
  *) An intace connection is monitored by "ping" packets, thus
     a secondary will notice a broken connection immediately.
Found and fixed a 64 Bits problem in the bitmap based syncer.

0.5.5
-----
SMP and ext3 fixes to the module.
Scripts should work on RedHat distributions now.
(Automatic) support for more than two devices.

0.5.4
-----
No more zombies, when a connection is canceled.
An important SMP fix. (It seems to work on SMP now)
A lot of small improvments.(benchmarking, stress testing... )

0.5.3
-----
More sanity checks.
Fix to protocol C.
Script for automatic benchmarking.
New heartbeat scripts.

0.5.2
-----
Improved the behaviour upon loss of connction. Now it
always goes into WFConnection state instead of Unconnected.

Added a command to drbdsetup to force a run of the basic syncer.

Things to be fixed: Heartbeat scripts, protocol C on SMP machines.

0.5.1
-----
Fixed the lockup upon loss of connection on SMP machines.
Added a kludge to make use with heartbeat possible.
Added scripts for use with heartbeat.

0.5
---
The code was considerably changed and enlarged.

There are now three wire protocols.
A) A write operation is complete as soon as the data is
   written to disk and sent to the network.
B) A write operation is complete as soon as a reception 
   acknowledgement arrived.
c) A write operation is complete as soon as a write
   acknowledgement arrived.

The basic syncer was replaced by a bitmap-based syncer. The new
one only updates the blocks which were modified during the
absence of the newly joined node.

A huge load of bug fixes.

Finally I cleaned up the drbdsetup utility. Now all the
features are accessible with command line options.

0.4
---
There is a basic syncer now. It will bring a newly joined
secondary node up to date by copying each block.
It is working at 250KB/second (hard coded in drbdsetup for now).

IO errors on the local disk are now reported as if there
was an io error on drbd.


0.3
---
There is a new timeout. If the primary node cannot send (TCP!)
within the timeout, it falls back into unconnected operation.

You can also disable the timeout (by setting it to zero), but in
case of a failure of the secondary node, your primary node will block!

Currently the timeout is hard coded into drbdsetup (3 Seconds).


0.2
---
This time I worked a lot looking into all possible deadlocks...
I think if you do not use any loop-back device it should
work without deadlocking. It is not working on top of the loop
block device and it is not working via the loop-back network!

This time it should handle all block size issues, and thus
reiserfs is feeling happy on top of drbd.


Status of drbd-0.1.tar.gz
-------------------------
This is a proof-it-is-no-vapo-ware-release and not more!
It is the first time it is somehow working without immediately crashing
my machine (you can "even" unload the module). It is not able to 
handle block sizes other than 1024 and there is not a single line of code
of the sync-a-new-secondary stuff yet.
The used port is hard coded into drbdsetup (7788) for now.
I have tested it on an Intel box and an alpha machine.


