Hello all, For (system) certification purposes, we have to upgrade our 4.4 machines to 4.7. In the past I usually have just reinstalled machines to save the (perceived) headaches of upgrading. That is not an option in this case. Are there any pitfalls to watch out for when upgrading? Is it even possible to go up 3 revisions? Thanks, John
At Thu, 24 Jun 2010 07:53:47 -0400 CentOS mailing list centos@centos.org wrote:
Hello all, For (system) certification purposes, we have to upgrade our 4.4 machines to 4.7. In the past I usually have just reinstalled machines to save the (perceived) headaches of upgrading. That is not an option in this case. Are there any pitfalls to watch out for when upgrading? Is it even possible to go up 3 revisions? Thanks, John
Why to 4.7? The current point release for CentOS 4 is 4.8. Going from 4.4 to 4.8 is trivial ('yum update' then 'shutdown -r now').
Only going to 4.7 because the required app is not certified for 4.8 (In the RHEL world which is what we are basing this on). 4.7 is as high as they will go. I know I will be doing this again in a month's time when they have 4.8 certified... I just do as I am told...To an extent... Thanks, John
On Thu, Jun 24, 2010 at 9:01 AM, Robert Heller heller@deepsoft.com wrote:
At Thu, 24 Jun 2010 07:53:47 -0400 CentOS mailing list centos@centos.org wrote:
Hello all, For (system) certification purposes, we have to upgrade our 4.4 machines
to
4.7. In the past I usually have just reinstalled machines to save the
(perceived)
headaches of upgrading. That is not an option in this case. Are there any pitfalls to watch out for when upgrading? Is it even
possible
to go up 3 revisions? Thanks, John
Why to 4.7? The current point release for CentOS 4 is 4.8. Going from 4.4 to 4.8 is trivial ('yum update' then 'shutdown -r now').
-- Robert Heller -- Get the Deepwoods Software FireFox Toolbar! Deepwoods Software -- Linux Installation and Administration http://www.deepsoft.com/ -- Web Hosting, with CGI and Database heller@deepsoft.com -- Contract Programming: C/C++, Tcl/Tk
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
John Kennedy wrote:
Only going to 4.7 because the required app is not certified for 4.8 (In the RHEL world which is what we are basing this on). 4.7 is as high as they will go. I know I will be doing this again in a month's time when they have 4.8 certified... I just do as I am told...To an extent...
If you can find a copy of the 4.7 iso you can upgrade from that. If you do this regularly, lagging well behind the repository, you might want to set up a repository mirror and keep snapshots at the points you expect to want later. I've always considered it a flaw in yum that it doesn't have an easy way to reproduce a known system state even though newer items have been added to the repositories - but even if it did, I don't think it would work across minor number revision upgrades the way the Centos repositories are handled.
On Thu, 24 Jun 2010, Les Mikesell wrote:
John Kennedy wrote:
Only going to 4.7 because the required app is not certified for 4.8 (In the RHEL world which is what we are basing this on). 4.7 is as high as
If you can find a copy of the 4.7 iso you can upgrade from that.
These older ISO images are retained in the vault.centos.org server appearance
-- Russ herrold
On Thu, Jun 24, 2010 at 09:16:43AM -0400, John Kennedy wrote:
Only going to 4.7 because the required app is not certified for 4.8 (In the RHEL world which is what we are basing this on). 4.7 is as high as they will go. I know I will be doing this again in a month's time when they have 4.8 certified... I just do as I am told...To an extent... Thanks, John
I didn't think that CentOS version numbers necessarily track RHEL version numbers. Kernel numbers do, of course, but not the distro or did I miss too much of the conversation?
////jerry
On Thu, Jun 24, 2010 at 9:01 AM, Robert Heller heller@deepsoft.com wrote:
At Thu, 24 Jun 2010 07:53:47 -0400 CentOS mailing list centos@centos.org wrote:
Hello all, For (system) certification purposes, we have to upgrade our 4.4 machines
to
4.7. In the past I usually have just reinstalled machines to save the
(perceived)
headaches of upgrading. That is not an option in this case. Are there any pitfalls to watch out for when upgrading? Is it even
possible
to go up 3 revisions? Thanks, John
Why to 4.7? The current point release for CentOS 4 is 4.8. Going from 4.4 to 4.8 is trivial ('yum update' then 'shutdown -r now').
-- Robert Heller -- Get the Deepwoods Software FireFox Toolbar! Deepwoods Software -- Linux Installation and Administration http://www.deepsoft.com/ -- Web Hosting, with CGI and Database heller@deepsoft.com -- Contract Programming: C/C++, Tcl/Tk
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-- Did you know that it costs forty thousand dollars a year to house each prisoner?...I don't think we should give free room and board to criminals. I think they should have to run twelve hours a day on a treadmill and generate electricity. And if they don't want to run, they can rest in the chair that's hooked up to the generator. -George Carlin
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
At Thu, 24 Jun 2010 12:16:52 -0400 CentOS mailing list centos@centos.org wrote:
On Thu, Jun 24, 2010 at 09:16:43AM -0400, John Kennedy wrote:
Only going to 4.7 because the required app is not certified for 4.8 (In the RHEL world which is what we are basing this on). 4.7 is as high as they will go. I know I will be doing this again in a month's time when they have 4.8 certified... I just do as I am told...To an extent... Thanks, John
I didn't think that CentOS version numbers necessarily track RHEL version numbers. Kernel numbers do, of course, but not the distro or did I miss too much of the conversation?
CentOS versions do track RHEL version numbers. CentOS n.m == RHEL n.m. The only difference is mostly the 'flavor' of the eye candy: RHEL n.m will have Red Hats (TM) showing up in various places and CentOS n.m will have a different graphic in place of the Red Hats (TM). In other places the words "Red Hat" have been replaced with "CentOS". This is just a replacement of tradmarked images and phrases. I think there are a couple of non open-source packages included in RHEL n.m that are not present in CentOS n.m (nothing essentual, just some extra 'goodies').
////jerry
On Thu, Jun 24, 2010 at 9:01 AM, Robert Heller heller@deepsoft.com wrote:
At Thu, 24 Jun 2010 07:53:47 -0400 CentOS mailing list centos@centos.org wrote:
Hello all, For (system) certification purposes, we have to upgrade our 4.4 machines
to
4.7. In the past I usually have just reinstalled machines to save the
(perceived)
headaches of upgrading. That is not an option in this case. Are there any pitfalls to watch out for when upgrading? Is it even
possible
to go up 3 revisions? Thanks, John
Why to 4.7? The current point release for CentOS 4 is 4.8. Going from 4.4 to 4.8 is trivial ('yum update' then 'shutdown -r now').
-- Robert Heller -- Get the Deepwoods Software FireFox Toolbar! Deepwoods Software -- Linux Installation and Administration http://www.deepsoft.com/ -- Web Hosting, with CGI and Database heller@deepsoft.com -- Contract Programming: C/C++, Tcl/Tk
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-- Did you know that it costs forty thousand dollars a year to house each prisoner?...I don't think we should give free room and board to criminals. I think they should have to run twelve hours a day on a treadmill and generate electricity. And if they don't want to run, they can rest in the chair that's hooked up to the generator. -George Carlin
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Thu, 24 Jun 2010, John Kennedy wrote:
For (system) certification purposes, we have to upgrade our 4.4 machines to 4.7.
* nod *
In the past I usually have just reinstalled machines to save the (perceived) headaches of upgrading. That is not an option in this case. Are there any pitfalls to watch out for when upgrading? Is it even possible to go up 3 revisions?
The testing done is usually an upgrade from recent to next in the pre-release beta testing, and us likely to remain that way, because there is a cross-product explosion as successive point releases issue, and frankly, the upstream model is that the 'latest' is the mose secure (and hopefully exhibiting a durable ABI/API profile, with some noted exceptions mentioned in Release Notes)
I would _suspect_ that there would no issues to bumping from an earlier 'point sub-version' directly to a later initially released 'base' of a later 'point' sub-version with CentOS as we do not back roll 'updates' into the 'base' image. Some other rebuilds do.
As you are 'qualifying' a new sub-version level, this implies that you have a set of behaviours you are testing for on a deployment testing bench. I think the best advice one can offer is: try it and report here and we'll all learn together ;)
-- Russ herrold
-
Jerry McAllister -
John Kennedy -
Les Mikesell -
R P Herrold -
Robert Heller