From a6803531925d2d0f695abb9ba421cf172e1e9513 Mon Sep 17 00:00:00 2001
From: Elijah Mock <28277163+ekcom@users.noreply.github.com>
Date: Sat, 14 Sep 2024 17:14:05 -0500
Subject: [PATCH 1/8] Fix inserting xor symbol

- previously, was putting hat over X character
---
 processes/processes.tex | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/processes/processes.tex b/processes/processes.tex
index 295a63d..d27cb09 100644
--- a/processes/processes.tex
+++ b/processes/processes.tex
@@ -114,7 +114,7 @@ \subsection{Memory Layout}
 The stack is the place where automatically allocated variables and function call return addresses are stored.
 Every time a new variable is declared, the program moves the stack pointer down to reserve space for the variable.
 This segment of the stack is writable but not executable.
-This behavior is controlled by the no-execute (NX) bit, sometimes called the W\^X (write XOR execute) bit, which helps prevent malicious code, such as \keyword{shellcode} from being run on the stack.
+		This behavior is controlled by the no-execute (NX) bit, sometimes called the W\^{}X (write XOR execute) bit, which helps prevent malicious code, such as \keyword{shellcode} from being run on the stack.
 
 If the stack grows too far -- meaning that it either grows beyond a preset boundary or intersects the heap -- the program will stack overflow error, most likely resulting in a SEGFAULT.
 \textbf{The stack is statically allocated by default; there is only a certain amount of space to which one can write.}

From 4a76bcfb7a321841fe2e9b124d49e3f91dc7a5b5 Mon Sep 17 00:00:00 2001
From: Elijah Mock <28277163+ekcom@users.noreply.github.com>
Date: Sat, 14 Sep 2024 17:15:45 -0500
Subject: [PATCH 2/8] Add missing word

---
 processes/processes.tex | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/processes/processes.tex b/processes/processes.tex
index d27cb09..b7e4b1f 100644
--- a/processes/processes.tex
+++ b/processes/processes.tex
@@ -444,7 +444,7 @@ \subsection{POSIX Fork Details}
 \begin{enumerate}
     \item Fork will return a non-negative integer on success.
     \item A child will inherit any open file descriptors of the parent.
-          That means if a parent half of the file and forks, the child will start at that offset.
+          That means if a parent reads half of the file and forks, the child will start at that offset.
           A read on the child's end will shift the parent's offset by the same amount.
           Any other flags are also carried over.
     \item Pending signals are not inherited.

From 7b7d037973acb42d3cfcac44056827086e5667cf Mon Sep 17 00:00:00 2001
From: Elijah Mock <28277163+ekcom@users.noreply.github.com>
Date: Sat, 14 Sep 2024 17:18:01 -0500
Subject: [PATCH 3/8] Syntax corrections

---
 processes/processes.tex | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/processes/processes.tex b/processes/processes.tex
index b7e4b1f..3357b7a 100644
--- a/processes/processes.tex
+++ b/processes/processes.tex
@@ -201,7 +201,7 @@ \subsection{Other Contents}
     \item \textbf{File Descriptors} - A list of mappings from integers to real devices (files, USB flash drives, sockets)
     \item \textbf{Permissions} - What \keyword{user} the file is running on and what \keyword{group} the process belongs to.
           The process can then only perform operations based on the permissions given to the \keyword{user} or \keyword{group}, such as accessing files.
-          There are tricks to make a program take a different user than who started the program i.e. \keyword{sudo} takes a program that a \keyword{user} starts and executes it as \keyword{root}.
+		There are tricks to make a program take a different user than who started the program (e.g., \keyword{sudo} takes a program that a \keyword{user} starts and executes it as \keyword{root}).
           More specifically, a process has a real user ID (identifies the owner of the process), an effective user ID (used for non-privileged users trying to access files only accessible by superusers), and a saved user ID (used when privileged users perform non-privileged actions).
     \item \textbf{Arguments} - a list of strings that tell your program what parameters to run under.
     \item \textbf{Environment Variables} - a list of key-value pair strings in the form \keyword{NAME=VALUE} that one can modify. These are often used to specify paths to libraries and binaries, program configuration settings, etc.
@@ -628,7 +628,7 @@ \section{Waiting and Executing}
 
 \subsection{Exit statuses}
 
-To find the return value of \keyword{main()} or value included in \keyword{exit()}), Use the \keyword{Wait macros} - typically a program will use \keyword{WIFEXITED} and \keyword{WEXITSTATUS} .
+To find the return value of \keyword{main()} or value included in \keyword{exit()}, use the \keyword{Wait macros}. Typically, a program will use \keyword{WIFEXITED} and \keyword{WEXITSTATUS}.
 See \keyword{wait}/\keyword{waitpid} man page for more information.
 
 \begin{lstlisting}[language=C]

From 4dcfeeb824eb3029225dec79bc5e2c3845bc7b1f Mon Sep 17 00:00:00 2001
From: Elijah Mock <28277163+ekcom@users.noreply.github.com>
Date: Sat, 14 Sep 2024 17:18:23 -0500
Subject: [PATCH 4/8] Specifically name getting values from child proc

---
 processes/processes.tex | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/processes/processes.tex b/processes/processes.tex
index 3357b7a..ca692b6 100644
--- a/processes/processes.tex
+++ b/processes/processes.tex
@@ -628,7 +628,7 @@ \section{Waiting and Executing}
 
 \subsection{Exit statuses}
 
-To find the return value of \keyword{main()} or value included in \keyword{exit()}, use the \keyword{Wait macros}. Typically, a program will use \keyword{WIFEXITED} and \keyword{WEXITSTATUS}.
+To find the return value of \keyword{main()} or value included in \keyword{exit()} from a child process, use the \keyword{Wait macros}. Typically, a program will use \keyword{WIFEXITED} and \keyword{WEXITSTATUS}.
 See \keyword{wait}/\keyword{waitpid} man page for more information.
 
 \begin{lstlisting}[language=C]

From 45b0bd98462546729fbb29d7b5578281265687c8 Mon Sep 17 00:00:00 2001
From: Elijah Mock <28277163+ekcom@users.noreply.github.com>
Date: Sat, 14 Sep 2024 17:19:37 -0500
Subject: [PATCH 5/8] Remove additional link text

- remove hyperlink text from page
- keyword is linked already
---
 processes/processes.tex | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/processes/processes.tex b/processes/processes.tex
index ca692b6..1cc3ea3 100644
--- a/processes/processes.tex
+++ b/processes/processes.tex
@@ -745,7 +745,7 @@ \subsection{Advanced: Asynchronously Waiting}
 
 \section{exec}
 
-To make the child process execute another program, use one of the \href{http://man7.org/linux/man-pages/man3/exec.3.html}{\keyword{exec}} functions after forking.
+To make the child process execute another program, use one of the \keyword{exec} functions after forking.
 The \keyword{exec} set of functions replaces the process image with that of the specified program.
 This means that any lines of code after the \keyword{exec} call are replaced with those of the executed program.
 Any other work a program wants the child process to do should be done before the \keyword{exec} call.

From b6b5323b145bf15e6572fed11387c83c89ee5890 Mon Sep 17 00:00:00 2001
From: Elijah Mock <28277163+ekcom@users.noreply.github.com>
Date: Sat, 14 Sep 2024 17:22:27 -0500
Subject: [PATCH 6/8] Various grammar fixes and consistency adjustments

---
 processes/processes.tex | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/processes/processes.tex b/processes/processes.tex
index 1cc3ea3..1fdc11b 100644
--- a/processes/processes.tex
+++ b/processes/processes.tex
@@ -813,9 +813,9 @@ \section{exec}
 There's no error checking in the above code (we assume close, open, chdir etc. work as expected).
 
 \begin{enumerate}
-    \item \keyword{open} -- will use the lowest available file descriptor (i.e. 1) ; so standard out(stdout) is now redirected to the log file.
-    \item \keyword{chdir} -- Change the current directory to /usr/include
-    \item \keyword{execl} -- Replace the program image with /bin/ls and call its main() method
+    \item \keyword{open} -- will use the lowest available file descriptor (i.e. 1), so standard out (stdout) is now redirected to the log file.
+    \item \keyword{chdir} -- Change the current directory to /usr/include.
+    \item \keyword{execl} -- Replace the program image with /bin/ls and call its main() method.
     \item \keyword{perror} -- We don't expect to get here - if we did then \keyword{exec} failed.
     \item We need the "return 0;" because compilers complain if we don't have it.
 \end{enumerate}
@@ -823,17 +823,17 @@ \section{exec}
 \subsection{POSIX Exec Details}
 
 POSIX details all of the semantics that exec needs to cover \cite{exec_2018}.
-Note the following
+Note the following:
 
 \begin{enumerate}
 \item File descriptors are preserved after an exec. That means if a program open a file and doesn't to close it, it remains open in the child.
   This is a problem because usually the child doesn't know about those file descriptors. Nevertheless, they take up a slot in the file descriptor table and could possibly prevent other processes from accessing the file.
   The one exception to this is if the file descriptor has the Close-On-Exec flag set (O\_CLOEXEC) -- we will go over setting flags later.
-\item Various signal semantics. The executed processes preserve the signal mask and the pending signal set but does not preserve the signal handlers since it is a different program.
-\item Environment variables are preserved unless using an environ version of exec
-\item The operating system may open up 0, 1, 2 -- stdin, stdout, stderr, if they are closed after exec, most of the time they leave them closed.
+\item Various signal semantics: the executed processes preserve the signal mask and the pending signal set but do not preserve the signal handlers since it is a different program.
+\item Environment variables are preserved unless using an environ version of exec.
+\item The operating system may open up 0, 1, 2 -- stdin, stdout, stderr, if they are closed after exec; most of the time they leave them closed.
 \item The executed process runs as the same PID and has the same parent and process group as the previous process.
-\item The executed process is run on the same user and group with the same working directory
+\item The executed process is run on the same user and group with the same working directory.
 \end{enumerate}
 
 \subsection{Shortcuts}
@@ -907,7 +907,7 @@ \subsection{Environment Variables}
 
 Environment variables are variables that the system keeps for all processes to use.
 Your system has these set up right now!
-In Bash, some are already defined
+In Bash, some are already defined.
 
 \begin{lstlisting}[language=bash]
 $ echo $HOME

From de5f2d24f97c3a9aeac7574976de6821dd831553 Mon Sep 17 00:00:00 2001
From: Elijah Mock <28277163+ekcom@users.noreply.github.com>
Date: Sat, 14 Sep 2024 17:23:32 -0500
Subject: [PATCH 7/8] Remove extra tag that was rendering as text

---
 processes/processes.tex | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/processes/processes.tex b/processes/processes.tex
index 1fdc11b..df8ba41 100644
--- a/processes/processes.tex
+++ b/processes/processes.tex
@@ -882,7 +882,7 @@ \section{The fork-exec-wait Pattern}
 \caption{Fork, exec, wait diagram}
 \end{figure}
 
-\begin{lstlisting}[language=C][language=C]
+\begin{lstlisting}[language=C]
 #include <unistd.h>
 
 int main() {

From de769af07e4e9d53416a6ecf2ddfc58c7f1a9729 Mon Sep 17 00:00:00 2001
From: Elijah Mock <28277163+ekcom@users.noreply.github.com>
Date: Sat, 14 Sep 2024 17:25:30 -0500
Subject: [PATCH 8/8] Fix indentation errors

---
 processes/processes.tex | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/processes/processes.tex b/processes/processes.tex
index df8ba41..dc065f1 100644
--- a/processes/processes.tex
+++ b/processes/processes.tex
@@ -114,7 +114,7 @@ \subsection{Memory Layout}
 The stack is the place where automatically allocated variables and function call return addresses are stored.
 Every time a new variable is declared, the program moves the stack pointer down to reserve space for the variable.
 This segment of the stack is writable but not executable.
-		This behavior is controlled by the no-execute (NX) bit, sometimes called the W\^{}X (write XOR execute) bit, which helps prevent malicious code, such as \keyword{shellcode} from being run on the stack.
+This behavior is controlled by the no-execute (NX) bit, sometimes called the W\^{}X (write XOR execute) bit, which helps prevent malicious code, such as \keyword{shellcode} from being run on the stack.
 
 If the stack grows too far -- meaning that it either grows beyond a preset boundary or intersects the heap -- the program will stack overflow error, most likely resulting in a SEGFAULT.
 \textbf{The stack is statically allocated by default; there is only a certain amount of space to which one can write.}
@@ -201,7 +201,7 @@ \subsection{Other Contents}
     \item \textbf{File Descriptors} - A list of mappings from integers to real devices (files, USB flash drives, sockets)
     \item \textbf{Permissions} - What \keyword{user} the file is running on and what \keyword{group} the process belongs to.
           The process can then only perform operations based on the permissions given to the \keyword{user} or \keyword{group}, such as accessing files.
-		There are tricks to make a program take a different user than who started the program (e.g., \keyword{sudo} takes a program that a \keyword{user} starts and executes it as \keyword{root}).
+          There are tricks to make a program take a different user than who started the program (e.g., \keyword{sudo} takes a program that a \keyword{user} starts and executes it as \keyword{root}).
           More specifically, a process has a real user ID (identifies the owner of the process), an effective user ID (used for non-privileged users trying to access files only accessible by superusers), and a saved user ID (used when privileged users perform non-privileged actions).
     \item \textbf{Arguments} - a list of strings that tell your program what parameters to run under.
     \item \textbf{Environment Variables} - a list of key-value pair strings in the form \keyword{NAME=VALUE} that one can modify. These are often used to specify paths to libraries and binaries, program configuration settings, etc.