Fix rmt ioctl command with UNIX clients (mtio opcodes Linux incompatibilities)

[dump.git] / CHANGES

diff --git a/CHANGES b/CHANGES
index 9c18c539e35a76e95f14b4866588b48a340731dd..e055370d6215a46659d5efab62badbe485342304 100644 (file)
--- a/CHANGES
+++ b/CHANGES
@@ -1,7 +1,18 @@
-$Id: CHANGES,v 1.169 2002/03/28 14:53:01 stelian Exp $
+$Id: CHANGES,v 1.173 2002/04/15 11:57:27 stelian Exp $
 
-Changes between versions 0.4b27 and 0.4b28 (released ?????????????????)
-=======================================================================
+Changes between versions 0.4b28 and 0.4b29 (released ??????????????)
+====================================================================
+
+1.     Fixed a problem in the rmt ioctl command, where ioctl's issued from
+       non Linux clients were misinterpreted. The description of the problem
+       (incompatible numbering in Linux mtio opcodes) is documented at
+       ftp://ftp.fokus.gmd.de/pub/unix/star/README.mtio . Thanks to
+       Jörg Schilling <schilling@fokus.gmd.de> for reporting this bug and
+       providing an excellent, cross-platform replacement for rmt in his
+       star package.
+       
+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
@@ -39,6 +50,16 @@ Changes between versions 0.4b27 and 0.4b28 (released ?????????????????)
        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)
 =======================================================================