Structure
Instructor: Alex
C. Snoeren, snoeren at cs.ucsd.edu.
Office hours: TR 2:00-3:00pm in EBU3B 3114, or by appointment.
Discussion/HW TA: Vikram Mavalankar, vmavalan at cs.ucsd.edu
Office hours: W 1:00-2:00pm.
Projects TA: John Fisher-Ogden, johnfish at cs.ucsd.edu
Office hours: EBU3B 3242 by appointment.
Lab hours: EBU3B B250 TU 12:00-12:30pm, W 1:15-3:15pm, TR 2:00-3:30pm
Lab: EBU3B B230
Mailing List: cse120@cs.ucsd.edu
Issues relating to the homework assignments will be handled largely in
the discussion section. The TA will likely be far more accommodating
to questions from those students who regularly attend discussion
sections. Project issues will generally be handled at the beginning
of lecture, during specially announced 'project' discussion sections,
and outside of class by the project TA. Please direct questions to
the appropriate TA; while they both are willing and able to help, they
have other responsibilities outside of this class.
Textbook
|
The required textbook for this course is Operating
Systems Concepts, by Silbershatz, Galvin, and Gagne. 7th Edition,
published by Wiley and Sons. ISBN 0-471-69466-5. Earlier editions
are also acceptable, although the homework assignments will use
problem numbers from the 7th edition. Readings will be assigned as
background material for the lectures, and are fair game for the
exams. Readings are not a substitute for lectures. You are
responsible for all material covered in lecture, whether or not it
appeared in any assigned readings.
|
Grading
This course will have roughly bi-weekly homework assignments taken
from the textbook, three or four programming assignments, a midterm,
and a final. Discussion sections will be held weekly to review the
lecture material and answer questions about the readings, homeworks,
and projects. Grade for this class will be based on:
- Homework 20%
- Programming projects 30%
- Midterm 20%
- Final 30%
No late assignments will be accepted. Exceptions for
UCSD-sponsored athletic or other extra-curricular activities,
documented medical emergencies, death of an immediate family member,
or other such life-altering situations must be requested from the
instructor as soon as possible.
Collaboration policy
All homework assignments must be completed
individually; projects must be completed by you and your fellow group members only. You (or your group members, in
the case of the projects) must write all solutions and code that you
submit, excepting any code that was provided to you as part of the
assignment. You are encouraged to discuss the assignments with
others, but you may not copy answers or code from another student or
make your code available to others. Exams will be individual effort
and closed book.
Each student is responsible for knowing and abiding by UCSD's policies on
Academic Dishonesty and on Student Conduct and the Jacobs
School Student Honor Code. Any student violating UCSD's Academic
Dishonesty or UCSD's Student Conduct policies will earn an 'F' in the
course and will be reported to their college Dean for administrative
processing. Committing acts that violate Student Conduct policies
that result in course disruption are cause for suspension or dismissal
from UCSD.
Charles Elkan's academic
honesty guidelines developed for CSE 130 explicitly spell out many
of your reponsibilities, and must be adhered to. If you have any
questions, please ask.
Don't cheat. It's not worth it.
Useful Books
The following books may help provide an alternative view on the
material. These are listed simply to suggest supplemental resources
should you desire additional reading. We will not refer to them
during the term. None of them are required.
- Operating Systems: A Modern Perspective, Nutt. Addison-Wesley.
- Modern Operating Systems, Tanenbaum. Prentice Hall.
- The Design and Implementation of the 4.4 BSD Operating
System, McKusick, Bostic, Karels, and Quarterman. Addison-Wesley.
