X-Git-Url: https://git.wh0rd.org/?p=dump.git;a=blobdiff_plain;f=TODO;h=11347c173c1b4142bf9e4a56660e2843362f0d80;hp=dfc067263f2049eed7de433bdadd64c015e8bce9;hb=54ec08c6ea42e9189423def508c5119f33466db2;hpb=ec387a1267f4cac7625cd5b6d1c1f080d39085b3

diff --git a/TODO b/TODO
index dfc0672..11347c1 100644
--- a/TODO
+++ b/TODO
@@ -1,31 +1,59 @@
-$Id: TODO,v 1.4 1999/10/11 13:31:04 stelian Exp $
+$Id: TODO,v 1.20 2001/07/18 12:54:06 stelian Exp $
 
-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.
+Need to verify:
+---------------
 
-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?
-
-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:
+-----------
 
-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...
+1.	More documentation? Examples, crontab?
 
-8.	Reimplement the ext2 specific code in a "backend" and
+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).
+
+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).
+	already have the code for this). The BSD code in traverse.c
+	(all those #ifdef _BSD) should go into the ffs backend.
+
+4.	Implement a DEBUG option which doesn't fork on each tape, making
+	it able to debug dump with gdb.
+
+5.	Extend the compression patch to use bzip2.
+
+6.	Make a bootable dump tape? I don't know if it is possible...
+
+7.	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.
+
+8.	Modify (or get rid of) rmt in order to work with non Linux
+	systems (limited succes has been reported). A good version 
+	of rmt to be looked at is part of star 
+	http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/star.html
+
+9.	EA/ACL support in dump (requested by Michael Ju. Tokarev 
+	<mjt@tls.msk.ru>.
+
+10.	Better readline completition in restore (escape spaces etc).
+
+11.	Dump compiled with RedHat's 7.0 gcc seems to hang for some
+	people. When compiled with kgcc all the problems disappear.
+	Will the RedHat's 7.1 gcc resolve this ?
+
+12.	Dump uses /dev/tty for reporting some messages. When invoked
+	from a script, /dev/tty may not exist. Why not using just
+	stderr ?