rtc: Fix Unix epoch conversion from RTC time.

[pintos-anon] / doc / filesys.tmpl

diff --git a/doc/filesys.tmpl b/doc/filesys.tmpl
index 4aefa437f1302b2ee0c6c2b0cd88ae49306ebd75..f3bd101d67f26c2d8c894ef45d5afdc68609f59c 100644 (file)
--- a/doc/filesys.tmpl
+++ b/doc/filesys.tmpl
@@ -1,8 +1,8 @@
-                            +-------------------------+
-                    |          CS 140         |
-                    | PROJECT 4: FILE SYSTEMS |
-                    |     DESIGN DOCUMENT     |
-                    +-------------------------+
+             +-------------------------+
+             |         CS 140          |
+             | PROJECT 4: FILE SYSTEMS |
+             |     DESIGN DOCUMENT     |
+             +-------------------------+
 
 ---- GROUP ----
 
@@ -21,8 +21,8 @@ FirstName LastName <email@domain.example>
 >> preparing your submission, other than the Pintos documentation, course
 >> text, lecture notes, and course staff.
 
-                    INDEXED AND EXTENSIBLE FILES
-                    ============================
+             INDEXED AND EXTENSIBLE FILES
+             ============================
 
 ---- DATA STRUCTURES ----
 
@@ -60,8 +60,8 @@ FirstName LastName <email@domain.example>
 >> structure, and what advantages and disadvantages does your
 >> structure have, compared to a multilevel index?
 
-                           SUBDIRECTORIES
-                           ==============
+                SUBDIRECTORIES
+                ==============
 
 ---- DATA STRUCTURES ----
 
@@ -74,9 +74,6 @@ FirstName LastName <email@domain.example>
 >> B2: Describe your code for traversing a user-specified path.  How
 >> do traversals of absolute and relative paths differ?
 
->> B3: Look over "pwd.c" in src/examples.  Briefly explain how it
->> determines the present working directory.
-
 ---- SYNCHRONIZATION ----
 
 >> B4: How do you prevent races on directory entries?  For example,
@@ -85,17 +82,17 @@ FirstName LastName <email@domain.example>
 >> create a file with the same name, and so on.
 
 >> B5: Does your implementation allow a directory to be removed if it
->> is in use as a process's current directory?  If so, what happens to
->> that process's future file system operations?  If not, how do you
->> prevent it?
+>> is open by a process or if it is in use as a process's current
+>> working directory?  If so, what happens to that process's future
+>> file system operations?  If not, how do you prevent it?
 
 ---- RATIONALE ----
 
 >> B6: Explain why you chose to represent the current directory of a
 >> process the way you did.
 
-                            BUFFER CACHE
-                            ============
+                 BUFFER CACHE
+                 ============
 
 ---- DATA STRUCTURES ----
 
@@ -126,8 +123,8 @@ FirstName LastName <email@domain.example>
 >> C7: Describe a file workload likely to benefit from buffer caching,
 >> and workloads likely to benefit from read-ahead and write-behind.
 
-                          SURVEY QUESTIONS
-                          ================
+               SURVEY QUESTIONS
+               ================
 
 Answering these questions is optional, but it will help us improve the
 course in future quarters.  Feel free to tell us anything you