Am Donnerstag, 31. Mai 2001 14:15 schrieben Sie:
Am Donnerstag, 31. Mai 2001 13:28 schrieben Sie:
Guido Tschakert wrote:
Hi list,
while trying to use cipe with 7.1 I run in the following troubles: The kernel module in the rpm of cipe is build for kernel version 2.4.0 but the 2.4-kernel on the distro is 2.4.0-4GB, so the module cannot be loaded. Next I tried to build cipe from the corresponding spm and hoped the module would be build for 2.4.0-4GB but it was copied to 2.4.0/misc and insmod/modprobe still says: You are using kernel 2.4.0-4GB, this module is for kernel 2.4.0, which is completely different :-( Is it possible just to rename the kernel (and if yes, how to do this exactly) or am I missing something while building cipe from th sources. (I used the command rpm -bi cipe.spec) Trying to use freeS/WAN I run in similar problems (module is for 2.2.18, I used kernel-udpdate 2.2.19). Mostly I want to use cipe with Kernel 2.2.19.
BTW. In the last week I posted 2 or 3 other questions about VPN but didn't get much answers. Are my questions too trivial or doesn't nobody on this list uses vpns with linux?
Hoping for some hints
If you don't need 4gb mem support then turn it off in the kernel and uname -r will no longer append the 4gb part and you should be able to use the module.
I think this idea will work (i didn't testet it), but on the other hand: wouldn't it make more sense to fit the cipe-module to the kernel than the other way round?
At the end I find a way to build a new module for cipe. The problem was in the kernel-source-tree: I had to change the definition of UTS_RELEASE in include/linux/version.h from 2.4.0 to 2.4.0-4GB. I'm not a kernel-guru, so I asked myself: Why is the kernel-release called 2.4.0-4GB when 2.4.0 is the definition of UTS_RELEASE. I thought SuSE builds the kernel with the sources shipped with the package or does enabling 4GB in the kernel change the release name without changing the definition in the sources? (I know this isn't anymore a security-question) Guido -- ----------------- Guido Tschakert SRC GmbH, SysAd -----------------