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