> world. Creating random pieces of code to be inserted in such an important
Kernel patches are hardly random. Ksplice probably works similarly to how run-time memory patchers/loaders work. > piece as the running kernel is quite opposite to this idea. So those pieces > of code would have to come from RH (compiled with the exact same toolchain > as the kernel they are inserted into) and they would have to be released and > tested for every possible kernel version that is affected... doesn't sound > easy. They try to do this already with normal kernel updates. Only RHEL (ksplice) updates would be supported obviously. _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
