Yea, you definitely don't wanna uninstall that stuff.
If I'm not mistaken there's a specific version of coreutils for BusyBox, but the standard coreutils stat binary compiles fine and seems to work with OS2008.
I think I compiled coreutils in Scratchbox and copied the binary. I have to research and see what others are doing as far as doing it cleanly with packages and dependencies and such.
Here's the stat binary by itself if you want to test it. Just dump it in /usr/bin and see if it works.
As you probably know, if you create a new crypt file in TC 5.x, you won't be able to open it in 4.3a (which is what EasyCrypt uses). However, any crypt files created in 4.3a are backwards compatible and TC 5.x will open them.
If you are using Truecrypt 5.x on your PC and have built crypt files with 5.x, those will NOT open in Truecrypt 4.3a (which is what I use in EasyCrypt). This is because Truecrypt 5.x uses the newer XTS mode of operation, which cannot be opened by 4.3a since 4.3a only understands LRW.
If you're using 4.3a on your PC and those crypt files still can't be opened on your IT, then there's something else going on that needs to be investigated.
As far as root access to the mount, EasyCrypt, in theory works like this:
If you mount an msdos or vfat file system crypt file, truecrypt mounts it with user mode (-u).
If you mount an ext2 or ext3 file system crypt file, truecrypt does not use user mode, but rather does a chown user.users on the mount point after it has mounted the crypt volume.
When your crypt volume is mounted and if only root can write to it, drop down to an xterm and let me know how it's chowned. As user, are you able to chown it to user.users succesfully and then write to it?
Just thought I would say that I have also gotten EasyCrypt working using the info on your site and from this forum. I did also need to install stat (and forgot to chmod it in my first 2 trials) but everything is up and working now. Thanks, I had been looking for truecrypt support since buying my N800.
I have now write access to the volume.
Only if I choose "fat" as filesystem, than I have no write access.
With "vfat" it works.
Isn't it better to set the default filesystem to vfat?
Or is there an advantage of fat compared to vfat. besides the write access isn't working with fat.
Thanks for troubleshooting that. I found the bug and will post an updated deb file with a few other changes too as soon as I can.
I'm not sure there's any advantage to using FAT. The original version of EasyCrypt included it so I just left it in. I suppose there might be some really obscure need for someone to have it.
I'm having a hard time installing because of its dependence on e2fsprogs. I can't install this because it says libcomerr2 is not installable. I don't have any Ext2/3 containers, only vfat ones. Is there some way to get this all happy?
