-
Tomb allows for creation of too small tomb that the underlying file system cannot use.
e.g. tomb create -s1 is valid, but won't work. (Ext2 needs at least 4M)
-
I would like to capture the total number of interactions in the database, the total number of unique interactors (this would include non-biological and unidentified stuff), and the total number of uni…
-
That's a strange issue.
Here's the scenario. A tomb is on a remote server. The key is on our usb pen.
We mount the remote server filesystem using sshfs. tomb has troubles when opening it.
Some notes:…
-
slam_tomb() should be revised: it don't slam tomb.
I'm unsure about fuser syntax; also, we don't implement an -f option, but the code above mentions it.
Anyone got this issue? Please check it out.
-
The undertaker is strongly based on the idea of "scheme" (for example, `http` is the scheme for `http://tomb.dyne.org/`
When undertaker is requested a scheme that it doesn't know, it should check for…
-
changing the password is sometimes needed, because the previous one could have been revealed some way.
This will also allow to have different key copies with different passwords.
-
the correct tomb invocation is: tomb [command] [options] [file] [place]
Also, the -k option do not accept argument, then the only way to use tomb is that the tomb file and key must be on the same dir…
-
Automatically reported error generated by the site at runtime:
```
Failed lookup for key [lat] in [{'block': , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ]>}, {…
peej updated
14 years ago
-
Automatically reported error generated by the site at runtime:
```
Failed lookup for key [lat] in [{'block': , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ]>}, {…
peej updated
14 years ago