> -----Original Message----- > From: Bryan J Smith [mailto:[email protected]] > Sent: 27 July 2010 14:51 > To: Red Hat Enterprise Linux 5 (Tikanga) discussion mailing-list > Cc: Nick Lunt > Subject: Re: [rhelv5-list] Updating to specific release of redhat > > Is there are a reason you are limiting your update to Red Hat > Enterprise Linux > Release 5 Update 2 (5.2)? > > Just keep several things in mind ... > > 1) The DVD will only have the bugfix and security errata applied > through that > update > > Red Hat Enterprise Linux Release 5 Update 2 (5.2) is over two (2) full > years old > (2008 May) > > 2) Running an older update is no longer current with engineering and > new errata > > Red Hat Enterprise Linux Release 5 Update 5 (5.5) is current release > update > (2010 March), > and errata, support and other services will be focused on this release. > Unless > your organization > has a known certification and support issue with 3rd party solutions, > this > should be the release > update your organization should be running. > > 3) Red Hat offers Extended Update Support (EUS) for older release > update > support > > #3 allows customers with independent software vendor (ISV) or other > certification > lifecycle issues to remain several releases updates back. Only limited > security > updates are > built for these older updates, and only for several updates back. > > The current EUS offerings for Red Hat Enterprsie Linux Release 5 > include ... > - Red Hat Enterprise Linux Release 5 Update 3 (EUS 5.3.z) > http://rhn.redhat.com/errata/rhel-server-5.3-errata.html > - Red Hat Enterprise Linux Release 5 Update 4 (EUS 5.4.z) > http://rhn.redhat.com/errata/rhel-server-5.4-errata.html > In addition to the current 5.5 (and EUS 5.5.z) > http://rhn.redhat.com/errata/rhel-server-errata.html > > The EUS support for Red Hat Enterprise Linux 5 Update 2 (EUS 5.2.z) > ended in > March: > > http://rhn.redhat.com/errata/rhel-server-5.2-errata.html > > As you'll note, there have been several security errata issue since > that time. > > Red Hat Enterprise Linux releases are designed to maintain ABI/API > compatibility, > ISV software compatibility and eliminate (or at least mitigate) > regressions in > upstream > software by backporting security and bugfixes, instead of rebasing to > new > versions. > http://www.redhat.com/security/updates/backporting/ > > This is one of the major values of the Red Hat Enterprise Linux > subscription. > As such, updating to the latest Update is typically not an issue, > unlike other, > popular OSes. > > Sustaining engineering is a primary focus of Red Hat Enterprise Linux, > not > pushing consumers > to always upgrade for features and, correspondingly, more sales. > Likewise, any > subscription > entitles the customer to any release, including newer versions that > were not > released at the > time of the original purchase of the subscription, removing the feature > v. > compatibility delima > (let alone added costs) for the customer.
Hi Bryan thanks for the detailed info, it's appreciated. However the reason for the upgrade to 5.2 from 5.0 is because it's part of a load balanced server family and the other servers are at 5.2. I want to get all servers to 5.2 first then we'll be looking at updating to 5.5 or 5.6 by the time we get round to it :) Thanks Nick . __________ Information from ESET NOD32 Antivirus, version of virus signature database 5316 (20100727) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
