On Tuesday 19 February 2008 11:27:27 Kai Ponte wrote:
On Monday 18 February 2008 06:39:43 pm Jonathan Ervine wrote:
Ummm - why should it be bizarre to run a script that compiles kernel modules every time the kernel is upgraded.
...simply because I fail to see why a third-party application would need to be linked so tightly to the kernel.
IMO, they should be abstracted, unless they're a hardware driver or a memory module.
Abstracted how? VMware and other virtualisation techniques have to make sure that each running VM doesn't try and access the same resources simultaneously. In order to do this they have to interact with the kernel. This involves creating network interfaces and monitoring the memory and processor requests etc. There's no way round this (yet) without requiring kernel modules. I don't think even the VMI code being put into the kernel will get away from this in the near future.
Same goes for the cisco vpn client.
Can't say I know the Cisco VPN client, but I imagine it uses IPsec and is also making use of network devices. For the same reason as above this requires an interface to the kernel and/or a new device being created. Not too sure how you propose doing that without requiring a kernel module. Jon -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org