|
From: Stelian P. <st...@po...> - 2002-11-15 10:40:42
|
Hi everybody, A new version of dump/restore, the Linux ext2/ext3 filesystem backup utilities, has been released today. This new release features several minor and not so minor bugfixes. For details, read the changelog, pasted below. As you all already know it, the dump/restore homepage is located at: http://dump.sourceforge.net Enjoy, Stelian. 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 <Ric...@ey...> 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 <jor...@us...> 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 <dtr...@us...> 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 <sof...@us...> 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 <ph...@fi...> 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 <eh...@m5...> in a Debian bug report. -- Stelian Pop <st...@po...> |