Red hat linux release versions

History of Red Hat Linux

There has been over a decade of Linux development at Red Hat. This document describes that history, particularly focusing on the development themes for each release of Linux provided by Red Hat. Release History

“You know, it’s a funny thing. We go ahead and do things, and afterward, people go and start making history out of it.” — Fred Weick, Aircraft Designer. For the first decade or so, we did not set out to write the history of Red Hat Linux, so some of this data is a bit fuzzy or conflicting. We hope to do more research into our own past to give more useful data. This history is embryonic. It is intended to give some sense of where we have been, to help build a shared understanding of what we did right, as well as what we have done wrong, in order to continue a tradition of excellence.

In the following table, the Version number is prefaced by «RHL» for Red Hat Linux, «RHEL» for Red Hat Enterprise Linux, and «FC» for Fedora Core.

This was the first approximately concurrent multi-architecture release; the (then) Digital Alpha platform was supported. (The binary file format was still a.out for the Alpha platform because the ELF standard for Alpha was not yet ratified; there were no shared libraries on Alpha, either.)

First release to include NPTL (Native POSIX Thread Library) support, using glibc 2.3.2 and kernel 2.4.20 with NPTL support backported from the 2.5.x development kernels. Also, KDE 3.1 and GNOME 2.2.

Naming convention

Starting with Picasso, Red Hat has given releases of Red Hat Linux code names. (These names are included in the /etc/redhat-release file, with the version number.) The code names follow a strict pattern — at least, we have tried to make them follow a strict pattern. Name n and n+1 must share an is-a (not a has-a) relationship, but n and n+2 must not share an is-a relationship. (Extra credit for finding the small mistakes we made; we are now aware that we have at least one case where n and n+2 share an is-a relationship. The best-laid plans of mice and men gang aft a-gley.) Sometimes the name has changed from one beta release to another; more often it has not. There is no subtle message encoded in whether the name changes from one beta release to the next. Red Hat Enterprise Linux releases have not had code names; only release names which have also been used in place of code names.

In the past few years, there have also been a set of release names applied to each release by product management; these names are per formal release, where the beta has the same name as the follow-on product. Red Hat has not formally published these names, but several of them have become common knowledge anyway. These names have been geographical; they were originally the birthplaces of various members of the product management team, but those ran out and we had to find other geographical names.

Red Hat Enterprise Linux have only release names, no code names. Fedora Core will have only code names, not release names, except that we had already chosen the name «Cambridge» as a release name for the project that became Fedora Core 1.

Neither set of names has a long queue of new names already chosen and waiting for it. Therefore, as common practice, we use C syntax to refer to future releases. For example, the release code-named «Shrike» has the release name «Gin Gin»; the next release we informally referred to as «Gin Gin++» until we chose the release name «Cambridge.»

Other Historical Information

For historical information specific to the Fedora logo, please refer to the Fedora logo history page.

Thanks

For several years, there have been at least two web pages maintaining a bit of history of Red Hat Linux, one by Stephen Smoogen one by Matthias Saou that were valuable summaries we used while writing this document. Kudos to Smooge and Matthias for maintaining them! Thanks to Thomas Chung for writing this page.

Copyright © 2023 Red Hat, Inc. and others. All Rights Reserved. For comments or queries, please contact us.

The Fedora Project is maintained and driven by the community and sponsored by Red Hat. This is a community maintained site. Red Hat is not responsible for content.

• This page was last edited on 6 November 2016, at 23:42.
• Content is available under Attribution-Share Alike 4.0 International unless otherwise noted.

• Privacy policy
• About Fedora Project Wiki
• Disclaimers
• Code of Conduct
• Sponsors
• Legal
• Trademark Guidelines

Источник

Red Hat Enterprise Linux

Red Hat Enterprise Linux versions 5, 6, and 7 each deliver ten years of support in Full Support, Maintenance Support 1 and Maintenance Support 2 Phases followed by an Extended Life Phase. In addition, for Red Hat Enterprise Linux 5 and 6, customers may purchase annual Add-on subscriptions called Extended Life-cycle Support (ELS) to extend limited subscription services beyond the Maintenance Support 2 Phase. With the introduction of Red Hat Enterprise Linux version 8, Red Hat is simplifying the RHEL product phases from four to three: Full Support, Maintenance Support, and Extended Life Phase.

Full Support Phase

During the Full Support Phase, qualified Critical and Important Security errata advisories (RHSAs) and Urgent and Selected High Priority Bug Fix errata advisories (RHBAs) may be released as they become available. If available, new or improved hardware enablement and select enhanced software functionality may be provided at Red Hat’s discretion.

Maintenance Support Phase

During the Maintenance Support Phase (called “Maintenance Support 2” for RHEL 7), qualified RHSAs and RHBAs may be released as they become available. Other errata advisories may be delivered as appropriate. New functionality and new hardware enablement is at the discretion of Red Hat, and varies by operating system release.

Extended Life Cycle Support (ELS)

• On RHEL 7 ELS is not available for the architectures System z (Structure A), ARM, and POWER9.
• On RHEL 6 ELS is only available for the IBM z Systems and the x86 architecture, both 32-bit and 64-bit variants.
• On RHEL 6 a specific number of packages are supported under ELS which is listed here.

More information is available on the Red Hat Enterprise Linux website.

You should be running one of the supported release numbers listed above in the rightmost column.

You can submit an improvement to this page on GitHub . This page has a corresponding Talk Page.

A JSON version of this page is available at /api/rhel.json. See the API Documentation for more information. You can subscribe to the iCalendar feed at /calendar/rhel.ics.

Источник

Даты выпуска Red Hat Enterprise Linux

В приведенных ниже таблицах перечислены основные и мелкие обновления Red Hat Enterprise Linux, даты их выпуска и версии ядра, которые были.

Red Hat обычно не раскрывает графики будущих выпусков.

Чтобы найти версию Red Hat Enterprise Linux, выполните:

$ cat /etc/redhat-release Red Hat Enterprise Linux Server release 6.6 (Santiago)

Чтобы найти версию своего ядра:

$ uname -a Linux geeklab 2.6.32-504.el6.x86_64 #1 SMP Tue Sep 16 01:56:35 EDT 2014 x86_64 x86_64 x86_64 GNU/Linux

Red Hat Enterprise Linux 7

Релиз	Общая дата доступности	Дата исправления	Версия ядра
RHEL 7.6	10/30/2018	2018-10-30 RHBA-2018:3014	3.10.0-957
RHEL 7.5	4/10/2018	2018-04-10 RHEA-2018:0700	3.10.0-862
RHEL 7.4	7/31/2017	2017-07-31 RHBA-2017:1850	3.10.0-693
RHEL 7.3	11/3/2016	2016-11-03 RHEA-2016-2544	3.10.0-514
RHEL 7.2	11/19/2015	2015-11-19 RHEA-2015:2461	3.10.0-327
RHEL 7.1	3/5/2015	2015-03-05 RHEA-2015:0524	3.10.0-229
RHEL 7.0 GA	6/9/2014	–	3.10.0-123
RHEL 7.0 Beta	12/11/2013	–	3.10.0-54.0.1

Codename: Maipo (основанный на сочетании Fedora 19, Fedora 20 и нескольких модификаций)

Red Hat Enterprise Linux 6

Релиз	Общая дата доступности	Дата исправления	Версия ядра
RHEL 6.10	2018-06-19	2018-06-19 RHBA-2018:1856	2.6.32-754
RHEL 6.9	2017-03-21	2017-03-21 RHSA-2017:0817	2.6.32-696
RHEL 6.8	2016-05-10	2016-05-10 RHSA-2016:0855-1	2.6.32-642
RHEL 6.7	2015-07-22	2015-07-22 RHEA-2015:1423	2.6.32-573
RHEL 6.6	2014-10-14	2014-10-13 RHEA-2014:1608	2.6.32-504
RHEL 6.5	2013-11-21	2013-11-20 RHSA-2013:1645-2	2.6.32-431
RHEL 6.4	2013-02-21	2013-02-21 RHSA-2013-0496	2.6.32-358
RHEL 6.3	2012-06-20	2012-06-19 RHSA-2012-0862	2.6.32-279
RHEL 6.2	2011-12-06	2011-12-06 RHEA-2011:1743	2.6.32-220
RHEL 6.1	2011-05-19	2011-05-19 RHEA-2011:0540	2.6.32-131.0.15
RHEL 6.0	2010-11-09	–	2.6.32-71

Codename: Santiago (основанный на сочетании Fedora 12, Fedora 13 и нескольких модификаций)

Red Hat Enterprise Linux 5

Релиз	Общая дата доступности	Дата исправления	Версия ядра
RHEL 5.11	2014-09-16	2014-09-16 RHEA-2014-1238	2.6.18-398
RHEL 5.10	2013-10-01	2013-09-30 RHEA-2013-1311	2.6.18-371
RHEL 5.9	2013-01-07	2013-01-07 RHEA-2013-0021	2.6.18-348
RHEL 5.8	2012-02-20	2012-02-20 RHEA-2012:0315	2.6.18-308
RHEL 5.7	2011-07-21	2011-07-20 RHEA-2011:0977	2.6.18-274
RHEL 5.6	2011-01-13	2011-01-12 RHEA-2011:0020	2.6.18-238
RHEL 5.5	2010-03-30	2010-03-30 RHEA-2010:0207	2.6.18-194
RHEL 5.4	2009-09-02	2009-09-02 RHEA-2009:1400	2.6.18-164
RHEL 5.3	2009-01-20	2009-01-20 RHEA-2009:0133	2.6.18-128
RHEL 5.2	2008-05-21	2008-05-20 RHEA-2008:0436	2.6.18-92
RHEL 5. 1	2007-11-07	2007-11-07 RHEA-2007:0854	2.6.18-53
RHEL 5.0	2007-03-15	–	2.6.18-8

Codename: Tikanga (на базе Fedora Core 6)

Red Hat Enterprise Linux 4

Релиз	Общая дата доступности	Дата исправления	Версия ядра
RHEL 4 Update 9	2011-02-16	2011-02-16 RHEA-2011:0251	2.6.9-100
RHEL 4 Update 8	2009-05-19	2009-05-18 RHEA-2009:1002	2.6.9-89
RHEL 4 Update 7	2008-07-29	2008-07-24 RHEA-2008:0769	2.6.9-78
RHEL 4 Update 6	2007-11-15	2007-11-15 RHBA-2007:0897	2.6.9-67
RHEL 4 Update 5	2007-05-01	2007-04-27 RHBA-2007:0196	2.6.9-55
RHEL 4 Update 4	2006-08-10	2006-08-10 RHBA-2006:0601	2.6.9-42
RHEL 4 Update 3	2006-03-12	2006-03-07 RHBA-2006:0149	2.6.9-34
RHEL 4 Update 2	2005-10-05	2005-10-05 RHEA-2005:786	2.6.9-22
RHEL 4 Update 1	2005-06-08	2005-06-08 RHEA-2005:318	2.6.9-11
RHEL 4 GA	2005-02-15	–	2.6.9-5

Codename: Nahant (на основе Fedora Core 3)

Red Hat Enterprise Linux 3

Релиз	Общая дата доступности	Версия ядра
RHEL 3 Update 9	2007-06-20	2.4.21-50
RHEL 3 Update 8	2006-07-20	2.4.21-47
RHEL 3 Update 7	2006-03-17	2.4.21-40
RHEL 3 Update 6	2005-09-28	2.4.21-37
RHEL 3 Update 5	2005-05-18	2.4.21-32
RHEL 3 Update 4	2004-12-12	2.4.21-27
RHEL 3 Update 3	2004-09-03	2.4.21-20
RHEL 3 Update 2	2004-05-12	2.4.21-15
RHEL 3 Update 1	2004-01-16	2.4.21-9
RHEL 3 GA	2003-10-22	2.4.21-4

Codename: Taroon (на основе Red Hat Linux 9)

Red Hat Enterprise Linux 2.1

Релиз	Общая дата доступности	Версия ядра
RHEL 2.1 Update 7	2005-04-28	–
RHEL 2.1 Update 6	2004-12-13	2.4.9-e.57
RHEL 2.1 Update 5	2004-08-18	2.4.9-e.49
RHEL 2.1 Update 4	2004-04-21	2.4.9-e.40
RHEL 2.1 Update 3	2004-12-19	2.4.9-e.34
RHEL 2.1 Update 2	2003-03-29	2.4.9-e.24
RHEL 2.1 Update 1	2003-02-14	2.4.9-e.12
RHEL 2.1 GA	2002-03-23	2.4.9-e.3

Codename: Pensacola (AS) / Panama (ES) (на основе Red Hat Linux 7.2)

itisgood

Как установить KVM на RHEL 8

Как настроить разрешение конфликтов DHCP?

You may also like

Как подготовить ноутбук перед продажей и кому его.

Как правильно оформить ипотеку на вторичное жильё?

Лаки Джет онлайн игра.

Можно ли выучить английский самостоятельно?

Техническая поддержка сайта на 1С-Битрикс: ключевые направления и.

Идеальные звуки: Всё, что нужно знать о лучших.

Продукты СБИС — ваш путь к эффективному бизнесу.

🐧 Сравнение команд Printf и Echo на Linux

Учите языки с играми для девочек онлайн!

Одноразовые vs перезаправляемые картриджи для принтера – отличия

1 comment

Leave a Comment Cancel Reply

• Свежие записи

• Категории

• Теги

• itsecforu.ru

• Страны посетителей

IT is good

В этой статье вы узнаете, как удалить удаленный Git-репозиторий. Процесс прост, но его полезно запомнить, чтобы избежать неожиданностей в будущем. Git – это…

В 11-й версии своей операционной системы Microsoft серьезно переработала интерфейс и убрала несколько привычных функций. Нововведения не всем пришлись по душе. Мы дадим…

Продажа ноутбука нередко становится хлопотным занятием. Кроме поиска покупателя, продавцу необходимо подготовить устройство перед проведением сделки. Но если последовательно выполнить все шаги, ничего…

Вы можете оказаться в ситуации, когда вам нужно использовать скрипт шелла для чтения файлов построчно. В этом руководстве я расскажу о нескольких способах…

Вторичное жильё выгоднее для молодых семей, желающих приобрести свою первую квартиру. Сталкиваясь с ипотечным кредитованием, можно избежать много лишней суеты и проблем, если…

Источник