@file{sun4u} or @file{i686} according to the type of computer you're
logged into.}
@example
-set path = ( $path /usr/class/cs140/`uname -m`/bin )
+set path = ( /usr/class/cs140/`uname -m`/bin $path )
@end example
@noindent
-(Notice that both @samp{`} are left single quotes or ``backticks.'')
+@strong{Notice that both @samp{`} are left single quotes or
+``backticks,'' not apostrophes (@samp{'}).}
It is a good idea to add this line to the @file{.cshrc} file
in your home directory. Otherwise, you'll have to type it every time
you log in.
Example code for condition variables (@pxref{Condition Variables}) is
from classroom slides originally by Dawson Engler and updated by Mendel
-Roseblum.
+Rosenblum.
@node Trivia
@section Trivia
Pintos originated as a replacement for Nachos with a similar design.
Since then Pintos has greatly diverged from the Nachos design. Pintos
differs from Nachos in two important ways. First, Pintos runs on real
-or simulated 80@var{x}86 hardware, whereas Nachos runs as a process on a
-host operating system. Second, like most real-world operating systems,
-Pintos is written in C, whereas Nachos is written in C++.
+or simulated 80@var{x}86 hardware, but Nachos runs as a process on a
+host operating system. Second, Pintos is written in C like most
+real-world operating systems, but Nachos is written in C++.
Why the name ``Pintos''? First, like nachos, pinto beans are a common
Mexican food. Second, Pintos is small and a ``pint'' is a small amount.