CentOS 6-6.3 -> No Updates And Security Fixes?

Home » CentOS » CentOS 6-6.3 -> No Updates And Security Fixes?
CentOS 4 Comments

Hi All.

I’ve found:

This directory (and version of CentOS) is depreciated. For normal users, you should use /6/ and not /6.3/ in your path. Please see this FAQ
concerning the CentOS release scheme:

http://www.CentOS.org/modules/smartfaq/faq.php?faqid4

If you know what you are doing, and absolutely want to remain at the 6.3
level, go to http://vault.CentOS.org/ for packages.

Please keep in mind that 6.0, 6.1, 6.2 and 6.3 no longer gets any updates, nor any security fix’s.

in http://eu-msync.CentOS.org/CentOS-6/6.3/readme

Is CentOS 6-6.3 really not updated anymore? Why so soon after release of
6.4?

Best regards, Rafal.

4 thoughts on - CentOS 6-6.3 -> No Updates And Security Fixes?

  • Hi Rafael,

    think of dot releases as a kind of service pack. It’s a sliding update. Once
    6.4 is out, all fixes go into 6.4 and not 6.3 any more. There are very few reasons to stick to 6.3 once the next dot release is out.

    The same is actually true for windows. Once a service pack is out, you won’t get updates for the OS without that SP applied.

    Greetings, Thomas

  • Point releases (the .3 or .4 in CentOS-6.3 or CentOS-6.4) are just a
    “Point in Time” snapshot of the packages in CentOS-6. CentOS-6 is the released distribution.

    At point release time, we regenerate the ISOs (to allow for installs on newer hardware.)

    If we create new ISOs (with new content), that means we also need to update the /os tree to also have that newer content for network installs.

    When we build updates, we build them in a Staged environment. That means that an update that is built today is based on a completely up2date CentOS-6 tree (currently 6.4 and all the updates since 6.4). That new updated RPM may not install on anything older than the libraries in place when it is built. That means is may not work on CentOS-6.3 or any other version of CentOS-6 because it may contain references to libraries that did not exist in that previous point in time.

    As someone else stated … If you are running Windows 7 with no service pack installed, you could not install updates that were designed for Win7SP1 on Win7SP0. To get the newer updates, you have to install SP1. That is exactly how it works with CentOS-6 as well … you need to have the version installed that the updates were designed for to have the system function properly.

    By default, all one has to do is to run yum to stay updated. Yum points to /6/ by default and that automatically gets you the latest point release, whatever that may be.

  • Point releases (the .3 or .4 in CentOS-6.3 or CentOS-6.4) are just a
    “Point in Time” snapshot of the packages in CentOS-6. CentOS-6 is the released distribution.

    At point release time, we regenerate the ISOs (to allow for installs on newer hardware.)

    If we create new ISOs (with new content), that means we also need to update the /os tree to also have that newer content for network installs.

    When we build updates, we build them in a Staged environment. That means that an update that is built today is based on a completely up2date CentOS-6 tree (currently 6.4 and all the updates since 6.4). That new updated RPM may not install on anything older than the libraries in place when it is built. That means is may not work on CentOS-6.3 or any other version of CentOS-6 because it may contain references to libraries that did not exist in that previous point in time.

    As someone else stated … If you are running Windows 7 with no service pack installed, you could not install updates that were designed for Win7SP1 on Win7SP0. To get the newer updates, you have to install SP1. That is exactly how it works with CentOS-6 as well … you need to have the version installed that the updates were designed for to have the system function properly.

    By default, all one has to do is to run yum to stay updated. Yum points to /6/ by default and that automatically gets you the latest point release, whatever that may be.

LEAVE A COMMENT