CPSC 331: Operating Systems (Fall 2007)Lecture 3:00 - 3:55 (period 7) Mon/Wed/Fri, Room Lansing 301 (Class Schedule)Web: http://math.hws.edu/mcorliss/fall07/cs331/index.html |
|
Announcements
StaffInstructor: Marc Corliss (corliss at hws dot edu)Office hours: Mon/Wed 12:15-1:15, Thu 10-12, Fri 1:30-2:30. Course SummaryAn operating system such as Windows, Linux, or Mac OS X is a fundamental part of any computing system. It is responsible for managing all the running processes as well as allowing the processes to safely share system resources such as the hard drive and network. This course is a general introduction to the design and implementation of modern operating systems. Although this course will look generally at operating system design, it will also look in more detail at two specific operating systems: Linux and Microsoft Windows. The subjects to be covered include historical development of operating systems, concurrency, synchronization, scheduling, paging, virtual memory, input/output devices, files, and security.The prerequite for this course is CPSC 225 (intermediate programming). Students must have taken this course and received a grade of at least a C-. If that is not the case, the student should meet with the instructor before enrolling for the course. Textbook"Modern Operating Systems" (2nd Edition) by Andrew S. TanenbaumScheduleThe tentative class schedule is online. The schedule is split into several topics that usually make up one chapter of the textbook. The readings for each day should be done before that class. Projects and homeworks are due at the start of each class they are due. Exams (both the review and the actual test) and vacation days are indicated on the schedule.Course WorkProjects. There will be three to four large programming projects. The projects will require a significant amount of time, so students should start early. As for late projects, there are three "grace" days to use to hand in late projects with no additional loss in points. These "grace" days are per semester not per project, so if a student uses all three for one project, they will have no more "grace" days for any subsequent projects. Weekends count as "grace" days, so for example, if a project is due on Friday and is handed in on the following Monday, then all three "grace" days are used up. Once a student runs out of "grace" days, they will lose 10% of the grade of the project per day.Homeworks. In addition to the project their will be six to eight homeworks that will help make sure that students keep up with textbook reading. These are to be completed individually. Homeworks are not accepted late. Exams. There will be two midterm exams and a final exam. The midterm exams will be in-class, written (no programming on the computer), and closed book/notes. They are tentatively scheduled for ... The final exam will be cumulative, but will emphasize aspects of the material covered in the second half of the course. The final exam will be held on Tuesday, December 11th from 7pm to 10pm in Lansing 301 (our normal classroom). Note: the final exam date and time is scheduled by the registrar's office and will not be changed. Rescheduling or making up of exams will only be allowed for *compelling* circumstances. Arrangements must be made in advance for non-emergencies. Making up a missed exam will only be allowed with documentation from an appropriate person (dean, doctor, etc.). Attendance/Participation. Due to the small size of this class, attendance is essential. To get full credit for participation, students can miss, at most, two lectures, unexcused (try to let the instructor know in advance). If a student needs to miss more than two lectures, then they must have a *compelling* reason and they must notify the instructor ahead of time. Otherwise, the student will lose 10% of their attendance/particpation grade per day missed. GradingProjects: 30% (6-8% each)Written assignments: 25% (3-4% each) Midterm exams: 20% (10% each) Final exam: 15% Participation, attendance, etc.: 10% Academic IntegrityThe Principle of Academic Integrity (see the HWS Catalogue, p. 33) governs the work completed in this course. The following outlines specifically how this principle applies.Exams. All exams are to be completed solely by the student whose name is on the paper. Unless otherwise specified, these are closed book/notes, which includes any materials not provided as part of the exam. Homework. Homework assignments are to be completed solely by the student whose name is on the paper. Projects. The projects are also to be completed solely by the student submitting the project for credit. Students may not work with other students, including discussing ideas, offering debugging help, or looking at their programs. Students may consult the book, their notes, any course materials provided in class or on the course website, and reference books found in the lab. Use of other materials (including websites) is not allowed. It is never acceptable to be in possession of another student's program, either hardcopy or electronic. Each program submitted for credit will be checked by a plaigarism detector called MOSS (http://theory.stanford.edu/~aiken/moss/) to determine if it was copied. MOSS is highly accurate at detecting plagiarized software (changing a few variable names, comments, etc., will not help). In addition, any student that submits a suspicious project will have to explain their code to the instructor. If they are unable to effectively explain the code, then they will not receive credit for the assignment (and the case may be taken to the committee on standards). Summary. The moral of the story is students should not cheat in this course. For each case of cheating, the student will receive a 0 on the assignment, and the case will be pursued with the HWS committee on standards. It is better to submit an incomplete solution rather than submit a plagiarized solution. Center for Teaching and LearningHobart and William Smith Colleges encourages students to seek the academic collaboration and resources that will enable them to demonstrate their best work. Students who would like to enhance their learning and/or academic performance should contact the CTL at ext. 3351 or visit our website.If you are a student with a disability for which you may need accommodations, you must register with Disability Services at the CTL and provide documentation of the disability. Services and accommodations will not be provided until this process is complete. Contact the Coordinator of Disability Services, David Silver (silver at hws dot edu) ext. 3140 for an appointment. Additional information is available at: http://www.hws.edu/academics/enrichment/ctl/disability.asp. Resources |