1 $Id: CHANGES,v 1.73 2000/08/19 23:48:10 stelian Exp $
3 Changes between versions 0.4b17 and 0.4b19 (released ?????????????)
4 ===================================================================
6 1. Fixed the signal handling in dump (which I broke in 0.4b17)
7 which was causing several strange dump failures (dump
8 hanged or segmentation faults etc).
10 2. Specified the default blocksize in the dump man page.
12 3. Changed two info messages of restore to be written on stdout
13 instead of stderr in order to leave stderr only for errors
14 or warnings. Thanks to Stephen Atwell
15 <satwell@urbana.css.mot.com> for the suggestion.
17 4. Corrected an off by one calculation which prevented
18 dumping a directory having a 1 character name length.
19 Thanks to Bernhard Erdmann <bernhard.erdmann@gmx.de>
20 for reporting the bug.
22 5. Reinforce dump in order to allow only level 0 and no
23 -u option when dumping a subdirectory, and document
24 this in the man page. Thanks to Bernhard Erdmann
25 <bernhard.erdmann@gmx.de> for reporting the bug.
27 Changes between versions 0.4b17 and 0.4b18 (released June 30, 2000)
28 ===================================================================
30 1. Fixed a potential buffer overflow in restore. Thanks
31 to Stan Bubrouski <satan@fastdial.net> for reporting
34 2. Fixed a readline-related bug which prevented
35 'cat DUMPFILE | restore -i -f -' from working. Thanks
36 to Charles Karney <karney@users.sourceforge.net>
39 3. Changed a few "panic" into "exit", causing restore to
40 be more stable against some attacks (like the last one
41 reported on Bugtraq, although the last version of restore
42 was not vulnerable - just dumped core). Thanks to
43 Andreas Hasenack <andreas@conectiva.com.br> for reporting
46 4. Removed the suid-root bit on dump and restore in the
47 default build (and generated RPMs). It should be safer
48 now. Users who need the suid-root capabilities in order
49 to make network backups should read first the man page
50 of dump and enable the suid bit manually.
52 5. Added -ltermcap to the compile parameters for restore
53 when using readline support, in order to make the compile
54 process work on some systems (SuSE ?). Thanks to
55 Patrik Schindler <poc@pocnet.net> for reporting the bug.
57 Changes between versions 0.4b16 and 0.4b17 (released June 1st, 2000)
58 ====================================================================
60 1. The -F script is called now *only* at the end of a tape,
61 not at the end of the dump. Thanks to Christian Haul
62 <haul@informatik.tu-darmstadt.de> for the bug report.
64 Normally, the device name and the current volume number
65 are passed on the command line of the script. However,
66 if you want the old style script (with no arguments
67 passed on the command line), you can enable it in
68 configure with the --enable-oldstylefscript.
70 2. Use posix signal handling to preserve dump functionality
71 with libc5. Thanks to Jeff Johnson <jbj@redhat.com> for
74 3. Made the exit code of restore in case of a 'C'ompare
75 command reflect the result of the compare. An exit status
76 of 0 means the dump archive is correct, 1 means tape errors,
77 2 means that some files were modified. Thanks to Kenneth Porter
78 <shiva@well.com> for the suggestion.
80 4. Made (finally) quotes work in interactive restore.
82 5. Small fixes in order to allow dump to compile with a
83 really old e2fsprogs version. Thanks to Ian Zimmerman
84 <itz@speakeasy.org> for the bug report.
86 6. Add GNU readline capabilities to interactive restore.
87 Use configure's --enable-readline flag to enable this feature.
88 Thanks to Patrik Schindler <poc@pocnet.net> for the
91 7. Do the compare on the fly in restore 'C' mode (this will
92 allow not to exhaust the available /tmp space when
93 ccmparing large files). Thanks to Kenneth Porter
94 <shiva@well.com> for the suggestion.
96 Changes between versions 0.4b15 and 0.4b16 (released March 11, 2000)
97 ====================================================================
99 1. Fixed some several duplicate 'DUMP: DUMP:' in the
102 2. Corrected the estimation of blocks to dump. Note that
103 this is still wrong for large directory inodes, due
104 to the size of a BSD directory entry on the tape
105 (estimation is based on the size of the ext2 directory,
106 which is smaller because it doesn't contain the null
107 character at the end).
109 3. Made dump report the total number of MB written to
110 tape at the end of run. Thanks to W. Reilly Cooley
111 <wcooley@nakedape.cc> for the patch.
113 4. Added the -X option to restore giving the possibility
114 to read the names of the files to be extracted/listed
115 from a text file (in addition of the command line).
116 Thanks to Dejan Muhamedagic <dejan@quant-x.com> for the
119 5. Added the device name and the current volume number
120 as arguments to the end of tape script (dump -F option).
122 6. Made the multi-volume dump work again (after having
123 broken it in 0.4b15).
125 Changes between versions 0.4b14 and 0.4b15 (released March 2, 2000)
126 ===================================================================
128 1. Added a prompt command in interactive restore mode. Thanks
129 to Andreas Dilger <adilger@home.com> for the patch.
131 2. Fixed a buffer overflow problem in dump (caused by
132 not checking the size of the filesystem parameter).
133 Thanks to Kim Yong-jun <loveyou@hackerslab.org> for
134 reporting this on Bugtraq (and to several dump users
135 who forwarded me his mail).
137 3. Added the '-F script' option to dump in order to
138 launch a script at the end of each tape (to be used
139 with a tape changer, or to notify the sysadmin by
142 4. Fixed a bug in restore compare code caused by the changes
145 5. Fixed the treatment of options using the old BSD syntax
146 in both dump and restore.
148 Changes between versions 0.4b13 and 0.4b14 (released February 10, 2000)
149 =======================================================================
151 1. Fixed a bug in dump which may have caused invalid deleted
152 directories to be dumped out if they were deleted after the
153 mapping pass. This could occure on active filesystem and lead
154 to heap corruption (causing dump malfunction in many possible ways).
155 Thanks to Jan Sanislo <oystr@cs.washington.edu> for finding this
156 bug and submitting the patch.
158 2. Fixed the handling of the filesystem parameter in dump. A
159 '/mnt/disk' parameter caused the disk contents to be dumped,
160 but a '/mnt/disk/' parameter caused the mountpoint directory
161 to be dumped (generally an empty directory).
163 3. Improved the output of dump in order to tell which directory
164 it is currently dumping (when dumping a subtree).
166 4. Added the '-e' exclude inode option to dump. Thanks to
167 Isaac Chuang <ike@isl.stanford.edu> for contributing with the patch.
169 5. Added a REPORTING-BUGS file in order to provide a guide
170 on how to correctly report a bug in dump/restore.
172 6. Fixed a restore problem when restoring a hard link to an inode
173 having the immutable or append-only attribute set. Thanks to
174 Ambrose Li <acli@mingpaoxpress.com> for submitting the patch.
176 7. Fixed a compatibility problem between dumps made on little
177 endian machines (the format was correct) and big endian
178 machines (the format was incorrect). This fix break the
179 compatibility with the older dumps made on big endian
180 machines (sparc, m86k, ppc etc). For the first time in
181 linux dump's history (I believe), the dumps made by *BSD,
182 Linux/alpha, Linux/sparc and Linux/x86 are compatible,
183 so interchangeable. Thanks to Rob Cermak
184 <cermak@ahab.rutgers.edu> for submitting the bug and
185 helping me test the fix.
187 8. Fixed the way dump reports the remaining percent/time, if
188 the number of blocks actually dumped exceeds the estimated
189 number of blocks. Thanks to Jean-Paul van der Jagt
190 <jeanpaul@dutepp0.et.tudelft.nl> for reporting the bug.
192 Changes between versions 0.4b12 and 0.4b13 (released January 21, 2000)
193 ======================================================================
195 1. Small Y2K fix in the man pages :). Thanks to Bernhard Sadlowski
196 <sadlowsk@Mathematik.Uni-Bielefeld.DE> for reporting the bug.
198 2. Removed the requirement to build the RPM as root from the
199 spec file. Thanks to Christian Weisgerber
200 <naddy@mips.rhein-neckar.de> for submitting this.
202 3. Fixed a bug in dump related to the 'filetype' feature of ext2fs,
203 causing dump to block when dumping really huge filesystems.
204 Many thanks to Patrik Schindler <poc@pocnet.net> for
205 helping me find this bug.
207 4. Fixed the treatment for an interrupt signal when dump access
208 the remote tape through RSH. Thanks to Christian Weisgerber
209 <naddy@mips.rhein-neckar.de> for providing the patch.
211 5. Fixed a bug which was causing dump/restore to display
212 garbage characters instead of the remote host name.
214 Changes between versions 0.4b11 and 0.4b12 (released January 8, 2000)
215 =====================================================================
217 1. Small fix in the dump man page. Thanks to Thorsten Kukuk
218 <kukuk@suse.de> for submitting the patch.
220 2. Fix for the exit code when using the size estimate option of
221 dump. Thanks to Matti Taskinen <mkt@rni.helsinki.fi> for
222 submitting the patch.
224 3. Handle EINTR in atomical reads/writes in dump, which was causing
225 dump to fail on some systems. Thanks to Eric Jergensen
226 <eric@dvns.com> for reporting the bug and submitting the patch.
228 4. Handle more than 16 characters for the device names in dumpdates.
229 (up to 255 now). Thanks to Rainer Clasen <bj@ncc.cicely.de> for
230 tracking down the problem and proposing the solution.
232 5. Fixed a bug in dump which prevented the creation of the
233 dumpdates file when doing a 0-level dump without already
234 having a dumpdates file. Thanks to Patrik Schindler
235 <poc@pocnet.net> for reporting the bug.
237 6. Changed the way dump 'S' flag reports the size estimate
238 from number of blocks into bytes (making it compatible
239 with the Solaris version, and simplifying things for
240 amanda users). Thanks to Jason L Tibbitts III
241 <tibbs@math.uh.edu> for reporting the bug.
243 7. Fixed a compatibility problem in linux/alpha dump tape format.
244 Now the linux/alpha dump are (again) compatible with the
245 other dump formats. But this breaks compatibility with
246 older dumps made on alpha. Thanks to Mike Tibor
247 <tibor@lib.uaa.alaska.edu> for helping me in finding this bug.
249 Changes between versions 0.4b10 and 0.4b11 (released December 5, 1999)
250 ======================================================================
252 1. Added a '--enable-kerberos' to configure.
254 2. Added a 'S' option to dump which determines the amount of space
255 that is needed to perform the dump without actually doing it, similar
256 to the Sun's ufsdump 'S' option. Patch contributed by Rob Cermak
257 <cermak@ahab.rutgers.edu>.
259 3. Added a 'M' multi-volume option to dump and restore which enables
260 dumping to multiple files (useful when dumping to an ext2
261 partition to make several dump files in order to bypass the 2GB
262 file size limitation). The 'f' argument is treated as a prefix and
263 the output files will be named <prefix>001, <prefix>002 etc. With
264 the 'M' flag, restore automatically selects the right file without
265 asking to enter a new tape each time.
267 4. Fixed a memory leak which was causing dump to grow very big
268 (270MB when dumping a 10GB filesystem...). Thanks to Jason
269 Fearon <jasonf@netrider.org.au> for reporting the bug.
271 Changes between versions 0.4b9 and 0.4b10 (released November 21, 1999)
272 ======================================================================
274 1. Make configure test if the system glob routines support
275 extended syntax (ALTDIRFUNC). If not, use the internal glob
276 routines instead of system ones. Thanks to Bernhard Sadlowski
277 <sadlowsk@Mathematik.Uni-Bielefeld.DE> for reporting the bug
278 and helping me resolve this and other minor libc5 compiling
281 2. Fix a problem when dumping a ext2fs with the 'filetype'
282 feature enabled. Thanks to Patrick J. LoPresti
283 <patl@cag.lcs.mit.edu> for reporting the bug and to
284 Theodore Y. Ts'o <tytso@mit.edu> for providing the patch.
286 3. Made the nodump flag work on directories. A directory which
287 has the nodump flag gets never dumped, regardless of its
290 4. Integrate a patch from Jeremy Fitzhardinge <jeremy@goop.org>
291 which allows dump on an active ext3 filesystem. However, this
292 is a "quick and dirty" patch which enables backup of an ext3
293 filesystem through the ext2 compatibility (by ignoring the
294 NEEDS_RECOVERY bit). The journal file is not recognized and
295 it is dumped (it should not).
297 5. Test the superblock compatibility flags when dumping, in order
298 to be sure that we know how to deal with specific features.
300 Changes between versions 0.4b8 and 0.4b9 (released November 5, 1999)
301 ====================================================================
303 1. Use lchown instead of chown, fixing a possible security problem
304 when restoring symlinks (a malicious user could use this
305 to deliberately corrupt the ownership of important system files).
306 Thanks to Chris Siebenmann <cks@utcc.utoronto.ca> for detecting
307 this and providing the patch.
309 Changes between versions 0.4b7 and 0.4b8 (released November 3, 1999)
310 ====================================================================
312 1. Put dump sources under CVS, added Id tags in all files so
313 one can use 'ident' on binary files.
315 2. Added the dump/restore version in the usage text so one can
316 easily verify the version he is using.
318 3. Small patch from Nuno Oliveira <nuno@eq.uc.pt> which fixes
319 a va_start/va_end problem on linux-ppc (always call va_start
320 va_end in pairs each time we use a vararg function).
322 4. Added again the DT_* constants because old libc does not
323 contain them :(. Thanks to Eric Maisonobe <virnet@nat.fr>
324 for submitting the bug report.
326 5. Use ext2fs_llseek instead of llseek. With recent e2fsprogs
327 this should enable dumping big (huge) filesystems.
329 6. Added the RSH environment variable in order to be able to
330 use a rsh replacement like ssh when doing remote backups (and
331 bypass the security limitations of rcmd). Now you can do remote
332 backups without being root (or making dump setuid root).
334 7. Modified again the way dumpdates works. For incremental dumps,
335 we need to read dumpdates even if we are not using 'u' option.
336 Thanks to Bdale Garbee <bdale@gag.com> for his ideas on how
339 Changes between versions 0.4b6 and 0.4b7 (released October 8, 1999)
340 ===================================================================
342 1. Removed the 'k' flag from the restore 'about' text if kerberos
345 2. Prototyped (f)setflags from e2fsprogs and corrected the calls
346 to them (fsetflags takes a char*, setflags an open fd!).
348 3. (f)setflags is called only if the flags aren't empty. If the
349 file is a special file, a warning is printed, because changing
350 flags implies opening the device. Normally, a special file
351 should not have any flag... (Debian bug #29775, patch provided
352 by Abhijit Dasgupta <abhijit@ans.net>).
354 4. Made possible to dump a file system not mentioned in /etc/fstab.
355 (Debian bug #11904, patch provided by Eirik Fuller <eirik@netcom.com>).
357 5. Changed the default behaviour to not create dumpdates
358 unless 'u' option is specified. Removed the old "debian-patch"
359 which provided the same thing. (Debian bug #38136, #33818).
361 6. Removed all those dump*announce, since they were getting old...
363 7. Added warning messages if dumpdates does not exist and
364 when an inferior level dump does not exist (except for a level 0
367 8. Debugged the glob calls in interactive mode: restore used a
368 dirent struct which was different from the /usr/include/dirent.h
369 one (this used to work, is it a glibc2 change?), so none of the
370 compat glob (which used /usr/include/dirent.h) or the system glob
371 worked. Restore use now the system dirent (and the system
372 DT_* constants), which are compatible with BSD ones.
374 9. Added a configure flag (--with-dumpdatespath) to specify
375 the location of dumpdates file. By default, it is
378 10. Added the "AUTHOR" and "AVAILABILITY" sections and
379 included the current date/version in man pages.
381 11. Corrected the estimation of remaining time when
382 the operator doesn't change the tapes quickly enough. This
383 was an old bug, I thought I corrected it, and discovered
384 that in fact it was corrected in two different places, so
385 the results canceled each other...
387 Changes between versions 0.4b5 and 0.4b6 (released October 1, 1999)
388 ===================================================================
390 1. Integrated multiple patches from RedHat, Debian and SuSE:
392 - tweak dump/itime.c to not try to read dumpdates if the 'u' option
394 - several fixes in the man pages.
395 - update the default tape device to /dev/st0.
396 - many updates for Linux Alpha (byte ordering, size_t etc).
398 - use environment variable for TMPDIR (instead of /tmp).
399 - use sigjmp_buf instead of jmp_buf (RedHat bug #3260).
400 - workaround egcs bug (RedHat bugs #4281 and #2989).
401 - wire $(OPT) throughout Makefile's.
403 2. Upgrade the dump revision to 1, making possible to dump filesystems
404 made with e2fsprogs-1.15 or newer. Nothing seems to break...
406 3. Fix some compile warnings, prototype all functions.
408 4. Use glibc err/glob instead of internal compatibility
409 routines (only if available).
411 5. Fix a compile error on Linux 2.2.7 / libc5 (5.4.44) (patch provided
412 by Bernhard Sadlowski <sadlowsk@mathematik.uni-bielefeld.de>).
414 Changes between versions 0.4b4 and 0.4b5 (released September 22, 1999)
415 ======================================================================
417 1. Integrated the changes from FreeBSD-3.1-RELEASE
418 (mostly bug fixes, buffer overruns, dump has now an "automatic
419 tape length calculation" flag, dump/restore can use kerberos now
420 (this is NOT tested), use environment variables for TAPE and
423 2. Integrated three RedHat patches ("glibc", "kernel" and "bread" patches)
425 3. Corrected a bug in restore when using 'C' option with multi-volumes
426 tapes (files splited accros two tapes give "size changed" errors
429 4. Corrected the long standing bug when dumping multiple tapes.
430 This works for me, needs further testing.
432 Changes between versions 0.4b3 and 0.4b4 (released January 17, 1997)
433 ====================================================================
435 1. Dump now runs correctly on kernels 2.1.x
436 Fix made by Gerald Peters <gapeters@worldnet.att.net>
438 Changes between versions 0.4b2 and 0.4b3
439 ========================================
441 1. Use realpath() if available
445 Changes between versions 0.4b1 and 0.4b2
446 ========================================
448 1. Fixed the bug fix from Greg Lutz (I had made a mistake when integrating
451 2. Fixed restore to make it able to read FreeBSD 2.x dumps again
453 3. Fixed configure.in to correctly handle --enable-rmt
455 Changes between versions 0.3 and 0.4b1
456 ======================================
458 1. Integrated the changes from 4.4BSD-Lite2
460 2. Integrated the patches from Debian and Red Hat
462 3. Portability changes: use the __u32, __u16, __s32, and __s16 types
464 4. Changed dump to use the Ext2fs library to get block addresses. This
465 should solve the endianness problem on SparcLinux.
467 5. Created a configure.in file (shamelessly stolen from the e2fsprogs
468 distribution's one) to use autoconf
470 6. Fixed a few minor bugs
472 Changes between versions 0.2e and 0.2f
473 ======================================
475 1. Added the creation of named pipes (fifos) in restore.
477 2. Added the -N flag in the restore manual page.
479 3. Added the file kernel.patch which contains the llseek() optimization
480 patch for 1.2.x kernels.
482 4. Fixed a bug in the restoration of symbolic links: owner and group were
485 5. Integrated some changes from FreeBSD 2.2.
487 6. Added a call to ftruncate() after restoring each file to restore
488 correctly files ending by a hole.
490 Changes between versions 0.2d and 0.2e
491 ======================================
493 1. Fixed a bug in the "set owner/mode" process. Every file was restored
494 with owner = root (0) and group = root/wheel/whatever (0).
496 Changes between versions 0.2c and 0.2d
497 ======================================
499 1. Dump is now able to backup 2GB+ filesystems.
501 2. Dump and restore can now be linked as static binaries.
503 Changes between versions 0.2b and 0.2c
504 ======================================
506 1. Fixed a bug when dumping ``slow'' (i.e. normal) symbolic links.
508 Changes between versions 0.2a and 0.2b
509 ======================================
511 1. Really fixed the bug that I should have corrected in 0.2a.
513 2. Enabled optimization again.
515 Changes between versions 0.2 and 0.2a
516 =====================================
518 1. Disabled the optimization during compilation.
520 Changes between versions 0.1 and 0.2
521 ====================================
523 1. Fixed a bug in fstab.c which caused a null pointer to be stored in
524 the fs_type field (actually, I modified the file fstab.c to make it
525 use the mntent functions).
527 2. Dump and restore now use a 4.3 BSD compatible dump format. Backups
528 made by dump should be readable by the BSD restore and backups made
529 by the BSD dump should be readable by restore. Unfortunately, this
530 means that the dump format has changed between version 0.1 and version
533 3. Dump is now able to backup a subtree, it is no longer limited to whole
534 filesystems like the BSD version.
536 4. Dump now uses ext2_llseek() so it is able to backup filesystems bigger
539 Changes between versions 0.0 and 0.1
540 ====================================
542 1. Now create links rdump and rrestore during the `make install' step.
544 2. Linux port specific bugs added to the manual pages
546 3. Incorrect estimation of the number of tapes blocks fixed when doing
549 4. Better ls-like format in restore in interactive mode.