On 11/01/2011 12:19 PM, Les Mikesell wrote: > On Tue, Nov 1, 2011 at 10:57 AM, Digimer <linux at alteeve.com> wrote: >> >> So long as I can do a 'yum update' and not get the next y-stream >> packages until the actual y-stream is released proper, > > But you also don't get potentially critical security updates until the > full release. That is, yum update won't give you anything. Having critical updates available in CR gives me the opportunity to, when I deem it sufficiently critical, to manually pull the package (and it's dependencies) down *or* enabling the CR repo entirely. >> I am happy. In >> other words, so long as the stability of my nodes is not effected in any >> way, and compatibility with upstream also remains, I am happy. :) > > What stability problems would you expect from updates beyond a point > release? The whole point of an 'enterprise' distribution is the > effort they make to not break api's across a whole major-rev's life. > Would an upstream system break if you selectively update packages > beyond a point release without doing a full update? As I mentioned earlier, after enabling CR I started seeing kernel oopses. I will need to be more diligent when I see the error next time and submit a bug report. >> I'm ashamed to say that I neglected to do so. I saw kernel oopses while >> working on other things and didn't get back to them... I'll be sure to >> file a bug next I see it. > > That's ummm, strange. Wouldn't you be running that kernel even if the > whole release had been completed? I really can't say, as I said, I wasn't sufficiently diligent at the time as I was fighting another fire. I do believe the kernel was upgraded when I went to the CR repo though. I'll build up another pair of machines and see if I can reproduce the issue tomorrow. -- Digimer E-Mail: digimer at alteeve.com Freenode handle: digimer Papers and Projects: http://alteeve.com Node Assassin: http://nodeassassin.org "omg my singularity battery is dead again. stupid hawking radiation." - epitron