]> git.wh0rd.org - dump.git/blame_incremental - CHANGES
Updated the autoconf system to 2.50. Forced the -D_BSD_SOURCE
[dump.git] / CHANGES
... / ...
CommitLineData
1$Id: CHANGES,v 1.232 2003/09/03 15:00:21 stelian Exp $
2
3Changes between versions 0.4b34 and 0.4b35 (released ??????????????)
4====================================================================
5
61. Added a note in the dump man page saying that the default
7 blocksize can be 32 if -d is used with a high density argument.
8 Thanks to Antonios Christofides <A.Christofides@itia.ntua.gr>
9 for the patch.
10
112. Fixed configure to correctly understand CPPFLAGS, CFLAGS,
12 LDFLAGS environment variables. Thanks to Arcady Genkin
13 <antipode@users.sourceforge.net> for reporting the bug.
14
153. Made -e/-E options of dump accept an unlimited number of inodes
16 to be excluded, rather than a hardcoded maximum. Thanks to
17 Dietrich Rothe <d-rothe@users.sourceforge.net> for the patch.
18
194. Updated the autoconf system to 2.50. Forced the -D_BSD_SOURCE
20 and -D_USE_BSD_SIGNAL defines in configure in order to solve
21 64bit build problems because quad_t is redifined with a
22 different signature. Thanks to Mike Harris <mharris@redhat.com>
23 for reporting this bug.
24
25Changes between versions 0.4b33 and 0.4b34 (released April 18, 2003)
26====================================================================
27
281. Fixed the INSTALL file to reflect the actual install paths.
29 Thanks to David Ronis <ronis@ronispc.chem.mcgill.ca> for
30 reporting the bug.
31
322. Fixed the configure script to only check for headers presence
33 instead of trying to compile them. This should fix issues
34 with old build environments. Thanks to Kari Lempiainen
35 <kari@funky.pp.fi> for reporting the bug.
36
373. Fixed restore to correctly ignore sockets when comparing
38 a dump (as socket cannot be properly restored anyway). Thanks
39 to Gunther Reiszig <gunther@mit.edu> for reporting the bug.
40
414. Fixed restore to correctly access the archive file (-A argument)
42 even when using a remote tape. Thanks to Fabrice Bellet
43 <fabrice@bellet.info> for reporting the bug.
44
455. Fixed (again) handling of long (largefile) seeks in rmt.
46 Thanks to Fabrice Bellet <fabrice@bellet.info> for reporting
47 the bug.
48
496. Fixed restore corner case when dealing with large block sizes
50 dump is able to write now (-b 1024). Thanks to Fabrice Bellet
51 <fabrice@bellet.info> for reporting the bug.
52
537. Fixed a bug preventing dump to access a filesystem having
54 a label exactly 16 bytes in length. Thanks to <minduni@ti-edu.ch>
55 for reporting the bug.
56
578. Made dump store dump dates using explicit timezones, fixing a
58 problem with incremental dumps if the timezone is modified
59 between the dumps. Thanks to Philippe Troin <phil@fifi.org> for
60 the bug report and the patch.
61
629. Fixed a bug encountered when dumping individual files (not full
63 filesystems or directories) and dangling symbolic links happen
64 to be in the list of files. For as far as dump is concerned,
65 dangling symbolic links are allowed, and are dumped as is.
66 Thanks to Jin-su Ahn <jsahn@ee.snu.ac.kr> for reporting the
67 bug and providing the fix.
68
6910. Fixed open and creation modes and permissions for QFA and
70 table-of-contents files in dump and restore. Thanks to
71 Philippe Troin <phil@fifi.org> for the patch.
72
7311. Fixed the archive file descriptor handling enabling it to be 0.
74 This can happen in some cases when shell redirections are used.
75 Thanks to Philippe Troin <phil@fifi.org> for the patch.
76
7712. Delayed the opening of archive file until after suid had been
78 dropped (fixing a possible security issue if dump is suid).
79 Thanks to Philippe Troin <phil@fifi.org> for the patch.
80
8113. Fixed the 'S' command handling in the rmt client part.
82 Thanks to Philippe Troin <phil@fifi.org> for the patch.
83
8414. Modified the end-of-tape script handling to print out statistics
85 (and stop the timer) before launching the eot script. Also, the eot
86 script does not get run anymore when using -M (which makes sense) or
87 when multiple tapes are listed on the command line
88 (-f tape0,tape1,tapen) (which also makes sense).
89 Thanks to Philippe Troin <phil@fifi.org> for the patch.
90
9115. Relicensed dump/restore under the 'revised' BSD license, as per
92 ftp://ftp.cs.berkeley.edu/ucb/4bsd/README.Impt.License.Change.
93
9416. Added LZO compression to dump. This new compression method has
95 the advantage of being super fast, thus not killing tape streaming
96 on slow machines. Thanks to Helmut Jarausch
97 <jarausch@igpm.rwth-aachen.de> for the patch and to
98 Markus Oberhumer <markus@oberhumer.com> for giving special permission
99 to include his miniLZO project (GPL licensed) in dump/restore.
100
10117. Some small buffer overruns fixes in rmt. Thanks to Antonomasia
102 <ant@notatla.demon.co.uk> for reporting the bugs.
103
10418. Added a special rmt version which can do encryption when writing
105 to tape. Read examples/encrypted_rmt/README for details on
106 how to enable and configure it. Thanks to Ken Lalonde
107 <ken@globalremit.com> for the patch.
108
10919. Made dump work with 2.5 kernel end of tape early warning semantics.
110 Thanks to Kai Makisara <Kai.Makisara@kolumbus.fi> for the patch.
111
11220. Fixed a bug which caused dump -w|-W not to work anymore, because
113 the fs_freq and fs_passno fields in /etc/mtab are always set
114 to 0 0. Thanks to Trent Piepho <xyzzy@speakeasy.org> for
115 reporting the bug.
116
117Changes between versions 0.4b32 and 0.4b33 (released February 10, 2003)
118=======================================================================
119
1201. Added a note in the restore man page clarifying the question
121 'set the permissions on the current directory ?' asked by
122 restore at the end of treatment in -i and -x modes.
123
1242. Fixed the endianess issues when reading compressed tapes.
125 Thanks to Dark Force <daq4th@users.sourceforge.net> for
126 reporting this bug and providing test cases.
127
1283. Fixed the "ACL won't be dumped" warning message (which showed
129 an extra, unrelated error message). Thanks to Dragan Krnic
130 <dkrnic@lycos.com> for reporting this bug.
131
1324. Made dump look first into /etc/mtab, then into /etc/fstab
133 when searching for filesystem paths. Also fixed some problems
134 caused by binding mounts or multiple block device mounts.
135 Thanks to Matus Uhlar <uhlar@fantomas.sk>, Elliott Mitchell
136 <ehem@m5p.com>, Greg Edwards <gedwards@users.sourceforge.net>,
137 Brian Hoy <brian.hoy@opus.co.nz>. (fixes Debian bugs #147086
138 and #160305, Sourceforge bugs #618699 and #679832).
139
1405. Made dump's -I option accept the value '0' meaning all the
141 read errors will be ignored. This can be useful when running
142 dump from unattended sessions (like cron jobs). Thanks to
143 John I Wang <jiwang@users.sourceforge.net> for the suggestion.
144
1456. Fixed the output of dump to indicate 'blocks' instead of
146 'tape blocks' in the various messages (blocks are always
147 1 Kilobyte, tape blocks are 1 BK * '-b' argument), and
148 made it clearly print the current blocksize at the start of
149 a dump. Thanks to Michal Szymanski <msz@astrouw.edu.pl> for
150 the suggestions.
151
1527. Made rmt understand long (largefiles) seeks.
153
1548. Fixed build with very old versions of libext2fs, where
155 EXT2_FT_* constants were undefined.
156
1579. Made dump accept the dumpdates path on the command line
158 (-D file option) instead of using only the hardcoded one.
159 Thanks to Piete Brooks <pb22@users.sourceforge.net> for the
160 suggestion.
161
16210. Enabled rmt, LFS, readline, QFA options by default in
163 ./configure. Updated the configure process (new versions
164 of config.guess, config.sub etc).
165
166Changes between versions 0.4b31 and 0.4b32 (released November 15, 2002)
167=======================================================================
168
1691. Changed dump to use fcntl(F_SETLK) style locking instead
170 of flock() when locking the dumpdates file. With the old
171 locking scheme, a local user having read rights on the
172 dumpdates file could be able to do a Denial of Service attack
173 on dump. In order to lock the dumpdates file with the new
174 scheme, the user would need to have write access on the file.
175 Thanks to Richard Johnson <Richard.Johnson3@ey.com> for
176 reporting the bug (originally a bugtraq post).
177
1782. Fixed interactive 'ls' which caused spurious errors warnings
179 about 'undefined filetypes' detected. Thanks to Jorgen Ostling
180 <jorgen_ostling@users.sourceforge.net> for reporting this
181 bug.
182
1833. Fixed dump's estimate when dealing with sparse inodes.
184
1854. Modified dump to allow setting a blocksize bigger than 32kB
186 (raised the limit to 1024kB), because newer hardware needs
187 this for proper operation. Thanks to Dirk Traenapp
188 <dtraenapp@users.sourceforge.net> for reporting this.
189
1905. Fixed a bug causing Dump to stop and report an error if an
191 inode number in the exclude file was followed by some amount
192 of whitespace. Thanks to Jeffrey Sofferin
193 <sofferin@users.sourceforge.net> for reporting this bug.
194
1956. Fixed a bug which caused restore, in some particular cases,
196 to ask some 'scary' questions and leave a bunch of RSTTMP
197 directories behind when restoring incremental tapes. Thanks
198 to Philippe Troin <phil@fifi.org> for reporting this bug and
199 providing the test cases.
200
2017. Changed the wording when inodes are excluded from dump:
202 replaced 'Added inode 7 to exclude list' with
203 'Excluding inode 7 (resize inode) from dump', as suggested
204 by Elliott Mitchell <ehem@m5p.com> in a Debian bug report.
205
206Changes between versions 0.4b30 and 0.4b31 (released July 30, 2002)
207===================================================================
208
2091. Fixed rmt open flags transmission (GNU's symbolic syntax over
210 rmt) which I broke in 0.4b29. Thanks to Eros Albertazzi
211 <eros@lamel.bo.cnr.it> for reporting the bug.
212
213Changes between versions 0.4b29 and 0.4b30 (released July 25, 2002)
214===================================================================
215
2161. Made dump print out the ext2 logical block number in case of a read
217 error, which can be given as an argument to debugfs' ncheck command,
218 in order to find out the affected inode. Added note about this
219 usage in dump's man page.
220
2212. Fixed a problem in restore when reading tapes written on big
222 endian machines with very old versions of dump. The patch was
223 contributed by George Helffrich <george@geology.bristol.ac.uk>.
224
2253. Fixed the tape length calculation when using large tapes
226 and compression. Thanks to Georg Lippold
227 <g_lippold@sourceforge.net> for reporting the bug.
228
2294. Added a new set of examples in dump_on_cd_2 directory, based
230 on dump_on_cd examples but somewhat enhanced, supporting DVD
231 media, and localized in english and german. Thanks to
232 Georg Lippold <g_lippold@sourceforge.net> for the new scripts.
233
2345. Made dump save 32 bit UID/GID. Internally, this was achieved
235 by switching from the old BSD inode format to the new BSD
236 inode format, which means that the tape format was changed.
237 However, since all restore versions out there should
238 transparently support both inode formats, the change should
239 have no side effects. Thanks to John Yu <jky@cs.bu.edu> for
240 reporting the bug.
241
2426. Fixed a lot of warnings in the code shown when compiling
243 with 'gcc -W'. Thanks to Matthias Andree
244 <matthias.andree@stud.uni-dortmund.de> for reporting this.
245
2467. Fixed a small markup bug in the dump man page. Thanks to
247 Eric S. Raymond <esr@minx.thyrsus.com> for submitting the
248 patch.
249
2508. Rewrote entirely the man pages using the tmac.an macro
251 package (Linux man page format) instead of the original BSD
252 format. They should be now cleaner and easier to modify.
253
254Changes between versions 0.4b28 and 0.4b29 (released June 8, 2002)
255==================================================================
256
2571. Fixed a problem in the rmt ioctl command, where ioctl's issued from
258 non Linux clients were misinterpreted. The description of the problem
259 (incompatible numbering in Linux mtio opcodes) is documented at
260 ftp://ftp.fokus.gmd.de/pub/unix/star/README.mtio . Thanks to
261