Hi Samuli, On Wed, Jun 08, 2005 at 12:17:37PM +0300, Samuli Suominen wrote: > in /usr/share/doc/loop-aes-source/README.Debian, starting from line 15 > it says: > > Kernel source requirement > ------------------------- > > loop-AES requires a full kernel source tree to build (kernel- > headers are not sufficient). Unless you already have a source > tree available, you could install one like this: > > # apt-get install kernel-source-VERSION > # cd /usr/src > # tar -xjf kernel-source-VERSION > > But in line 78 it says it's different for 2.6 users. Seems like > kernel-headers IS sufficient for 2.6.8-2 users!
Maybe this line created a false impression :) kernel-headers are not sufficient, also with 2.6 kernels. This is because the Makefile for loop-AES needs the full kernel source (or rather the file loop.c) to determine which settings should be used for a particular kernel. The note on line 78 about Module.symvers is to help create a source tree that resembles the original as closely as possible - including the correct value for symbol versions. Without that line the module still works, but will taint the kernel when it's inserted. So the note is meant as: Do all the steps for 2.4 kernels, and all the steps plus the one that says "only for 2.6" for 2.6 kernels. Maybe this is confusing or badly worded, perhaps you have an idea how it could be expressed better. > And module-assistant auto-install loop-aes works. The interesting question is: What did you do to make it work? Is it possible that you used module-assistant fakesource to create that source tree? Compilation with auto-install and only kernel-headers should fail with a description of the problem, because loop-aes-source and module-assistant know that it needs a full kernel source tree and include checks for this. > I guess this won't hit sarge but would be nice to get it fixed for > Etch users. The requirement for full kernel source will probably stay for a while. But "module-assistant fakesource" does basically the same as the steps described in README.Debian and is much easier, so the way forward will probably be to document this command instead. cheers, Max -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
