CS 4348/5348 Operating Systems
NEWS
General Information about the Exams
- All Exams will be on elearning. Students need to take the exams on
their laptops in person in class. No remote exams are allowed.
- During exam time, students shall not use any other electronic devices
besides the device for taking the exam. Also, students shall only view
the exam questions during the exam.
Openning any window other than the exam questions or using any other
electronic devices will be considered as cheating.
- There shall be no discussion during the exam. Any issues should be
raised to the proctor instead of among students. Any discussion between
students will be considered as cheating.
- Cheating during the exams will result in an F grade, irrespect of your
role in the event.
- A piece of cheat sheet and a piece of scratch paper are allowed.
- Food and drinks are allowed during the exam.
- Since the exam duration is not very long, breaks for restrooms, etc.
are strongly discouraged (exceptions can be made based on needs).
Policies related to Homework Assignments
- There is no late due for homework assignments. You have to complete
your homework before 11:59pm of the due date.
- Plagiarism is strictly prohibited for homework assignments. If you are
caught for plagiarism, you will get an F grade for the course.
Policies related to Programming Projects
- All project tests will be performed on CS Linux servers.
You can develop your code on any computer, but have to test your code
on Department Linux systems.
- Submission and grading related
- All projects are due at 11:59pm of the given due date.
You are given a 3-day late due period with a 5 points (out of 100)
penalty. After 3 days, we will not accept any submission, unless
there are critical circumstances, such as medical conditions (with proof).
- Projects that do not compile or do not work even partially
will not get any partial credits.
- You have to follow the file naming and input specifications exactly.
TA will run your programs the same way as specified in the handout.
If your code does not work by such testing, you will not get any credit.
- If you do have some reason and have to deviate from the spec,
you have to specify how to run your code and what to expect
in the "readme" file. Of course, if you do deviate from the spec without
a justifiable reason (determined by TA), you will lose some points.
- If your project does work, but has failed TA's test, you may
discuss with TA to see what to do. If it is because that you do not
follow the spec and do not specify it in the readme file, then
even if your code works perfectly, you will still lose points.
- Some policies about helping with projects:
- Some important questions will be answered in the Q&A file (below).
- We will not answer any question about the project when it is
within 3 days of the project due date. Please start early to avoid
delays due to unexpected problems.
- As a CS student, debugging is a skill that you need to develop.
Go through the program logic carefully and print out the results
after each major step (best is to use a debugger to do this).
Please do not seek for help in debugging your program logic.
Do it by yourself. I have instructed TA not to debug for students.
- You can get help if you do not understand some compilation errors
or if you are sure a system call is giving you problem and do
not know how to make it work correctly.
- Plagiarism
- No discussions among students are allowed for project assignments.
Questions regarding assignments can be discussed with TA or the instructor.
- At the end of the semester, we will conduct
plagiarism detection on all projects using AI based software.
Students who are involved in plagiarism will get an F grade
for the course.
- If student x copied the answer from student y, both x and y will get
an F grade, irrespective of their roles in the plagiarism event.
So, never show your code to anyone.
Web resources that may be helpful for the projects