[BlueOnyx:00947] CentOS-5.3 has been released

[Michael Stauber]

Hi all,

A small heads up:

The CentOS team has just released CentOS-5.3 and patches are now available 
through YUM.

Release notes: 

http://wiki.centos.org/Manuals/ReleaseNotes/CentOS5.3

Please note:
==========

I'm currently testing what effect running a "yum update" has on BlueOnyx and 
based on the release notes I can see that there may be some issues here  and 
there in certain areas.

Cautious souls are encouraged to disable automatic YUM updates for a few days 
until those issues are ironed out.

My findings so far:

Stand alone BlueOnyx installs (ISO or TAR-ball installs):
============================================

Seems to be the most trouble-free. Had two stand alone servers running through 
"yum update" without issues. A third one had the error detailed in the release 
notes and reported this error message:

"rpmdb: unable to lock mutex: Invalid argument". 

This could be overcome by running ...

	yum update glibc

... first and then running "yum update" again.


BlueOnyx OS template for Aventurin{e} / OpenVZ :
=======================================

At this time it is not possible to "yum update" a BlueOnyx Aventurin{e} / 
OpenVZ OS template due to dependency issues:

Package hwdata needs module-init-tools >= 3.2, this is not available.
Package initscripts needs module-init-tools, this is not available.

This will be resolved sometime today with an updated "dummy-centos-5.3" RPM 
out of the Virtual BlueOnyx YUM repository. 

Once that new RPM has been released, it will be possible to "yum update" 
BlueOnyx VPS's again as well.

---

Of course this also means that there will be some upcomming code changes to 
BlueOnyx during the next few days to cope with CentOS-5.3 (very few, mostly 
detailing with the install).

Additionally an updated ISO image and an updated OS template for Aventurin{e} 
and OpenVZ will be available within the next couple of days.

--

If you run into errors while updating BlueOnyx with YUM, then please post your 
error message here.

-- 
With best regards

Michael Stauber