Here's something I'd like to share with you: encfs (cf. http://www.arg0.net/encfs) for the N810/Diablo.

I originally wanted to do this properly as .deb packages, but found it too cumbersome: encfs uses two small parts of libboost, which is quite a large beast all by itself, librlog, and fuse - all of different origins - and requires the fuse kernel module. In my understanding these would all have to be done as separate packages resulting in 5 separate packages - fuse kernel module, fuse-utils, librlog, libboost, encfs - just to provide a single usable functionality.

I've therefore chosen to create a single compressed tar archive that needs to be untarred as root in '/' and wrapped the setup code in a shell procedure named runencfs.

I've created this stuff mostly because I wanted a better way to safely store data on my n810 - so "your mileage may vary" and "caveat user".

What are your general feelings on providing useful functionality outside of the packaging environment? Is this a no-go for you? Would you rather not have some functionality than having it this "amateurish" way?