Summary: | KV variable inappropriate for some kernels with cisco-vpnclient-3des | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Adam Carheden <adam.carheden> |
Component: | New packages | Assignee: | Chris Gianelloni (RETIRED) <wolf31o2> |
Status: | RESOLVED NEEDINFO | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 2005.1 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Adam Carheden
2006-01-27 07:48:41 UTC
Ehh, KV should always be the version of the kernel linked to by /usr/src/linux and not `uname -r`, at all. In your case, it is valid because that is your booted kernel. Basically, you should be able to compile a new kernel, then the vpn client, without having to reboot to you new kernel first. Anyway, since your solution is only run if the KV dir cannot be found, it'll work for now. I'm guessing that thre's something appending the Xen string improperly, as it isn't showing up in the Makefile for KV to pick up. (In reply to comment #1) > I'm guessing that thre's something appending the Xen string improperly, as it > isn't showing up in the Makefile for KV to pick up. My kernel came from the xen-sources package, so possibly this bug should be assigned there. I appended the _DATE at the end, but -xen came from the package. I just updated all of the ebuilds in CVS for another bug (bug #119057). Can you see if this resolves the issue for you, also. I think it might work around the issue. I never got a response, so I'm going to assume that this fixed it. If it didn't feel free to REOPEN the bug and we'll look at it some more. |