Time to download the minimal ISO to configure as an install on my ProxMox server for KVM use.December 1st 2013
The CentOS team is pleased to announce the immediate availability of CentOS 6.5 for i386 and x86_64 architectures.
Time to do a repository cleanup and remove the unneeded packages...
Is this one upgradeable?December 1st 2013
The CentOS team is pleased to announce the immediate availability of CentOS 6.5 for i386 and x86_64 architectures.
Time to do a repository cleanup and remove the unneeded packages...
6.X --> 6.X easily done via yum update
5.X --> 6.X --> can be done, but the last time I tried, it broke the test server, so I went for a fresh install on the latest version.
Every documentation, including their own official site says that upgrading is not supported. Even you admit, that it breaks the system trying.6.X --> 6.X easily done via yum update
5.X --> 6.X --> can be done, but the last time I tried, it broke the test server, so I went for a fresh install on the latest version.
Where have you read that?Every documentation, including their own official site says that upgrading is not supported. Even you admit, that it breaks the system trying.
A "fresh install" is not always an option for people who have high traffic sites and don't want to take their site offline in order to start over. Of course you can go around that by getting an extra vsp or dedicated server, but that's going to cost you extra.
Either way, I wish you all luck.
So why is not as simple as doing an upgrade?
I agree with the principle of doing a clean install on a major version change. If an upgrade supported or not, ill still do a clean install.
apt-get update
apt-get apt-get dist-upgrade
apt-get update
apt-get upgrade
apt-get update
apt-get apt-get dist-upgrade
Well that's what I'm talking about.... 5.x to 6.x. And this isn't the 1st time either, I recall v4 could not be upgraded to v5.Where have you read that?
Upgrading from says CentOS 5.9 to 6.5 is a big no no, but upgrading from CentOS 6.4 to CentOS 6.5 is a simple "yum update" and reload for a new kernel. This is a minor point release, so upgrading isn't an issue is you are already on the 6.X release. My initial VPS build was on 6.2, and yum update put it onto 6.4.
I'm just really curious and maybe a little confused as to why people would "put up" with the accepted idea of it being the norm to always do a fresh install in order to upgrade centos?
There is no issue in upgrading Ubuntu 12.x to 13.x It's supported and encouraged in that there is even a built in tool to do it.True, same as you can from Ubuntu from 12.X to 13.X
Why? I personally don't know. I'd guess because they are vastly different between major releases.
http://wiki.centos.org/FAQ/General#head-3ac1bdb51f0fecde1f98142cef90e887b1b12a00
Do I expect all the add-ons to work in XenForo 2.0 upon it's release?Whats to "put up" with?
With a major upgrade I almost certainly expect main opperational items to be upgraded or replaced to the point of breaking backwards compatability. Otherwise, its just another example of poor versioning, why mark something as a "major" update if it isn't *actually* a major update? As an example, do you expect all your current addons to work with XenForo 2.0?
Do I expect all the add-ons to work in XenForo 2.0 upon it's release?
No, but then again I'll be able to upgrade XenForo 1.x to XenForo 2.x without having to start over.
I expect the same from Microsoft Windows. If I upgrade Windows Vista to Windows 8, I expect some programs to need to be upgraded or replaced. The same can be true for most any OS you upgrade, you're going to need to update the programs you use on it.You can also upgrade a blank (=empty) CentOS 5.9 server to CentOS 6.5 without problems.
However you have to expect that software and daemons you run at it may break.
There are way to many library changes in between major versions, performing an upgrade will simply break the upgrade process.I just find it a little more hard to accept never being able to upgrade the OS to the next major version. As it seems to be the case with CentOS (which does not provide an upgrade path).
There are way to many library changes in between major versions, performing an upgrade will simply break the upgrade process.
I understand other distros are able to upgrade easier... I invite you to look at this chart and see which:
I personally believe the proper way to upgrade a major version is to do a fresh install, even if the upgrade will "work". I real life is not a "clean" upgrade, even if you think it is. Incidentally, Fedora has the easiest install/upgrade process, yet it always breaks when you perform a major upgrade.
I always use minimal installs... and always get a kick out of that graphic... All I can assume is that it pertains to a LiveCD or regular FULL install with a graphic front end. I have yet to find a minimal install (or network install) ISO for Fedora (have found EC2 cloud images - but I don't use EC2 and everything I read indicates you have to create your own minimal install). At least with centOS and Debian (the only two distro's I'm playing with currently) you can do minimal installs. Never saw the need for a graphical front end on a dedicated server.This and systemd are the reasons why I still put in the extra work to use Arch on my servers. I got tired of the stress and risks of major upgrades (Arch updates are always 100% painless assuming all instructions are followed), and systemd is an absolute godsend for servers.
Ya, Fedora have a full Desktop iso. I never use a Desktop version also, all my setups are minimal CentOS installs. The thing is, even if you select the minimal install on a full 4Gb disk, it is not "minimal" CentOS will install a bunch of useless packages, even on minimal. The only way I do it is by using a true minimal .iso. I remember way back I had a Desktop setup on CentOS. When I was compiling certain RPM's, they were adding crazy deps from Desktop, so when you added that package on a minimal setup, it would add extra packages.I always use minimal installs... and always get a kick out of that graphic... All I can assume is that it pertains to a LiveCD or regular FULL install with a graphic front end.
We use essential cookies to make this site work, and optional cookies to enhance your experience.