Andrew J Glover flexifoil@btinternet.com writes:
/usr/include/linux is supposed to be a symlink to /usr/src/linux/include/linux, isnt it?
No. Never.
If you do that, if you replace your kernel source (eg to start moving to another kernel version or patchset, but not immediately), you could find yourself linking against the wrong kernel headers. Especially if (like me), you have more than one kernel lying around in similar locations. Or what if you decide to delete the kernel source because you broke it badly while hacking it?
On debian, you'll also confuse the kernel-headers package that was installed when you installed your system. I think other distributions have similar packages.
Use the kernel-headers package made by your make-kpkg. You know it makes sense. (Make sure that it's the right one for the kernel, though.)
MJ Ray wrote:
No. Never.
too late! ;)
If you do that, if you replace your kernel source (eg to start moving to another kernel version or patchset, but not immediately), you could find yourself linking against the wrong kernel headers. Especially if (like me), you have more than one kernel lying around in similar locations. Or what if you decide to delete the kernel source because you broke it badly while hacking it?
On debian, you'll also confuse the kernel-headers package that was installed when you installed your system. I think other distributions have similar packages.
Use the kernel-headers package made by your make-kpkg. You know it makes sense. (Make sure that it's the right one for the kernel, though.)
Ahh.... I'll do that next. There isnt actually a headers package installed, but I'll make one now.
Ta!
Andrew
All compiled, loaded, but using losetup doesnt work..
losetup -e blowfish /dev/loop0 .private Unsupported encryption type blowfish
Anyone had this problem before?
Andrew
For those interested, theres another method I just came across:
http://mail.nl.linux.org/linux-crypto/2001-04/msg00025.html
Andrew
-
Andrew J Glover -
MJ Ray