On Sun, 20 Jan 2019 at 21:41, Michal Kubecek
On Sat, Jan 19, 2019 at 02:05:44PM +0100, Rainer Hantsch wrote:
So it seems that a new ISO with kernel 4.19 everywhere, should fix most of this troubles.
It might... except it would also _bring_ one big problem you seem to be ignoring (even if Stefan already hinted at it): finding a volunteer who would spend time on preparing such image and - even more important - keep maintaining the respective kernel branch.
Not to mention that if this hypothetical image kept following upstream stable-4.19.y, it would become (in your terms) "ancient" pretty soon anyway. Because even if stable branches receive a lot of patches which wouldn't be considered in the past, their aim still isn't backporting of new device drivers.
Having an image with Tumbleweed kernel would make way more sense - and would mean much less work.
Michal Kubecek
I agree that the Tumbleweed kernel is a better choice for this scenario than any other kernel we have If we're seriously entertaining the idea of alternative installation media for Leap I would like to advocate for it not just focusing on an alternative Kernel Like I've said repeatedly, in my experience Leap 15.0's kernel has never been the cause of a problem on new hardware, but issues with shim/grub2 have crept up multiple times. Also udev once. If we really do want to universally solve this for Leap, I think we'd need to look at casting the net wider and including more than just an updated kernel else we'll just find ourselves reading threads like these again. And while I wouldn't consider SUSE's lack of interest in this being a blocker to such an effort, given Leap is based on SLE and we're talking about replacing key parts of that SLE base system (even if it's on an optional basis), I'd also wonder whether SUSE, especially SUSE Product Management would be interested in something like this also? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org