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