Made restore able to understand extra TS_ADDR headers when ufsdump dumped inodes...

[dump.git] / CHANGES

diff --git a/CHANGES b/CHANGES
index 0af096f4bb334d9f2ed1b678646df9cb9384c837..9c18c539e35a76e95f14b4866588b48a340731dd 100644 (file)
--- a/CHANGES
+++ b/CHANGES
@@ -1,7 +1,46 @@
-$Id: CHANGES,v 1.159 2002/01/31 10:25:55 stelian Exp $
+$Id: CHANGES,v 1.169 2002/03/28 14:53:01 stelian Exp $
 
-Changes between versions 0.4b26 and 0.4b27 (released ???????????????)
-=====================================================================
+Changes between versions 0.4b27 and 0.4b28 (released ?????????????????)
+=======================================================================
+
+1.     Fixed a bug in the QFA feature which could have caused 
+       a bad tape positionning on restore (causing extra delays in
+       restore). Credits go to Uwe Gohlke <uwe@ugsoft.de>.
+
+2.     Added a small note in the dump man page specifying that
+       there should be no white space between the option letter and
+       the -j or -z parameter, thanks to Kenneth Porter <shiva@well.com>
+
+3.     Made restore work with older versions of the readline library,
+       by checking in configure for several extended symbols. Restore
+       can now be compiled with a readline as old as the 2.0 release
+       (though it may be a good idea to upgrade it to a more recent
+       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.
+
+Changes between versions 0.4b26 and 0.4b27 (released February 15, 2002)
+=======================================================================
 
 1.     Fixed behaviour of dump when exceeding resource limits
        (SIGXFSZ treatment).
@@ -32,6 +71,18 @@ Changes between versions 0.4b26 and 0.4b27 (released ???????????????)
 7.     Small fix in restore making it able to read some (broken ?)
        Solaris ufsdump tapes.
 
+8.     Fixed dump to correctly recognise the root filesystem when using
+       ext2 disk labels (LABEL=/). Thanks to John Yu <jky@it.bu.edu>
+       for reporting this bug.
+
+9.     Added the -P <file> option to restore to create a
+       Quick File Access file from an already made dump. Patch 
+       contributed by Uwe Gohlke <uwe@ugsoft.de>.
+
+10.    Made restore compile and run on Solaris, making it a 
+       possible replacement for the standard ufsrestore. Port was
+       contributed by Uwe Gohlke <uwe@ugsoft.de>.
+
 Changes between versions 0.4b25 and 0.4b26 (released January 7, 2002)
 =====================================================================