]> git.wh0rd.org - dump.git/blame_incremental - CHANGES
Fixed labels exactly 16 bytes in length.
[dump.git] / CHANGES
... / ...
CommitLineData
1$Id: CHANGES,v 1.218 2003/02/25 14:06:47 stelian Exp $
2
3Changes between versions 0.4b33 and 0.4b34 (released ?????????????????)
4=======================================================================
5
61. Fixed the INSTALL file to reflect the actual install paths.
7 Thanks to David Ronis <ronis@ronispc.chem.mcgill.ca> for
8 reporting the bug.
9
102. Fixed the configure script to only check for headers presence
11 instead of trying to compile them. This should fix issues
12 with old build environments. Thanks to Kari Lempiainen
13 <kari@funky.pp.fi> for reporting the bug.
14
153. Fixed restore to correctly ignore sockets when comparing
16 a dump (as socket cannot be properly restored anyway). Thanks
17 to Gunther Reiszig <gunther@mit.edu> for reporting the bug.
18
194. Fixed restore to correctly access the archive file (-A argument)
20 even when using a remote tape. Thanks to Fabrice Bellet
21 <fabrice@bellet.info> for reporting the bug.
22
235. Fixed (again) handling of long (largefile) seeks in rmt.
24 Thanks to Fabrice Bellet <fabrice@bellet.info> for reporting
25 the bug.
26
276. Fixed restore corner case when dealing with large block sizes
28 dump is able to write now (-b 1024). Thanks to Fabrice Bellet
29 <fabrice@bellet.info> for reporting the bug.
30
317. Fixed a bug preventing dump to access a filesystem having
32 a label exactly 16 bytes in length. Thanks to <minduni@ti-edu.ch>
33 for reporting the bug.
34
35Changes between versions 0.4b32 and 0.4b33 (released February 10, 2003)
36=======================================================================
37
381. Added a note in the restore man page clarifying the question
39 'set the permissions on the current directory ?' asked by
40 restore at the end of treatment in -i and -x modes.
41
422. Fixed the endianess issues when reading compressed tapes.
43 Thanks to Dark Force <daq4th@users.sourceforge.net> for
44 reporting this bug and providing test cases.
45
463. Fixed the "ACL won't be dumped" warning message (which showed
47 an extra, unrelated error message). Thanks to Dragan Krnic
48 <dkrnic@lycos.com> for reporting this bug.
49
504. Made dump look first into /etc/mtab, then into /etc/fstab
51 when searching for filesystem paths. Also fixed some problems
52 caused by binding mounts or multiple block device mounts.
53 Thanks to Matus Uhlar <uhlar@fantomas.sk>, Elliott Mitchell
54 <ehem@m5p.com>, Greg Edwards <gedwards@users.sourceforge.net>,
55 Brian Hoy <brian.hoy@opus.co.nz>. (fixes Debian bugs #147086
56 and #160305, Sourceforge bugs #618699 and #679832).
57
585. Made dump's -I option accept the value '0' meaning all the
59 read errors will be ignored. This can be useful when running
60 dump from unattended sessions (like cron jobs). Thanks to
61 John I Wang <jiwang@users.sourceforge.net> for the suggestion.
62
636. Fixed the output of dump to indicate 'blocks' instead of
64 'tape blocks' in the various messages (blocks are always
65 1 Kilobyte, tape blocks are 1 BK * '-b' argument), and
66 made it clearly print the current blocksize at the start of
67 a dump. Thanks to Michal Szymanski <msz@astrouw.edu.pl> for
68 the suggestions.
69
707. Made rmt understand long (largefiles) seeks.
71
728. Fixed build with very old versions of libext2fs, where
73 EXT2_FT_* constants were undefined.
74
759. Made dump accept the dumpdates path on the command line
76 (-D file option) instead of using only the hardcoded one.
77 Thanks to Piete Brooks <pb22@users.sourceforge.net> for the
78 suggestion.
79
8010. Enabled rmt, LFS, readline, QFA options by default in
81 ./configure. Updated the configure process (new versions
82 of config.guess, config.sub etc).
83
84Changes between versions 0.4b31 and 0.4b32 (released November 15, 2002)
85=======================================================================
86
871. Changed dump to use fcntl(F_SETLK) style locking instead
88 of flock() when locking the dumpdates file. With the old
89 locking scheme, a local user having read rights on the
90 dumpdates file could be able to do a Denial of Service attack
91 on dump. In order to lock the dumpdates file with the new
92 scheme, the user would need to have write access on the file.
93 Thanks to Richard Johnson <Richard.Johnson3@ey.com> for
94 reporting the bug (originally a bugtraq post).
95
962. Fixed interactive 'ls' which caused spurious errors warnings
97 about 'undefined filetypes' detected. Thanks to Jorgen Ostling
98 <jorgen_ostling@users.sourceforge.net> for reporting this
99 bug.
100
1013. Fixed dump's estimate when dealing with sparse inodes.
102
1034. Modified dump to allow setting a blocksize bigger than 32kB
104 (raised the limit to 1024kB), because newer hardware needs
105 this for proper operation. Thanks to Dirk Traenapp
106 <dtraenapp@users.sourceforge.net> for reporting this.
107
1085. Fixed a bug causing Dump to stop and report an error if an
109 inode number in the exclude file was followed by some amount
110 of whitespace. Thanks to Jeffrey Sofferin
111 <sofferin@users.sourceforge.net> for reporting this bug.
112
1136. Fixed a bug which caused restore, in some particular cases,
114 to ask some 'scary' questions and leave a bunch of RSTTMP
115 directories behind when restoring incremental tapes. Thanks
116 to Philippe Troin <phil@fifi.org> for reporting this bug and
117 providing the test cases.
118
1197. Changed the wording when inodes are excluded from dump:
120 replaced 'Added inode 7 to exclude list' with
121 'Excluding inode 7 (resize inode) from dump', as suggested
122 by Elliott Mitchell <ehem@m5p.com> in a Debian bug report.
123
124Changes between versions 0.4b30 and 0.4b31 (released July 30, 2002)
125===================================================================
126
1271. Fixed rmt open flags transmission (GNU's symbolic syntax over
128 rmt) which I broke in 0.4b29. Thanks to Eros Albertazzi
129 <eros@lamel.bo.cnr.it> for reporting the bug.
130
131Changes between versions 0.4b29 and 0.4b30 (released July 25, 2002)
132===================================================================
133
1341. Made dump print out the ext2 logical block number in case of a read
135 error, which can be given as an argument to debugfs' ncheck command,
136 in order to find out the affected inode. Added note about this
137 usage in dump's man page.
138
1392. Fixed a problem in restore when reading tapes written on big
140 endian machines with very old versions of dump. The patch was
141 contributed by George Helffrich <george@geology.bristol.ac.uk>.
142
1433. Fixed the tape length calculation when using large tapes
144 and compression. Thanks to Georg Lippold
145 <g_lippold@sourceforge.net> for reporting the bug.
146
1474. Added a new set of examples in dump_on_cd_2 directory, based
148 on dump_on_cd examples but somewhat enhanced, supporting DVD
149 media, and localized in english and german. Thanks to
150 Georg Lippold <g_lippold@sourceforge.net> for the new scripts.
151
1525. Made dump save 32 bit UID/GID. Internally, this was achieved
153 by switching from the old BSD inode format to the new BSD
154 inode format, which means that the tape format was changed.
155 However, since all restore versions out there should
156 transparently support both inode formats, the change should
157 have no side effects. Thanks to John Yu <jky@cs.bu.edu> for
158 reporting the bug.
159
1606. Fixed a lot of warnings in the code shown when compiling
161 with 'gcc -W'. Thanks to Matthias Andree
162 <matthias.andree@stud.uni-dortmund.de> for reporting this.
163
1647. Fixed a small markup bug in the dump man page. Thanks to
165 Eric S. Raymond <esr@minx.thyrsus.com> for submitting the
166 patch.
167
1688. Rewrote entirely the man pages using the tmac.an macro
169 package (Linux man page format) instead of the original BSD
170 format. They should be now cleaner and easier to modify.
171
172Changes between versions 0.4b28 and 0.4b29 (released June 8, 2002)
173==================================================================
174
1751. Fixed a problem in the rmt ioctl command, where ioctl's issued from
176 non Linux clients were misinterpreted. The description of the problem
177 (incompatible numbering in Linux mtio opcodes) is documented at
178 ftp://ftp.fokus.gmd.de/pub/unix/star/README.mtio . Thanks to
179