Introduce PID_ERROR as an invalid exec return value.

[pintos-anon] / doc / filesys.texi

diff --git a/doc/filesys.texi b/doc/filesys.texi
index 5ffcb755246456be754dc0820e2442b21c2d36a1..804c5a7344c2d8e8f695d8d8a1f0f93e68d50aa5 100644 (file)
--- a/doc/filesys.texi
+++ b/doc/filesys.texi
@@ -1,4 +1,4 @@
-@node Project 4--File Systems, , Project 3--Virtual Memory, Top
+@node Project 4--File Systems, Multilevel Feedback Scheduling, Project 3--Virtual Memory, Top

 @chapter Project 4: File Systems
 
 In the previous two assignments, you made extensive use of a
 @chapter Project 4: File Systems
 
 In the previous two assignments, you made extensive use of a


@@ -23,27 +23,7 @@ filesystem implementation.
 
 FIXME FIXME FIXME
 The first step is to understand the default filesystem provided by the
 
 FIXME FIXME FIXME
 The first step is to understand the default filesystem provided by the

-base code.  The first things you should look at are
-@file{threads/init.c} and @file{filesys/fsutil.c}: there are special
-command line arguments to Pintos which are used to format and
-manipulate the emulated disk.  Specifically, @option{-f} formats the
-file system disk for use with Pintos, and @option{-cp @var{src}
-@var{dst}} copies @var{src} on the Unix filesystem to @var{dst} on the
-file system disk.  With this information, you should be able to
-compile the base code and try out the command: @samp{pintos -f -cp
-./small small} to copy the file @file{small} from your working
-directory into the Pintos file system.
-
-FIXME FIXME FIXME
-One thing you should realize immediately is that, until you use the
-above operation to copy the shell (or whatever your initial program
-is) to the emulated disk, Pintos will be unable to do very much useful
-work (it'll try to open the shell and fail, thereby quitting out).  You
-will also find that you won't be able to do interesting things until
-you copy a variety of programs to the disk.  A useful technique, once
-your inode formats are finalized, is to create a clean reference disk
-and copy that over whenever you trash your disk beyond a useful state
-(which will probably happen quite often while debugging).
+base code.  

 
 @menu
 * File System New Code::        
 
 @menu
 * File System New Code::