Just find out about it on Hacker News, have fun updating!
http://lists.centos.org/pipermail/centos-announce/2013-December/020032.html
http://lists.centos.org/pipermail/centos-announce/2013-December/020032.html
Last edited by a moderator:
Can be fixed. http://www.webhostingtalk.com/showthread.php?p=8934739#post8934739Word of warning, I attempted an update to 6.5 on an OpenVZ container running on the 2.6.18 kernel (I believe that means the host node is using RHEL5) and the network ceased functioning. I did a reinstall and the network resumed working until I attempted another 6.5 upgrade. That may just be me or my host, but be warned. I did the same update on a container running the 2.6.32 kernel and everything worked fine.
Run uname -r. It's also easy to know if you've got 2.6.32 if you have vSwap or memory allocations that aren't fucky.For the end users, how do you determine what kernel the host is running?
#centos4lyfePointless thread.
#debian
Here's my workaround for this - https://www.fitvps.com/members/announcements/84/Upgrading-to-CentOS-65---the-workaround.htmlWord of warning, I attempted an update to 6.5 on an OpenVZ container running on the 2.6.18 kernel (I believe that means the host node is using RHEL5) and the network ceased functioning. I did a reinstall and the network resumed working until I attempted another 6.5 upgrade. That may just be me or my host, but be warned. I did the same update on a container running the 2.6.32 kernel and everything worked fine.
Quit hatin' brahPointless thread.
#debian