(I manage a handful of CentOS boxen and have found this out the hard way.)
(I manage a handful of CentOS boxen and have found this out the hard way.)
Between 6.x and 7.0 is another story and I wouldn't do this with any distro. Risk is too high. Just build new kit, test it then migrate services and data over piecemeal.
Debian screwing up dovecot configuration terribly between 6 and 7 is a fine example of why you shouldn't do this.
I've managed about 60 CentOS/RHEL machines, 30+ Debian machines, 20 FreeBSD machines and 200 Solaris machines and I've never done a major release in place upgrade.
I design stuff to be resilient to host reboots. Then again we have a lot of kit to play with.
DO turn SELinux off on their kernels and take ages to update so I can't really take them seriously for production to be honest. Also they appear to be VC backed which is usually a sign of shortcuts taking priority over proper due diligence.
Then again for $5/month, pay peanuts, get monkeys. Not bad monkeys for the money. I've paid 3x the amount and got worse monkeys.
The 6.3 -> 6.4 and 6.4 -> 6.5 updates arrived simply as software updates using the usual process just involving the download 340Mb of files. I gather the 6.x designation relates to updating the installer and packages available on the release DVDs
I think you are referring to 5 to 6 and ultimately 6 to 7. Major versions.