rtc: Fix Unix epoch conversion from RTC time.

[pintos-anon] / doc / filesys.texi

diff --git a/doc/filesys.texi b/doc/filesys.texi
index 2567d6ae38c39b4f3162d944ac101d96805e4960..41f860f63eea2cc53627e0b711d5bd5bf0d263c3 100644 (file)
--- a/doc/filesys.texi
+++ b/doc/filesys.texi
@@ -11,7 +11,7 @@ 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.  You can receive up
+@file{filesys/Make.vars} to enable VM functionality. You can receive up
 to 5% extra credit if you do enable VM.
 
 @menu
@@ -174,8 +174,9 @@ rationale for it in your design documentation, and as long as it does
 not suffer from external fragmentation (as does the extent-based file
 system we provide).
 
-You can assume that the disk will not be larger than 8 MB.  You must
-support files as large as the disk (minus metadata).  Each inode is
+You can assume that the file system partition will not be larger than
+8 MB.  You must
+support files as large as the partition (minus metadata).  Each inode is
 stored in one disk sector, limiting the number of block pointers that it
 can contain.  Supporting 8 MB files will require you to implement
 doubly-indirect blocks.
@@ -189,7 +190,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 file cannot exceed the size of the disk (minus metadata).  This
+that a file cannot exceed the size of the file system (minus metadata).  This
 also applies to the root directory file, which should now be allowed
 to expand beyond its initial limit of 16 files.
 
@@ -303,7 +304,7 @@ are straightforward once the above syscalls are implemented.
 We have also provided @command{pwd}, which is not so straightforward.
 The @command{shell} program implements @command{cd} internally.
 
-The @code{pintos} @option{put} and @option{get} commands should now
+The @code{pintos} @option{extract} and @option{append} commands should now
 accept full path names, assuming that the directories used in the
 paths have already been created.  This should not require any significant
 extra effort on your part.
@@ -456,10 +457,12 @@ modified by the reference solution.
  30 files changed, 2721 insertions(+), 286 deletions(-)
 @end verbatim
 
-@item Can @code{DISK_SECTOR_SIZE} change?
+@item Can @code{BLOCK_SECTOR_SIZE} change?
 
-No, @code{DISK_SECTOR_SIZE} is fixed at 512.  This is a fixed property
-of IDE disk hardware.
+No, @code{BLOCK_SECTOR_SIZE} is fixed at 512.  For IDE disks, this
+value is a fixed property of the hardware.  Other disks do not
+necessarily have a 512-byte sector, but for simplicity Pintos only
+supports those that do.
 @end table
 
 @menu
@@ -474,9 +477,10 @@ of IDE disk hardware.
 @table @b
 @item What is the largest file size that we are supposed to support?
 
-The disk we create will be 8 MB or smaller.  However, individual files
-will have to be smaller than the disk to accommodate the metadata.
-You'll need to consider this when deciding your inode organization.
+The file system partition we create will be 8 MB or smaller.  However,
+individual files will have to be smaller than the partition to
+accommodate the metadata.  You'll need to consider this when deciding
+your inode organization.
 @end table
 
 @node Subdirectories FAQ