Due credit to Jörg Schilling for RMT extended protocol.

[dump.git] / CHANGES

diff --git a/CHANGES b/CHANGES
index 776bedf9e740ef84b6a4719cef1c85692bd65ea2..82097e91c703ad7632637169a9b129c805aba9cc 100644 (file)
--- a/CHANGES
+++ b/CHANGES
@@ -1,7 +1,7 @@
-$Id: CHANGES,v 1.165 2002/02/25 13:54:52 stelian Exp $
+$Id: CHANGES,v 1.172 2002/04/12 12:45:50 stelian Exp $
 
-Changes between versions 0.4b27 and 0.4b28 (released ?????????????????)
-=======================================================================
+Changes between versions 0.4b27 and 0.4b28 (released April 12, 2002)
+====================================================================
 
 1.     Fixed a bug in the QFA feature which could have caused 
        a bad tape positionning on restore (causing extra delays in
@@ -18,6 +18,37 @@ Changes between versions 0.4b27 and 0.4b28 (released ?????????????????)
        version...). Thanks to Andrew Donkin <ard@waikato.ac.nz> for
        reporting the build failures.
 
+4.     Fixed a performance problem with the QFA file creation in
+       dump, which made unnecessary seeks on the tape slowing down
+       the dump. Thanks to Andrew Donkin <ard@waikato.ac.nz> for
+       reporting this issue.
+
+5.     Removed the inclusion of some kernel headers in the dump
+       source, which prevented the compile in some kernel/glibc
+       headers/architecture combination. Thanks to Bdale Garbee
+       <bdale@gag.com> for reporting the bug.
+
+6.     Added the appropriate error message when dump fails to
+       open the output file for writing. Thanks to Amith Varghese
+       <amithv@yahoo.com> for reporting this bug.
+
+7.     Made restore able to understand large Solaris ufsdump tapes 
+       (containing inodes bigger than 4194304). Sun have introduced
+       an "extension" to the dump tape format when dealing with
+       those inodes, which was uncorrectly handled by Linux restore.
+       Thanks to Uwe Gohlke <uwe@ugsoft.de> for reporting the bug and
+       providing a test case.
+
+8.     Added the -m parameter to dump which optimises the output for
+       inodes having been changed but not modified since the last dump
+       ('changed' and 'modified' have the meaning defined in stat(2)).
+       For those inodes, dump will save only the metadata, instead of
+       saving the entire inode contents. Inodes which are either 
+       directories or have been modified since the last dump are saved
+       in a regular way.  Uses of this flag must be consistent, meaning
+       that either every dump in an incremental dump set have the flag,
+       or no one has it.
+
 Changes between versions 0.4b26 and 0.4b27 (released February 15, 2002)
 =======================================================================