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