X-Git-Url: https://git.wh0rd.org/?p=dump.git;a=blobdiff_plain;f=CHANGES;h=82097e91c703ad7632637169a9b129c805aba9cc;hp=214829ce6323a100fbbc1f3a545c6404ef4ab293;hb=97d9098250fd2a49d9ef70d6bf93f49badff0f6c;hpb=fe0e02857a1ff7db4bf8cb28780de7ecf2f24234 diff --git a/CHANGES b/CHANGES index 214829c..82097e9 100644 --- a/CHANGES +++ b/CHANGES @@ -1,7 +1,56 @@ -$Id: CHANGES,v 1.161 2002/02/04 11:18:45 stelian Exp $ +$Id: CHANGES,v 1.172 2002/04/12 12:45:50 stelian Exp $ -Changes between versions 0.4b26 and 0.4b27 (released ???????????????) -===================================================================== +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 + restore). Credits go to Uwe Gohlke . + +2. Added a small note in the dump man page specifying that + there should be no white space between the option letter and + the -j or -z parameter, thanks to Kenneth Porter + +3. Made restore work with older versions of the readline library, + by checking in configure for several extended symbols. Restore + can now be compiled with a readline as old as the 2.0 release + (though it may be a good idea to upgrade it to a more recent + version...). Thanks to Andrew Donkin for + reporting the build failures. + +4. Fixed a performance problem with the QFA file creation in + dump, which made unnecessary seeks on the tape slowing down + the dump. Thanks to Andrew Donkin 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 + for reporting the bug. + +6. Added the appropriate error message when dump fails to + open the output file for writing. Thanks to Amith Varghese + 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 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) +======================================================================= 1. Fixed behaviour of dump when exceeding resource limits (SIGXFSZ treatment).