|
 |
dbaab5 |
%
|
|
|
dbaab5 |
% Describe The CentOS Distribution Release Schema.
|
|
|
dbaab5 |
%
|
|
|
dbaab5 |
\documentclass{article}
|
|
|
dbaab5 |
|
|
|
dbaab5 |
\usepackage{hyperref}
|
|
|
dbaab5 |
|
|
|
dbaab5 |
\title{The CentOS Release Brand}
|
|
|
dbaab5 |
\author{Alain Reguera Delgado}
|
|
|
dbaab5 |
|
|
|
dbaab5 |
\begin{document}
|
|
|
dbaab5 |
|
|
|
dbaab5 |
\maketitle
|
|
|
dbaab5 |
|
|
|
dbaab5 |
\begin{abstract}
|
|
|
dbaab5 |
This is abstract.
|
|
|
dbaab5 |
\end{abstract}
|
|
|
dbaab5 |
|
|
|
dbaab5 |
\tableofcontents
|
|
|
dbaab5 |
|
|
|
dbaab5 |
\section{Introduction}
|
|
|
dbaab5 |
|
|
|
dbaab5 |
The upstream vendor has released 3 versions of Enterprise Linux that
|
|
|
dbaab5 |
CentOS Project rebuilds the freely available SRPMS for\footnote{
|
|
|
dbaab5 |
\url{http://wiki.centos.org/About}}. So, the major CentOS releases are
|
|
|
dbaab5 |
CentOS 3, CentOS 4 and CentOS 5. The upstream vendor releases security
|
|
|
dbaab5 |
updates as required by circumstances. CentOS Project releases rebuilds
|
|
|
dbaab5 |
of security updates as soon as possible. Usually within 24 hours (our
|
|
|
dbaab5 |
stated goal is with 72 hours, but we are usually much faster).
|
|
|
dbaab5 |
|
|
|
dbaab5 |
The upstream vendor also releases numbered update sets for Version 3,
|
|
|
dbaab5 |
Version 4 and Version 5 of their product (i.e. EL 3 update 9, EL 4
|
|
|
dbaab5 |
update 6 and EL 5 update 1) 2 to 4 times per year. There are new ISOs
|
|
|
dbaab5 |
from the upstream vendor provided for these update sets. Update sets
|
|
|
dbaab5 |
will be completed as soon as possible after the vendor releases their
|
|
|
dbaab5 |
version\ldots generally within 2 weeks. CentOS Project follows these
|
|
|
dbaab5 |
conventions as well, so CentOS 3.9 correlates with EL 3 update 9 and
|
|
|
dbaab5 |
CentOS 4.6 correlates with EL 4 update 6, CentOS 5.1 correlates to EL
|
|
|
dbaab5 |
5 update 1, etc.
|
|
|
dbaab5 |
|
|
|
dbaab5 |
One thing some people have problems understanding is that if you have
|
|
|
dbaab5 |
any CentOS-3 product and update it, you will be updated to the latest
|
|
|
dbaab5 |
CentOS-3.x version. The same is true for CentOS-4 and CentOS 5. If you
|
|
|
dbaab5 |
update any CentOS-4 product, you will be updated to the latest
|
|
|
dbaab5 |
CentOS-4.x version, or to the latest CentOS 5.x version if you are
|
|
|
dbaab5 |
updating a CentOS 5 system. This is exactly the same behavior as the
|
|
|
dbaab5 |
upstream product. Let's assume that the latest EL4 product is update
|
|
|
dbaab5 |
6. If you install the upstream original EL4 CDs (the ones before any
|
|
|
dbaab5 |
update set) and upgrade via their up2date, you will have latest update
|
|
|
dbaab5 |
set installed (EL4 update 6 in our example).
|
|
|
dbaab5 |
|
|
|
dbaab5 |
Since all updates within a major release (CentOS 3, CentOS 4, CentOS
|
|
|
dbaab5 |
5) always upgrade to the latest version when updates are performed
|
|
|
dbaab5 |
(thus mimicking upstream behavior), only the latest version is
|
|
|
dbaab5 |
maintained in each main tree on the CentOS
|
|
|
dbaab5 |
Mirrors\footnote{\url{http://mirrors.centos.org/}}.
|
|
|
dbaab5 |
|
|
|
dbaab5 |
There is a CentOS Vault\footnote{\url{http://vault.centos.org/}}
|
|
|
dbaab5 |
containing old CentOS trees. This vault is a picture of the older tree
|
|
|
dbaab5 |
when it was removed from the main tree, and does not receive updates.
|
|
|
dbaab5 |
It should only be used for reference.
|
|
|
dbaab5 |
|
|
|
dbaab5 |
\section{Workplace}
|
|
|
dbaab5 |
|
|
|
dbaab5 |
\begin{itemize}
|
|
|
dbaab5 |
\item SVN:trunk/Identity/Logos/svg/type/2c-tmr.svg
|
|
|
dbaab5 |
\item SVN:trunk/Identity/Logos/svg/type/build/tmr3.svg
|
|
|
dbaab5 |
\item SVN:trunk/Identity/Logos/svg/type/build/tmr4.svg
|
|
|
dbaab5 |
\item SVN:trunk/Identity/Logos/svg/type/build/tmr5.svg
|
|
|
dbaab5 |
\end{itemize}
|
|
|
dbaab5 |
|
|
|
dbaab5 |
\section{Design}
|
|
|
dbaab5 |
|
|
|
dbaab5 |
It is very important that people differentiate which is the major
|
|
|
dbaab5 |
release of CentOS Distribution they are using. To achive this, we use
|
|
|
dbaab5 |
a special brand called \textit{The Release Brand} of CentOS
|
|
|
dbaab5 |
Distribution.
|
|
|
dbaab5 |
|
|
|
dbaab5 |
There is one Release Brand for each Major Release of CentOS
|
|
|
dbaab5 |
Distribution. The Release Brand of CentOS Distribution is placed on
|
|
|
dbaab5 |
images controlling the CentOS Distribution Visual Style.
|
|
|
dbaab5 |
|
|
|
dbaab5 |
The Release Brand of CentOS Distribution is built using two
|
|
|
dbaab5 |
components: 1. The CentOS Trademark, 2. The Major Release Number of
|
|
|
dbaab5 |
CentOS Distribution.
|
|
|
dbaab5 |
|
|
|
dbaab5 |
The height of the Release Number is twice the CentOS Trademark height
|
|
|
dbaab5 |
and it is placed on the right side of CentOS Trademark, both bottom
|
|
|
dbaab5 |
aligned.
|
|
|
dbaab5 |
|
|
|
dbaab5 |
Sometimes The CentOS Message can be added as third component to The
|
|
|
dbaab5 |
Release Brand. In these cases The CentOS Message remains on English
|
|
|
dbaab5 |
language, it is not translated. Because of this, The Release Brand
|
|
|
dbaab5 |
that includes The CentOS Message should be avoided or used in places
|
|
|
dbaab5 |
where there is no posibility for the user to select a different
|
|
|
dbaab5 |
language but English. Examples of these kind of images are Anaconda
|
|
|
dbaab5 |
Prompt and GRUB.
|
|
|
dbaab5 |
|
|
|
dbaab5 |
\section{Rendering}
|
|
|
dbaab5 |
|
|
|
dbaab5 |
\end{document}
|