summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJohn Ogness <john.ogness@linutronix.de>2019-02-28 15:14:41 +0106
committerJohn Ogness <john.ogness@linutronix.de>2019-02-28 15:14:41 +0106
commit68c9546756610ceda38a0274eefdaa48d37b6c9f (patch)
treef1923781f4c7973a71faeddec933d054aa13705c
parent5e1885940c38385dc8309702b2d80023212a929f (diff)
linux-processes: also mention clone() syscall
Since these days fork() is just a wrapper for the clone() syscall, it makes sense to at least mention it on the slide. Signed-off-by: John Ogness <john.ogness@linutronix.de>
-rw-r--r--linux-basics/linux-processes/pres_linux-processes_en.tex2
1 files changed, 1 insertions, 1 deletions
diff --git a/linux-basics/linux-processes/pres_linux-processes_en.tex b/linux-basics/linux-processes/pres_linux-processes_en.tex
index de5227e..dd3aa08 100644
--- a/linux-basics/linux-processes/pres_linux-processes_en.tex
+++ b/linux-basics/linux-processes/pres_linux-processes_en.tex
@@ -32,7 +32,7 @@ of the executable. Linux uses the ELF format (Executable Linking Format)
From the operating system's point of view there are basically two steps
that are performed when starting a process.
\begin{itemize}
-\item A process is created using the fork() system call
+\item A process is created using the fork() or clone() system calls
\item The execve() system call loads a new program into the process memory
\end{itemize}
\end{frame}