Hi All,

I've just installed TrueCrypt 4.0 on my windows system. Of course it would be nice to use it from my linux system as well, and here's where the fun starts:

- my system was slackware 10.2 with default kernel 2.4.31, truecrypt needs kernel 2.6.8 or higher

i decided to download the latest stable kernel 2.6.14.2 and although i had bad experiences with self-compiled kernels in the past, this was pretty easy.

Once the kernel was installed i ran truecrypt installer again. Now it complains that it needs dmsetup. After some searching i came to figure out that it is the device-mapper. So i downloaded and installed device-mapper. Truecrypt is still complaining. It appears that my newly created kernel didn't support it.
After adding LVM support to the kernel this problem was finally solved.
Truecrypt is installed successfully but when i try to mount my encrypted container it gives the following errormessage: truecrypt: No free loopback device available for file-hosted volume

Of course i ran truecrypt as root, so it shouldn't be an access issue.
Since lo is available as always i don't really understand what to do with this. So to make a long story short ;-)

Anyone has any idea on how to solve this 'little' problem?

Thanks in advance!

Rgds,

Mark

Do you use udev? If yes add to devfs.rules: KERNEL=="loop[0-9]*", NAME="loop/%n"
If no:
mknod /dev/loop0 b 7 0
mknod /dev/loop1 b 7 1
.....
mknod /dev/loop7 b 7 7

Thanks for your response!

I've first used the udev option, but my devfs.rules was called devfs.rules.unsupported
I've renamed the file to devfs.rules

finally i've tried the other one as well with mknod, but with every loop[0-7] it returned "File exists"

So this should mean they are already there, shouldn't it?
Any other ideas?

Hmm, sorry. I assumed the loop nodes didn't exist. Hopefully someone else knows whats wrong with it, as I'm now out of ideas.

I already found what the problem is:

i had to add the following in the kernel configuration:

devicedrivers --> block devices --> loopback support.

After recompiling the problem is solved.
Thanks for your help anyway !