X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=doc%2Ffilesys.tmpl;h=db792bfed2af176e65a70afc88264a17444f3740;hb=3edcfedb8e62970f3293fa676b6691f8658c3c11;hp=2bb2d1bc20d484f448eaf19f2401aa6f7aa86f7a;hpb=2b4cbbd50d1752a6b26341ba78e7e285f7b947f3;p=pintos-anon diff --git a/doc/filesys.tmpl b/doc/filesys.tmpl index 2bb2d1b..db792bf 100644 --- a/doc/filesys.tmpl +++ b/doc/filesys.tmpl @@ -31,7 +31,7 @@ FirstName LastName >> enumeration. Identify the purpose of each in 25 words or less. >> A2: What is the maximum size of a file supported by your inode -structure? +>> structure? Show your work. ---- SYNCHRONIZATION ---- @@ -74,9 +74,6 @@ structure? >> 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,9 +82,9 @@ structure? >> 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 ----