X-Git-Url: https://git.wh0rd.org/?a=blobdiff_plain;f=CHANGES;h=a4d1b44a8e22c5109278914126c513e9a6f4ce9f;hb=aa1b1e7f1a9c7201ba1ac4eb35921e2c9df26729;hp=b98f214d48c6e9a2b2eefa0c52ed420ea3583b47;hpb=7ad0e4095900bf99e57eedf254d7162ef5112f43;p=dump.git diff --git a/CHANGES b/CHANGES index b98f214..a4d1b44 100644 --- a/CHANGES +++ b/CHANGES @@ -1,7 +1,58 @@ -$Id: CHANGES,v 1.167 2002/03/11 10:17:42 stelian Exp $ +$Id: CHANGES,v 1.181 2002/06/10 14:04:59 stelian Exp $ -Changes between versions 0.4b27 and 0.4b28 (released ?????????????????) -======================================================================= +Changes between versions 0.4b29 and 0.4b30 (released ????????????????) +====================================================================== + +1. Made dump print out the ext2 logical block number in case of a read + error, which can be given as an argument to debugfs' ncheck command, + in order to find out the affected inode. Added note about this + usage in dump's man page. + +Changes between versions 0.4b28 and 0.4b29 (released June 8, 2002) +================================================================== + +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 for reporting this bug and + providing an excellent, cross-platform replacement for rmt in his + star package. + +2. Fixed a bug reported by Andy Mentges + which caused restore to fail when the inode maps were not entirely + contained on the first volume (when using really small volumes or + when dumping a huge number of inodes). + +3. Fixed a problem in dump, where files in subdirectories of directories + that have the nodump flag set (or being excluded with -e/-E) were + sometimes incorrectly dumped (instead of being excluded). The original + fix is from David C Lawrence in the FreeBSD version + of dump: http://www.FreeBSD.org/cgi/query-pr.cgi?pr=32414 + Thanks to Ted Grzesik for reporting the bug and + help testing the patch. + +4. Added some example scripts from Gerd Bavendiek + which makes one able to pipe the output of dump, by the net, to + a remote CD-burner server. + +5. Made dump use O_CREAT|O_TRUNC both locally and remotely (over rmt), + and use GNU's symbolic syntax over rmt instead of numerical values + to assure multiple platform compatibility. + +6. Documented the -d option in restore. + +7. Added a -v (verbose) mode to dump. For now it just prints the number + of the inode being dumped, but this could evolve in future versions + to include interesting debugging output. + +8. Added a -o flag to restore, which automatically restores the current + directory permissions in -i or -x mode, without asking the operator + whether to do so. Patch submitted by Tony Clayton + and Peter Samuel . + +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 @@ -28,6 +79,27 @@ Changes between versions 0.4b27 and 0.4b28 (released ?????????????????) 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) =======================================================================