+Changes between versions 0.4b28 and 0.4b29 (released ??????????????)
+====================================================================
+
+1. Fixed a problem in the rmt ioctl command, where ioctl's issued from
+ non Linux clients were misinterpreted. The description of the problem
+ (incompatible numbering in Linux mtio opcodes) is documented at
+ ftp://ftp.fokus.gmd.de/pub/unix/star/README.mtio . Thanks to
+ Jörg Schilling <schilling@fokus.gmd.de> for reporting this bug and
+ providing an excellent, cross-platform replacement for rmt in his
+ star package.
+
+2. Fixed a bug reported by Andy Mentges <amentges@jumpline.com>
+ which caused restore to fail when the inode maps were not entirely
+ contained on the first volume (when using really small volumes or
+ when dumping a huge number of inodes).
+
+3. Fixed a problem in dump, where files in subdirectories of directories
+ that have the nodump flag set (or being excluded with -e/-E) were
+ sometimes incorrectly dumped (instead of being excluded). The original
+ fix is from David C Lawrence <tale@dd.org> in the FreeBSD version
+ of dump: http://www.FreeBSD.org/cgi/query-pr.cgi?pr=32414
+ Thanks to Ted Grzesik <tedgyz@roostme.com> for reporting the bug and
+ help testing the patch.
+
+4. Added some example scripts from Gerd Bavendiek <bav@epost.de>
+ which makes one able to pipe the output of dump, by the net, to
+ a remote CD-burner server.
+
+5. Made dump use O_CREAT|O_TRUNC both locally and remotely (over rmt),
+ and use GNU's symbolic syntax over rmt instead of numerical values
+ to assure multiple platform compatibility.
+
+6. Documented the -d option in restore.
+
+7. Added a -v (verbose) mode to dump. For now it just prints the number
+ of the inode being dumped, but this could evolve in future versions
+ to include interesting debugging output.
+
+8. Added a -o flag to restore, which automatically restores the current
+ directory permissions in -i or -x mode, without asking the operator
+ whether to do so. Patch submitted by Tony Clayton <tonyc@e-smith.com>
+ and Peter Samuel <peters@e-smith.com>.
+
+Changes between versions 0.4b27 and 0.4b28 (released April 12, 2002)
+====================================================================
+
+1. Fixed a bug in the QFA feature which could have caused
+ a bad tape positionning on restore (causing extra delays in
+ restore). Credits go to Uwe Gohlke <uwe@ugsoft.de>.
+
+2. Added a small note in the dump man page specifying that
+ there should be no white space between the option letter and
+ the -j or -z parameter, thanks to Kenneth Porter <shiva@well.com>
+
+3. Made restore work with older versions of the readline library,
+ by checking in configure for several extended symbols. Restore
+ can now be compiled with a readline as old as the 2.0 release
+ (though it may be a good idea to upgrade it to a more recent
+ version...). Thanks to Andrew Donkin <ard@waikato.ac.nz> for
+ reporting the build failures.
+
+4. Fixed a performance problem with the QFA file creation in
+ dump, which made unnecessary seeks on the tape slowing down
+ the dump. Thanks to Andrew Donkin <ard@waikato.ac.nz> for
+ reporting this issue.
+
+5. Removed the inclusion of some kernel headers in the dump
+ source, which prevented the compile in some kernel/glibc
+ headers/architecture combination. Thanks to Bdale Garbee
+ <bdale@gag.com> for reporting the bug.
+
+6. Added the appropriate error message when dump fails to
+ open the output file for writing. Thanks to Amith Varghese
+ <amithv@yahoo.com> for reporting this bug.
+
+7. Made restore able to understand large Solaris ufsdump tapes
+ (containing inodes bigger than 4194304). Sun have introduced
+ an "extension" to the dump tape format when dealing with
+ those inodes, which was uncorrectly handled by Linux restore.
+ Thanks to Uwe Gohlke <uwe@ugsoft.de> for reporting the bug and
+ providing a test case.
+
+8. Added the -m parameter to dump which optimises the output for
+ inodes having been changed but not modified since the last dump
+ ('changed' and 'modified' have the meaning defined in stat(2)).
+ For those inodes, dump will save only the metadata, instead of
+ saving the entire inode contents. Inodes which are either
+ directories or have been modified since the last dump are saved
+ in a regular way. Uses of this flag must be consistent, meaning
+ that either every dump in an incremental dump set have the flag,
+ or no one has it.
+
+Changes between versions 0.4b26 and 0.4b27 (released February 15, 2002)