+$Id: CHANGES,v 1.22 1999/11/22 21:39:37 tiniou Exp $
+
+Changes between versions 0.4b10 and 0.4b11 (released ????????????????)
+======================================================================
+
+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 doint 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.
+
+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
+ routines instead of system ones. Thanks to Bernhard Sadlowski
+ <sadlowsk@Mathematik.Uni-Bielefeld.DE> for reporting the bug
+ and helping me resolve this and other minor libc5 compiling
+ glitches.
+
+2. Fix a problem when dumping a ext2fs with the 'filetype'
+ feature enabled. Thanks to Patrick J. LoPresti
+ <patl@cag.lcs.mit.edu> for reporting the bug and to
+ Theodore Y. Ts'o <tytso@mit.edu> for providing the patch.
+
+3. Made the nodump flag work on directories. A directory which
+ 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)
+====================================================================
+
+1. Use lchown instead of chown, fixing a possible security problem
+ when restoring symlinks (a malicious user could use this
+ to deliberately corrupt the ownership of important system files).
+ Thanks to Chris Siebenmann <cks@utcc.utoronto.ca> for detecting
+ this and providing the patch.
+
+Changes between versions 0.4b7 and 0.4b8 (released November 3, 1999)
+====================================================================
+
+1. Put dump sources under CVS, added Id tags in all files so
+ one can use 'ident' on binary files.
+
+2. Added the dump/restore version in the usage text so one can
+ easily verify the version he is using.
+
+3. Small patch from Nuno Oliveira <nuno@eq.uc.pt> which fixes
+ a va_start/va_end problem on linux-ppc (always call va_start
+ va_end in pairs each time we use a vararg function).
+
+4. Added again the DT_* constants because old libc does not
+ contain them :(. Thanks to Eric Maisonobe <virnet@nat.fr>
+ for submitting the bug report.
+
+5. Use ext2fs_llseek instead of llseek. With recent e2fsprogs
+ this should enable dumping big (huge) filesystems.
+
+6. Added the RSH environment variable in order to be able to
+ use a rsh replacement like ssh when doing remote backups (and
+ bypass the security limitations of rcmd). Now you can do remote
+ backups without being root (or making dump setuid root).
+
+7. Modified again the way dumpdates works. For incremental dumps,
+ we need to read dumpdates even if we are not using 'u' option.
+ Thanks to Bdale Garbee <bdale@gag.com> for his ideas on how
+ this should work.
+