-$Id: CHANGES,v 1.17 1999/11/21 00:17:12 tiniou Exp $
+$Id: CHANGES,v 1.31 2000/01/09 23:37:01 tiniou Exp $
-Changes between versions 0.4b9 and 0.4b10 (released ???????????????)
-====================================================================
+Changes between versions 0.4b12 and 0.4b13 (released ???????????????)
+=====================================================================
+
+1. Small Y2K fix in the man pages :). Thanks to Bernhard Sadlowski
+ <sadlowsk@Mathematik.Uni-Bielefeld.DE> for reporting the bug.
+
+Changes between versions 0.4b11 and 0.4b12 (released January 8, 2000)
+=====================================================================
+
+1. Small fix in the dump man page. Thanks to Thorsten Kukuk
+ <kukuk@suse.de> for submitting the patch.
+
+2. Fix for the exit code when using the size estimate option of
+ dump. Thanks to Matti Taskinen <mkt@rni.helsinki.fi> for
+ submitting the patch.
+
+3. Handle EINTR in atomical reads/writes in dump, which was causing
+ dump to fail on some systems. Thanks to Eric Jergensen
+ <eric@dvns.com> for reporting the bug and submitting the patch.
+
+4. Handle more than 16 characters for the device names in dumpdates.
+ (up to 255 now). Thanks to Rainer Clasen <bj@ncc.cicely.de> for
+ tracking down the problem and proposing the solution.
+
+5. Fixed a bug in dump which prevented the creation of the
+ dumpdates file when doing a 0-level dump without already
+ having a dumpdates file. Thanks to Patrik Schindler
+ <poc@pocnet.net> for reporting the bug.
+
+6. Changed the way dump 'S' flag reports the size estimate
+ from number of blocks into bytes (making it compatible
+ with the Solaris version, and simplifying things for
+ amanda users). Thanks to Jason L Tibbitts III
+ <tibbs@math.uh.edu> for reporting the bug.
+
+7. Fixed a compatibility problem in linux/alpha dump tape format.
+ Now the linux/alpha dump are (again) compatible with the
+ other dump formats. But this breaks compatibility with
+ older dumps made on alpha. Thanks to Mike Tibor
+ <tibor@lib.uaa.alaska.edu> for helping me in finding this bug.
+
+Changes between versions 0.4b10 and 0.4b11 (released December 5, 1999)
+======================================================================
+
+1. Added a '--enable-kerberos' to configure.
+
+2. Added a 'S' option to dump which determines the amount of space
+ that is needed to perform the dump without actually doing it, similar
+ to the Sun's ufsdump 'S' option. Patch contributed by Rob Cermak
+ <cermak@ahab.rutgers.edu>.
+
+3. Added a 'M' multi-volume option to dump and restore which enables
+ dumping to multiple files (useful when dumping to an ext2
+ partition to make several dump files in order to bypass the 2GB
+ file size limitation). The 'f' argument is treated as a prefix and
+ the output files will be named <prefix>001, <prefix>002 etc. With
+ the 'M' flag, restore automatically selects the right file without
+ asking to enter a new tape each time.
+
+4. Fixed a memory leak which was causing dump to grow very big
+ (270MB when dumping a 10GB filesystem...). Thanks to Jason
+ Fearon <jasonf@netrider.org.au> for reporting the bug.
+
+Changes between versions 0.4b9 and 0.4b10 (released November 21, 1999)
+======================================================================
1. Make configure test if the system glob routines support
extended syntax (ALTDIRFUNC). If not, use the internal glob
has the nodump flag gets never dumped, regardless of its
contents.
+4. Integrate a patch from Jeremy Fitzhardinge <jeremy@goop.org>
+ which allows dump on an active ext3 filesystem. However, this
+ is a "quick and dirty" patch which enables backup of an ext3
+ filesystem through the ext2 compatibility (by ignoring the
+ NEEDS_RECOVERY bit). The journal file is not recognized and
+ it is dumped (it should not).
+
+5. Test the superblock compatibility flags when dumping, in order
+ to be sure that we know how to deal with specific features.
+
Changes between versions 0.4b8 and 0.4b9 (released November 5, 1999)
====================================================================