On 07/29/2018 08:01 AM, Carlos E. R. wrote:
It has been explained many times.
openSUSE uses the SUSE (SLES) kernel, and this one, once a candidate version is chosen, undergoes a period of testing with paying customers to verify that it works with them. This process takes months, thousands of man-hours and on sites. They are not going to repeat the costly process just because there is a new kernel upstream.
An off the shelf kernel can not be used unless upstream does that costly testing (certification) procedure.
That was the point, if 4.0.4 worked, then those capabilities would still be in 4.14, they wouldn't disappear? By the time a kernel is a year old, it is one on the most tested pieces of software world wide. There is nothing that makes suse customer machines any different from redhat customer machines. Further, there would be no need for the massive back-porting of new capabilities and security fixes to the old kernel, and customers with new hardware are supported out-of-the-box. Personally, it doesn't make any difference to me, I don't have a dog in that fight, but from a basic business 101 standpoint, if I can reduce the cost of my inputs by 90% -- that's 90% I'm losing now.... Obviously, it has worked for suse, but it has always been one of those curiosities... which I would wager if suse pulled LTS and pushed it out in SLE with the normal SLE config -- it would be seamless, and it would have been done with a savings of 999,999,995 man-hours from the original billion based on the functionality and security fixes already in LTS that would otherwise be part of the massive backport-and-tweak effort. To each, his own... I guess. -- David C. Rankin, J.D.,P.E.