Keith J. O'Hara

teaching

CPSC 45

Operating Systems (F2025)

overview | logistics | schedule | edstem | assignments | resources

Class: Tue & Thu 9:55-11:10am (Martin 327)
Lab: Mon 1:05-2:35pm (Martin 213)
Office Hours: Tue 11:15am-12:15pm & Thu 1:15-2:15pm and by appointment (Martin 234)

Textbooks

• Operating Systems: Three Easy Pieces. Remzi H. Arpaci-Dusseau and Andrea C. Arpaci-Dusseau (University of Wisconsin-Madison). 2023.
• xv6: a simple, Unix-like teaching operating system. Russ Cox, Frans Kaashoek, and Robert Morris. August 2024.
• The Linux Programming Interface: A Linux and UNIX System Programming Handbook by Michael Kerrisk. No Starch Press. 2010.
• Bite Size Command Line, Linux and Bash by Julia Evans. Computer Wizard Industries. 2018.

Grade Breakdown

• Labs (40%): Weekly programming assignments
• Quizzes (40%): Five in-class pencil-and-paper quizzes
• Participation (20%): Discussion and homework (every class)

Policies

• Participate. There will be myriad opportunities: in class, lab, google docs, github, dropbox paper, excalidraw, office hours, edstem.
• When reading, studying, and listening, be active by taking notes and asking questions.
• Visit the professor's drop-in office hours.
• Attend class & be on time (whenever possible given COVID reality).
• Make sure to have read the required reading BEFORE class.
• Start all the assignments early.
• Check EdStem & this class website.
• Be respectful of your fellow classmates; my rule of thumb for judging whether a response is worthwhile: Is it Nice? Is it True? Is it Necessary? Pick at least two.
• Adhere to the Code of Ethics and Professional Conduct for the Association for Computing Machinery.
• Cooperate carefully and thoughtfully:
  • Work within your pair, and visit drop-in hours, before seeking help beyond.
  • Credit work, including all sources you used from the web, other books, etc.
  • Sharing ideas is encouraged, but blatantly copying work without attribution will be treated as scholastic dishonesty and receive no credit.
  • Be prepared to demonstrate the theory of your program (Peter Naur).
  • Keep your work backed-up and private.