more spellchecking

Author: Vladimir Kotal

Makefile

@@ -73,6 +73,7 @@ spellcheck:
 			    sed 's/pdfbookmark\[[0-9]\]{\([^{}]*\)}{.*}/pdfbookmark{\1}/' | \
 			    sed 's/\\\-//g' | \
 			    sed 's/\\texttt{[^{]*}//g' | \
+			    sed 's/\\\funnm{[^{]*}//g' | \
 			    sed 's/\\emprg{.*}//g' | \
 			    aspell -t --personal=./unix_dict.txt list; \
 		done

file-api.tex

@@ -275,7 +275,7 @@
 or terminates.
 \item If a process needs a temporary file, it can create it, unlink it right
 away, and work with it using the existing file descriptor.  When the file
-descriptor is closed (and all of its possible duplications), the file data is
+descriptor is closed (and all of its possible duplicates), the file data is
 released.
 \item Even \texttt{close} may fail.  For example, some filesystems may write the
 data on file closure, and if that write fails, \texttt{close} fails.

files.tex

@@ -38,7 +38,7 @@
 \texttt{FAT32} does no provide user and access rights for files so those are
 faked when such filesystem is mounted.
 \item Upon the system boot, the root filesystem is mounted first, other
-filesystems are later mounted via the \texttt{mount} commmand, usually from
+filesystems are later mounted via the \texttt{mount} command, usually from
 specific startup services based on the system you use.  The startup services
 sometimes use file \texttt{/etc/fstab} as a source of information about what
 filesystems to mount.  You can also use \texttt{mount} manually.  To unmount a

network.tex

@@ -655,7 +655,7 @@
 \item If \texttt{connect} was used then \texttt{send} can be used instead of
 \texttt{sendto}.
 \item Successful return from either \emsl{does not mean successful delivery of
-the message to the remote side}, but only instertion of the data to local buffer
+the message to the remote side}, but only insertion of the data to local buffer
 which is yet to be sent out.
 \item It is possible to use \texttt{sendto} for stream service, however the
 address will be ignored. The only reason not to use \texttt{write} would be to
@@ -695,7 +695,7 @@
 \item Once closed, TCP socket can remain in transitory state which is defined in
 TCP protocol for connection closing. Before the socket is completely destroyed,
 it is not possible to use another socket with the same port, unless this
-behavior was overriden with the \texttt{SO\_REUSEADDR} flag using the
+behavior was overridden with the \texttt{SO\_REUSEADDR} flag using the
 \texttt{setsockopt} function, see page \pageref{SETSOCKOPT}.
 \item Connection reset is abnormal connection termination. In case of TCP
 a packet with \texttt{RST} flag is used for such termination. The remote side
@@ -771,10 +771,10 @@
 (\texttt{EAFNOSUPPORT}). \texttt{inet\_ntop} returns \texttt{dst} if everything
 is OK otherwise returns \texttt{NULL} with \texttt{errno} set.
 \item Addresses and ports in binary form are stored as big endian.
-\item \texttt{dst} has to be suffciently sized because there is no parameter
+\item \texttt{dst} has to be sufficiently sized because there is no parameter
 specifying the size. This is not a problem since according to the value of
 \texttt{af} appropriate address structure or character array can be passed in.
-For maximal lenghts of strings for addresses, 2 macros can be used --
+For maximal lengths of strings for addresses, 2 macros can be used --
 \texttt{INET\_ADDRSTR\-LEN} (16) or \texttt{INET6\_ADDRSTRLEN} (48). 
 These values contain space for terminating \texttt{\bs{}0}.
 \item \texttt{size} is string size of \texttt{dst}. If not sufficient, the call

proc.tex

@@ -462,7 +462,7 @@
 \texttt{init} process, that will take care of the zombie after the process ends.
 \end{description}
 \begin{itemize}
-\item To get information about running processes programatically is possible
+\item To get information about running processes programmatically is possible
 using non-standard API (e.g. the \texttt{libproc} library on Solaris built
 on top of the \texttt{procfs} filesystem that is mounted under \texttt{/proc}).
 \item Note that using \texttt{getppid} value to check if parent exited is not
@@ -697,14 +697,14 @@
 
 \begin{itemize}
 \item The UNIX standard does not specify what executable file format systems
-should use.  While most of the UNIX and Unix-like systems (eg. Linux distros)
-use ELF, there are other widely used systems that do not.  One example is
-macOS (which is a certified UNIX system) that uses the \emph{Mach-O} file
-format, short for \emph{Mach Object}.  Each Mach-O file is made
+should use.  While most of the UNIX and Unix-like systems (eg. Linux
+distributions) use ELF, there are other widely used systems that do not. One
+example is macOS (which is a certified UNIX system) that uses the \emph{Mach-O}
+file format, short for \emph{Mach Object}. Each Mach-O file is made
 up of one Mach-O header, followed by a series of load commands, followed by one
 or more segments, each of which contains between 0 and 255 sections.
 \item On Solaris, the \texttt{elfdump} command allows listing sections of the
-ELF file in a human readable form.  On Linux distros, use \texttt{readelf}.
+ELF file in a human readable form. On Linux distributions, use \texttt{readelf}.
 \item The \emph{ELF header} contains basic information about the file.  Try
 ``\texttt{readelf -h /bin/ls}'' on any Linux distro.
 \item The \emph{program header table} is only present in files that are

synchro.tex

@@ -572,7 +572,7 @@
 \end{minipage}
 \begin{itemize}
 \item creates or opens a new POSIX semaphore.  \emph{mode} is same as for
-\funnm{open}().  Use ``/somename'' for the \emph{name}.
+\funnm{open}().  Use ``\texttt{/somename}'' for the \emph{name}.
 \end{itemize}
 \texttt{int \funnm{sem\_wait}(sem\_t *\emph{sem});}
 \begin{itemize}

sys-v-semaphores.tex

@@ -4,7 +4,8 @@
 
 \begin{slide}
 \sltitle{System V semaphore API }
-\texttt{int \funnm{semget}(key\_t \emph{key}, int \emph{nsems}, int \emph{semflg});}
+\texttt{int \funnm{semget}(key\_t \emph{key}, int \emph{\texttt{nsems}},
+int \emph{\texttt{semflg}});}
 \begin{itemize}
 \item returns identifier of an array of \texttt{nsems} semaphores associated
 with the \texttt{key} key (\texttt{IPC\_PRIVATE} key \dots{} private semaphores,
@@ -13,13 +14,14 @@
 \texttt{IPC\_CREAT} (create if does not exist),
 \texttt{IPC\_EXCL} (error, if exists). 
 \end{itemize}
-\texttt{int \funnm{semctl}(int \emph{semid}, int \emph{semnum},
-int \emph{cmd}, ...);}
+\texttt{int \funnm{semctl}(int \emph{\texttt{semid}},
+int \emph{\texttt{semnum}}, int \emph{\texttt{cmd}}, ...);}
 \begin{itemize}
 \item controlling function, optional 4th argument \texttt{arg} is of the
 \texttt{union~semun} type.
 \end{itemize}
-\texttt{int \funnm{semop}(int \emph{semid}, struct sembuf *\emph{sops}, size\_t \emph{nsops});}
+\texttt{int \funnm{semop}(int \emph{\texttt{semid}},
+struct sembuf *\emph{\texttt{sops}}, size\_t \emph{\texttt{nsops}});}
 \begin{itemize}
 \item generic operations P and V.
 \end{itemize}

threads.tex

@@ -563,7 +563,7 @@
 then unlocks them in the \emph{post-fork} handler (both for the parent and the
 child), you will avoid such deadlocks.  When locking mutexes in the
 pre-fork handler, other threads are still running so the mutexes held by them
-can be released (usually each thread exits a crititcal section in a short time
+can be released (usually each thread exits a critical section in a short time
 in well written code).  Example: \example{pthreads/atfork.c}.  For more on this
 topic, see [Butenhof].
 \item See page \pageref{MUTEXES} on why mutexes locked in other threads on
@@ -710,8 +710,8 @@
 \item Mutex = \emph{mutual exclusion}
 \item Special form of Dijkstra semaphores -- the difference between mutexes and
 binary semaphores is that \emsl{mutex has an owner and locked mutex must be
-unlocked only by the thread that acquied it.} This is not the case with
-semephores. In order to check whether given mutex was locked by different thread
+unlocked only by the thread that acquired it.} This is not the case with
+semaphores. In order to check whether given mutex was locked by different thread
 when acquiring it, it is necessary to test return value of
 \texttt{p\-thread\_mutex\_lock}, and also have the lock checking set, see below.
 \item Mutexes are meant to be held for short time only. They are used for
@@ -766,7 +766,7 @@
 % \cline{2-4}
 \end{tabular}}
 \item Static mutex initialization using before mentioned macro will set default
-attributes. It is possbile to use initializer function also for statically
+attributes. It is possible to use initializer function also for statically
 allocated mutex. If a mutex is dynamically allocated, it is always necessary to
 use \texttt{pthread\_mutex\_init}, even if the default attributes are desired or
 not.
@@ -819,7 +819,7 @@
 \item Locking a mutex that is being held by another thread is not correct.
 Sometimes a (self)deadlock can ensue, see the previous page. If you need to
 unlock a mutex locked by different thread, use binary semaphores instead.
-\item When creating a program where effectivity is paramount, it is necessary to
+\item When creating a program where efficiency is paramount, it is necessary to
 think about how many mutexes will be needed and how exactly will be used.
 Even a library that was not written with threads in mind can be converted to be
 thread-safe (see page \pageref{THREADSAFE}) by inserting arbitrary function from
@@ -873,7 +873,7 @@
 7}''. Conditional variable can be in fact compared to a flag of certain color;
 if it is lifted up, it means that the threads waiting for the flag to be waved
 are informed (= woken up) and can use this information according its own
-judgement. Some threads can wait for \texttt{n} to be bigger than 7, the other
+judgment. Some threads can wait for \texttt{n} to be bigger than 7, the other
 can be waiting solely for \texttt{n} to change anyhow. It is only up to the
 programmer, if for concrete situation uses just one condition variable or
 for all situations. For the second situation, the threads waiting on 
@@ -967,7 +967,7 @@
 \item one conditional variable can be used to announce multiple situations
 at once -- e.g. when inserting or removing an item to/from a queue.
 Because of this, it is necessary to test the condition the thread is waiting
-for. Another consequence of this is that it is neccessary to use broadcast
+for. Another consequence of this is that it is necessary to use broadcast
 in such situation. Let's assume that both readers and writers are waiting for
 condition ``state of queue has changed''. If only single wakeup event is made
 after item insertion to the queue, then another writer can be woken up,
@@ -1308,7 +1308,7 @@
 \sltitle{Thread-safe versus reentrant}
 
 \begin{itemize}
-\item \emph{thead-safe} means that the function can be called from multiple
+\item \emph{thread-safe} means that the function can be called from multiple
 threads in parallel without destructive consequences
 \begin{itemize}
 \item a function which was not designed to be thread-safe can be
@@ -1390,7 +1390,7 @@
 \item Solaris
 \begin{itemize}
 \item \funnm{pthread\_cond\_reltimedwait\_np}\texttt{(\dots)}
-\item[$\rightarrow$] like timedwait, however the timeout is relative
+\item[$\rightarrow$] like \texttt{timedwait}, however the timeout is relative
 \end{itemize}
 
 \item OpenBSD

unix_dict.txt

@@ -711,7 +711,17 @@ pdfkeywords
 pagebackref
 Gingell
 Dekker
+Dekker's
 TLS
 iOS
 verhogen
 verlagen
+programmatically
+virtualized
+namespaces
+decrement
+increment
+incrementing
+decrementing
+endianess
+Downey