6.824 - Spring 2005

Lab Information

Lab assignments

Lab 1 - Lock Server
Lab 2 - Basic File Server
Lab 3 - File Server: Reading, Writing and Sharing Files
Lab 4 - MKDIR, REMOVE, and Locking
Lab 5 - Cache Consistency

Class Machines

The class machines are:

anguish.lcs.mit.edu
suffering.lcs.mit.edu
blood.lcs.mit.edu

anguish is the fastest. We have multiple machines so that you can test your networking code on multiple hosts.

Getting an account

To obtain an account on the class machines register on the 6.824 lab registration page.

You might find this page useful for basic information about logging into Unix and compiling programs.

Changing your password

Your initial password will be mailed to you when your account is created. Please change your password as soon as possible. If you do not change your password, we will assume you are not taking the class and will deactivate your account. Change your password with the passwd command on anguish.lcs.mit.edu. Passwords are copied automatically from anguish to the other machines every few minutes.

Aids for working on labs

There are a number of resources available to help you with the lab portion of this course:

The SFS source code: All the labs use the RPC, asynchronous I/O, and utility libraries that come with the SFS source code. You may need to browse the SFS source to figure out how it works. You may also find the SFS and file system tookit papers useful. It's available on the class machines in /u/6.824/sfs-0.7.2 or at the SFS project page.
FreeBSD Architecture: You can find a good summary of how FreeBSD works in an appendix to the Operating Systems Concepts book by Silberschatz, Galvin, and Gagne. (FreeBSD is the UNIX variant running on the 6.824 machines.)
UNIX network programming: W. Richard Stevens' books ``UNIX Network Programming'' Volume 1 and 2 are classic references for network programming. If you are struggling with the sockets interface it could be a helpful purchase. See the suggested books list for other helpful references.
core files: When/if your program crashes it will leave a core file behind (named something.core). Examining core files with gdb is a valuable way to learn what went wrong. To get started with gdb type: "gdb program program.core" and then type the gdb command "bt". GDB will return a trace showing exactly where the program crashed. GDB offers many more features. Check out the GDB manual for full documentation.

Questions or comments regarding 6.824? Send e-mail to 6.824-staff@pdos.lcs.mit.edu.

Top // 6.824 home //