1 $Id: CHANGES,v 1.128 2001/07/20 12:41:53 stelian Exp $
3 Changes between versions 0.4b22 and 0.4b23 (released July 20, 2001)
4 ===================================================================
6 1. Fixed a buffer overflow in restore/tape.c. Patch provided by
7 Marcus Meissner (Caldera International Security Dept.).
9 2. Implement the Sun rmt extended protocol. Patch submitted
10 by Ian Gordon <iangordon@users.sourceforge.net>.
12 3. Check for the e2fsprogs header <ext2fs/ext2_fs.h> instead of
13 the linux kernel header. This ensures that dump always has the
14 latest version of this file. Patch submitted by
15 Andreas Dilger <adilger@turbolinux.com>.
17 4. Report any filesystem present in either /etc/fstab with a
18 positive passno or /etc/dumpdates in dump -w output.
19 Patch submitted by Andreas Dilger <adilger@turbolinux.com>.
21 5. Fixed the looping problem in dump introduced in the
24 6. Changed the -B option of dump to limit the size of
25 _compressed_ output per volume if compression is on.
26 Patch contributed by Helmut Jarausch
27 <jarausch@igpm.rwth-aachen.de>. Note however that, since
28 it is impossible to predict the size of the compressed
29 data before doing the compression, the -B limit is a bit
32 7. Fixed a bug in reading the operator typed file/tape path for
33 the next volume in restore.
35 8. Implemented a "-F script" option to restore which permits the
36 user to specify a script which will be launched at the
37 beginning of each tape, useful for automatic programming of
38 tape changers for example. See the restore man page for the
39 script parameters and return codes.
41 9. Small fix for the QFA routines provided by Uwe Gohlke
42 <uwe@ugsoft.de>, and some recommendations for QFA uses in
45 10. Fixed the multivolume restoring where making a mistake
46 to the 'Mount next tape' prompt caused several blocks to
49 11. Enhanced the -e option of dump to take as a parameter a
50 comma separated list of inode numbers.
52 12. Added the -E option to dump which specify a file containing
53 inode numbers to exclude from the dump.
55 13. Fixed the compressed multi-volume dump + restore.
57 Changes between versions 0.4b21 and 0.4b22 (released May 12, 2001)
58 ==================================================================
60 1. Made dump report the number of blocks dumped per volume.
61 Thanks to Kenneth Porter <shiva@well.com> for the suggestion.
63 2. Fix a bug in dump where waiting too much at the 'change volumes'
64 question caused the volume to be rewritten. Thanks to
65 Graham Reed <greed@users.sourceforge.net> for reporting the
66 bug and providing a patch.
68 3. Added a compression option to dump, contributed by Jerry
69 Peters <gapeters@worldnet.att.net>.
71 WARNING: the compression works only on files/pipes and
72 drives supporting variable block size.
74 WARNING2: tapes created using the compression feature are
75 incompatible with the standard dump tape format, and a
76 version of restore >= 0.4b22 will be needed for extraction.
78 4. Fixed some compilation problems for glibc 2.2.2 and 64 bit
79 architectures. Thanks to Paul Slootman <paul@debian.org> for
80 the patch and to Bdale Garbee <bdale@gag.com> for forwarding
83 5. Many cleanups (CPP defines, const char warnings, check of
84 ext2fs COMPAT flags, time_t cleanups, added libext2 version
85 in dump usage text) by Andreas Dilger <adilger@turbolinux.com>.
87 6. Made --prefix option work in configure. All the install path
88 are now based on the configure parameters.
90 7. Added the Quick File Access mode in dump/restore, contributed
91 by Uwe Gohlke <uwe@ugsoft.de>. In this mode, dump stores in
92 a file tape position for each inode, and this file is used by
93 restore (if called with parameter Q and the filename)
94 to directly position the tape at the file restore is currently
95 working on. This saves hours when restoring single files from
96 large backups, saves the tapes and the drive's head. Use
97 --enable-qfa option of configure to compile in the QFA support.
99 8. Added the possibility to dump several files and directories
100 in a single invocation of dump. Thanks to Uwe Gohlke
101 <uwe@ugsoft.de> for implementing this option.
103 9. Fixed the dumping and restoring of files with holes
104 (files ending with holes didn't get dumped or restored
107 10. Fixed a socket descriptor leak in dump, which leaved opened
108 3 file descriptors per dump process (and there is one dump
111 11. Fixed dump large file system support, by explicit use of
112 open64/lseek64/etc functions (explicit use needed because
113 e2fsprogs libraries don't behave well when compiled with
114 FILE_OFFSET_BITS=64).
116 Changes between versions 0.4b20 and 0.4b21 (released January 13, 2001)
117 ======================================================================
119 1. Fixed some bugs in the dump -w|-W logic introduced by
120 the previous version. Thanks to Andreas Dilger
121 <adilger@turbolinux.com> for his help on this one.
123 2. Fixed again a compilation problem when using old e2fs
124 headers (filesystem label related). Thanks to many users
125 who reported this stupid error.
127 3. Fixed a build problem on old lib5 based systems dealing with
128 _PATH_MNTTAB being undefined. Thanks to John Adams
129 <johna@onevista.com> for reporting the bug.
131 4. Improved the error detection in restore when creating
132 the temporary files in TMPDIR. Now restore will corectly
133 report a 'no space left on device' error instead of
134 strange errors which could imply an archive corruption.
135 Thanks to Gabriel Somlo <somlo@cs.colostate.edu> and
136 bgjenero <bgjenero@sympatico.ca> for reporting the bug.
138 5. Added the throughput information in dump's progression
139 messages. Thanks to Andreas Dilger <adilger@turbolinux.com>
142 6. Use libext2fs's inode scanning routines, which are particularly
143 robust when dealing with errors (especially when having some
144 bad blocks on the filesystem). Many thanks to Colin
145 <colin@horizon.com> for reporting the bug, investigating
146 the issues, finding a workaround, writing the patch and
147 fully testing it... (of course, if this patch will break
148 anything, he is to blame for :-)).
150 7. Made dump and restore LFS aware. Dump can dump a filesystem
151 containing large files, generate a large file on output and
152 restore can restore them. This feature is not enabled by
153 default, use --enable-largefile option of configure to enable
154 it (you need to have a LFS aware glibc though). Thanks to
155 Andrea Arcangeli <andrea@suse.de> for submitting the patch,
156 and to Theodore T'so <tytso@valinux.com> for his always
159 8. Made dump ask upon a tape write error if it should rewrite
160 the current volume (assume this is a bad tape) or if it should
161 assume an end-of-tape condition (useful for tape drives which
162 behaves badly at the end of the tape). Thanks to Andreas
163 Dilger <adilger@turbolinux.com> for the suggestion.
165 Changes between versions 0.4b19 and 0.4b20 (released November 10, 2000)
166 =======================================================================
168 1. Fixed a small compilation problem due to a change
169 in the definintion of the struct sigaction in
170 glibc 2.0 / libc5. Thanks to Gunther Schlegel
171 <schlegel@riege.de> for reporting the bug and to
172 Dave Platt <dplatt@snulbug.mtview.ca.us> for suggesting
175 2. Modified the label and uuid analysis in order to be
176 self-contained (independant of kernel/libc headers). This
177 should fix the compile with older kernel/libc headers and
178 will preserve the functionality. Thanks to Bernhard Erdmann
179 <bernhard.erdmann@gmx.de> for reporting the bug.
181 3. The 'exclude inode' option, if applied to a directory
182 inode, excludes now correctly all the leaves of this
183 directory. Thanks to John R. Dennison
184 <gerdesas@users.sourceforge.net> for reporting the bug.
186 4. Fixed the '-e' option to disable the possibility
187 to exclude the root inode (which causes the dumps to
188 be unreadable by restore). Prevented array overflow
189 when multiple -e options are used.
191 5. Fixed dump to correctly interpret a filesystem argument
192 which is a mountpoint and it is not an absolute path
193 (as specified in the fstab). Thanks to Bernhard R. Erdmann
194 <be@berdmann.de> for reporting the bug.
196 6. Made dump able to backup files larger than 2 GB. Note that
197 dump still doesn't cope with files larger than 4 GB.
199 7. Restore the real uid and gid before invoking an external
200 RSH program (big hole when dump or restore is suid root!).
202 8. Get the values for the default tape device and the location
203 of fstab file from the system headers. Thanks to
204 Andreas Dilger <adilger@turbolinux.com> for the patch.
206 9. Made dump -w|-W report all recognized filesystems
207 present in either /etc/fstab or /etc/dumpdates, and present
208 the list in the same order as in fstab file. Thanks
209 to Andreas Dilger <adilger@turbolinux.com> for the patch.
211 10. Made dump's -a (automatic end of tape detection) the
212 default. Specifying one of -B, -c, -d or -s options will
213 override the EOM detection. Thanks to Andreas Dilger
214 <adilger@turbolinux.com> for the patch.
216 11. Save the ext2 filesystem label into the dump volume label.
217 Specifying a volume label on the command line (-L option)
218 will override this feature. Thanks to Andreas Dilger
219 <adilger@turbolinux.com> for the patch.
221 Changes between versions 0.4b18 and 0.4b19 (released August 20, 2000)
222 =====================================================================
224 1. Fixed the signal handling in dump (which I broke in 0.4b17)
225 which was causing several strange dump failures (dump
226 hanged or segmentation faults etc).
228 2. Specified the default blocksize in the dump man page.
230 3. Changed two info messages of restore to be written on stdout
231 instead of stderr in order to leave stderr only for errors
232 or warnings. Thanks to Stephen Atwell
233 <satwell@urbana.css.mot.com> for the suggestion.
235 4. Corrected an off by one calculation which prevented
236 dumping a directory having a 1 character name length.
237 Thanks to Bernhard Erdmann <bernhard.erdmann@gmx.de>
238 for reporting the bug.
240 5. Reinforce dump in order to allow only level 0 and no
241 -u option when dumping a subdirectory, and document
242 this in the man page. Thanks to Bernhard Erdmann
243 <bernhard.erdmann@gmx.de> for reporting the bug.
245 6. Fixed a small harmless bug in restore which caused
246 in some conditions hard links to be restored several
247 times (therefore generation some warning messages).
248 Thanks to Kenneth Porter <shiva@well.com> for
251 7. Updated the RPM spec file to the latest RedHat version,
252 providing FHS packaging and other cosmetic changes.
253 You will need RPM version >= 3.0.5 in order to build the RPM.
255 8. Updated the configure script to check for libtermcap
256 before checking for libreadline, because we need this
257 library in order to compile the readline support.
259 9. Made dump understand the LABEL= and UUID= notation
260 both in /etc/fstab and on the command line. Note that
261 you will need the /proc filesystem in order to use
262 these notations. Thanks to Erik Troan <ewt@redhat.com>
263 for providing the patch.
265 Changes between versions 0.4b17 and 0.4b18 (released June 30, 2000)
266 ===================================================================
268 1. Fixed a potential buffer overflow in restore. Thanks
269 to Stan Bubrouski <satan@fastdial.net> for reporting
272 2. Fixed a readline-related bug which prevented
273 'cat DUMPFILE | restore -i -f -' from working. Thanks
274 to Charles Karney <karney@users.sourceforge.net>
277 3. Changed a few "panic" into "exit", causing restore to
278 be more stable against some attacks (like the last one
279 reported on Bugtraq, although the last version of restore
280 was not vulnerable - just dumped core). Thanks to
281 Andreas Hasenack <andreas@conectiva.com.br> for reporting
284 4. Removed the suid-root bit on dump and restore in the
285 default build (and generated RPMs). It should be safer
286 now. Users who need the suid-root capabilities in order
287 to make network backups should read first the man page
288 of dump and enable the suid bit manually.
290 5. Added -ltermcap to the compile parameters for restore
291 when using readline support, in order to make the compile
292 process work on some systems (SuSE ?). Thanks to
293 Patrik Schindler <poc@pocnet.net> for reporting the bug.
295 Changes between versions 0.4b16 and 0.4b17 (released June 1st, 2000)
296 ====================================================================
298 1. The -F script is called now *only* at the end of a tape,
299 not at the end of the dump. Thanks to Christian Haul
300 <haul@informatik.tu-darmstadt.de> for the bug report.
302 Normally, the device name and the current volume number
303 are passed on the command line of the script. However,
304 if you want the old style script (with no arguments
305 passed on the command line), you can enable it in
306 configure with the --enable-oldstylefscript.
308 2. Use posix signal handling to preserve dump functionality
309 with libc5. Thanks to Jeff Johnson <jbj@redhat.com> for
312 3. Made the exit code of restore in case of a 'C'ompare
313 command reflect the result of the compare. An exit status
314 of 0 means the dump archive is correct, 1 means tape errors,
315 2 means that some files were modified. Thanks to Kenneth Porter
316 <shiva@well.com> for the suggestion.
318 4. Made (finally) quotes work in interactive restore.
320 5. Small fixes in order to allow dump to compile with a
321 really old e2fsprogs version. Thanks to Ian Zimmerman
322 <itz@speakeasy.org> for the bug report.
324 6. Add GNU readline capabilities to interactive restore.
325 Use configure's --enable-readline flag to enable this feature.
326 Thanks to Patrik Schindler <poc@pocnet.net> for the
329 7. Do the compare on the fly in restore 'C' mode (this will
330 allow not to exhaust the available /tmp space when
331 ccmparing large files). Thanks to Kenneth Porter
332 <shiva@well.com> for the suggestion.
334 Changes between versions 0.4b15 and 0.4b16 (released March 11, 2000)
335 ====================================================================
337 1. Fixed some several duplicate 'DUMP: DUMP:' in the
340 2. Corrected the estimation of blocks to dump. Note that
341 this is still wrong for large directory inodes, due
342 to the size of a BSD directory entry on the tape
343 (estimation is based on the size of the ext2 directory,
344 which is smaller because it doesn't contain the null
345 character at the end).
347 3. Made dump report the total number of MB written to
348 tape at the end of run. Thanks to W. Reilly Cooley
349 <wcooley@nakedape.cc> for the patch.
351 4. Added the -X option to restore giving the possibility
352 to read the names of the files to be extracted/listed
353 from a text file (in addition of the command line).
354 Thanks to Dejan Muhamedagic <dejan@quant-x.com> for the
357 5. Added the device name and the current volume number
358 as arguments to the end of tape script (dump -F option).
360 6. Made the multi-volume dump work again (after having
361 broken it in 0.4b15).
363 Changes between versions 0.4b14 and 0.4b15 (released March 2, 2000)
364 ===================================================================
366 1. Added a prompt command in interactive restore mode. Thanks
367 to Andreas Dilger <adilger@home.com> for the patch.
369 2. Fixed a buffer overflow problem in dump (caused by
370 not checking the size of the filesystem parameter).
371 Thanks to Kim Yong-jun <loveyou@hackerslab.org> for
372 reporting this on Bugtraq (and to several dump users
373 who forwarded me his mail).
375 3. Added the '-F script' option to dump in order to
376 launch a script at the end of each tape (to be used
377 with a tape changer, or to notify the sysadmin by
380 4. Fixed a bug in restore compare code caused by the changes
383 5. Fixed the treatment of options using the old BSD syntax
384 in both dump and restore.
386 Changes between versions 0.4b13 and 0.4b14 (released February 10, 2000)
387 =======================================================================
389 1. Fixed a bug in dump which may have caused invalid deleted
390 directories to be dumped out if they were deleted after the
391 mapping pass. This could occure on active filesystem and lead
392 to heap corruption (causing dump malfunction in many possible ways).
393 Thanks to Jan Sanislo <oystr@cs.washington.edu> for finding this
394 bug and submitting the patch.
396 2. Fixed the handling of the filesystem parameter in dump. A
397 '/mnt/disk' parameter caused the disk contents to be dumped,
398 but a '/mnt/disk/' parameter caused the mountpoint directory
399 to be dumped (generally an empty directory).
401 3. Improved the output of dump in order to tell which directory
402 it is currently dumping (when dumping a subtree).
404 4. Added the '-e' exclude inode option to dump. Thanks to
405 Isaac Chuang <ike@isl.stanford.edu> for contributing with the patch.
407 5. Added a REPORTING-BUGS file in order to provide a guide
408 on how to correctly report a bug in dump/restore.
410 6. Fixed a restore problem when restoring a hard link to an inode
411 having the immutable or append-only attribute set. Thanks to
412 Ambrose Li <acli@mingpaoxpress.com> for submitting the patch.
414 7. Fixed a compatibility problem between dumps made on little
415 endian machines (the format was correct) and big endian
416 machines (the format was incorrect). This fix break the
417 compatibility with the older dumps made on big endian
418 machines (sparc, m86k, ppc etc). For the first time in
419 linux dump's history (I believe), the dumps made by *BSD,
420 Linux/alpha, Linux/sparc and Linux/x86 are compatible,
421 so interchangeable. Thanks to Rob Cermak
422 <cermak@ahab.rutgers.edu> for submitting the bug and
423 helping me test the fix.
425 8. Fixed the way dump reports the remaining percent/time, if
426 the number of blocks actually dumped exceeds the estimated
427 number of blocks. Thanks to Jean-Paul van der Jagt
428 <jeanpaul@dutepp0.et.tudelft.nl> for reporting the bug.
430 Changes between versions 0.4b12 and 0.4b13 (released January 21, 2000)
431 ======================================================================
433 1. Small Y2K fix in the man pages :). Thanks to Bernhard Sadlowski
434 <sadlowsk@Mathematik.Uni-Bielefeld.DE> for reporting the bug.
436 2. Removed the requirement to build the RPM as root from the
437 spec file. Thanks to Christian Weisgerber
438 <naddy@mips.rhein-neckar.de> for submitting this.
440 3. Fixed a bug in dump related to the 'filetype' feature of ext2fs,
441 causing dump to block when dumping really huge filesystems.
442 Many thanks to Patrik Schindler <poc@pocnet.net> for
443 helping me find this bug.
445 4. Fixed the treatment for an interrupt signal when dump access
446 the remote tape through RSH. Thanks to Christian Weisgerber
447 <naddy@mips.rhein-neckar.de> for providing the patch.
449 5. Fixed a bug which was causing dump/restore to display
450 garbage characters instead of the remote host name.
452 Changes between versions 0.4b11 and 0.4b12 (released January 8, 2000)
453 =====================================================================
455 1. Small fix in the dump man page. Thanks to Thorsten Kukuk
456 <kukuk@suse.de> for submitting the patch.
458 2. Fix for the exit code when using the size estimate option of
459 dump. Thanks to Matti Taskinen <mkt@rni.helsinki.fi> for
460 submitting the patch.
462 3. Handle EINTR in atomical reads/writes in dump, which was causing
463 dump to fail on some systems. Thanks to Eric Jergensen
464 <eric@dvns.com> for reporting the bug and submitting the patch.
466 4. Handle more than 16 characters for the device names in dumpdates.
467 (up to 255 now). Thanks to Rainer Clasen <bj@ncc.cicely.de> for
468 tracking down the problem and proposing the solution.
470 5. Fixed a bug in dump which prevented the creation of the
471 dumpdates file when doing a 0-level dump without already
472 having a dumpdates file. Thanks to Patrik Schindler
473 <poc@pocnet.net> for reporting the bug.
475 6. Changed the way dump 'S' flag reports the size estimate
476 from number of blocks into bytes (making it compatible
477 with the Solaris version, and simplifying things for
478 amanda users). Thanks to Jason L Tibbitts III
479 <tibbs@math.uh.edu> for reporting the bug.
481 7. Fixed a compatibility problem in linux/alpha dump tape format.
482 Now the linux/alpha dump are (again) compatible with the
483 other dump formats. But this breaks compatibility with
484 older dumps made on alpha. Thanks to Mike Tibor
485 <tibor@lib.uaa.alaska.edu> for helping me in finding this bug.
487 Changes between versions 0.4b10 and 0.4b11 (released December 5, 1999)
488 ======================================================================
490 1. Added a '--enable-kerberos' to configure.
492 2. Added a 'S' option to dump which determines the amount of space
493 that is needed to perform the dump without actually doing it, similar
494 to the Sun's ufsdump 'S' option. Patch contributed by Rob Cermak
495 <cermak@ahab.rutgers.edu>.
497 3. Added a 'M' multi-volume option to dump and restore which enables
498 dumping to multiple files (useful when dumping to an ext2
499 partition to make several dump files in order to bypass the 2GB
500 file size limitation). The 'f' argument is treated as a prefix and
501 the output files will be named <prefix>001, <prefix>002 etc. With
502 the 'M' flag, restore automatically selects the right file without
503 asking to enter a new tape each time.
505 4. Fixed a memory leak which was causing dump to grow very big
506 (270MB when dumping a 10GB filesystem...). Thanks to Jason
507 Fearon <jasonf@netrider.org.au> for reporting the bug.
509 Changes between versions 0.4b9 and 0.4b10 (released November 21, 1999)
510 ======================================================================
512 1. Make configure test if the system glob routines support
513 extended syntax (ALTDIRFUNC). If not, use the internal glob
514 routines instead of system ones. Thanks to Bernhard Sadlowski
515 <sadlowsk@Mathematik.Uni-Bielefeld.DE> for reporting the bug
516 and helping me resolve this and other minor libc5 compiling
519 2. Fix a problem when dumping a ext2fs with the 'filetype'
520 feature enabled. Thanks to Patrick J. LoPresti
521 <patl@cag.lcs.mit.edu> for reporting the bug and to
522 Theodore Y. Ts'o <tytso@mit.edu> for providing the patch.
524 3. Made the nodump flag work on directories. A directory which
525 has the nodump flag gets never dumped, regardless of its
528 4. Integrate a patch from Jeremy Fitzhardinge <jeremy@goop.org>
529 which allows dump on an active ext3 filesystem. However, this
530 is a "quick and dirty" patch which enables backup of an ext3
531 filesystem through the ext2 compatibility (by ignoring the
532 NEEDS_RECOVERY bit). The journal file is not recognized and
533 it is dumped (it should not).
535 5. Test the superblock compatibility flags when dumping, in order
536 to be sure that we know how to deal with specific features.
538 Changes between versions 0.4b8 and 0.4b9 (released November 5, 1999)
539 ====================================================================
541 1. Use lchown instead of chown, fixing a possible security problem
542 when restoring symlinks (a malicious user could use this
543 to deliberately corrupt the ownership of important system files).
544 Thanks to Chris Siebenmann <cks@utcc.utoronto.ca> for detecting
545 this and providing the patch.
547 Changes between versions 0.4b7 and 0.4b8 (released November 3, 1999)
548 ====================================================================
550 1. Put dump sources under CVS, added Id tags in all files so
551 one can use 'ident' on binary files.
553 2. Added the dump/restore version in the usage text so one can
554 easily verify the version he is using.
556 3. Small patch from Nuno Oliveira <nuno@eq.uc.pt> which fixes
557 a va_start/va_end problem on linux-ppc (always call va_start
558 va_end in pairs each time we use a vararg function).
560 4. Added again the DT_* constants because old libc does not
561 contain them :(. Thanks to Eric Maisonobe <virnet@nat.fr>
562 for submitting the bug report.
564 5. Use ext2fs_llseek instead of llseek. With recent e2fsprogs
565 this should enable dumping big (huge) filesystems.
567 6. Added the RSH environment variable in order to be able to
568 use a rsh replacement like ssh when doing remote backups (and
569 bypass the security limitations of rcmd). Now you can do remote
570 backups without being root (or making dump setuid root).
572 7. Modified again the way dumpdates works. For incremental dumps,
573 we need to read dumpdates even if we are not using 'u' option.
574 Thanks to Bdale Garbee <bdale@gag.com> for his ideas on how
577 Changes between versions 0.4b6 and 0.4b7 (released October 8, 1999)
578 ===================================================================
580 1. Removed the 'k' flag from the restore 'about' text if kerberos
583 2. Prototyped (f)setflags from e2fsprogs and corrected the calls
584 to them (fsetflags takes a char*, setflags an open fd!).
586 3. (f)setflags is called only if the flags aren't empty. If the
587 file is a special file, a warning is printed, because changing
588 flags implies opening the device. Normally, a special file
589 should not have any flag... (Debian bug #29775, patch provided
590 by Abhijit Dasgupta <abhijit@ans.net>).
592 4. Made possible to dump a file system not mentioned in /etc/fstab.
593 (Debian bug #11904, patch provided by Eirik Fuller <eirik@netcom.com>).
595 5. Changed the default behaviour to not create dumpdates
596 unless 'u' option is specified. Removed the old "debian-patch"
597 which provided the same thing. (Debian bug #38136, #33818).
599 6. Removed all those dump*announce, since they were getting old...
601 7. Added warning messages if dumpdates does not exist and
602 when an inferior level dump does not exist (except for a level 0
605 8. Debugged the glob calls in interactive mode: restore used a
606 dirent struct which was different from the /usr/include/dirent.h
607 one (this used to work, is it a glibc2 change?), so none of the
608 compat glob (which used /usr/include/dirent.h) or the system glob
609 worked. Restore use now the system dirent (and the system
610 DT_* constants), which are compatible with BSD ones.
612 9. Added a configure flag (--with-dumpdatespath) to specify
613 the location of dumpdates file. By default, it is
616 10. Added the "AUTHOR" and "AVAILABILITY" sections and
617 included the current date/version in man pages.
619 11. Corrected the estimation of remaining time when
620 the operator doesn't change the tapes quickly enough. This
621 was an old bug, I thought I corrected it, and discovered
622 that in fact it was corrected in two different places, so
623 the results canceled each other...
625 Changes between versions 0.4b5 and 0.4b6 (released October 1, 1999)
626 ===================================================================
628 1. Integrated multiple patches from RedHat, Debian and SuSE:
630 - tweak dump/itime.c to not try to read dumpdates if the 'u' option
632 - several fixes in the man pages.
633 - update the default tape device to /dev/st0.
634 - many updates for Linux Alpha (byte ordering, size_t etc).
636 - use environment variable for TMPDIR (instead of /tmp).
637 - use sigjmp_buf instead of jmp_buf (RedHat bug #3260).
638 - workaround egcs bug (RedHat bugs #4281 and #2989).
639 - wire $(OPT) throughout Makefile's.
641 2. Upgrade the dump revision to 1, making possible to dump filesystems
642 made with e2fsprogs-1.15 or newer. Nothing seems to break...
644 3. Fix some compile warnings, prototype all functions.
646 4. Use glibc err/glob instead of internal compatibility
647 routines (only if available).
649 5. Fix a compile error on Linux 2.2.7 / libc5 (5.4.44) (patch provided
650 by Bernhard Sadlowski <sadlowsk@mathematik.uni-bielefeld.de>).
652 Changes between versions 0.4b4 and 0.4b5 (released September 22, 1999)
653 ======================================================================
655 1. Integrated the changes from FreeBSD-3.1-RELEASE
656 (mostly bug fixes, buffer overruns, dump has now an "automatic
657 tape length calculation" flag, dump/restore can use kerberos now
658 (this is NOT tested), use environment variables for TAPE and
661 2. Integrated three RedHat patches ("glibc", "kernel" and "bread" patches)
663 3. Corrected a bug in restore when using 'C' option with multi-volumes
664 tapes (files splited accros two tapes give "size changed" errors
667 4. Corrected the long standing bug when dumping multiple tapes.
668 This works for me, needs further testing.
670 Changes between versions 0.4b3 and 0.4b4 (released January 17, 1997)
671 ====================================================================
673 1. Dump now runs correctly on kernels 2.1.x
674 Fix made by Gerald Peters <gapeters@worldnet.att.net>
676 Changes between versions 0.4b2 and 0.4b3
677 ========================================
679 1. Use realpath() if available
683 Changes between versions 0.4b1 and 0.4b2
684 ========================================
686 1. Fixed the bug fix from Greg Lutz (I had made a mistake when integrating
689 2. Fixed restore to make it able to read FreeBSD 2.x dumps again
691 3. Fixed configure.in to correctly handle --enable-rmt
693 Changes between versions 0.3 and 0.4b1
694 ======================================
696 1. Integrated the changes from 4.4BSD-Lite2
698 2. Integrated the patches from Debian and Red Hat
700 3. Portability changes: use the __u32, __u16, __s32, and __s16 types
702 4. Changed dump to use the Ext2fs library to get block addresses. This
703 should solve the endianness problem on SparcLinux.
705 5. Created a configure.in file (shamelessly stolen from the e2fsprogs
706 distribution's one) to use autoconf
708 6. Fixed a few minor bugs
710 Changes between versions 0.2e and 0.2f
711 ======================================
713 1. Added the creation of named pipes (fifos) in restore.
715 2. Added the -N flag in the restore manual page.
717 3. Added the file kernel.patch which contains the llseek() optimization
718 patch for 1.2.x kernels.
720 4. Fixed a bug in the restoration of symbolic links: owner and group were
723 5. Integrated some changes from FreeBSD 2.2.
725 6. Added a call to ftruncate() after restoring each file to restore
726 correctly files ending by a hole.
728 Changes between versions 0.2d and 0.2e
729 ======================================
731 1. Fixed a bug in the "set owner/mode" process. Every file was restored
732 with owner = root (0) and group = root/wheel/whatever (0).
734 Changes between versions 0.2c and 0.2d
735 ======================================
737 1. Dump is now able to backup 2GB+ filesystems.
739 2. Dump and restore can now be linked as static binaries.
741 Changes between versions 0.2b and 0.2c
742 ======================================
744 1. Fixed a bug when dumping ``slow'' (i.e. normal) symbolic links.
746 Changes between versions 0.2a and 0.2b
747 ======================================
749 1. Really fixed the bug that I should have corrected in 0.2a.
751 2. Enabled optimization again.
753 Changes between versions 0.2 and 0.2a
754 =====================================
756 1. Disabled the optimization during compilation.
758 Changes between versions 0.1 and 0.2
759 ====================================
761 1. Fixed a bug in fstab.c which caused a null pointer to be stored in
762 the fs_type field (actually, I modified the file fstab.c to make it
763 use the mntent functions).
765 2. Dump and restore now use a 4.3 BSD compatible dump format. Backups
766 made by dump should be readable by the BSD restore and backups made
767 by the BSD dump should be readable by restore. Unfortunately, this
768 means that the dump format has changed between version 0.1 and version
771 3. Dump is now able to backup a subtree, it is no longer limited to whole
772 filesystems like the BSD version.
774 4. Dump now uses ext2_llseek() so it is able to backup filesystems bigger
777 Changes between versions 0.0 and 0.1
778 ====================================
780 1. Now create links rdump and rrestore during the `make install' step.
782 2. Linux port specific bugs added to the manual pages
784 3. Incorrect estimation of the number of tapes blocks fixed when doing
787 4. Better ls-like format in restore in interactive mode.