Dump accepts ext3 filesystems. Checking the superblock features.

[dump.git] / TODO

diff --git a/TODO b/TODO
index 1fdb8e3214e2f10dd919267cc29f600873b8ea35..bdb4783621a4c7a07f5b64b62c8f39ac5c539ed8 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,29 +1,42 @@
-1.     Make dump honor the no-dump attribute on directories.  Currently, it
-       honours it only on files.  This means that a directory flagged with
-       the no-dump attribute will be dumped if it contains a file without
-       the no-dump flag.
+$Id: TODO,v 1.8 1999/11/21 02:24:45 tiniou Exp $
 
-2.     Make dump able to backup several directories and/or files in one
-       invocation, like the SunOS version.
-
-3.     Verify that dump works correctly on rev 1 ext2fses (need success
-       reports)
-
-4.     More documentation? Examples, crontab?
+Need to verify:
+---------------
 
-5.     Verify that dump works with kerberos authentification (this
+1.     Verify that dump works with kerberos authentification (this
        was ported from *BSD and was not tested - in fact, this
        wasn't even compiled in!). Need success reports for this.
 
-6.     Explore and correct dump problems on a 4GB+ filesystem.
+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.
+
+2.     More documentation? Examples, crontab?
 
-7.     Clean-up the code by removing all those #ifdef _BSD, 
-       since nobody would ever re-compile this on a BSD system. 
-       Since the tape format is the same, the native BSD
-       restore can be used to restore tapes...
+3.     Explore and correct dump problems on active filesystems 
+       (lseek/read negative count).
 
-8.     Reimplement the ext2 specific code in a "backend" and
+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).
+       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.     Add some support in dump and restore for numbering in sequence
+       the output files (when dumping to a file). Something like -N <prefix>
+       which creates (or reads) <prefix>-1, <prefix>-2 etc...
+
+8.     Make a bootable dump tape? I don't know if it is possible...
+