Removed some remarks about a future thread system.

doc/scsh-manual/syscalls.tex

@@ -930,7 +930,7 @@ buffering is turned off
 \end{defundesc}
 
 \subsection{File locking}
-
+\label{sec:filelocking}
 Scsh provides {\Posix} advisory file locking.
 \emph{Advisory} locks are locks that can be checked by user code, 
 but do not affect other I/O operations.
@@ -1973,20 +1973,11 @@ values \ex{'early}, \ex{'late}, or {\sharpf} (\ie, no autoreap).
         The child is reaped from the {\Unix} kernel's process table
         into scsh as soon as it dies. This is done by having a
         signal handler for the \ex{SIGCHLD} signal reap the process.
-        \emph{
-        If a scsh program sets its own handler for the \ex{SIGCHLD}
-        signal, the handler must reap dead children
-        by calling \ex{wait}, \ex{wait-any}, or \ex{reap-zombies}.}
-        We deprecate interrupt-driven code, and hope to provide
-        alternative tools in a future, multi-threaded release of scsh.
 
 \item [late]
         The child is not autoreaped until it dies \emph{and} the scsh program
         drops all pointers to its process object. That is, the process
         table is cleaned out during garbage collection.
-        \oops{The \ex{late} policy is not supported under the current
-        release of scsh. It requires more sophisticated gc hooks than
-        we can get from the release of {\scm} that we use.}
 
 \item [\sharpf]
         If autoreaping is turned off, process reaping is completely under