Prepare for 0.4b42 release

[dump.git] / TODO

diff --git a/TODO b/TODO
index 0a6f1a750f108b1cc5128a979139cd4b79ffecb1..349b1d15e0c9421445f06b84ca98d80804334d4f 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,4 +1,4 @@
-$Id: TODO,v 1.14 2000/05/28 18:16:42 stelian Exp $
+$Id: TODO,v 1.25 2005/05/02 15:10:44 stelian Exp $
 
 Need to verify:
 ---------------
@@ -13,40 +13,22 @@ Urgent items (for the next stable version):
 All others:
 -----------
 
-1.     Make dump able to backup several directories and/or files in one
-       invocation, like the SunOS version.
+1.     More documentation? Examples, crontab?
 
-2.     More documentation? Examples, crontab?
-
-3.     Explore and correct dump problems on active filesystems 
+2.     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
+3.     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
+4.     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.
-
-9.     Add readline capabilities to interactive restore. Does
-       this mean huge static restore or not?
+5.     Make a bootable dump tape? I don't know if it is possible...
 
-10.    Do the compare on the fly in restore C mode (useful
-       when comparing huge files and you have not enough space
-       in /tmp).
+6.     Better readline completition in restore (escape spaces etc).