+
+2. More documentation? Examples, crontab?
+
+3. Explore and correct dump problems on active filesystems
+ (lseek/read negative count) (This should be OK as of 0.4b14.
+ Unfortunately, this seems to continue for a very few users).
+
+4. Reimplement the ext2 specific code in a "backend" and
+ make the dump code more generic. This would allow creation
+ of other backends for other filesystems. Implementing a
+ (v)fat backend should be quite easy, as for BSD ffs (we
+ already have the code for this). The BSD code in traverse.c
+ (all those #ifdef _BSD) should go into the ffs backend.
+
+5. Implement a DEBUG option which doesn't fork on each tape, making
+ it able to debug dump with gdb.
+
+6. Add a compression mode using zlib on each file (see
+ http://www.cdrom.com/pub/infozip/zlib).
+
+7. Make a bootable dump tape? I don't know if it is possible...
+
+8. From Kjetil Torgrim Homme <kjetilho@ifi.uio.no>:
+ a archive_file
+ Archive file. Archive a dump table-of-contents in
+ the specified archive_file to be used by
+ ufsrestore(1M) to determine whether a file is in
+ the dump file that is being restored.