summaryrefslogtreecommitdiff
path: root/kernel-devel
diff options
context:
space:
mode:
authorManuel Traut <manut@vogone.(none)>2011-03-21 23:43:21 +0100
committerManuel Traut <manut@vogone.(none)>2011-03-21 23:43:21 +0100
commit056beea4fa614e6b381ee0d5ab6db2d474002fcb (patch)
tree10f437835e39406a4b12729309b838331b723314 /kernel-devel
parent39550bd9ea86090e5fa05f61c36e701ce740487f (diff)
added kernel versioning, next, staging, tempo
Signed-off-by: Manuel Traut <manut@vogone.(none)>
Diffstat (limited to 'kernel-devel')
-rw-r--r--kernel-devel/kernel-basics/pres_kernel-basics_de.tex73
1 files changed, 73 insertions, 0 deletions
diff --git a/kernel-devel/kernel-basics/pres_kernel-basics_de.tex b/kernel-devel/kernel-basics/pres_kernel-basics_de.tex
index 372ada2..3c252fa 100644
--- a/kernel-devel/kernel-basics/pres_kernel-basics_de.tex
+++ b/kernel-devel/kernel-basics/pres_kernel-basics_de.tex
@@ -72,6 +72,79 @@
\end{itemize}
\end{frame}
+\subsubsection{Versionierung}
+\begin{frame}
+\frametitle{Versionierung}
+\begin{itemize}
+\item 2.6.38.1 oder 2.6.39-rc1
+\pause
+\item 2.6 - historisch gegeben (aus altem Schema)
+\pause
+\item .38 - aktuelle Version
+\pause
+\item .1 - Security Fix
+\pause
+\item .rc1 - Release Candidate
+\end{itemize}
+\end{frame}
+
+\subsubsection{staging und next}
+\begin{frame}
+\frametitle{staging}
+\begin{block}
+\begin{itemize}
+\item Verzeichnis im Kernelsourcetree
+\item erm\"oglicht Entwicklung im 'Mainline' Tree
+\item enth\"alt haupts\"achlich Treiber
+\item Voraussetzung: aktive Weiterentwicklung im Code
+\end{itemize}
+\end{block}
+\end{frame}
+
+\begin{frame}[fragile]
+\frametitle{next}
+\begin{itemize}
+\item \"Anderungen welche vermutlich in die n\"achste Version aufgenommen
+werden
+\item tracked andere Trees und quilt queues
+\end{itemize}
+\begin{lstlisting}
+Feb-2008, Stephen Rothwell:
+I hope to recreate this tree every day automatically.
+In order to do this, any tree that has a conflict will
+be dropped from that days tree.
+The maintainer will be notified. I hope to provide some
+clue as to what the conflict is with, but probably not
+initially. I will attempt to build the tree between each
+merge (and a failed build will again cause the offending
+tree to be dropped). These builds will be necessarily
+restricted to probably one architecture/config.
+\end{lstlisting}
+\end{frame}
+
+\subsubsection{Entwicklungstempo}
+\begin{frame}
+\frametitle{Entwicklungstempo}
+\begin{itemize}
+\item 2 \dots 3 months release cycle
+\item \dots about 10,000 patches each cycle
+\item \dots from over 1000 developers
+\item \dots about 200 companies
+\end{itemize}
+Quelle: http://www.linuxfoundation.org/docs/lf\_linux\_kernel\_development\_2010.pdf
+\end{frame}
+
+\begin{frame}
+\frametitle{Entwicklungstempo}
+\begin{itemize}
+\item 2 \dots 3 months release cycle
+\item \dots about 10,000 patches each cycle
+\item \dots from over 1000 developers
+\item \dots about 200 companies
+\end{itemize}
+Quelle: http://www.linuxfoundation.org/docs/lf\_linux\_kernel\_development\_2010.pdf
+\end{frame}
+
\subsubsection{Konfiguration}
\begin{frame}
\frametitle{Kernel-Konfiguration}