From 68c9546756610ceda38a0274eefdaa48d37b6c9f Mon Sep 17 00:00:00 2001 From: John Ogness Date: Thu, 28 Feb 2019 15:14:41 +0106 Subject: 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 --- linux-basics/linux-processes/pres_linux-processes_en.tex | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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} -- cgit v1.2.3