General Information

Course description

This course teaches how interals of modern operating systems are working with hardware/software stack. In the course, we will learn fundamental concepts of operating systems by building an operating system by our own hand. In particular, Labs are based on JOS, an educational OS project, and will build it starting from booting (lab1), to virtual memory (lab2), to process (lab3), and finally to multi-tasking (lab4). We will also covers concurrency issues in systems by learning on how to implement locks and other synchronization mechanisms and how to resolve deadlock issues.

This course borrows lots of materials from MIT’s 6.828 (https://pdos.csail.mit.edu/6.828/2018/overview.html), the original course that developed JOS, and also from CS3210 of the Georgia Institute of Technology (https://tc.gts3.org/cs3210/2016/spring/index.html) and CSE 451 of the University of Washington (https://courses.cs.washington.edu/courses/cse451/18au/).

Prerequisite

  • Computer Architecture and Assembly Language (CS 271 at OSU) or ECE 375
  • Operating Systems I (CS 344 at OSU)
  • Linux System Administration (CS 312 at OSU, not required but recommended)

Class meetings

Lecture videos will be posted online on YouTube, and the links will be posted at Canvas.

Lab meetings

Lab tutorial videos will be posted online on YouTube, and the links will be posted at Canvas.

Office hours and recitation

Yeongjin will have office hours from 18:00 to 19:30 on Wed, every week (this could be changed at the instructor’s discretion), on the Discord Server Course Discord Server.

TA office hours will be posted here accordingly.

Grading policy

  • 70% JOS Lab (10%, 15%, 20% and 25% per each of lab1, lab2, lab3 and lab4, respectively).
  • 30% Quizzes (Quiz1, Quiz2, Quiz3)
  • Some extra credits in JOS Labs (1% or 2% each)

Online Discussion

Online discussion is strongly encouraged and it will help you a lot in solving lab problems.

Please join Piazza and post your questions, ideas and thoughts.

Please also join Discord to have a more faster feedback on your questions; we will try to reply to your questions ASAP, but in the worst case, please allow us to reply within a day.

Policy

CS 444/544 has strict due dates for lab assignments but allows late submissions with penalty. In this regard, 100% of points from your lab assignment submission will be given if you submit the assignment before the due date. However, once you miss the due date, you will get 75% of points from 1-week late submission, and you will get 50% of points from more than 1-week delayed late assignment submission. All assignments must be submitted before 12/11/2020 11:59pm (PST) to get the point with penalty.

Assignment submission after that day (12/11) will get 0 points.

Regarding plagiarism, We strictly follow the OSU policy (read OSU’s Code of Student Conduct).

If the instructor detects plagiarism in assignment submissions such as copied code from web, other student’s submission, etc., then the assignment will be given to have 0 pts or the student who submitted the assignment will get F from the course.

Please do not copy other’s code. Write your code for the assignments.

Important

Cheating vs. collaboration

Collaboration is a very good thing. On the other hand, cheating is considered a very serious offense and is vigorously prosecuted. Vigorous prosecution requires that you be advised of the cheating policy of the course before the offending act.

For this semester, the policy is simple: don’t cheat:
  • Never share code or text on the project.
  • Never use someone else’s code or text in your solutions.
  • Never consult potential solutions on the Internet.
On the other hand, for this class, you are strongly encouraged to:
  • Share ideas.
  • Explain your code to someone to see if they know why it doesn’t work.
  • Help someone else debug if they’ve run into a wall.

If you obtain help of any kind, always write the name(s) of your sources.

(ref. http://courses.cs.washington.edu/courses/cse451/15au/)