Fix maps overflow in restore when doing incremental restores (and MAXINO becomes...

[dump.git] / CHANGES

$Id: CHANGES,v 1.197 2002/11/15 09:25:25 stelian Exp $

Changes between versions 0.4b31 and 0.4b32 (released ?????????????)
===================================================================

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 <Richard.Johnson3@ey.com> 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 
	<jorgen_ostling@users.sourceforge.net> 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
	<dtraenapp@users.sourceforge.net> 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 
	<sofferin@users.sourceforge.net> 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 <phil@fifi.org> for reporting this bug and
	providing the test cases.

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
	<eros@lamel.bo.cnr.it> 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 <george@geology.bristol.ac.uk>.

3.	Fixed the tape length calculation when using large tapes
	and compression. Thanks to Georg Lippold 
	<g_lippold@sourceforge.net> 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 <g_lippold@sourceforge.net> 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 <jky@cs.bu.edu> for
	reporting the bug.

6.	Fixed a lot of warnings in the code shown when compiling
	with 'gcc -W'. Thanks to Matthias Andree 
	<matthias.andree@stud.uni-dortmund.de> for reporting this.

7.	Fixed a small markup bug in the dump man page. Thanks to
	Eric S. Raymond <esr@minx.thyrsus.com> 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