]> git.wh0rd.org - dump.git/blob - CHANGES
Y2K bug in man pages.
[dump.git] / CHANGES
1 $Id: CHANGES,v 1.31 2000/01/09 23:37:01 tiniou Exp $
2
3 Changes between versions 0.4b12 and 0.4b13 (released ???????????????)
4 =====================================================================
5
6 1. Small Y2K fix in the man pages :). Thanks to Bernhard Sadlowski
7 <sadlowsk@Mathematik.Uni-Bielefeld.DE> for reporting the bug.
8
9 Changes between versions 0.4b11 and 0.4b12 (released January 8, 2000)
10 =====================================================================
11
12 1. Small fix in the dump man page. Thanks to Thorsten Kukuk
13 <kukuk@suse.de> for submitting the patch.
14
15 2. Fix for the exit code when using the size estimate option of
16 dump. Thanks to Matti Taskinen <mkt@rni.helsinki.fi> for
17 submitting the patch.
18
19 3. Handle EINTR in atomical reads/writes in dump, which was causing
20 dump to fail on some systems. Thanks to Eric Jergensen
21 <eric@dvns.com> for reporting the bug and submitting the patch.
22
23 4. Handle more than 16 characters for the device names in dumpdates.
24 (up to 255 now). Thanks to Rainer Clasen <bj@ncc.cicely.de> for
25 tracking down the problem and proposing the solution.
26
27 5. Fixed a bug in dump which prevented the creation of the
28 dumpdates file when doing a 0-level dump without already
29 having a dumpdates file. Thanks to Patrik Schindler
30 <poc@pocnet.net> for reporting the bug.
31
32 6. Changed the way dump 'S' flag reports the size estimate
33 from number of blocks into bytes (making it compatible
34 with the Solaris version, and simplifying things for
35 amanda users). Thanks to Jason L Tibbitts III
36 <tibbs@math.uh.edu> for reporting the bug.
37
38 7. Fixed a compatibility problem in linux/alpha dump tape format.
39 Now the linux/alpha dump are (again) compatible with the
40 other dump formats. But this breaks compatibility with
41 older dumps made on alpha. Thanks to Mike Tibor
42 <tibor@lib.uaa.alaska.edu> for helping me in finding this bug.
43
44 Changes between versions 0.4b10 and 0.4b11 (released December 5, 1999)
45 ======================================================================
46
47 1. Added a '--enable-kerberos' to configure.
48
49 2. Added a 'S' option to dump which determines the amount of space
50 that is needed to perform the dump without actually doing it, similar
51 to the Sun's ufsdump 'S' option. Patch contributed by Rob Cermak
52 <cermak@ahab.rutgers.edu>.
53
54 3. Added a 'M' multi-volume option to dump and restore which enables
55 dumping to multiple files (useful when dumping to an ext2
56 partition to make several dump files in order to bypass the 2GB
57 file size limitation). The 'f' argument is treated as a prefix and
58 the output files will be named <prefix>001, <prefix>002 etc. With
59 the 'M' flag, restore automatically selects the right file without
60 asking to enter a new tape each time.
61
62 4. Fixed a memory leak which was causing dump to grow very big
63 (270MB when dumping a 10GB filesystem...). Thanks to Jason
64 Fearon <jasonf@netrider.org.au> for reporting the bug.
65
66 Changes between versions 0.4b9 and 0.4b10 (released November 21, 1999)
67 ======================================================================
68
69 1. Make configure test if the system glob routines support
70 extended syntax (ALTDIRFUNC). If not, use the internal glob
71 routines instead of system ones. Thanks to Bernhard Sadlowski
72 <sadlowsk@Mathematik.Uni-Bielefeld.DE> for reporting the bug
73 and helping me resolve this and other minor libc5 compiling
74 glitches.
75
76 2. Fix a problem when dumping a ext2fs with the 'filetype'
77 feature enabled. Thanks to Patrick J. LoPresti
78 <patl@cag.lcs.mit.edu> for reporting the bug and to
79 Theodore Y. Ts'o <tytso@mit.edu> for providing the patch.
80
81 3. Made the nodump flag work on directories. A directory which
82 has the nodump flag gets never dumped, regardless of its
83 contents.
84
85 4. Integrate a patch from Jeremy Fitzhardinge <jeremy@goop.org>
86 which allows dump on an active ext3 filesystem. However, this
87 is a "quick and dirty" patch which enables backup of an ext3
88 filesystem through the ext2 compatibility (by ignoring the
89 NEEDS_RECOVERY bit). The journal file is not recognized and
90 it is dumped (it should not).
91
92 5. Test the superblock compatibility flags when dumping, in order
93 to be sure that we know how to deal with specific features.
94
95 Changes between versions 0.4b8 and 0.4b9 (released November 5, 1999)
96 ====================================================================
97
98 1. Use lchown instead of chown, fixing a possible security problem
99 when restoring symlinks (a malicious user could use this
100 to deliberately corrupt the ownership of important system files).
101 Thanks to Chris Siebenmann <cks@utcc.utoronto.ca> for detecting
102 this and providing the patch.
103
104 Changes between versions 0.4b7 and 0.4b8 (released November 3, 1999)
105 ====================================================================
106
107 1. Put dump sources under CVS, added Id tags in all files so
108 one can use 'ident' on binary files.
109
110 2. Added the dump/restore version in the usage text so one can
111 easily verify the version he is using.
112
113 3. Small patch from Nuno Oliveira <nuno@eq.uc.pt> which fixes
114 a va_start/va_end problem on linux-ppc (always call va_start
115 va_end in pairs each time we use a vararg function).
116
117 4. Added again the DT_* constants because old libc does not
118 contain them :(. Thanks to Eric Maisonobe <virnet@nat.fr>
119 for submitting the bug report.
120
121 5. Use ext2fs_llseek instead of llseek. With recent e2fsprogs
122 this should enable dumping big (huge) filesystems.
123
124 6. Added the RSH environment variable in order to be able to
125 use a rsh replacement like ssh when doing remote backups (and
126 bypass the security limitations of rcmd). Now you can do remote
127 backups without being root (or making dump setuid root).
128
129 7. Modified again the way dumpdates works. For incremental dumps,
130 we need to read dumpdates even if we are not using 'u' option.
131 Thanks to Bdale Garbee <bdale@gag.com> for his ideas on how
132 this should work.
133
134 Changes between versions 0.4b6 and 0.4b7 (released October 8, 1999)
135 ===================================================================
136
137 1. Removed the 'k' flag from the restore 'about' text if kerberos
138 was not compiled in.
139
140 2. Prototyped (f)setflags from e2fsprogs and corrected the calls
141 to them (fsetflags takes a char*, setflags an open fd!).
142
143 3. (f)setflags is called only if the flags aren't empty. If the
144 file is a special file, a warning is printed, because changing
145 flags implies opening the device. Normally, a special file
146 should not have any flag... (Debian bug #29775, patch provided
147 by Abhijit Dasgupta <abhijit@ans.net>).
148
149 4. Made possible to dump a file system not mentioned in /etc/fstab.
150 (Debian bug #11904, patch provided by Eirik Fuller <eirik@netcom.com>).
151
152 5. Changed the default behaviour to not create dumpdates
153 unless 'u' option is specified. Removed the old "debian-patch"
154 which provided the same thing. (Debian bug #38136, #33818).
155
156 6. Removed all those dump*announce, since they were getting old...
157
158 7. Added warning messages if dumpdates does not exist and
159 when an inferior level dump does not exist (except for a level 0
160 dump).
161
162 8. Debugged the glob calls in interactive mode: restore used a
163 dirent struct which was different from the /usr/include/dirent.h
164 one (this used to work, is it a glibc2 change?), so none of the
165 compat glob (which used /usr/include/dirent.h) or the system glob
166 worked. Restore use now the system dirent (and the system
167 DT_* constants), which are compatible with BSD ones.
168
169 9. Added a configure flag (--with-dumpdatespath) to specify
170 the location of dumpdates file. By default, it is
171 /etc/dumpdates.
172
173 10. Added the "AUTHOR" and "AVAILABILITY" sections and
174 included the current date/version in man pages.
175
176 11. Corrected the estimation of remaining time when
177 the operator doesn't change the tapes quickly enough. This
178 was an old bug, I thought I corrected it, and discovered
179 that in fact it was corrected in two different places, so
180 the results canceled each other...
181
182 Changes between versions 0.4b5 and 0.4b6 (released October 1, 1999)
183 ===================================================================
184
185 1. Integrated multiple patches from RedHat, Debian and SuSE:
186
187 - tweak dump/itime.c to not try to read dumpdates if the 'u' option
188 isn't specified.
189 - several fixes in the man pages.
190 - update the default tape device to /dev/st0.
191 - many updates for Linux Alpha (byte ordering, size_t etc).
192 - buffer overruns.
193 - use environment variable for TMPDIR (instead of /tmp).
194 - use sigjmp_buf instead of jmp_buf (RedHat bug #3260).
195 - workaround egcs bug (RedHat bugs #4281 and #2989).
196 - wire $(OPT) throughout Makefile's.
197
198 2. Upgrade the dump revision to 1, making possible to dump filesystems
199 made with e2fsprogs-1.15 or newer. Nothing seems to break...
200
201 3. Fix some compile warnings, prototype all functions.
202
203 4. Use glibc err/glob instead of internal compatibility
204 routines (only if available).
205
206 5. Fix a compile error on Linux 2.2.7 / libc5 (5.4.44) (patch provided
207 by Bernhard Sadlowski <sadlowsk@mathematik.uni-bielefeld.de>).
208
209 Changes between versions 0.4b4 and 0.4b5 (released September 22, 1999)
210 ======================================================================
211
212 1. Integrated the changes from FreeBSD-3.1-RELEASE
213 (mostly bug fixes, buffer overruns, dump has now an "automatic
214 tape length calculation" flag, dump/restore can use kerberos now
215 (this is NOT tested), use environment variables for TAPE and
216 RMT etc.).
217
218 2. Integrated three RedHat patches ("glibc", "kernel" and "bread" patches)
219
220 3. Corrected a bug in restore when using 'C' option with multi-volumes
221 tapes (files splited accros two tapes give "size changed" errors
222 when comparing).
223
224 4. Corrected the long standing bug when dumping multiple tapes.
225 This works for me, needs further testing.
226
227 Changes between versions 0.4b3 and 0.4b4 (released January 17, 1997)
228 ====================================================================
229
230 1. Dump now runs correctly on kernels 2.1.x
231 Fix made by Gerald Peters <gapeters@worldnet.att.net>
232
233 Changes between versions 0.4b2 and 0.4b3
234 ========================================
235
236 1. Use realpath() if available
237
238 2. Report statistics
239
240 Changes between versions 0.4b1 and 0.4b2
241 ========================================
242
243 1. Fixed the bug fix from Greg Lutz (I had made a mistake when integrating
244 the patch)
245
246 2. Fixed restore to make it able to read FreeBSD 2.x dumps again
247
248 3. Fixed configure.in to correctly handle --enable-rmt
249
250 Changes between versions 0.3 and 0.4b1
251 ======================================
252
253 1. Integrated the changes from 4.4BSD-Lite2
254
255 2. Integrated the patches from Debian and Red Hat
256
257 3. Portability changes: use the __u32, __u16, __s32, and __s16 types
258
259 4. Changed dump to use the Ext2fs library to get block addresses. This
260 should solve the endianness problem on SparcLinux.
261
262 5. Created a configure.in file (shamelessly stolen from the e2fsprogs
263 distribution's one) to use autoconf
264
265 6. Fixed a few minor bugs
266
267 Changes between versions 0.2e and 0.2f
268 ======================================
269
270 1. Added the creation of named pipes (fifos) in restore.
271
272 2. Added the -N flag in the restore manual page.
273
274 3. Added the file kernel.patch which contains the llseek() optimization
275 patch for 1.2.x kernels.
276
277 4. Fixed a bug in the restoration of symbolic links: owner and group were
278 not restored.
279
280 5. Integrated some changes from FreeBSD 2.2.
281
282 6. Added a call to ftruncate() after restoring each file to restore
283 correctly files ending by a hole.
284
285 Changes between versions 0.2d and 0.2e
286 ======================================
287
288 1. Fixed a bug in the "set owner/mode" process. Every file was restored
289 with owner = root (0) and group = root/wheel/whatever (0).
290
291 Changes between versions 0.2c and 0.2d
292 ======================================
293
294 1. Dump is now able to backup 2GB+ filesystems.
295
296 2. Dump and restore can now be linked as static binaries.
297
298 Changes between versions 0.2b and 0.2c
299 ======================================
300
301 1. Fixed a bug when dumping ``slow'' (i.e. normal) symbolic links.
302
303 Changes between versions 0.2a and 0.2b
304 ======================================
305
306 1. Really fixed the bug that I should have corrected in 0.2a.
307
308 2. Enabled optimization again.
309
310 Changes between versions 0.2 and 0.2a
311 =====================================
312
313 1. Disabled the optimization during compilation.
314
315 Changes between versions 0.1 and 0.2
316 ====================================
317
318 1. Fixed a bug in fstab.c which caused a null pointer to be stored in
319 the fs_type field (actually, I modified the file fstab.c to make it
320 use the mntent functions).
321
322 2. Dump and restore now use a 4.3 BSD compatible dump format. Backups
323 made by dump should be readable by the BSD restore and backups made
324 by the BSD dump should be readable by restore. Unfortunately, this
325 means that the dump format has changed between version 0.1 and version
326 0.2 :-(
327
328 3. Dump is now able to backup a subtree, it is no longer limited to whole
329 filesystems like the BSD version.
330
331 4. Dump now uses ext2_llseek() so it is able to backup filesystems bigger
332 than 2 GB.
333
334 Changes between versions 0.0 and 0.1
335 ====================================
336
337 1. Now create links rdump and rrestore during the `make install' step.
338
339 2. Linux port specific bugs added to the manual pages
340
341 3. Incorrect estimation of the number of tapes blocks fixed when doing
342 incremental backups.
343
344 4. Better ls-like format in restore in interactive mode.