Roddy Rodstein wrote:There isn't one. There aren't any Ksplice repositories and this completely defeats the purpose of Ksplice. The entire point is to patch the kernel for all security errata with zero downtime. You could chose to apply individual Ksplice updates, but that would be remarkably tedious, I suspect. Even the new offline Ksplice RPMs work by taking the original kernel and applying all available patches to it.
Could you share your tips and tricks to be able to use Ksplice for minor OL/RHEL releases, i.e. 5.4, 5.5, 5.6, 6.1, 6.2, etc.....?
Roddy Rodstein wrote:It's really the same response though: Ksplice patches the in memory kernel, but doesn't change the on-disk kernel. If the server were to reboot or restart for any reason, you'd need to re-Ksplice the kernel to get it back to where it was. Thus, we recommend doing both: using Ksplice to change the in-memory kernel, but also using yum to upgrade so that if for any reason you have to reboot, you still have all the fixes/patches that were previously Kspliced. They are complimentary processes, not conflicting ones.
We really like O supports response!
Would you happen to know if using OEM deployment procedures for ksplice is bundled with oracle Linux support, or does the customer need to buy the application management pack to use deployment procedures for ksplice?You don't need the AMP as far as I know to use Deployment Procedures to run a shell script. It's part of the EM base functionality that's included with Oracle Linux suport.
Would you happen to know if ksplice is on Cloud Control's road map, i.e. will it be integrated into the Linux Host Patching feature?Of course it is. :) However, I have no idea when it'll be available.