CentOS 5.2 has been released
Posted: Tue Jun 24, 2008 11:30 am
Page 1 of 2
Posted: Tue Jun 24, 2008 11:34 am
Somebody has it running already? or do we have to wait till ASL is compatible?
Posted: Tue Jun 24, 2008 11:45 am
There should be no problems, but I haven't had the time to try it yet.
Posted: Tue Jun 24, 2008 11:58 am
Please let us/me know when you did 
Thx!
Thx!Posted: Tue Jun 24, 2008 3:02 pm
Works just fine on the one machine I tested it on just now.
You might want to read the release notes and release announcement before upgrading, as there are some known issues. Most notably the performance issue with 3ware RAID cards. CentOS has an alternative kernel in testing and I expect Red Hat to release an update for this soon.
Also don't forget to use 'yum upgrade' instead of 'yum update' when installing a new OS upgrade.
You might want to read the release notes and release announcement before upgrading, as there are some known issues. Most notably the performance issue with 3ware RAID cards. CentOS has an alternative kernel in testing and I expect Red Hat to release an update for this soon.
Also don't forget to use 'yum upgrade' instead of 'yum update' when installing a new OS upgrade.
Posted: Tue Jun 24, 2008 3:12 pm
There was one warning from the new selinux-policy-targeted package:
We don't use SELinux on our servers (ASL even disables it for the ASL kernel), but I don't know if would be a problem when you do use SELinux.qscand homedir /var/spool/qscan or its parent directory conflicts with a defined context in /etc/selinux/targeted/contexts/files/file_contexts, /usr/sbin/genhomedircon will not create a new context. This usually indicates an incorrectly defined system account. If it is a system account please make sure its login shell is /sbin/nologin.
Posted: Wed Jun 25, 2008 5:17 am
What about this: http://kb.parallels.com/en/234
Has anyone did this or just yum upgrade without editing yum.conf?
Has anyone did this or just yum upgrade without editing yum.conf?
Posted: Wed Jun 25, 2008 5:41 am
I don't use those instructions.
sendmail, bind-chroot and caching-nameserver should not be installed on your server and they won't spontaneously be installed when running yum upgrade or yum update. You could add them to the exclude list to be sure though, it doesn't hurt either.
I recommend not putting kernel* in the exclude list. Kernel upgrades are important, there was a local root exploit not too long ago that affected a lot of machines.
sendmail, bind-chroot and caching-nameserver should not be installed on your server and they won't spontaneously be installed when running yum upgrade or yum update. You could add them to the exclude list to be sure though, it doesn't hurt either.
I recommend not putting kernel* in the exclude list. Kernel upgrades are important, there was a local root exploit not too long ago that affected a lot of machines.
Posted: Wed Jun 25, 2008 6:16 am
It´s a virtual maschine (VE) not a hardware-root-maschine.
Does it matter?
Does it matter?
Posted: Wed Jun 25, 2008 6:38 am
If it's Virtuozzo/OpenVZ then your server uses the kernel of the host machine and then you cannot control the kernel yourself. In that case you probably don't even have a kernel package installed in your virtual server, so it doesn't really matter.
Posted: Wed Jun 25, 2008 6:40 am
I updated two ASL2 machines without problems (yet)
Posted: Wed Jun 25, 2008 6:44 am
I guess this is not the case for the ART kernels? I have one server with a 3Ware RAID controller...Most notably the performance issue with 3ware RAID cards. CentOS has an alternative kernel in testing and I expect Red Hat to release an update for this soon.
Posted: Wed Jun 25, 2008 6:50 am
No, that is just an issue with the current RHEL/CentOS 5.2 kernel.
Posted: Wed Jun 25, 2008 6:52 am
Thx! then I am going to update that one to now
then I am going to update that one to now Posted: Wed Jun 25, 2008 8:45 am
mmm, it messed up the ART YUM GUI in Plesk: http://atomicrocketturtle.com/forum/vie ... 2906#12906