General Information

Catalog description // Communication // Grading // Labs // Text books // Homework // Collaboration // Class meetings // Staff // Office hours Miscellaneous

HMC catalog description

Prereq.: CS 105

Design and implementation of operating systems, including processes, memory management, synchronization, scheduling, protection, filesystems, and I/O. These concepts are used to illustrate wider concepts in the design of other large software systems, including simplicity; efficiency; event-driven programming; abstraction design; client-server architecture; mechanism vs. policy; orthogonality; naming and binding; static vs. dynamic, space vs. time, and other tradeoffs; optimization; caching; and managing large codebases. Group projects provide experience in working with and extending a real operating system.

Communication

We will distribute assignments on the course web site, and make all announcements through piazza. The course web site has the schedule for the term.

Grading policy

Grades in CS 134 will be based on:

You must submit all labs in order to pass the class. The course is not graded on a curve. The percentage score will be used to determine a final letter grade as follows:
Percentage score Grade
≥90% A
≥80%-<90% B
≥65%-<80% C
≥50%-<65% D
<50% F
Pluses and minuses will be attached to the letter grades as the instructor deems appropriate.

Labs

To turn in each lab, run make handin in your lab directory. The handin must be received by 11:59pm on the day that the lab is due. You can turn in as many times as you like before the deadline. Lab results will be returned in GitHub.

You have a total of 72 late hours for the semester. Each hour late in excess of 72 hours will penalize your total lab grade by 1%. We calculate your final lab grade using the configuration of late hours and lab submissions which results in the highest grade. These late hours are intended for cases where you fall behind due to illness, job interviews, HMC athletic events, deadlines in other classes, etc. For extensions under extenuating circumstances (e.g., you are sick for a week), we require a letter from one of the student deans.

Homework

The homeworks are intended to make you think about the lecture topic and/or get your hands dirty. Programming homework and paper questions are due before the start of lecture (by 1pm) on the specified due dates. I do not grade your answers for correctness, but merely check-off that you put reasonable effort into them.

No late homework will be accepted, but I'll drop the lowest homework score.

Textbooks

CS 134 relies on the following three books:

In addition, the class relies on tons of reference material on x86 instructions, PC hardware specs, etc. All that material is available on the reference page.

Collaboration

  1. All students enrolled in this course are bound by the HMC Honor Code. More information on the HMC Honor Code can be found in the HMC Student Handbook.
  2. It is your responsibility to determine whether your actions adhere to the HMC Honor Code. If this document does not clarify the legitimacy of a particular action, you should contact the course instructor and request clarification.
  3. Work you submit for individual assignments should be your own, and you should complete all assignments based on your own understanding of the underlying material. If you work with, or receive help from, another individual on an assignment, provide a written acknowledgement in complete sentences that includes the person’s name and the nature of the help.
  4. When you submit a group assignment, the group should complete all assignments based on your group’s understanding of the underlying material. If your group works with, or receive help from another individual or group on an assignment, provide a written acknowledgement in complete sentences that includes the person’s name and the nature of the help. The submitted assignment should be based on joint work among all members of the group, and all group members should understand the entire assignment and submittal. If one or more members of the group did not participate in an assignment, provide an explanatory statement as part of the submission..
  5. This document is not meant to be an exhaustive list of every possible Honor Code violation. Infractions not explicitly mentioned here may still violate the Honor Code.
  6. Boundaries of Collaboration: verbal collaboration with other students on individual assignments is encouraged. However, all submitted written work should be written by yourself individually, and not a collaborative effort or copied from a common source (e.g., a chalkboard).
  7. Use of Web Resources: the use of Internet resources to aid in course work is acceptable, as long it does not substitute for an understanding of the course material. Plagiarism and direct copying from online (or any other) sources is strictly prohibited. However, you may not look at source code for labs or homework from the internet or from other students.
  8. Use of Your Own Work from Previous Semesters: if you have previously attempted this course, you may refer to your work from previous semesters, but may not resubmit it as this semester’s coursework.
  9. Use of Other Course Resources from Previous Semesters: You may not reference assignments of this course from previous semesters or tests from previous semesters (other than those explicitly provided by the instructor as study aids).
  10. Retention of Course Resources: assignments and exams from this course may not be committed to dorm repositories or otherwise used to help future students.

    Do not post your lab or homework solutions on publicly accessible web sites (such as a public repository on GitHub).

    Class meetings

    Lectures will be held on Monday and Wednesday from 1:15pm to 2:30pm in Shanahan 3425.

    A lab is also scheduled for this class from 7pm to 9pm in Beckman B105. Although it is not required to attend this lab, it is highly encouraged. The instructor will be present during lab hours, available to help with both lab and homework.

    Staff

    Lecturer
    Neil Rhodes

    Grutor
    Mars Park

    Piazza
    We'll use Piazza for questions. Use private posts to me only for specific code examples or personal issues—instead, prefer public posts so everyone can share in the question and answer, and so that other students can answer as well.

    Grutor hours

    Wednesday: 7-10 (Beckman B105)

    Instructor office hours

    Monday: 4-6 (Beckman B105) Wednesday: 11:30-12:30 (Olin 1255) Wednesday: 2:30-3:30 (Cafe) I'll spend my office hours (except as noted) in the computer lab; if you need to meet with me privately, let me know, and we'll move to my office (Olin 1255).
    Appointments with the instructor outside of the listed office hours can be setup via email.

    If you need accommodations for a documented disability, please talk to me or contact Brandon Ice, the HMC Student Accommodation Advisor (bice@hmc.edu). You will find information about disability resources on the college website: https://www.hmc.edu/ability. Students from the other Claremont Colleges should contact their home college’;s disability officer. If I learn of a potential violation of the college’s gender-based misconduct policy (see https://www.hmc.edu/tix), I am required to report it to Leslie Hughes, the HMC Title IX Coordinator. If you want to speak to someone confidentially, the following resources are available on and off campus: the EmPOWER Center (909-607-2689), the Monsour Counseling Center (909-621-8202), and the McAlister Chaplains (909-621-8685).

    Accessibility

    HMC https://www.hmc.edu/website-accessibility/
    This is derivative work based on MIT 6.828 used under Creative Commons License.

    Creative Commons License Top // CS 134 home // Last updated Wed Feb 27 07:42:59 PST 2019