For incrementals, we *must* read dumpdates (fail if it's not there!).

[dump.git] / CHANGES

diff --git a/CHANGES b/CHANGES
index 5695986ff612bb8b25d4dcc38c5c076231a5c9b2..607a400f78831b73bdc42db0d60effcdf8d6b9fe 100644 (file)
--- a/CHANGES
+++ b/CHANGES
@@ -1,3 +1,32 @@
+$Id: CHANGES,v 1.10 1999/10/31 19:48:25 tiniou Exp $
+
+Changes between versions 0.4b7 and 0.4b8 (released ???????????????)
+===================================================================
+
+1.     Put dump sources under CVS, added Id tags in all files so
+       one can use 'ident' on binary files.
+
+2.     Added the dump/restore version in the usage text so one can
+       easily verify the version he is using.
+
+3.     Small patch from Nuno Oliveira <nuno@eq.uc.pt> which fixes
+       a va_start/va_end problem on linux-ppc (always call va_start
+       va_end in pairs each time we use a vararg function).
+
+4.     Added again the DT_* constants because old libc does not
+       contain them :(. Thanks to Eric Maisonobe <virnet@nat.fr>
+       for submitting the bug report.
+
+5.     Added the RSH environment variable in order to be able to
+       use a rsh replacement like ssh when doing remote backups (and
+       bypass the security limitations of rcmd). Now you can do remote
+       backups without being root (or making dump setuid root).
+
+6.     Modified again the way dumpdates works. For incremental dumps,
+       we need to read dumpdates even if we are not using 'u' option.
+       Thanks to Bdale Garbee <bdale@gag.com> for his ideas on how
+       this should work.
+
 Changes between versions 0.4b6 and 0.4b7 (released October 8, 1999)
 ===================================================================