Skip to main content

CentOS

CentOSCommunity Enterprise Operating System)是Linux发布版之一,它是来自于Red Hat Enterprise Linux依照开放源代码规定发布的源代码所编译而成。由于出自同样的源代码,因此有些要求高度稳定性的服务器以CentOS替代商业版的Red Hat Enterprise Linux使用。两者的不同,在于CentOS并不包含封闭源代码软件。CentOS 对上游代码的主要修改是为了移除不能自由使用的商标。[1]

处理器架构

CentOS有下列处理器平台的版本:
  • Intel x86及兼容架构(32位)
  • Intel Itanium(64位)(新版本不再支持)
  • x86-64 (AMD64和Intel 64,64位)
  • PowerPC G3及G4(测试版)(新版本不再支持)
  • IBMeServer z系列及S/390大型主机(新版本不再支持)
另外有限度的支持两款旧型处理器:

版本

CentOS版本号有两个部份,一个主要版本和一个次要版本,主要和次要版本号分别对应于RHEL的主要版本与更新包,CentOS采取从RHEL的源代码包来构建。例如CentOS 4.4构建在RHEL 4.0的更新第4版。
自2006年中,CentOS 4.4版本开始(前身为RHEL 4.0更新第4版),Red Hat采用了和CentOS完全相同的版本约定,例如:Red Hat 4.5。

发布历史

数据源为 CentOS WikiDistrowatch CentOS
版本 平台 RHEL 版本 发布日期 RHEL 发布日期
2 i386 2.1 2004-05-14[2] 2002-05-17[3]
3.1 i386, x86_64, ia64, s390, s390x 3 2004-03-19[4] 2003-10-23[3]
3.4 - Server CD i386, x86_64, ia64, s390, s390x 3.4 2005-01-23 -
3.7 i386, x86_64, ia64, s390, s390x 3.7 2006-04-11[5] -
3.8 i386, x86_64 3.8 2006-08-25[6] 2006-07-20
3.9 i386, x86_64, ia64, s390, s390x 3.9 2007-07-26[7] 2007-06-15
4 i386, x86_64, various 4 2005-03-09[8] 2005-02-14[9]
4.6 i386, x86_64, ia64, alpha, s390, s390x, ppc (beta), sparc (beta) 4.6 2007-12-16[10] 2007-11-16[11]
4.7 i386, x86_64 4.7 2008-09-13[12] 2008-07-24[13]
4.7 - Server CD i386, x86_64 4.7 2008-10-17[14] -
4.8 i386, x86-64 4.8 2009-08-21[15] 2009-05-18[16]
4.9 i386, x86-64 4.9 2011-03-02[17] 2011-02-16[18]
5 i386, x86_64 5 2007-04-12[19] 2007-03-14[20]
5.1 i386, x86_64 5.1 2007-12-02[21] 2007-11-07[22]
5.1 - LiveCD i386 5.1 2008-02-18[23] -
5.2 i386, x86_64 5.2 2008-06-24[24] 2008-05-21[25]
5.2 - LiveCD i386 5.2 2008-07-17[26] -
5.3 i386, x86_64 5.3 2009-03-31[27] 2009-01-20[28]
5.3 - Live CD i386 5.3 2009-05-27[29] -
5.4 i386, x86_64 5.4 2009-10-21[30] 2009-09-02[31]
5.5 i386, x86_64 5.5 2010-05-14[32] 2010-03-31[33]
5.5 - LiveCD i386, x86-64 5.5 2010-05-14[32] -
5.6 i386, x86-64 5.6 2011-04-08[34] 2011-01-13[35]
5.7 i386, x86-64 5.7 2011-09-13[36] 2011-07-21[37]
5.8 i386, x86-64 5.8 2012-03-07[38] 2012-02-21[39]
5.9 i386, x86-64 5.9 2013-01-17[40]
5.10 i386, x86-64 5.10 2013-10-19[41]
6 i386, x86-64 6 2011-07-10[42] 2010-11-10[43]
6.0 - LiveCD i386, x86-64 6.0 2011-07-25[44] -
6.0 - LiveDVD i386, x86-64 6.0 2011-07-27[45] -
6.0 - MinimalCD i386, x86-64 6.0 2011-07-28[46] -
6.1 i386, x86-64 6.1 2011-12-09[47] 2011-05-19[48]
6.1 - LiveCD i386, x86-64 6.1 2011-12-09[49] -
6.1 - LiveDVD i386, x86-64 6.1 2011-12-09[50] -
6.1 - MinimalCD i386, x86-64 6.1 2011-12-09[51] -
6.2 i386, x86-64 6.2 2011-12-20[52] 2011-12-06[53]
6.2 - LiveCD i386, x86-64 6.2 2011-12-20[54] -
6.2 - LiveDVD i386, x86-64 6.2 2011-12-20[54] -
6.2 - MinimalCD i386, x86-64 6.2 2011-12-20[52] -
6.3 i386, x86-64 6.3 2012-07-09[55]
6.4 i386, x86-64 6.4 2013-03-09[56]
6.5 i386, x86-64 6.5 2013-12-01[57]
按照CentOS 5和6 RHEL的生命周期策略与上游供应商的改变也将支持为10年。

支持时程

发布版本 完整更新 维护更新
3 2006-07-20 2010-10-31
4 2009-03-31 2012-02-29
5 Q1 2014 2017-03-31
6 Q2 2017 2020-11-30
http://gengwg.blogspot.com/

Comments

Popular posts from this blog

CKA Simulator Kubernetes 1.22

  https://killer.sh Pre Setup Once you've gained access to your terminal it might be wise to spend ~1 minute to setup your environment. You could set these: alias k = kubectl                         # will already be pre-configured export do = "--dry-run=client -o yaml"     # k get pod x $do export now = "--force --grace-period 0"   # k delete pod x $now Vim To make vim use 2 spaces for a tab edit ~/.vimrc to contain: set tabstop=2 set expandtab set shiftwidth=2 More setup suggestions are in the tips section .     Question 1 | Contexts Task weight: 1%   You have access to multiple clusters from your main terminal through kubectl contexts. Write all those context names into /opt/course/1/contexts . Next write a command to display the current context into /opt/course/1/context_default_kubectl.sh , the command should use kubectl . Finally write a second command doing the same thing into ...

OWASP Top 10 Threats and Mitigations Exam - Single Select

Last updated 4 Aug 11 Course Title: OWASP Top 10 Threats and Mitigation Exam Questions - Single Select 1) Which of the following consequences is most likely to occur due to an injection attack? Spoofing Cross-site request forgery Denial of service   Correct Insecure direct object references 2) Your application is created using a language that does not support a clear distinction between code and data. Which vulnerability is most likely to occur in your application? Injection   Correct Insecure direct object references Failure to restrict URL access Insufficient transport layer protection 3) Which of the following scenarios is most likely to cause an injection attack? Unvalidated input is embedded in an instruction stream.   Correct Unvalidated input can be distinguished from valid instructions. A Web application does not validate a client’s access to a resource. A Web action performs an operation on behalf of the user without checkin...