That doesn't happen as soon as you might think. I still get regular updates on CentOS 5.11; so THAT horse ain't dead yet, even though it's supposedly been EOS for a while now.

For all practical purposes, 6.x will probably continue getting updates for at least 5 years. That's probably longer than the life of the server.

In another year or so, I would be comfortable with 7, and it will have more widespread support, and fewer bugs.

bp
<part15sbs{at}gmail{dot}com>

On 11/10/2015 1:07 PM, Justin Wilson - MTIN wrote:
I would do 7 just because of the support nature of it. There will become a time, sooner than 7, that 6 will no longer receive updates. Bite the bullet and do it now. CentOS7 has a little bit of a learning curve. Gone are the init scripts replaced by sys control. This is the biggest change folks have to get used to.


Justin Wilson
[email protected] <mailto:[email protected]>

---
http://www.mtin.net Owner/CEO
xISP Solutions- Consulting – Data Centers - Bandwidth

http://www.midwest-ix.com  COO/Chairman
Internet Exchange - Peering - Distributed Fabric

On Nov 10, 2015, at 8:44 AM, Josh Luthman <[email protected] <mailto:[email protected]>> wrote:

New server?  7 no question.

Josh Luthman
Office: 937-552-2340
Direct: 937-552-2343
1100 Wayne St
Suite 1337
Troy, OH 45373

On Nov 10, 2015 1:34 AM, "Eric Kuhnke" <[email protected] <mailto:[email protected]>> wrote:

    7, for the 3.x series kernel if nothing else.



    On Mon, Nov 9, 2015 at 9:41 PM, Ken Hohhof <[email protected]
    <mailto:[email protected]>> wrote:

        There seems to be a fair bit of dissatisfaction with
        RHEL7/CentOS 7.  I'm building a couple new servers, if my
        others are running CentOS 6 and do what I need, should I
        resist the temptation to jump to 7?  I think CentOS 6 EOS
        dates are 2017 for full updates and 2020 for maintenance updates?

        I know some people will say switch to Ubuntu or Debian or
        whatever, let's assume I am staying with CentOS, I'm just
        asking 6 or 7?




Reply via email to