X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=doc%2Fintro.texi;h=e49a6c6f89af5c51436b7a9481f9a84ed3347ab6;hb=e6237bd933978064816ecad90367f6d58b0ac97d;hp=81b54fb5e11057721d5617675bf12168ad89896c;hpb=01679e7fec5244d137cc9b2cfc2d72e946c4d9d2;p=pintos-anon diff --git a/doc/intro.texi b/doc/intro.texi index 81b54fb..e49a6c6 100644 --- a/doc/intro.texi +++ b/doc/intro.texi @@ -9,10 +9,10 @@ project team will strengthen its support in all three of these areas. 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/, , @@ -79,7 +79,7 @@ Now you can extract the source for Pintos into a directory named @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. @@ -210,7 +210,7 @@ are not very useful for our purposes. (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