Originally Posted by vano
Thanks for the info, so I guess the idea is to symlink (in the case of 1 for example, it would be symlinking the whole OmniFocus dir to the encrypted fs) correct? I guess there is no better way, right?
Regarding FileVault, the problem is that if it gets corrupted (and it does get corrupted when you run low on disk space, when going into standby goes wrong or etc.) you are pretty much out of luck. It has bitten me twice already. Also if it matters, FileVault uses sparse bundles, which is not the same as a disk image.
Anyhow I am interested in putting this inside an encrypted filesystem (MacFUSE with EncFS).
You've had recent corruption issues with FileVault? I really know of few, if any, with 10.5. 10.5 uses Sparse Bundles, which are much more resilient than Sparse Images. Also, in the cases where I _have_ seen corruption (with Sparse Images and 10.4), DiskWarrior was able to repair them (thankfully).
Note a SparseBundle _is_ a disk image. It is one type of image.
The disadvantage of alternative file systems shimmed in via MacFUSE is that MacFUSE is a kernel extension, and there's no knowing whether it will work across OS upgrades. I'm sure, given time and testing, it will, but I don't personally like that kind of shim as they tend to delay my OS adoption curve, and I'm a bleeding edger :)