Use the libext2fs inode-scanning functions.

[dump.git] / CHANGES

diff --git a/CHANGES b/CHANGES
index 5d690aa6c474e78bc0779c2441923403c5b82fdc..13a5cbce9d49316c4eac32759e3c82ec0c75f3dd 100644 (file)
--- a/CHANGES
+++ b/CHANGES
@@ -1,4 +1,4 @@
-$Id: CHANGES,v 1.92 2000/11/30 09:53:10 stelian Exp $
+$Id: CHANGES,v 1.97 2000/12/05 16:57:37 stelian Exp $
 
 Changes between versions 0.4b20 and 0.4b21 (released ?????????????????)
 =======================================================================
@@ -11,6 +11,29 @@ Changes between versions 0.4b20 and 0.4b21 (released ?????????????????)
        headers (filesystem label related). Thanks to many users
        who reported this stupid error.
 
+3.     Fixed a build problem on old lib5 based systems dealing with 
+       _PATH_MNTTAB being undefined. Thanks to John Adams
+       <johna@onevista.com> for reporting the bug.
+
+4.     Improved the error detection in restore when creating
+       the temporary files in TMPDIR. Now restore will corectly
+       report a 'no space left on device' error instead of 
+       strange errors which could imply an archive corruption.
+       Thanks to Gabriel Somlo <somlo@cs.colostate.edu> and
+       bgjenero <bgjenero@sympatico.ca> for reporting the bug.
+
+5.     Added the throughput information in dump's progression
+       messages.  Thanks to Andreas Dilger <adilger@turbolinux.com> 
+       for the patch.
+
+6.     Use libext2fs's inode scanning routines, which are particularly
+       robust when dealing with errors (especially when having some
+       bad blocks on the filesystem). Many thanks to Colin
+       <colin@horizon.com> for reporting the bug, investigating
+       the issues, finding a workaround, writing the patch and
+       fully testing it... (of course, if this patch will break
+       anything, he is to blame for :-)).
+
 Changes between versions 0.4b19 and 0.4b20 (released November 10, 2000)
 =======================================================================