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