VSEL includes a feature called Kernel Module Versioning (Mod-Versioning), which greatly reduces the Kernel version dependencies seen in earlier versions and provides On-Access Scanning on new Kernels without having to recompile the Kernel Modules.
How Kernel Module Versioning works
If a client is running Kernel version 2.6.x with VSEL 1.6 (or newer), VSEL has modules for this version of the Kernel and On-Access scanning is enabled. The Kernel is then upgraded to 2.6.y from 2.6.x and the client is restarted.
When the client boots into the new Kernel, the VSEL startup scripts automatically check if the modules for Kernel 2.6.x will work with Kernel 2.6.y. If yes, then On-Access scanning is automatically made available on Kernel 2.6.y.
Kernel symbols are used to provide this feature. In most cases the symbols do not change as frequently as the Kernel version.
If the modules compiled for Kernel 2.6.x are not compatible with Kernel 2.6.y, then VSEL will start all services other than On-Access scanning.
