-cd $top/m5/build
-scons TARGET/OPTLEVL # e.g. ALPHA_FS/m5.opt, use -j N if you have a MP system
-cd $top/m5-test
-./do-tests.pl -B ALPHA_SE # test what you just built
-./do-tests.pl -B ALPHA_FS # test what you just built
-# wait for tests to run...
-# should end with "finished do-tests successfully!"
+Different targets are built in different subdirectories of m5/build.
+Binaries with the same target but different optimization levels share
+the same directory. Note that you can build m5 in any directory you
+choose;p just configure the target directory using the 'mkbuilddir'
+script in m5/build.
+
+The following steps will build and test the simulator. The variable
+"$top" refers to the top directory where you've unpacked the files,
+i.e., the one containing the m5, m5-test, and ext directories. If you
+have a multiprocessor system, you should give scons a "-j N" argument (like
+make) to run N jobs in parallel.
+
+To build and test the syscall-emulation simulator:
+
+ cd $top/m5/build
+ scons ALPHA_SE/test/opt/quick
+
+This process takes under 10 minutes on a dual 3GHz Xeon system (using
+the '-j 4' option).
+
+To build and test the full-system simulator:
+
+1. Unpack the full-system binaries from m5_system_1.1.tar.bz2. (See
+ above for directions on obtaining this file if you don't have it.)
+ This package includes disk images and kernel, palcode, and console
+ binaries for Linux and FreeBSD.
+2. Edit the SYSTEMDIR search path in $top/m5-test/SysPaths.py to
+ include the path to your local copy of the binaries.
+3. In $top/m5/build, run "scons ALPHA_FS/test/opt/quick".
+
+This process also takes under 10 minutes on a dual 3GHz Xeon system
+(again using the '-j 4' option).
+