Updated to use Bochs 2.6.11

[pintos-anon] / doc / intro.texi

diff --git a/doc/intro.texi b/doc/intro.texi
index ad5e28633fb49629e43ec6b34748dff1bbbc8e60..5372f74bb6a266d2787ec1c45264823996bd2ae7 100644 (file)
--- a/doc/intro.texi
+++ b/doc/intro.texi
@@ -9,7 +9,7 @@ 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.
 You will also add a virtual memory implementation.
 
 Pintos could, theoretically, run on a regular IBM-compatible PC.

-Unfortunately, it is impractical to supply every @value{coursenumber} student
+Unfortunately, it is impractical to supply every student

 a dedicated PC for use with Pintos.  Therefore, we will run Pintos projects
 in a system simulator, that is, a program that simulates an 80@var{x}86
 CPU and its peripheral devices accurately enough that unmodified operating
 a dedicated PC for use with Pintos.  Therefore, we will run Pintos projects
 in a system simulator, that is, a program that simulates an 80@var{x}86
 CPU and its peripheral devices accurately enough that unmodified operating


@@ -19,7 +19,7 @@ systems and software can run under it.  In class we will use the
 QEMU} simulators.  Pintos has also been tested with
 @uref{http://www.vmware.com/, , VMware Player}.
 
 QEMU} simulators.  Pintos has also been tested with
 @uref{http://www.vmware.com/, , VMware Player}.
 

-These projects are hard.  @value{coursenumber} has a reputation of taking a lot of
+These projects are hard.  They have a reputation of taking a lot of

 time, and deservedly so.  We will do what we can to reduce the workload, such
 as providing a lot of support material, but there is plenty of
 hard work that needs to be done.  We welcome your
 time, and deservedly so.  We will do what we can to reduce the workload, such
 as providing a lot of support material, but there is plenty of
 hard work that needs to be done.  We welcome your


@@ -68,11 +68,8 @@ environment.
 Now you can extract the source for Pintos into a directory named
 @file{pintos/src}, by executing
 @example
 Now you can extract the source for Pintos into a directory named
 @file{pintos/src}, by executing
 @example

-zcat @value{localpintostarpath} | tar x
+git clone @value{gitrepo}

 @end example
 @end example

-Alternatively, fetch
-@uref{@value{localpintoshttppath}}
-and extract it in a similar way.

 
 Let's take a look at what's inside.  Here's the directory structure
 that you should see in @file{pintos/src}:
 
 Let's take a look at what's inside.  Here's the directory structure
 that you should see in @file{pintos/src}: