Force restore -C to imply -N

[dump.git] / CHANGES

diff --git a/CHANGES b/CHANGES
index 391d7594e503f1d38cc63f2de55d6bbb38c9ec4a..91f827e549898f08815b21bceadf5e7e5915701b 100644 (file)
--- a/CHANGES
+++ b/CHANGES
@@ -1,4 +1,4 @@
-$Id: CHANGES,v 1.264 2005/01/13 12:13:46 stelian Exp $
+$Id: CHANGES,v 1.268 2005/01/14 13:04:56 stelian Exp $
 
 Changes between versions 0.4b38 and 0.4b39 (released ???????????????)
 =====================================================================
@@ -7,6 +7,26 @@ Changes between versions 0.4b38 and 0.4b39 (released ???????????????)
        with an updated version from Andrew Basterfield
        <bob@cemetery.homeunix.org>.
 
+2.     Made restore to chdir() back into the initial directory when
+       dumping core while aborting a comparision operation. The
+       previous behaviour was to write the corefile at the root of
+       the directory being compared, which could very well be 
+       read only and preventing the corefile generation. Thanks
+       to Kenneth Porter <shiva@sewingwitch.com> for the bug report.
+
+3.     Silenced the failure to call fgetflags() when comparing an
+       entry which has no ext2 attributes (as in lsattr()).
+
+4.     Fix a brown paper bug in restore -C which broke restore and
+       caused modifications on the filesystem being compared
+       (directories containing a file with the same name as the
+       directory get renamed to RSTTMP...). Thanks to Kenneth Porter
+       <shiva@sewingwitch.com> for finding the bug and helping me
+       reproduce it.
+
+5.     Made restore -C force the -N flag (no writing allowed on
+       the disk) in order to prevent more bugs like the above one.
+
 Changes between versions 0.4b37 and 0.4b38 (released January 7, 2005)
 =====================================================================