dump hang workaround.

[dump.git] / CHANGES

diff --git a/CHANGES b/CHANGES
index 7d3142652b5b9685b95ae0e76c3e7424a3de2658..1fbbb9864eaf20d31b73c484079e06313882cf38 100644 (file)
--- a/CHANGES
+++ b/CHANGES
@@ -1,4 +1,4 @@
-$Id: CHANGES,v 1.143 2001/11/16 14:09:07 stelian Exp $
+$Id: CHANGES,v 1.145 2001/11/17 10:44:18 stelian Exp $
 
 Changes between versions 0.4b24 and 0.4b25 (released ??????????????????)
 ========================================================================
@@ -27,7 +27,14 @@ Changes between versions 0.4b24 and 0.4b25 (released ??????????????????)
        to know this information when reading a remote compressed 
        dump. Previously, this information was autodetected, but
        the autodetection code fails (with ioctl: Inappropriate ioctl 
-       for device) when using a non Linux remote box.
+       for device) when using a non Linux remote box. Thanks to 
+       many users and especially to Eros Albertazzi 
+       <eros@lamel.bo.cnr.it> for reporting this.
+
+7.     Found a workaroung for the dump deadlock problem (3 childs 
+       stuck in pause(), father in read()). The workaround seems
+       to work for me and several beta-testers. If it doesn't work
+       for you, please report back.
        
 Changes between versions 0.4b23 and 0.4b24 (released September 12, 2001)
 ========================================================================