-You'll need to consider this when deciding your @struct{inode}
-organization.
-@end enumerate
-
-@node Problem 4-3 Subdirectory FAQ
-@subsection Problem 4-3: Subdirectory FAQ
-
-@enumerate 1
-@item
-@b{What's the answer to the question in the spec about why
-@command{ls} and @command{mkdir} are user programs, while @command{cd}
-is a shell command?}
-
-Each process maintains its own current working directory, so it's much
-easier to change the current working directory of the shell process if
-@command{cd} is implemented as a shell command rather than as another
-user process. In fact, Unix-like systems don't provide any way for
-one process to change another process's current working directory.
-
-@item
-@b{When the spec states that directories should be able to grow beyond
-ten files, does this mean that there can still be a set maximum number
-of files per directory that is greater than ten, or should directories
-now support unlimited growth (bounded by the maximum supported file
-size)?}
-
-We're looking for directories that can support arbitrarily large
-numbers of files. Now that directories can grow, we want you to
-remove the concept of a preset maximum file limit.
-
-@item
-@b{When should the @code{lsdir} system call return?}
-
-The @code{lsdir} system call should not return until after the
-directory has been printed. Here's a code fragment, and the desired
-output:
-
-@example
-printf ("Start of directory\n");
-lsdir ();
-printf ("End of directory\n");
-@end example
-
-This code should create the following output:
-
-@example
-Start of directory
-... directory contents ...
-End of directory
-@end example
-
-@item
-@b{Do we have to implement both absolute and relative pathnames?}
-
-Yes. Implementing @file{.} and @file{..} is extra credit, though.
-
-@item
-@b{Should @func{remove} also be able to remove directories?}
-
-Yes. The @code{remove} system call should handle removal of both
-regular files and directories. You may assume that directories can
-only be deleted if they are empty, as in Unix.
-@end enumerate
-
-@node Problem 4-4 Buffer Cache FAQ
-@subsection Problem 4-4: Buffer Cache FAQ
-
-@enumerate 1
-@item
-@b{We're limited to a 64-block cache, but can we also keep an
-@struct{inode_disk} inside @struct{inode}, the way the provided code
-does?}
+You'll need to consider this when deciding your inode organization.
+@end table
+
+@node Subdirectories FAQ
+@subsection Subdirectories FAQ
+
+@table @b
+@item Why is @command{cd} a shell command?
+
+The current directory of each process is independent. A @command{cd}
+program could change its own current directory, but that would have no
+effect on the shell. In fact, Unix-like systems don't provide any way
+for one process to change another process's current working directory.
+@end table
+
+@node Buffer Cache FAQ
+@subsection Buffer Cache FAQ
+
+@table @b
+@item Can we keep a @struct{inode_disk} inside @struct{inode}?