Jaromil

I suspect this won't solve the issue. Cryptsetup `close` command is different from `losetup -d` which will fail anyway until the *actual* close is done, plus this is not a...

hi Steve! indeed that should be it. Lets add support for this corner case however, close could detect and strip the .tomb extension passed on command line.

There was a list once used, but not anymore (silent since years) for all things crypto at dyne that is https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/crypto best is anyway IRC channel `#dyne` on our server...

Ack, slam sometimes fails on that. Mapper volumes should be closed by `cryptsetup luksClose` but when the loopback is missing underneath they may be left hanging.

Hi! can you please confirm this issue is solved using latest version from git?

if we make it configurable, what's the best way to check which filesystem the tomb is formatted? I mean, without mounting it? this is needed for instance in case one...

Bumping this issue since I want to use ZFS now on some tombs. It features history and compression. So I'll take it from here and hack something together soon. I...

ZFS works in a very different way than other Linux filesystems, it needs to have ad-hoc code for its usage. Why do you think FAT is great? can you sketch...

Don't use FAT to solve such a problem. FAT will never make it in Tomb for such a reason, it is a complex way to solve a simple problem and...

ACK, true there is no -R in that chown I've pointed. Hellekin analysis here is fairly complete. about 1) yes, "specific reasons" come in mind, however I can't think of...