On 19. 07. 19, 10:09, Hans-Peter Jansen wrote:
Am Freitag, 19. Juli 2019, 05:38:03 CEST schrieb simonizor:
The kernel releases for Tumbleweed have been coming out pretty slowly lately. When I started using Tumbleweed in November of 2017, it was not at all uncommon for Tumbleweed to get a new kernel release before Arch got the same kernel release. Now, it seems like we get new kernel releases a week after they are released upstream at best. I personally have been using kernel:stable because of this, but due to the kmp setup and not using dkms, not everyone can do this.
Is there a reason for this? I personally have not had a single issue with the kernels from the kernel:stable repo (I'm using 5.2.1 right now without a single hiccup), so the quality of the kernels does not seem to be the issue.
While I guess, the basic reason is about human resources, or better the lack thereof, I second a slightly more conservative kernel release management, as it is practiced today.
There is at least one caveat. If something breaks in that many (even stable) releases, it's quite harder to find the culprit in thousands patches instead of a hundred.
What does it buy you to live one or two weeks ahead, especially in the major kernel release version gap, other than dealing with yet another NVidia fallout, Virtualbox hassles, ... Check the change logs for reverts. They're done for a reason. I don't want to be my systems *that* reason.
There are people not using nvidia, vbox or other out-of-tree thing at all. Anyway, those are usually problem only on major version updates.
After all, kernel:stable is there to be used from the more adventurous ones. All the kernel guys are doing a fantastic job, but we're living in a complicated world nowadays.
Sure, kernel is 30 millions line of code... Even if every 1'000th line had a bug, we would have 3000 bugs (there are likely many more). thanks, -- js suse labs -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org