Notices

Ah the problem is the n900 doesn't use the standard init.d stuff. LOL no wonder it wasn't working at all!

It uses upstart.

To fix as root:
Nathan

I wouldn't even use TrueCrypt. It's non-free and not open source and legally dangerous, as explained in https://fedoraproject.org/wiki/ForbiddenItems#TrueCrypt and http://lists.freedesktop.org/archive...er/000276.html. Also see the Wikipedia article about it.

We have much better encryption solutions, on the block level and on the file level (e.g. using ecryptfs).

Great work guys, it works now!

PS: I am a bit of a Linux noob (but I'm learning)!

Everyone is entitled to their own opinion -- including fedora. I read through both links, and several of their "problems" have already been addressed in the newer license that have been released since 7/2008. I've been using Truecrypt since it was forked from E4M. The issues you raise are more FUD than anything substantial for us.

However for cross system compatibility (Linux, Windows, Mac OS) -- Truecrypt is the primary solution. None of the other solutions to my knowledge work _reliably_ on Windows.

If you want a Linux only solution, yes their are better solutions. But since I compiled it for my own use (including the attached ntfs & cifs), I figured I would share with the community.

Nathan.

So lets says I got all of this working and mounted a drive with the code:
or something similar. How would I create a script to auto mount on startup? Step by step instructions would be awesome, I haven't done this in a long time (messed around with this on the n810 but got fed up).

How about putting it into /etc/fstab?

because I don't know what that means

See http://www.tuxfiles.org/linuxhelp/fstab.html or http://wiki.linuxquestions.org/wiki/Fstab.

But if you're playing with such stuff, you should know it.

here a working /etc/fstab example:
works for me, so i just need to issue "mount some_directory" in xterm to get access. if you change "noauto" to "auto", it should happen automatically at bootup, but usually that's not a good idea. changing "ro" to "rw" will enable write access.

i haven't tested without noauto, but it could really stretch your boot-time if the device waits for some time-out when you're nowhere near your local net.

also, this is a CLEARTEXT password! so create a user with minimal rights on the server just for this purpose, the "pass=" parameter is not optional if you want to use fstab.

edit:
/etc/fstab is autogenerated, so the above line has to be put somewhere else to be permanent, but i got no time to look now

Nathan, I appreciate your effort, as it's the only thing I've seen this far that gives CIFS/Samba support. I will not try this, as it is too much "tinker until it temporarily works" for my comfort level, but I do appreciate it.

I hope someone will take this a few steps forwards so we can one day find key words like "samba" in extras-testing. Hopefully without the words "this firmware version".