subscribe cs-134-l in the body of the
message to listkeeper@hmc.edu.
For more information on mailing lists, see the
listkeeper
documentation.
My weekly schedule is posted on the Web
for all to see.
I am generally in my office every day except Friday. If the door is
open, please feel free to drop in with your questions. Even if I
happen to be busy, I'll at least know that you need to talk to me and
we can set up an appointment to talk. If you are on a computer, the
command finger @mallet will generally tell you whether
I'm logged in and have multiple active windows, which is a very good
sign that I'm in the office.
As a general rule, the talk utility is not a
good way to reach me, regardless of what machine you are trying to
reach me at. I usually keep my command windows closed and my bell
disabled, so I will never see the talk request.
On Fridays I do research. You can sometimes reach me by calling 310-825-7307, though you'll rarely get an answer between noon and 3 PM, when I'm in meetings. In general, if I'm available to answer the phone, I'm also available to answer questions. If you can't get me by phone, send e-mail.
Communication (client-server model, remote procedure call, and multicast), processes (threads, real-time, fault tolerance), clock synchronization, mutual exclusion, deadlocks, distributed file systems, semantics of file sharing, shared memory (consistency, object-based), case studies.
Prerequisites: Computer Science 110. 3 credit hours.
In this course, you should learn:
Homework assignments will generally be written, not programming. Many will be problems taken from the textbooks.
The exact number of homework assignments will be determined later. Assignments will be posted here and announced on the class mailing list.
Reading assignments are selected from both texts. You will probably find Singhal & Shivaratri significantly more difficult to digest than Tanenbaum, and should plan your time accordingly.
Each "current paper" will be discussed in class. You are expected to be familiar with the contents of the papers before the session begins.
To encourage keeping up with the reading and useful discussion, every student will be expected to come prepared with one meaningful question or observation regarding each paper that is scheduled to be discussed that day. You should also be prepared to answer random questions regarding the papers.
See the administrivia page for details of administrative matters:
You are responsible for being familiar with the contents of the administrivia page!
If you have questions that you prefer not to ask during class, or suggestions that you would rather have remain anonymous, there is now a class suggestion box on the Web. This interface will allows you to send e-mail to the instructor such that it appears to have also come from him, instead of from youself.
This page is maintained by Geoff Kuenning.