projects
/
pintos-anon
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
|
inline
| side by side (parent:
dc9d1a1
)
Note about testing.
author
Ben Pfaff
<blp@cs.stanford.edu>
Wed, 4 Jan 2006 20:03:28 +0000
(20:03 +0000)
committer
Ben Pfaff
<blp@cs.stanford.edu>
Wed, 4 Jan 2006 20:03:28 +0000
(20:03 +0000)
doc/userprog.texi
patch
|
blob
|
history
diff --git
a/doc/userprog.texi
b/doc/userprog.texi
index e4e6098b5e8f77acdaf691b967af34d6cc0ef89d..b7d356ff0790b13b639ea1072429decc78e324dc 100644
(file)
--- a/
doc/userprog.texi
+++ b/
doc/userprog.texi
@@
-19,6
+19,12
@@
start with a fresh copy. No code from project 1 is required for this
assignment. The ``alarm clock'' functionality may be useful in
projects 3 and 4, but it is not strictly required.
assignment. The ``alarm clock'' functionality may be useful in
projects 3 and 4, but it is not strictly required.
+You might find it useful to go back and reread how to run the tests
+(@pxref{Testing}). In particular, the tests for project 2 and later
+projects will probably run faster if you use the qemu emulator, e.g.@:
+via @code{make check PINTOSOPTS='--qemu'}. The qemu emulator is
+available only on the Linux machines.
+
@menu
* Project 2 Background::
* Project 2 Suggested Order of Implementation::
@menu
* Project 2 Background::
* Project 2 Suggested Order of Implementation::
@@
-222,9
+228,10
@@
pintos -p ../../examples/echo -a echo -- -f -q run 'echo x'
If you don't want to keep the file system disk around for later use or
inspection, you can even combine all four steps into a single command.
If you don't want to keep the file system disk around for later use or
inspection, you can even combine all four steps into a single command.
-The @code{--fs-disk=2} option creates a temporary disk just for the
-duration of the @command{pintos} run. The Pintos automatic test suite
-makes extensive use of this syntax:
+The @code{--fs-disk=@var{n}} option creates a temporary disk
+approximately @var{n} megabytes in size just for the duration of the
+@command{pintos} run. The Pintos automatic test suite makes extensive
+use of this syntax:
@example
pintos --fs-disk=2 -p ../../examples/echo -a echo -- -f -q run 'echo x'
@example
pintos --fs-disk=2 -p ../../examples/echo -a echo -- -f -q run 'echo x'