Project 2: Processes and Scheduling
Important Dates And Notes
Questions about the project? Send them to
P2A :Fri 10/03 by 11:59 pm.
P2B: Sat 10/11 by 11:59 pm.
You are allowed to have ONE partner for this project. Copying code
(from other groups) is considered cheating.
There are two parts to this project:
- Shell: to be done on the mumble lab, so you can
learn more about programming in C on a typical UNIX-based platform (Linux)
- Scheduling: to be done in our xv6 OS hacking
Click on the above links to learn more about what you should do. READ EACH CAREFULLY!
Handing It In
The handin directory is
your login and XXX is the section you are in.
For the C/Linux part of this project (the shell), you should turn in one
mysh.c. 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. You should also include a simple
makefile, so we can simply type
make and build your testable
binary. The binary should be named
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 p2
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
make clean to remove unneeded files.
Finally, into your p2 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. It is
enough if only one of the partners submit their code.