Release For CentOS-7 On X86_64

Home » CentOS-Announce » Release For CentOS-7 On X86_64
CentOS-Announce 28 Comments

We would like to announce the general availability of CentOS Linux 7
for 64 bit x86 compatible machines.

This is the first release for CentOS-7 and is version marked as 7.0-1406

First, please read through the release notes at :
http://wiki.CentOS.org/Manuals/ReleaseNotes/CentOS7 – these notes contain important information about the release and details about some of the content inside the release from the CentOS QA team. These notes are updated constantly to include issues and incorporate feedback from the users.

– ——–

28 thoughts on - Release For CentOS-7 On X86_64

  • Thanking everyone most sincerely for giving us C 7.0.

    London, West (near LHR) Dojo ?

  • Always Learning wrote:
    I missed that notice over the weekend. 1++

    And thanks to all for no huge thread of WHEN’S IT GOING TO BE RELEASED!!!

    mark

  • 2014-07-07 21:42 GMT+02:00 Darr247 :

    ​It’s on CentOS-announce and seven.CentOS.org​
    ​http://lists.CentOS.org/pipermail/CentOS-announce/2014-July/020393.html

    ​ – Jitse​

  • Yes, CentOS 7 is released …

    Good job, everyone involved.

    Thanks, Johnny Hughes

  • and it’s on the front page at CentOS.org.

    —
    —- Fred Smith — fredex@fcshome.stoneham.ma.us —————————–
    “For the word of God is living and active. Sharper than any double-edged
    sword, it penetrates even to dividing soul and spirit, joints and marrow;
    it judges the thoughts and attitudes of the heart.”
    —————————- Hebrews 4:12 (niv) ——————————

  • yay… Congratulations to CentOS development team and other user who use CentOS on their desktop, servers and etc…

    —
    Roozbeh Shafiee Linux/BSD System Administrator and Python Developer RoozbehShafiee.Com

  • Great to see. Now how long to wait for C7-i386 and perhaps more importantly C7-arm (for the v7s)?

    :)

    No really. I DO have some i386 platforms and I DO have this Cubieboard
    2 that I am working with…

  • It’s derived from Redhat 7,.. CentOS is always derived from Redhat Enterprise Linux. Fedora is normally a preview of the next upcoming RHEL
    release.

  • Robert Moskowitz wrote:

    I’m waiting for 7.0.1, with all the upstream fixes that were missed.

    mark “don’t trust x.0 of anything”

  • You’re right.. RHEL includes things that get pushed and tested in Fedora, but I guess I looked at the question a different way. That’s all.

  • Until recently, RHEL really lagged behind Fedora. With RHEL 7, they seemed to have taken on walking the talk and being as current as possible (F19 was the current release when RHEL7 development seemed to have started). It is great that this leap forward was made. Of course has the ‘service’ command been replaced with ‘systemd’? That will be a big shock to CentOS admins.

  • Thank you for your reply.

    This is appealing for my desktops, since I’m still on FC18 (I got burned out with 1 1/2 year FC EOL cycle). I’d just soon install a system knowing that it’s going to be around for the next 6 years, and all I have to do is run yum update.

    MP
    pyz@brama.com

  • And thus it is not in RHEL 6. If an admin has not been working with Fedora, then there is no experience with it. Plus it was easy to ignore systemctl in Fedora for a while, though by F18 it was hard to say the least.

    Yes the wrapper is there, but at least on Fedora, I notice that related items like chkconfig no longer worked as well, and I really needed to buckle down and learn systemctl.

    Which was a great hint to figure out what this systemctl was all about.

  • Robert Moskowitz wrote:

    Wasn’t there an upstart somewhere?

    I think I’ll write an alias for chkconfig to systemctl. *bleah* As far as I’m concerned, it was a solution to something that wasn’t a problem, just like this urge to make config files xml.

    mark

  • Oh, I don’t mean that it is not there. Rather it doesn’t interact the way it use to. For example on F20:

    chkconfig

    Note: This output shows SysV services only and does not include native
    systemd services. SysV configuration data might be overridden by native
    systemd configuration.

    If you want to list systemd services use ‘systemctl list-unit-files’.
    To see services enabled on particular target use
    ‘systemctl list-dependencies [target]’.

    netconsole 0:off 1:off 2:off 3:off 4:off 5:off 6:off network 0:off 1:off 2:off 3:off 4:off 5:off 6:off

    ===================================
    Basically telling you to get with the program.

  • –Meh.

    Normally, when putting things into production, I would agree with you. However, as I recently commented to a client, paraphrasing somewhat:

    You’re in a bind right now because in order to support your current
    business requirements you need to deploy more servers and the line
    of servers that you have running RHEL5 are no longer made. They have
    been replaced by a line that [for reasons I’m not getting into on
    the CentOS list but related to specific hardware configurations]
    will run RHEL6 but not RHEL5. So while you’ve got a bit of timeline
    lee-way, waiting a long time is not an option.

    You can start deploying on RHEL6, but at this point your supported
    timeline is about half over. RHEL7 is out which will about double the
    supported lifetime of the new systems, but you’re understandably
    skittish about dot-zero version numbers.

    First mitigation: RedHat does a pretty decent job of testing things
    before they release them. There have been hiccoughs in the past, but
    (for the use case involved) they’re few and far between. No promises,
    but there’s a good chance that 7.0.nothing will be just fine.

    Second mitigation: [The client] has a well defined lab/PoC environment,
    followed by a rigorous UAT environment before hitting production.
    And before that there is of course the hardware procurement schedule.
    By the time you’re half way through your UAT even if RHEL isn’t at
    7.1, it’ll have a decent amount of time for post-7.0 patches to have
    come out.

    So unless there’s required 3rd party software that isn’t yet working
    on RHEL7 and for which you don’t have a release timeline (or an acceptable
    release timeline), leapfrog over RHEL6 to RHEL7 and start building
    and testing your lab environment, and planning your UAT/production
    environments. By the time UAT is done, you’re ready to go.

    s,RHEL,CentOS,g;

    Of course, as I finish writing this I notice that you said “7.0.1”
    and not “7.1”. So we may not be too far off on our perspectives anyway.

    Devin

  • Am 07.07.2014 um 20:30 schrieb Karanbir Singh :

    Hi Karanbir, JFYI: wrong GnomeLive.iso-URI in this announcement.

  • :-)

    Why, of course, as in:
    [lowen@dhcp-pool107 ~]$ rpm -qa|grep ^upstart upstart-0.6.5-13.el6_5.3.x86_64
    [lowen@dhcp-pool107 ~]$

    This box is CentOS 6. Upstart was around for a few Fedora releases up through F14; I don’t recall when it was introduced, but wikipedia tells me it was F9.

    It was a problem for some, even if not for you or for me.

  • yeah, :(

    it would’nt really have been a real CentOS announcement had I not fat finggered something.

    I’m really not just trying to make all Gnome users use Kde instead.

    – KB