more spellchecking

Author: Vladimir Kotal

common.tex

@@ -21,6 +21,8 @@
 \usepackage{multicol}
 \usepackage{tabularx}
 
+\usepackage{nth}
+
 %\input{seminar.bg2}
 %\usepackage{seminar}
 

file-api.tex

@@ -609,7 +609,7 @@
 will learn about the \texttt{exec} calls on page \pageref{EXEC}.
 \item To fully understand how redirection works it is good to draw the file
 descriptor table for each step and where the slots point to.  For example, for
-the 2nd example in the slide, we have the initial state, after \texttt{close(1)}
+the \nth{2} example in the slide, we have the initial state, after \texttt{close(1)}
 and \texttt{open("out", ...)}, and the final state, as follows:
 
 \begin{verbatim}
@@ -622,7 +622,7 @@
 +-------+              +-------+              +-------+
 \end{verbatim}
 
-\item You need to pay attention to the state of descriptors.  The 2nd example
+\item You need to pay attention to the state of descriptors.  The \nth{2} example
 will not work if the descriptor 0 is already closed, as 
 \texttt{open} returns 0 (the first available descriptor) and \texttt{dup} fails
 while trying to duplicate an already closed descriptor.  Possible

history.tex

@@ -7,7 +7,7 @@
 \sltitle{Books on UNIX history}
 \begin{itemize}
 \item Peter Salus: \emsl{A Quarter Century of UNIX}, Addison-Wesley;
-1st~edition (1994)
+\nth{1}~edition (1994)
 \item Libes D., Ressler, S.: \emsl{Life With Unix: A Guide for
 Everyone}, Prentice Hall (1989)
 \item \emsl{Open Sources: Voices from the Open Source Revolution},
@@ -52,7 +52,7 @@
 patronage (virtual memory, multiprocessors, \dots) till 1985.
 The last Multics installation worked in the Canadian Department of National
 Defense and the system was used actively for example during the Persian gulf
-war. Definitive shutdown was made 31st October 2000. More information can be
+war. Definitive shutdown was made \nth{31} October 2000. More information can be
 found on \url{http://www.multicians.org}.
 \item Before the work on the development environment for PDP-7 started, Thmopson
 wrote the \emph{Space Travel} program, that was developed in other environment

intro.tex

@@ -295,14 +295,14 @@
 
 \begin{enumerate}
 \item Uresh Vahalia: \emsl{UNIX Internals: The New Frontiers}.
- Prentice Hall; 1st edition, 1995
+ Prentice Hall; \nth{1} edition, 1995
 \item Bach, Maurice J.: \emsl{The Design of the UNIX Operating System}.
 Prentice Hall, 1986
 \item McKusick, M. K., Neville-Neil, G. V.: \emsl{The Design and
 Implementation of the FreeBSD Operating System}. Addison-Wesley, 2004
 %\item Goodheart, B.; Cox, J.: \emsl{The Magic Garden Explained: the
 %Internals of UNIX System~V Release 4}. Prentice Hall, 1994
-\item McDougall, R.; Mauro, J.: \emsl{Solaris Internals}. Prentice Hall; 2nd
+\item McDougall, R.; Mauro, J.: \emsl{Solaris Internals}. Prentice Hall; \nth{2}
 edition, 2006.
 \item \emsl{Linux Documentation Project}. \url{http://tldp.org/}
 \end{enumerate}
@@ -314,7 +314,7 @@
 
 \begin{enumerate}
 \item A great book on Unix in general and compares SVR4.2, 4.4BSD, Solarix~2.x
-and Mach systems.  The 2nd edition, scheduled for 2005, never happened,
+and Mach systems.  The \nth{2} edition, scheduled for 2005, never happened,
 unfortunately.
 \item UNIX classic book. On UNIX System~V Rel.~2, and partially 3 as well.
 While outdated, it is one of the best books ever written on Unix.  In 1993 a
@@ -335,14 +335,14 @@
 \sltitle{Books on Unix programming}
 \begin{enumerate}
 \item Stevens, W. R., Rago, S. A.: \emsl{Advanced Programming in UNIX(r)
-Environment}. Addison-Wesley, 2nd edition, 2005.
+Environment}. Addison-Wesley, \nth{2} edition, 2005.
 \item Rochkind, M. J.: \emsl{Advanced UNIX Programming},
-Addison-Wesley; 2nd edition, 2004
+Addison-Wesley; \nth{2} edition, 2004
 \item Stevens, W. R., Fenner B., Rudoff, A. M.: \emsl{UNIX Network
 Programming, Vol. 1 -- The Sockets Networking API}. Prentice Hall,
-3rd edition, 2004
+\nth{3} edition, 2004
 \item Butenhof, D. R.: \emsl{Programming with POSIX Threads},
-Addison-Wesley; 1st edition, 1997
+Addison-Wesley; \nth{1} edition, 1997
 % I don't why but after I switched from FreeBSD to Solaris, I can't typeset
 % word "unix" anymore. It's like it wasn't there. Using {} trick helps.
 \item UNIX specifications, see \url{http://www.unix.org}
@@ -368,7 +368,7 @@
 \item Detailed descriptions of system calls and functions.
 \item \label{POSIX4} A book that did not fit the slide and covers topics outside
 of the scope of this class: Gall\-meis\-ter, B. R.: \emsl{POSIX.4 Programmers
-Guide: Programming for the Real World}, O'Reilly; 1st edition, 1995.  A great
+Guide: Programming for the Real World}, O'Reilly; \nth{1} edition, 1995.  A great
 book on real-time POSIX extensions with a beautiful cover.  See also pages
 \pageref{REALTIMEEXTENSIONS} a \pageref{SIGWAITINFO}.
 \item[\ldots] Go to Amazon and search for ``unix''.  If you ever buy anything,
@@ -449,7 +449,7 @@
 standard came to existence as ANSI X3.159-1989 ``Programming Language C,'' and
 is mostly known as ``ANSI C'', or C89, and the command line name for the
 compiler itself was \texttt{c89}.
-\item The 2nd edition of the C book (1988) was updated for the upcoming
+\item The \nth{2} edition of the C book (1988) was updated for the upcoming
 standard as it used one of its final drafts.  In 1990, ANSI C was adopted by ISO
 as ISO/IEC 9899:1990; that standard is sometimes called C90.  It's the same as
 C89 but it renumbered its sections and removed the rationale document which was
@@ -1882,7 +1882,7 @@
 \item Passing the environment in the third parameter of type
 \texttt{char**} is not part of the normative part of the C standard, only the
 informative one.  C compilers typically support that though.
-The \texttt{main} variant with the 3rd parameter looks like this:\\ \texttt{int
+The \texttt{main} variant with the \nth{3} parameter looks like this:\\ \texttt{int
 \funnm{main}(int \emph{argc}, char *\emph{argv}[], char *\emph{envp}[]);}
 \item The return value type of \texttt{main} should be always \texttt{int}.
 \emsl{Only lower 8 bits from that integer are only used though.}  It is always a
@@ -1971,7 +1971,7 @@
 convention.  \texttt{wget} does not follow convention and uses
 \texttt{http\_proxy} and \texttt{https\_proxy} as environment variables to set
 the proxy to be used, and other lower case variables as well.
-\item If \emph{envp} is the 3rd argument of \texttt{main}, it is the same pointer
+\item If \emph{envp} is the \nth{3} argument of \texttt{main}, it is the same pointer
 as is in the standard global variable \texttt{environ}.
 \item Example: \example{main/print-env.c} (see below how to clear out inherited
 environment from the shell using the \texttt{env} command):

proc.tex

@@ -521,8 +521,8 @@
 \item runs a program defined via \emph{path}
 \item arguments that follow, including \emph{arg0}, are given to the program via
 \texttt{argc} and \texttt{argv} of its \texttt{main()}
-\item the argument list must end with \texttt{(char *)0}, ie. \texttt{NULL}
-\item \emph{arg0} should contain the program name (ie. not the full path)
+\item the argument list must end with \texttt{(char *)0}, i.e. \texttt{NULL}
+\item \emph{arg0} should contain the program name (i.e. not the full path)
 \item \emsl{open file descriptors are unaffected by \funnm{exec}}
 \begin{itemize}
 \item \dots{}aside from file descriptors with flag \texttt{FD\_CLOEXEC}
@@ -541,7 +541,7 @@
 is not important for the sake of a discussion.
 \item Sometimes \texttt{argv[0]} is different from the executable file name.
 For example, \texttt{login} command prefixes the shell file name with
-\texttt{'-'}, eg. \texttt{-bash}.  The shell then knows it is supposed to
+\texttt{'-'}, e.g. \texttt{-bash}.  The shell then knows it is supposed to
 function as a login shell.  A login shell reads \texttt{/etc/profile}, for
 example.
 \item \funnm{exec} does not transfer the control to the program in memory
@@ -623,14 +623,14 @@
 \end{slide}
 
 \begin{itemize}
-\item \emsl{l} = list (ie. list of arguments), \emsl{v} = vector (ie.  an array
-of string pointers), \emsl{e}~=~environment (ie. environment variables are
+\item \emsl{l} = list (i.e. list of arguments), \emsl{v} = vector (i.e.  an array
+of string pointers), \emsl{e}~=~environment (i.e. environment variables are
 passed to the function via an argument), \emsl{p} = \texttt{PATH} is used.
 \item Aside from \funnm{execlp} and \funnm{execvp}, it is always needed to use
 the full path to the executable program, either an absolute or relative one.
 \item All variants aside from \funnm{execle} and \funnm{execve}
 are also passing to the program being executed the environment variables of the
-calling process, ie. the \texttt{environ} array.
+calling process, i.e. the \texttt{environ} array.
 \item For some unknown historical reasons, there is no ``p'' with ``e'' together
 in the standard.  However, GNU provides \funnm{execvpe} as an extension.
 \item \label{EXEC_DATE} Example: \example{exec/exec-date.c}
@@ -697,7 +697,7 @@
 
 \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
+should use.  While most of the UNIX and Unix-like systems (e.g. 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
@@ -850,9 +850,9 @@
     \item producer blocks on writing if the pipe is full
     \item consumer blocks on reading if the pipe is empty
     \end{itemize}
-\item consumer gets EOF (ie. \texttt{read()} returns
+\item consumer gets EOF (i.e. \texttt{read()} returns
 \texttt{0}) only if all copies of \texttt{fildes[1]} are closed.
-\item named pipe (ie. fifo, see \funnm{mkfifo}) works the same way.  The
+\item named pipe (i.e. fifo, see \funnm{mkfifo}) works the same way.  The
 difference is any process can use it.
 \end{itemize}
 \end{slide}
@@ -866,7 +866,7 @@
 u{}nix-domain socket.  However, such a workaround is out of scope for this
 class.
 \item If the function \funnm{write} writes at most \texttt{PIPE\_BUF} bytes to
-the pipe, it is guaranteed that the write will be atomic, ie. such bytes will
+the pipe, it is guaranteed that the write will be atomic, i.e. such bytes will
 not be intermingled with bytes written by other producers.
 \item \label{TWO_WAY_PIPES} The SUSv3 standard does not specify whether
 \texttt{fildes[0]} is also open for writing and if \texttt{fildes[1]} is also
@@ -908,13 +908,13 @@
 \funnm{pipe}, we have to call \texttt{dup2(pd[1], 1)} in the producer as
 otherwise \texttt{dup(pd[1])} could reuse the file descriptor \texttt{0} in
 place of expected \texttt{1}.  You might also need to check if \verb#pd[1] == 1#
-(ie. standard output was closed before calling \funnm{pipe}) as in that case we
+(i.e. standard output was closed before calling \funnm{pipe}) as in that case we
 could actually close one end of the pipe.  Similarly, in the consumer you might
 need to check if \verb#pd[0] == 0#.
 \item It is better to create a pipe from a child to its parent as typically the
 process writing the pipe finishes first, then the consumer reads the rest of the
 data, processes it, and then finally exits.  Remember, the shell waits for the
-program it started, ie. the parent, and it does not care at all about children
+program it started, i.e. the parent, and it does not care at all about children
 the running program spawned during its life.  If the pipe was created the other
 way around, the shell could print the prompt after the parent finished while the
 data from the child might still be flowing to the console.
@@ -924,7 +924,7 @@
 was formed.  Ie. the first command in the pipeline was created as the last
 process.
 \item However, in \texttt{bash}, all processes in a pipeline are direct children
-of the shell itself, ie. \texttt{bash} calls \funnm{fork} that many times as is
+of the shell itself, i.e. \texttt{bash} calls \funnm{fork} that many times as is
 the number of programs in the pipeline.  Before the prompt is printed, it waits
 for all processes it directly created to finish.
 \end{itemize}
@@ -1211,7 +1211,7 @@
     For \funnm{dlopen}, the default is \texttt{RTLD\_LOCAL}.  It means you can
     map the same library multiple time via \funnm{dlopen} and the symbols in the
     mapped instances of the same library will not overlap.  However, all
-    globally mapped symbols from there are shared, eg. \texttt{errno}.
+    globally mapped symbols from there are shared, e.g. \texttt{errno}.
     \end{itemize}
 \item \label{RTLD_NEXT} Special handle \texttt{RTLD\_NEXT} searches the symbol
 only in libraries loaded after the library that called \funnm{dlsym}.  Handy for

synchro.tex

@@ -308,15 +308,15 @@
 \item to set locks for file \texttt{fildes}:
 \texttt{cmd}: 
     \begin{itemize}
-    \item \texttt{F\_GETLK} \dots{} takes lock description from 3rd argument
+    \item \texttt{F\_GETLK} \dots{} takes lock description from \nth{3} argument
     and replaces it with description of existing lock that collides with it.
-    \item \texttt{F\_SETLK} \dots{} sets or destroys lock described by the 3rd
+    \item \texttt{F\_SETLK} \dots{} sets or destroys lock described by the \nth{3}
     argument. If the lock cannot be set immediately returns $-1$.
     \item \texttt{F\_SETLKW} \dots{} like \texttt{F\_SETLK}, however puts
     the process to sleep if it is not possible to set the lock 
     (\texttt{W} means ``wait'')
     \end{itemize}
-\item 3rd argument contains lock description and is pointer to 
+\item \nth{3} argument contains lock description and is pointer to 
 \texttt{struct flock}
 \end{itemize}
 \end{slide}