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