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