You will also add a virtual memory implementation.
Pintos could, theoretically, run on a regular IBM-compatible PC. As
-fun as it might be, it is impractical to supply every student in CS
-140 with his or her own PC. Therefore, we will run Pintos projects in
-a PC simulator, that is, a program that simulates an 80@var{x}86 CPU
-and its peripheral devices well enough that unmodified operating
+much fun as it might be, it is impractical to supply every student in
+CS 140 with his or her own PC. Therefore, we will run Pintos projects
+in a PC simulator, that is, a program that simulates an 80@var{x}86
+CPU and its peripheral devices well enough that unmodified operating
systems and software can run under it. In class we will use the
@uref{http://bochs.sourceforge.net, , Bochs} simulator. Pintos has
also been tested within @uref{http://fabrice.bellard.free.fr/qemu/, ,
@example
tar xzf /usr/class/cs140/pintos/pintos.tar.gz
@end example
-Alternatively
+Alternatively, retrieve
@uref{http://www.stanford.edu/class/cs140/pintos/pintos.tar.gz} and
extract it in a similar way.
(If no window appeared at all, and you just got a terminal full of
corrupt-looking text, then you're probably logged in remotely and X
forwarding is not set up correctly. In this case, you can fix your X
-setup, or you can use the @option{nv} option.)
+setup, or you can use the @option{-v} option.)
The text printed by Pintos inside Bochs probably went by too quickly
to read. However, you've probably noticed by now that the same text