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. ----- Original Message ---- From: Nick Lunt <[email protected]> To: Red Hat Enterprise Linux 5 (Tikanga) discussion mailing-list <[email protected]> Sent: Tue, July 27, 2010 9:06:22 AM Subject: Re: [rhelv5-list] Updating to specific release of redhat > -----Original Message----- > From: [email protected] [mailto:rhelv5-list- > [email protected]] On Behalf Of [email protected] > Sent: 27 July 2010 13:59 > To: Red Hat Enterprise Linux 5 (Tikanga) discussion mailing-list > Cc: [email protected]; [email protected] > Subject: Re: [rhelv5-list] Updating to specific release of redhat > > > Hi folks > > got a box running RH5.0 which I need to update to RH5.2. > > Can this be done with yum or do I have to download RH5.2 and rpm - > > Uvh the 5.2 rpms ? > > The way I've always done it has been to download the DVD, and host it > as a yum repo locally. Going with rpm -Uvh could be a pain if there are > any package additions or replacements, and probably to many packages to do > at once. Sounds like a good plan, thanks Greg. _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
