Get rid of -rndpg option for now, because none of the tests use it.

[pintos-anon] / doc / filesys.texi

diff --git a/doc/filesys.texi b/doc/filesys.texi
index e0c1618b49e46b74786b28d1476aa0521019a5a6..9f06510b114e972fb3046ab5e25ffbeb32f9cebf 100644 (file)
--- a/doc/filesys.texi
+++ b/doc/filesys.texi
@@ -11,8 +11,8 @@ You may build project 4 on top of project 2 or project 3.  In either
 case, all of the functionality needed for project 2 must work in your
 filesys submission.  If you build on project 3, then all of the project
 3 functionality must work also, and you will need to edit
-@file{filesys/Make.vars} to enable VM functionality.  A small amount of
-extra credit is available if you do build on project 3.
+@file{filesys/Make.vars} to enable VM functionality.  You can receive up
+to 5% extra credit if you do enable VM.
 
 @menu
 * Project 4 Background::        
@@ -125,7 +125,7 @@ every time a write is made off the end of the file.  Your file system
 must allow this.
 
 There should be no predetermined limit on the size of a file, except
-that a disk cannot exceed the size of the disk (minus metadata).  This
+that a file cannot exceed the size of the disk (minus metadata).  This
 also applies to the root directory file, which should now be allowed
 to expand beyond its initial limit of 16 files.
 
@@ -261,6 +261,11 @@ return to the process immediately.  The read-ahead request for disk
 block 2 should be handled asynchronously, in the background.
 @end table
 
+@strong{We recommend integrating the cache into your design early.}  In
+the past, many groups have tried to tack the cache onto a design late in
+the design process.  This is very difficult.  These groups have often
+turned in projects that failed most or all of the tests.
+
 @node File System Synchronization
 @subsection Synchronization