1 $Id: CHANGES,v 1.49 2000/03/08 10:51:29 stelian Exp $
3 Changes between versions 0.4b15 and 0.4b16 (released ?????????????)
4 ===================================================================
6 1. Fixed some several duplicate 'DUMP: DUMP:' in the
9 2. Corrected the estimation of blocks to dump. Note that
10 this is still wrong for large directory inodes, due
11 to the size of a BSD directory entry on the tape
12 (estimation is based on the size of the ext2 directory,
13 which is smaller because it doesn't contain the null
14 character at the end).
16 3. Made dump report the total number of MB written to
17 tape at the end of run. Thanks to W. Reilly Cooley
18 <wcooley@nakedape.cc> for the patch.
20 Changes between versions 0.4b14 and 0.4b15 (released March 2, 2000)
21 ===================================================================
23 1. Added a prompt command in interactive restore mode. Thanks
24 to Andreas Dilger <adilger@home.com> for the patch.
26 2. Fixed a buffer overflow problem in dump (caused by
27 not checking the size of the filesystem parameter).
28 Thanks to Kim Yong-jun <loveyou@hackerslab.org> for
29 reporting this on Bugtraq (and to several dump users
30 who forwarded me his mail).
32 3. Added the '-F script' option to dump in order to
33 launch a script at the end of each tape (to be used
34 with a tape changer, or to notify the sysadmin by
37 4. Fixed a bug in restore compare code caused by the changes
40 5. Fixed the treatment of options using the old BSD syntax
41 in both dump and restore.
43 Changes between versions 0.4b13 and 0.4b14 (released February 10, 2000)
44 =======================================================================
46 1. Fixed a bug in dump which may have caused invalid deleted
47 directories to be dumped out if they were deleted after the
48 mapping pass. This could occure on active filesystem and lead
49 to heap corruption (causing dump malfunction in many possible ways).
50 Thanks to Jan Sanislo <oystr@cs.washington.edu> for finding this
51 bug and submitting the patch.
53 2. Fixed the handling of the filesystem parameter in dump. A
54 '/mnt/disk' parameter caused the disk contents to be dumped,
55 but a '/mnt/disk/' parameter caused the mountpoint directory
56 to be dumped (generally an empty directory).
58 3. Improved the output of dump in order to tell which directory
59 it is currently dumping (when dumping a subtree).
61 4. Added the '-e' exclude inode option to dump. Thanks to
62 Isaac Chuang <ike@isl.stanford.edu> for contributing with the patch.
64 5. Added a REPORTING-BUGS file in order to provide a guide
65 on how to correctly report a bug in dump/restore.
67 6. Fixed a restore problem when restoring a hard link to an inode
68 having the immutable or append-only attribute set. Thanks to
69 Ambrose Li <acli@mingpaoxpress.com> for submitting the patch.
71 7. Fixed a compatibility problem between dumps made on little
72 endian machines (the format was correct) and big endian
73 machines (the format was incorrect). This fix break the
74 compatibility with the older dumps made on big endian
75 machines (sparc, m86k, ppc etc). For the first time in
76 linux dump's history (I believe), the dumps made by *BSD,
77 Linux/alpha, Linux/sparc and Linux/x86 are compatible,
78 so interchangeable. Thanks to Rob Cermak
79 <cermak@ahab.rutgers.edu> for submitting the bug and
80 helping me test the fix.
82 8. Fixed the way dump reports the remaining percent/time, if
83 the number of blocks actually dumped exceeds the estimated
84 number of blocks. Thanks to Jean-Paul van der Jagt
85 <jeanpaul@dutepp0.et.tudelft.nl> for reporting the bug.
87 Changes between versions 0.4b12 and 0.4b13 (released January 21, 2000)
88 ======================================================================
90 1. Small Y2K fix in the man pages :). Thanks to Bernhard Sadlowski
91 <sadlowsk@Mathematik.Uni-Bielefeld.DE> for reporting the bug.
93 2. Removed the requirement to build the RPM as root from the
94 spec file. Thanks to Christian Weisgerber
95 <naddy@mips.rhein-neckar.de> for submitting this.
97 3. Fixed a bug in dump related to the 'filetype' feature of ext2fs,
98 causing dump to block when dumping really huge filesystems.
99 Many thanks to Patrik Schindler <poc@pocnet.net> for
100 helping me find this bug.
102 4. Fixed the treatment for an interrupt signal when dump access
103 the remote tape through RSH. Thanks to Christian Weisgerber
104 <naddy@mips.rhein-neckar.de> for providing the patch.
106 5. Fixed a bug which was causing dump/restore to display
107 garbage characters instead of the remote host name.
109 Changes between versions 0.4b11 and 0.4b12 (released January 8, 2000)
110 =====================================================================
112 1. Small fix in the dump man page. Thanks to Thorsten Kukuk
113 <kukuk@suse.de> for submitting the patch.
115 2. Fix for the exit code when using the size estimate option of
116 dump. Thanks to Matti Taskinen <mkt@rni.helsinki.fi> for
117 submitting the patch.
119 3. Handle EINTR in atomical reads/writes in dump, which was causing
120 dump to fail on some systems. Thanks to Eric Jergensen
121 <eric@dvns.com> for reporting the bug and submitting the patch.
123 4. Handle more than 16 characters for the device names in dumpdates.
124 (up to 255 now). Thanks to Rainer Clasen <bj@ncc.cicely.de> for
125 tracking down the problem and proposing the solution.
127 5. Fixed a bug in dump which prevented the creation of the
128 dumpdates file when doing a 0-level dump without already
129 having a dumpdates file. Thanks to Patrik Schindler
130 <poc@pocnet.net> for reporting the bug.
132 6. Changed the way dump 'S' flag reports the size estimate
133 from number of blocks into bytes (making it compatible
134 with the Solaris version, and simplifying things for
135 amanda users). Thanks to Jason L Tibbitts III
136 <tibbs@math.uh.edu> for reporting the bug.
138 7. Fixed a compatibility problem in linux/alpha dump tape format.
139 Now the linux/alpha dump are (again) compatible with the
140 other dump formats. But this breaks compatibility with
141 older dumps made on alpha. Thanks to Mike Tibor
142 <tibor@lib.uaa.alaska.edu> for helping me in finding this bug.
144 Changes between versions 0.4b10 and 0.4b11 (released December 5, 1999)
145 ======================================================================
147 1. Added a '--enable-kerberos' to configure.
149 2. Added a 'S' option to dump which determines the amount of space
150 that is needed to perform the dump without actually doing it, similar
151 to the Sun's ufsdump 'S' option. Patch contributed by Rob Cermak
152 <cermak@ahab.rutgers.edu>.
154 3. Added a 'M' multi-volume option to dump and restore which enables
155 dumping to multiple files (useful when dumping to an ext2
156 partition to make several dump files in order to bypass the 2GB
157 file size limitation). The 'f' argument is treated as a prefix and
158 the output files will be named <prefix>001, <prefix>002 etc. With
159 the 'M' flag, restore automatically selects the right file without
160 asking to enter a new tape each time.
162 4. Fixed a memory leak which was causing dump to grow very big
163 (270MB when dumping a 10GB filesystem...). Thanks to Jason
164 Fearon <jasonf@netrider.org.au> for reporting the bug.
166 Changes between versions 0.4b9 and 0.4b10 (released November 21, 1999)
167 ======================================================================
169 1. Make configure test if the system glob routines support
170 extended syntax (ALTDIRFUNC). If not, use the internal glob
171 routines instead of system ones. Thanks to Bernhard Sadlowski
172 <sadlowsk@Mathematik.Uni-Bielefeld.DE> for reporting the bug
173 and helping me resolve this and other minor libc5 compiling
176 2. Fix a problem when dumping a ext2fs with the 'filetype'
177 feature enabled. Thanks to Patrick J. LoPresti
178 <patl@cag.lcs.mit.edu> for reporting the bug and to
179 Theodore Y. Ts'o <tytso@mit.edu> for providing the patch.
181 3. Made the nodump flag work on directories. A directory which
182 has the nodump flag gets never dumped, regardless of its
185 4. Integrate a patch from Jeremy Fitzhardinge <jeremy@goop.org>
186 which allows dump on an active ext3 filesystem. However, this
187 is a "quick and dirty" patch which enables backup of an ext3
188 filesystem through the ext2 compatibility (by ignoring the
189 NEEDS_RECOVERY bit). The journal file is not recognized and
190 it is dumped (it should not).
192 5. Test the superblock compatibility flags when dumping, in order
193 to be sure that we know how to deal with specific features.
195 Changes between versions 0.4b8 and 0.4b9 (released November 5, 1999)
196 ====================================================================
198 1. Use lchown instead of chown, fixing a possible security problem
199 when restoring symlinks (a malicious user could use this
200 to deliberately corrupt the ownership of important system files).
201 Thanks to Chris Siebenmann <cks@utcc.utoronto.ca> for detecting
202 this and providing the patch.
204 Changes between versions 0.4b7 and 0.4b8 (released November 3, 1999)
205 ====================================================================
207 1. Put dump sources under CVS, added Id tags in all files so
208 one can use 'ident' on binary files.
210 2. Added the dump/restore version in the usage text so one can
211 easily verify the version he is using.
213 3. Small patch from Nuno Oliveira <nuno@eq.uc.pt> which fixes
214 a va_start/va_end problem on linux-ppc (always call va_start
215 va_end in pairs each time we use a vararg function).
217 4. Added again the DT_* constants because old libc does not
218 contain them :(. Thanks to Eric Maisonobe <virnet@nat.fr>
219 for submitting the bug report.
221 5. Use ext2fs_llseek instead of llseek. With recent e2fsprogs
222 this should enable dumping big (huge) filesystems.
224 6. Added the RSH environment variable in order to be able to
225 use a rsh replacement like ssh when doing remote backups (and
226 bypass the security limitations of rcmd). Now you can do remote
227 backups without being root (or making dump setuid root).
229 7. Modified again the way dumpdates works. For incremental dumps,
230 we need to read dumpdates even if we are not using 'u' option.
231 Thanks to Bdale Garbee <bdale@gag.com> for his ideas on how
234 Changes between versions 0.4b6 and 0.4b7 (released October 8, 1999)
235 ===================================================================
237 1. Removed the 'k' flag from the restore 'about' text if kerberos
240 2. Prototyped (f)setflags from e2fsprogs and corrected the calls
241 to them (fsetflags takes a char*, setflags an open fd!).
243 3. (f)setflags is called only if the flags aren't empty. If the
244 file is a special file, a warning is printed, because changing
245 flags implies opening the device. Normally, a special file
246 should not have any flag... (Debian bug #29775, patch provided
247 by Abhijit Dasgupta <abhijit@ans.net>).
249 4. Made possible to dump a file system not mentioned in /etc/fstab.
250 (Debian bug #11904, patch provided by Eirik Fuller <eirik@netcom.com>).
252 5. Changed the default behaviour to not create dumpdates
253 unless 'u' option is specified. Removed the old "debian-patch"
254 which provided the same thing. (Debian bug #38136, #33818).
256 6. Removed all those dump*announce, since they were getting old...
258 7. Added warning messages if dumpdates does not exist and
259 when an inferior level dump does not exist (except for a level 0
262 8. Debugged the glob calls in interactive mode: restore used a
263 dirent struct which was different from the /usr/include/dirent.h
264 one (this used to work, is it a glibc2 change?), so none of the
265 compat glob (which used /usr/include/dirent.h) or the system glob
266 worked. Restore use now the system dirent (and the system
267 DT_* constants), which are compatible with BSD ones.
269 9. Added a configure flag (--with-dumpdatespath) to specify
270 the location of dumpdates file. By default, it is
273 10. Added the "AUTHOR" and "AVAILABILITY" sections and
274 included the current date/version in man pages.
276 11. Corrected the estimation of remaining time when
277 the operator doesn't change the tapes quickly enough. This
278 was an old bug, I thought I corrected it, and discovered
279 that in fact it was corrected in two different places, so
280 the results canceled each other...
282 Changes between versions 0.4b5 and 0.4b6 (released October 1, 1999)
283 ===================================================================
285 1. Integrated multiple patches from RedHat, Debian and SuSE:
287 - tweak dump/itime.c to not try to read dumpdates if the 'u' option
289 - several fixes in the man pages.
290 - update the default tape device to /dev/st0.
291 - many updates for Linux Alpha (byte ordering, size_t etc).
293 - use environment variable for TMPDIR (instead of /tmp).
294 - use sigjmp_buf instead of jmp_buf (RedHat bug #3260).
295 - workaround egcs bug (RedHat bugs #4281 and #2989).
296 - wire $(OPT) throughout Makefile's.
298 2. Upgrade the dump revision to 1, making possible to dump filesystems
299 made with e2fsprogs-1.15 or newer. Nothing seems to break...
301 3. Fix some compile warnings, prototype all functions.
303 4. Use glibc err/glob instead of internal compatibility
304 routines (only if available).
306 5. Fix a compile error on Linux 2.2.7 / libc5 (5.4.44) (patch provided
307 by Bernhard Sadlowski <sadlowsk@mathematik.uni-bielefeld.de>).
309 Changes between versions 0.4b4 and 0.4b5 (released September 22, 1999)
310 ======================================================================
312 1. Integrated the changes from FreeBSD-3.1-RELEASE
313 (mostly bug fixes, buffer overruns, dump has now an "automatic
314 tape length calculation" flag, dump/restore can use kerberos now
315 (this is NOT tested), use environment variables for TAPE and
318 2. Integrated three RedHat patches ("glibc", "kernel" and "bread" patches)
320 3. Corrected a bug in restore when using 'C' option with multi-volumes
321 tapes (files splited accros two tapes give "size changed" errors
324 4. Corrected the long standing bug when dumping multiple tapes.
325 This works for me, needs further testing.
327 Changes between versions 0.4b3 and 0.4b4 (released January 17, 1997)
328 ====================================================================
330 1. Dump now runs correctly on kernels 2.1.x
331 Fix made by Gerald Peters <gapeters@worldnet.att.net>
333 Changes between versions 0.4b2 and 0.4b3
334 ========================================
336 1. Use realpath() if available
340 Changes between versions 0.4b1 and 0.4b2
341 ========================================
343 1. Fixed the bug fix from Greg Lutz (I had made a mistake when integrating
346 2. Fixed restore to make it able to read FreeBSD 2.x dumps again
348 3. Fixed configure.in to correctly handle --enable-rmt
350 Changes between versions 0.3 and 0.4b1
351 ======================================
353 1. Integrated the changes from 4.4BSD-Lite2
355 2. Integrated the patches from Debian and Red Hat
357 3. Portability changes: use the __u32, __u16, __s32, and __s16 types
359 4. Changed dump to use the Ext2fs library to get block addresses. This
360 should solve the endianness problem on SparcLinux.
362 5. Created a configure.in file (shamelessly stolen from the e2fsprogs
363 distribution's one) to use autoconf
365 6. Fixed a few minor bugs
367 Changes between versions 0.2e and 0.2f
368 ======================================
370 1. Added the creation of named pipes (fifos) in restore.
372 2. Added the -N flag in the restore manual page.
374 3. Added the file kernel.patch which contains the llseek() optimization
375 patch for 1.2.x kernels.
377 4. Fixed a bug in the restoration of symbolic links: owner and group were
380 5. Integrated some changes from FreeBSD 2.2.
382 6. Added a call to ftruncate() after restoring each file to restore
383 correctly files ending by a hole.
385 Changes between versions 0.2d and 0.2e
386 ======================================
388 1. Fixed a bug in the "set owner/mode" process. Every file was restored
389 with owner = root (0) and group = root/wheel/whatever (0).
391 Changes between versions 0.2c and 0.2d
392 ======================================
394 1. Dump is now able to backup 2GB+ filesystems.
396 2. Dump and restore can now be linked as static binaries.
398 Changes between versions 0.2b and 0.2c
399 ======================================
401 1. Fixed a bug when dumping ``slow'' (i.e. normal) symbolic links.
403 Changes between versions 0.2a and 0.2b
404 ======================================
406 1. Really fixed the bug that I should have corrected in 0.2a.
408 2. Enabled optimization again.
410 Changes between versions 0.2 and 0.2a
411 =====================================
413 1. Disabled the optimization during compilation.
415 Changes between versions 0.1 and 0.2
416 ====================================
418 1. Fixed a bug in fstab.c which caused a null pointer to be stored in
419 the fs_type field (actually, I modified the file fstab.c to make it
420 use the mntent functions).
422 2. Dump and restore now use a 4.3 BSD compatible dump format. Backups
423 made by dump should be readable by the BSD restore and backups made
424 by the BSD dump should be readable by restore. Unfortunately, this
425 means that the dump format has changed between version 0.1 and version
428 3. Dump is now able to backup a subtree, it is no longer limited to whole
429 filesystems like the BSD version.
431 4. Dump now uses ext2_llseek() so it is able to backup filesystems bigger
434 Changes between versions 0.0 and 0.1
435 ====================================
437 1. Now create links rdump and rrestore during the `make install' step.
439 2. Linux port specific bugs added to the manual pages
441 3. Incorrect estimation of the number of tapes blocks fixed when doing
444 4. Better ls-like format in restore in interactive mode.