Project 1: Warm-up Project

Important Dates

Questions about the project? Send them to 537-help@cs.wisc.edu .

Due: Monday, 9/19, by 9pm.

Overview

There are two parts to this project:

  • Sorting: to be done on the mumble lab, so you can learn more about programming in C on a typical UNIX-based platform (Linux)
  • Kernel Intro: to be done in our xv6 hacking environment, so you can learn more about what actually goes on in a real kernel.

Click on the above links to learn more about what you should do. READ EACH CAREFULLY!

Notes

Before beginning: Read this tutorial. It has some useful tips for programming in the C environment.

This project, like all others this semester, can be done with a single partner. Copying code (from other groups) is considered cheating. Read this for more info on what is OK and what is not!

Handing It In

For the C/Linux part of this project (sorting), you should turn in one file, called fastsort.c . We will compile it in the following way:

shell% gcc -O -Wall -o fastsort fastsort.c
so make sure it compiles in such a manner. You should copy this file into your handin directory into the subdirectory called linux . If you have a partner, only put the code in ONE of your directories.

The handin directory is ~cs537-1/handin/login/p1 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/p1 . Copying of these files is accomplished with the cp program, as follows:

shell% cp fastsort.c ~cs537-1/handin/remzi/p1/linux/

For the xv6 part of the project, copy all of your source files (but not .o files, please, or binaries!) into the xv6/ subdirectory of your p1 directory. A simple way to do this is to copy everything into the destination directory directory, then type make to make sure it builds, and then type make clean to remove unneeded files.

Finally, into your p1 directory, please make a README file. In there, describe what you did a little bit. The most important bit, at the top, however, should be the authorship of the project, particularly if you had a partner. Include both partner's names and CS logins to receive credit.