X-Git-Url: https://git.wh0rd.org/?p=dump.git;a=blobdiff_plain;f=CHANGES;h=354c38e06f697f631c9e2060d4c5138beb196136;hp=ee9b9d6a81335ea6e857c55155e8e4e6855620f0;hb=51c11d00ad6213e3d00e484eff39d3fc734afa8e;hpb=35952b8fbb9df4f18fe7c470dc62ed318d4ce695 diff --git a/CHANGES b/CHANGES index ee9b9d6..354c38e 100644 --- a/CHANGES +++ b/CHANGES @@ -1,12 +1,185 @@ -$Id: CHANGES,v 1.163 2002/02/21 09:25:31 stelian Exp $ +$Id: CHANGES,v 1.199 2002/11/15 10:03:37 stelian Exp $ -Changes between versions 0.4b27 and 0.4b28 (released ?????????????????) +Changes between versions 0.4b31 and 0.4b32 (released November 15, 2002) ======================================================================= +1. Changed dump to use fcntl(F_SETLK) style locking instead + of flock() when locking the dumpdates file. With the old + locking scheme, a local user having read rights on the + dumpdates file could be able to do a Denial of Service attack + on dump. In order to lock the dumpdates file with the new + scheme, the user would need to have write access on the file. + Thanks to Richard Johnson for + reporting the bug (originally a bugtraq post). + +2. Fixed interactive 'ls' which caused spurious errors warnings + about 'undefined filetypes' detected. Thanks to Jorgen Ostling + for reporting this + bug. + +3. Fixed dump's estimate when dealing with sparse inodes. + +4. Modified dump to allow setting a blocksize bigger than 32kB + (raised the limit to 1024kB), because newer hardware needs + this for proper operation. Thanks to Dirk Traenapp + for reporting this. + +5. Fixed a bug causing Dump to stop and report an error if an + inode number in the exclude file was followed by some amount + of whitespace. Thanks to Jeffrey Sofferin + for reporting this bug. + +6. Fixed a bug which caused restore, in some particular cases, + to ask some 'scary' questions and leave a bunch of RSTTMP + directories behind when restoring incremental tapes. Thanks + to Philippe Troin for reporting this bug and + providing the test cases. + +7. Changed the wording when inodes are excluded from dump: + replaced 'Added inode 7 to exclude list' with + 'Excluding inode 7 (resize inode) from dump', as suggested + by Elliott Mitchell in a Debian bug report. + +Changes between versions 0.4b30 and 0.4b31 (released July 30, 2002) +=================================================================== + +1. Fixed rmt open flags transmission (GNU's symbolic syntax over + rmt) which I broke in 0.4b29. Thanks to Eros Albertazzi + for reporting the bug. + +Changes between versions 0.4b29 and 0.4b30 (released July 25, 2002) +=================================================================== + +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. + +2. Fixed a problem in restore when reading tapes written on big + endian machines with very old versions of dump. The patch was + contributed by George Helffrich . + +3. Fixed the tape length calculation when using large tapes + and compression. Thanks to Georg Lippold + for reporting the bug. + +4. Added a new set of examples in dump_on_cd_2 directory, based + on dump_on_cd examples but somewhat enhanced, supporting DVD + media, and localized in english and german. Thanks to + Georg Lippold for the new scripts. + +5. Made dump save 32 bit UID/GID. Internally, this was achieved + by switching from the old BSD inode format to the new BSD + inode format, which means that the tape format was changed. + However, since all restore versions out there should + transparently support both inode formats, the change should + have no side effects. Thanks to John Yu for + reporting the bug. + +6. Fixed a lot of warnings in the code shown when compiling + with 'gcc -W'. Thanks to Matthias Andree + for reporting this. + +7. Fixed a small markup bug in the dump man page. Thanks to + Eric S. Raymond for submitting the + patch. + +8. Rewrote entirely the man pages using the tmac.an macro + package (Linux man page format) instead of the original BSD + format. They should be now cleaner and easier to modify. + +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 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) =======================================================================