On 5/13/2011 5:11 PM, Greg KH wrote:
On Thu, May 12, 2011 at 08:41:41PM -0700, Jason Newton wrote:
aww, this is causing me lots system unstabilities (any kernel call @ one particular drive causes unkillable process deadlock)... I'd hate to waste the time of recompiling locally what will be out in a few days. Would it be possible to push the patch any sooner, even if directly atop what's out now?
If I'd have known I'd have stayed on the previous kernel (an older tumbleweed release from at least a month ago). I didn't see a stable kernel regression like this coming though.
Regressions happen no matter how hard we try, it's just a fact of life, sorry.
If you use tumbleweed, or heck, any release, I STRONGLY suggest that you keep at least one kernel installed on your system that you know works properly. zypper can easily handle multiple kernels, use that if you want, or keep one around by hand.
thanks,
greg k-h
That's not good enough. The repo should actually provide a way to manually choose older known-working builds. The updates repo does not delete the packages it updates. One is always the newest that gets installed by default, but every incremental package is still there also. For kotd , especially stable , I think that is really called for. Maybe in head you can say "hey, this is head" just like Factory is Factory and is always turning over. But push an untested kernel out, blowing away the current one irrecoverably, into a "stable" repo ? That is very unexpected, and now that I do know that it is allowed to happen, only _now_ I'll know, the hard way, to make my own one-way mirror of the repo so that in my copy the old packages don't go away. Merely enabling multiple kernels in zypper is not a good enough answer. If the current packages are bad in the repo, even if I have an old one still installed currently and don't uninstall it, I'm still screwed because I can't install any of the matching packages I might need, nor can I re-install the version I currently have, say if I uninstalled it or broke it, like say I had the source package, and some proprietary crapola 3rd party driver scribbled all over the source and I need to start over *cough*Dialogic/Eicon T1 cards*cough*. Nor can I install new machines and bring them to parity with the other machines already installed. I have to go back to the updates kernel, or wait until the kotd is good again, neither is always simple to accept. It's not the end of the world but it's not good. I think if k:stable isn't going to preserve at least some old packages (even if not every single rebuild, pick whatever milestones you like) then people should be warned against even using it. Might as well use head. The whole k:stable/standard vs distro-specific repos is still a mess too. I think it's a plain broken scheme but I'm still testing things and getting my thoughts and facts in order about that. With the old repos, as time goes on, and as the kernel inevitably breaks compatibility with the older distros, no problem, the old version-specific repos just stopped progressing at some point and for an old distro you'd still have a kernel that was far newer than the updates kernel for that distro, and only the other distros would continue to track the current kernel. Now what you have is for a given distro, the kernel gets higher, higher, higher over time, and then explodes and disappears completely one day and you only have whatever is in updates which could be 2 years old and be bad for you for any number of reasons. -- bkw -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org