Syllabus for CSC421 Computer Operating Systems.
This is a course in computer operating systems. The goals of the course are,
- to present
the most common mechanisms used by operating systems to implement useful behavior, and
- to understand the trade-offs between mechanisms given available technologies
and human demands.
In addition, the student will gain experience working with "real code",
that is, the code of the linux operating system kernel, as well as developer tools for
working with code in a collaborative environment.
- Join the class slack channel csc-courses.slack.com, #csc421-241.
- Required reading:
- Suggested reading:
- The Cathedral and the Bazaar, by Eric Raymond.
- Mythical Man-Month, possibly the most influential software engineering/operating systems book ever.
- Operating Systems: Principles and Practice, by Anderson and Dahlin.
- The Design and Implementation of the
FreeBSD Operating System, by McKusick and Neville-Neil
- Windows
Internals, by Russinovich, Solomon and Ionescu
- Mac OS X Internals: A Systems Approach, by Amit Singh
- Operating Systems: Three Easy Pieces, by
Remzi H. Arpaci-Dusseau and Andrea C Arpaci-Dusseau.
- Linux
Kernel Development (3rd Edition), by Love
- Operating System Concepts, Abraham and Silberschatz
(also known as "The Dragon Book", because of the cover)
- Lion's book. Source code for Sixth Edition Unix.
- What you will do:
- Quizzes and presentations: There might be quizzes on particular topics, or
students might present from readings or from their own code (code stand-ups).
- Exams: a midterm and final.
- Projects:
- A series projects, assigned from a Monday to the second following Monday. However, this
might vary according to pace and vacation schedule.
- Project grading: Projects are generally scored on a 0 to 5 scale, with 5 being reserved for excellent projects.
Short or longer projects have their total points adjusted.
- Project grades depend on completeness, correctness, and originality and sincerity of effort.
- Projects must make proper use of git, Makefiles, and proper folder and file names.
- Grading:
- Lateness: Three days grace automatic on projects. Over that, one point off and an additional one point
for each week late, up to some reserve number of points.
- No lateness for quizzes or presentations.
- No work accepted once reading days end.
- Class grading: After normalizations, 20% quiz and presentations, 20% each midterm and final, 40% projects.
- Who will help you:
- Our TA is Satyarth Arora, sxa1654@miami.edu; Tuesday 3:30–6:00 and Thursday 4.00–5.30 PM.
-
Honor Code:
- Class participants read and accept the University Honor Code,
available from the Dean of Students.
- Work resulting from an integrity violation will not be graded. A no-grade arising
in this way can be numerically distinct from a zero.