Questions?
Send questions using piazza or use office hours. If the question is about your code, copy all of of your code into your handin directory (details below) and include your login in your email (you are free to modify the contents of your handin directory prior to the due date). Do not put code snippets into piazza (unless they are very short). Also include all other relevant information, such as cutting and pasting what you typed and the results from the screen. In general, the more information you give, the more we can help.
Overview
The project description is found here. Please read this carefully in order to understand exactly what to do.
This project is to be done on the lab machines (listed here ), so you can learn more about programming in C on a typical UNIX-based platform (Linux).
Notes
Before beginning: If you don't remember much about the Unix/C environment, read this tutorial. It has some useful tips for programming.
This project should be done alone. Copying code (from others) is considered cheating. Read this for more info on what is OK and what is not. Please help us all have a good semester by not doing this.
Contest
There will be a contest for the fastest KV store. It will be announced soon (and the due date for the contest will be later than the turned-in version for credit). Whoever writes the code that is the the fastest KV will win fame, glory, and an amazing 537 prize! But mostly fame.
Handing It In
You should turn in one file, kv.c , which we will compile and test.
The handin directory is ~cs537-1/handin/login/p1a where login is your login. For example, Remzi's login is remzi , and thus he would copy his beautiful code into ~cs537-1/handin/remzi/p1a . Copying of these files is accomplished with the cp program, as follows:
prompt> cp kv.c ~cs537-1/handin/remzi/p1a/
When done, type ls ~cs537-1/handin/remzi/p1a to see that all the files are in place correctly.
Finally, in your p1a directory, please include a README file. In there, describe what you did a little bit. There is no particular requirement for the length of the README; just get in the habit of writing a little bit about what you did, so that another human could understand it.
