Andrew Lentvorski wrote:
Joshua Penix wrote:
What are you trying to do that's so sensitive to the -10 that it won't
accept -3 or a recompile against the updated 2.4.20 kernel? Binary
drivers?
Stupid VPN software. Checkpoint Firewall-1.
And, it *might* work. I don't know. The point is that it requests a
specific version of the kernel. After I establish that it works, then I
can establish that it works with later versions.
I have a source RPM for kernel-2.4.18-17 and I have one for the original
kernel-2.4.18-3. The kernel patches can probably be massaged to recreate
the kernel-2.4.18-10 based on the changelog if you're willing to try it.
Wow, computer archeology!
Once I get this encapsulated, I expect to dump it into a VMWare machine
and proxy the stupid VPN so that I can use an OS that isn't 6 years old.
Of course, the only reason I have to even worry about this is because
Linux finds it beneath themselves to worry about silly things like
kernel API compatibility. Otherwise, I'd just make the jump to .20 and
be done with it.
I won't ask why you are stuck with proprietary software. But it seems to
me that blaming Linux for your failure to maintain proper archives and
the failure of Checkpoint to stay up to date is not the way to go ;)
Gus
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
