]>
Commit | Line | Data |
---|---|---|
1 | $Id: TODO,v 1.25 2005/05/02 15:10:44 stelian Exp $ | |
2 | ||
3 | Need to verify: | |
4 | --------------- | |
5 | ||
6 | 1. Verify that dump works with kerberos authentification (this | |
7 | was ported from *BSD and was not tested - in fact, this | |
8 | wasn't even compiled in!). Need success reports for this. | |
9 | ||
10 | Urgent items (for the next stable version): | |
11 | ------------------------------------------- | |
12 | ||
13 | All others: | |
14 | ----------- | |
15 | ||
16 | 1. More documentation? Examples, crontab? | |
17 | ||
18 | 2. Explore and correct dump problems on active filesystems | |
19 | (lseek/read negative count) (This should be OK as of 0.4b14. | |
20 | Unfortunately, this seems to continue for a very few users). | |
21 | ||
22 | 3. Reimplement the ext2 specific code in a "backend" and | |
23 | make the dump code more generic. This would allow creation | |
24 | of other backends for other filesystems. Implementing a | |
25 | (v)fat backend should be quite easy, as for BSD ffs (we | |
26 | already have the code for this). The BSD code in traverse.c | |
27 | (all those #ifdef _BSD) should go into the ffs backend. | |
28 | ||
29 | 4. Implement a DEBUG option which doesn't fork on each tape, making | |
30 | it able to debug dump with gdb. | |
31 | ||
32 | 5. Make a bootable dump tape? I don't know if it is possible... | |
33 | ||
34 | 6. Better readline completition in restore (escape spaces etc). |