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