current KEYWORDS="~amd64 ~ia64 ~ppc64 ~sparc ~x86" target KEYWORDS="amd64 ~ia64 ~ppc64 ~sparc x86" thanks
it looks like vserver-herd took care of the stabilisation in the past - and I'd be happy if it stays like that.
Thilo, let me check it tomorrow on my servers and I'll mark them stable after that.
Sorry for delay. I just noticed that this is rhel5 based kernel which is broken in that many aspects that I don't think we want it to be stable. It's really pain to build it - too many config options combinations just don't work. I still fail to boot one of my stations with it for still unknown reason (while it works fine with vanilla).
pva: well, the reasoning for asking for stable marking, is that we have an older release marked stable. i'd prefer to have the 2.6.24 marked stable anyday... what do you suggest we do wrt those people who use the 2.6.18 redhat based stable kernel?
(In reply to comment #4) > pva: well, the reasoning for asking for stable marking, is that we have an > older release marked stable. No, we have different kernel stable - vanilla kernel. None of rhel5 based kernels were marked stable. 2.6.24 is a different topic. I still want to follow whatever upstream suggests us and last time I've asked they suggested to use 2.6.18. That's said I've asked 1 year ago. I'll try to upgrade my systems onto 2.6.24 and I've already awaiting for reply from upstream about their thought on this topic... As soon as they answer I'll follow their reply to vserver alias.
> > No, we have different kernel stable - vanilla kernel. None of rhel5 based > kernels were marked stable. i haven't fully understood what you mean, but this is what i am talking about: http://packages.gentoo.org/package/openvz-sources version 2.6.18.028.056.1 is marked stable on amd64 and x86. what migration path do you suggest for those users?
(In reply to comment #6) > > No, we have different kernel stable - vanilla kernel. None of rhel5 based > > kernels were marked stable. > > i haven't fully understood what you mean, but this is what i am talking about: > http://packages.gentoo.org/package/openvz-sources Heh, looks like you missed that there are different kernels inside single kernel package. This is really historical reasons and mess we had due to long time forward 2.6.26/27 kernels. openvz-sources-2.6.18.028.056.1.ebuild and openvz-sources-2.6.18.028.059.6.ebuild are *different* kernels. The first one is based on vanilla linus kernel + openvz patch while another on vanilla kernel + rhel5 patches + openvz patches. The kernel with rhel5 patchset is really hell to maintain for source based distribution and we should avoid it in stable. OTOH rhel5 patchset backports lot's of drivers to support recent hardware. Having one kernel in stable and another in testing reflects the fact that I want users first try vanilla openvz kernel and if it does not support some hardware rhel5 based kernels. > version 2.6.18.028.056.1 is marked stable on amd64 and x86. what migration > path do you suggest for those users? Um, see vserver-devs alias (and personal mails, btw). I think the only viable solution for us is to move forward to 2.6.27.
(In reply to comment #7) cool - thanks for clearing that up. looking forward to 2.6.27...
