Assignment Submission Guidelines
All materials submitted for grading must conform to the following guidelines,
failure to do so may result in loss of credit.
Academic Integrity
All programs submitted must be your own work, and you are expected to develop
your programs independently. You may receive as much help as you wish on the use of the operating
system, text editors, debuggers, file transfer protocols and so on. You may consult with other members
of the class about interpreting the assignment, and you may get help in finding bugs, but not fixing
bugs, but you are not allowed to look at or copy another person's code or discuss design decisions with
others, and you cannot show your code to others. Students found to be in violation of these guidelines
will fail the project, and will be reported to the dean.
What should be submitted
- A Readme file describing the contents of the directory.
- A Makefile with rules which will perform the following tasks:
- Compile all code.
- Clean up the directory, removing core files and object files.
- Any other required tasks.
- All source code required for the problem.
- Any test files or configuration files required for the problem.
- Documentation explaining the solution to the problem or answer to the
question.
What should NOT be submitted
- Object files. These can be recreated from the source code.
- Core files. These should NOT be recreate-able from the source code.
General Guidelines
- Your work should be submitted as a shar file. This file should expand
to a directory, named after your username, containing the answer to the
question, as described above.
- Unless otherwise noted in the assignment notice, your answer must
compile/run/work on one of the departmental machines. If your solution
is platform dependent, please note this in the Readme file.
- It is the responsibility of the student to submit valid, readable
shar files to the correct address. Corrupt or incomplete files are
unacceptable and may be judged incorrect.
How to create an acceptable shar file
The following example is how a user with username fred would submit homework 4.
In the directory where you developed the code make a subdirectory:
mkdir fred
Move all relevant files to the new subdirectory:
mv Readme Makefile foo.c bar.c foo.h fred
Create a sharfile of the subdirectory:
shar fred > homework4.shar
If the shar file is larger than 1000 lines, split it into smaller
files - this should not be necessary for this course
split homework4.shar
mail the sharfile(s) to me and a copy to the grader,
Seung-Su Yang, with mail subject "OS homework n", or "OS project n",
where n is the written homework or programming project number.
mutt -s "OS homework 4" farrell@cs.kent.edu syang@cs.kent.edu < homework4.shar
or
mutt -s "OS homework 4 part 1" farrell@cs.kent.edu syang@cs.kent.edu < xaa
mutt -s "OS homework 4 part 2 "farrell@cs.kent.edu syang@cs.kent.edu < xab
...