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

[dump.git] / CHANGES

diff --git a/CHANGES b/CHANGES
index d073757d51b68d6b25e61a611b69d04f7393b5c6..9c18c539e35a76e95f14b4866588b48a340731dd 100644 (file)
--- a/CHANGES
+++ b/CHANGES
@@ -1,4 +1,4 @@
-$Id: CHANGES,v 1.166 2002/02/27 09:47:48 stelian Exp $
+$Id: CHANGES,v 1.169 2002/03/28 14:53:01 stelian Exp $
 
 Changes between versions 0.4b27 and 0.4b28 (released ?????????????????)
 =======================================================================
@@ -23,6 +23,22 @@ Changes between versions 0.4b27 and 0.4b28 (released ?????????????????)
        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)
 =======================================================================