CS 503: Operating Systems
Spring 2008
|
-
Kihong Park, LWSN 1211, 494-7821, park@cs.purdue.edu
Office Hours:
- M 12:30-1:30pm, WF 1-2pm; or
by appointment
-
Jacques Thomas,
jthomas@cs.purdue.edu
Office hours:
| Tu: |
1:30-2:30 pm |
LWSN 3133 (in the conference room) |
| W: |
1:30-2:30 pm |
same |
| Th: |
1:30-2:30 pm |
same |
PSO: M 1:30 - 3:20 pm (HAAS 257)
PSOs:
Students are strongly encouraged to attend
PSO sessions. PSOs will commence the second week of class
along with the first assignment. If you
have a registration schedule conflict, please notify Dr. William Gorman.
Graduate standing in
Computer Science,
previous operating system class at the undergraduate level (CS 354 or
equivalent),
ability to read and understand a large non-trivial system written in C,
ability to program extensively in C, and command of system
development tools.
03
| Assignments |
50% |
Midterm
|
25% |
Final exam
|
25% |
We will use the XINU
operating system for the programming assignments. The XINU lab is
located in the Haas Building room HAAS 257.
Getting your CS account. Students can get
their CS account information on-line. Go to CS homepage, use the ITaP
login and password in the upper right-hand corner. This will take you
to a page where you agree to the access and usage policies, and then
get your
CS login and initial password. You also use the same site for doing
mid-semester reviews, evaluations, etc. If you have signed up but don't
have an account, please use the accounts@cs.purdue.edu alias.
For other account related questions, please contact Candace
Walters (clw@cs, LWSN 2116H).
Due Dates
All assignments are due on the dates and
times specified. Late assignments are not accepted.
It is the
student's responsibility to manage their time so that the
assignments
can be submitted before the deadline.
Academic Dishonesty
We wish to foster an open and collegial class
environment. At the same
time, we are vigorously opposed to academic dishonesty
because it seriously
detracts from the education of honest students. Because of this, we
have
the following standard policy on academic honesty, consistent with
Purdue
University's official policy.
- It is permissible to discuss a general
method of
solution with other students,
or to make use of reference materials in the library or online. If you
do this, you will be expected to clearly disclose with whom you
discussed
the method of solution, or to cite the references used. Failure to do
so
will be considered cheating or plagiarism. The use of "method of
solution"
means a general discussion of technique or algorithm, such as one would
reasonably expect to occur standing in front of a whiteboard, and
precludes
the detailed discussion of code or written assignments. Specifically,
looking at another student's code on his/her computer monitor is NOT
allowed.
- Unless otherwise explicitly specified,
all
written assignments or code
that is submitted is to be entirely the students own work. Using any
code
or copying any assignment from others is strictly prohibited without
advance
prior permission from the instructor. This includes the use of code
others
have submitted in the past.
- All students work is their own. Students
who
do share their work with others
are as responsible for academic dishonesty as the student
receiving
the material. Students are not to show work to other students, in the
class
or not. Students are responsible for the security of their work and
should
ensure that printed copies are not left in accessible places, and that
file/directory permissions are set to be unreadable
to others (e.g. use "chmod -R 700 *" from your home directory).
If you need assistance protecting your work, please contact
the TA or the instructor.
- Students who encourage others to cheat
or
plagiarize, or students who are
aware of plagiarism or cheating and do not report it are also
participating
in academically dishonest behavior.
- Be aware that we will use a software
tool
called MOSS (http://www.cs.berkeley.edu/~aiken/moss.html)
to check for copying among submitted assignments. Additionally, the
instructor
and TA will be inspecting all submitted material to ensure honesty.
Any case of
academic dishonesty will
be dealt with by a severe grade penalty in the overall class
grade
and referral to the office of the Dean of Students.
CS Ph.D. Qualifier:
This course is one of the courses for Qual I
of the CS Ph.D. program.
Additional questions will be given on the final exam for students
wishing to take the qualifier. The regular final plus the additional
questions will comprise the Qual I exam.
This course examines
operating system design concepts and their implementation in
the XINU operating system. The
topics to be covered
include: