From 6baba546cefbd4e5aba83fe6673f2b748ea45bd2 Mon Sep 17 00:00:00 2001
From: John Ogness <john.ogness@linutronix.de>
Date: Thu, 21 Jun 2018 15:41:46 +0206
Subject: linux processes: talk about daemons sooner

The daemon slides are sitting in the middle of the scheduling
section. Very odd. Move them to after the Parent/Child slides.
There it makes more sense.

Signed-off-by: John Ogness <john.ogness@linutronix.de>
---
 .../linux-processes/pres_linux-processes_en.tex    | 42 +++++++++++-----------
 1 file changed, 21 insertions(+), 21 deletions(-)

(limited to 'linux-basics')

diff --git a/linux-basics/linux-processes/pres_linux-processes_en.tex b/linux-basics/linux-processes/pres_linux-processes_en.tex
index 440a69e..67fb762 100644
--- a/linux-basics/linux-processes/pres_linux-processes_en.tex
+++ b/linux-basics/linux-processes/pres_linux-processes_en.tex
@@ -50,6 +50,27 @@ turned into a ''Zombie''
 \end{itemize}
 \end{frame}
 
+\subsection{Daemons}
+\begin{frame}
+\frametitle{Daemons}
+\begin{alertblock}{What is a Daemon?}
+A Daemon runs in background and is not attached to a terminal. Daemons are
+used for specific tasks, such as a web-server, a printer server, ...
+\end{alertblock}
+\end{frame}
+
+\begin{frame}
+\frametitle{How a Daemon gets created}
+\begin{itemize}
+\item Like any other process, a Daemon is created using fork()
+\item after forking the parent exits, which causes the child to be ''adopted''
+by PID 1
+\item then the child calls setsid(), to create a new session for that process
+\item afterwards several administrative tasks will be done (like changing the
+working directory and so on...)
+\end{itemize}
+\end{frame}
+
 \begin{frame}
 \frametitle{Task states}
 Each task can have one of the following states:
@@ -197,27 +218,6 @@ int setrlimit(int resource,
 \end{lstlisting}
 \end{frame}
 
-\subsection{Daemons}
-\begin{frame}
-\frametitle{Daemons}
-\begin{alertblock}{What is a Daemon?}
-A Daemon runs in background and is not attached to a terminal. Daemons are
-used for specific tasks, such as a web-server, a printer server, ...
-\end{alertblock}
-\end{frame}
-
-\begin{frame}
-\frametitle{How a Daemon gets created}
-\begin{itemize}
-\item Like any other process, a Daemon is created using fork()
-\item after forking the parent exits, which causes the child to be ''adopted''
-by PID 1
-\item then the child calls setsid(), to create a new session for that process
-\item afterwards several administrative tasks will be done (like changing the
-working directory and so on...)
-\end{itemize}
-\end{frame}
-
 \subsection{Multicore specific scheduling}
 \begin{frame}[fragile]
 \frametitle{Scheduling on Multicore Systems}
-- 
cgit v1.2.3