LFS compatibility.

[dump.git] / CHANGES

diff --git a/CHANGES b/CHANGES
index 02aa723bf51c7df24506a2f62fd740fb55c387d8..775a3f899be79d6c341bf5b10dddd4f103f4da9b 100644 (file)
--- a/CHANGES
+++ b/CHANGES
@@ -1,4 +1,4 @@
-$Id: CHANGES,v 1.96 2000/12/05 16:31:35 stelian Exp $
+$Id: CHANGES,v 1.98 2000/12/21 11:14:52 stelian Exp $
 
 Changes between versions 0.4b20 and 0.4b21 (released ?????????????????)
 =======================================================================
@@ -26,6 +26,23 @@ Changes between versions 0.4b20 and 0.4b21 (released ?????????????????)
        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 :-)).
+
+7.     Make dump and restore LFS aware. Dump can dump a filesystem
+       containing large files, generate a large file on output and
+       restore can restore them. This feature is not enabled by
+       default, use --enable-largefile option of configure to enable
+       it (you need to have a LFS aware glibc though). Thanks to
+       Andrea Arcangeli <andrea@suse.de> for submitting the patch,
+       and to Theodore T'so <tytso@valinux.com> for his always
+       useful thoughts.
+
 Changes between versions 0.4b19 and 0.4b20 (released November 10, 2000)
 =======================================================================