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

What should NOT be submitted

General Guidelines

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

    ...