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