CS4411 Introduction to Operating Systems
Course Information Page
Fall 2010

Course Instructor		Dr. C.-K. Shene
Office		Rekhi 305
Class Meeting		Monday, Wednesday, Friday 16:05 - 16:55
Classroom		Fisher 328
Office Hour		Monday, Tuesday and Thursday 15:30 - 16:00
Phone		(906) 487-3392
e-mail		shene@mtu.edu

Click here to see the most recent announcements (December 11, 2010)
Click here to see the most recent ThreadMentor FAQ (October 1, 2006)
Click here for the most recent grade posting (December 19, 2010)

Happy Holidays

Some Important Advises

This course will use C and C++ exclusively. Since we will not cover C/C++ in this course, you should get a good reference of C/C++ in hand.

Always start doing your programming assignment EARLY. Waiting until the last few hours is definitely not a wise move, because there could be too many people running their programs at the same time making system response time extremely slow. Moreover, machines may crash causing extra delay. Normally, I do not grant any extension if your home machine, your phone line or the department machines crash in the last minutes. Always start early.

Multithreaded programming requires a careful planning, which may need a mindset that is different from that of sequential programming you learned in previous courses. When you receive a programming assignment, do not sit in front of a workstation and start typing your program immediately. This trial-and-error approach, in general, DOES NOT work and may require longer time to finish your assignment. The best way of doing multithreaded programming assignments is to think carefully with a pencil and a piece of paper before touching a computer keyboard.

Since the behavior of a multithreaded program is dynamic, which means it acts differently from time to time, you should try to reason about the correctness of your program. In general, just running for one or two test cases is not sufficient. Your grader will read your program to find possible errors. When writing sequential programs, the same bug appears at the same place every time you run the same program. However, bugs of a multithreaded program (e.g., race conditions and deadlocks) may not appear every time. As a result, you may have an incorrect program even though you may have had hundreds correct test output.

Due to security reasons, starting with Fall of 2008, you will not receive submission confirmation e-mails. As a result, you should use the interactive version of submit and ensure all required files are submitted properly. If you choose to use the command line version of submit, you should use the recover command to verify your submission. More information will be available later in this semester.
After submitting your assignment, DO NOT modify your files so that the system administrator can retrieve your files in case your submission did not go through successfully.

Always read the assigned materials listed in the weekly reading lists and do the problems. Weekly reading lists are available near the bottom of this page.

Textbook

Abraham Silberschatz, Peter Bear Galvin, Greg Gagne,
Operating Systems Concepts, 8th edition
John Wiley & Sons, 2009

Other Materials

Make your program
Multithreaded Programming with ThreadMentor
Solaris multithreaded programming
Unix Multiprocess Programming
Signals
Non-Local GOTO: setjmp() and longjmp()

Meeting Time and Office Hours

	Monday	Tuesday	Wednesday	Thursday	Friday
14:05 - 15:00		CS3911		CS3911
15:00 - 15:30		CS3911		CS3911	Dept. Seminar
15:30 - 16:00	Office Hour	Office Hour		Office Hour	Dept. Seminar
16:00 - 17:00	CS4411		CS4411		CS4411

After class and e-mail discussions are welcome

Course Syllabus

*Week*		*Topics*	*Reading*
1	August 30	Overview	Chap. 1 - 2
2	September 6	Processes and Threads	Chap. 3 - 4
3	September 13	Processes and Threads	Chap. 3 - 4
4	September 20	Synchronization	Chap 6 and web notes
5	September 27
6	October 4
7	October 11	CPU Scheduling	Chap 5
8	October 18	Deadlock	Chap. 7
9	October 25	Memory Management	Chap. 8 - 9
10	November 1
11	November 8
12	November 15	File and Input/Output Systems	Chap. 10 - 13
13	November 29	File and Input/Output Systems	Chap. 10 - 13
14	December 6	Protection and Security	Chap. 14 - 15

Important Dates

Week 4	September 24	Friday	11pm	Program 1 due
Week 5	September 29	Wednesday	in class	Exam 1 (50 min)
Week 7	October 15	Friday	11pm	Program 2 due
Week 9	October 29	Friday	11pm	Program 3 due
Week 10	November 3	Wednesday	in class	Exam 2 (50 min)
Week 11	November 10	Wednesday	11pm	Program 4 due
Week 12	November 19	Friday	11pm	Program 5 due
Week 13	November 29	Monday	0am	Mini-Project starts
Week 14	December 10	Friday	11pm	Mini-Project due
Final Week	December 13	Monday	5:30-7:30pm	Final (2 hours) Fisher 328

Weights Assigned to Programs

*Program 1*	*Program 2*	*Program 3*	*Program 4*	*Program 5*	*Mini-Project*
50	70	70	70	70	100

Weights Assigned to Exams

*Exam 1*	*Exam 2*	*Final*
100	100	200

Grading

There are 830 points possible in this course - 430 from programs, 400 from the exams. You will be graded on the percentage of these points you accumulate. Grading will be based approximately on the scale shown in the table below.

Grade	A	AB	B	BC	C	CD	D	F
Scale	90-100%	85-89%	80-84%	75-79%	70-74%	65-69%	60-64%	0-59%

In addition, you will not receive a passing grade in the course unless you receive a passing grade on the exams alone (i.e., 60% or 300 points). Likewise, you will not receive a passing grade in the course unless you receive a passing grade on the programming assignments alone (i.e., 60% or 258 points).

Late Policy

No late programming assignments will be graded, except that you have a valid excuse.

Collaboration and Cheating

No assignment-specific assistance should be given nor received on any programming assignment. Any outside help concerning the use of the computer facilities is acceptable. You may discuss the meaning or intent of an assignment, but not ways to program it. All work turned in must be completely your own. You must not share code or even outlines! Any and all use of programs from other texts or references must be explicitly stated as part of program documentation. In general, any acts of plagiarism will result in a failing grade for the course along with the submission of a report to the Dean of Students. See the hand-out on Computer Science Policy on Cheating and Academic Integrity Policy for more details.

Exams and Final

You are responsible for avoiding exam time conflicts!!

ADA

``MTU complies with all federal and state laws and regulations regarding discrimination, including the Americans with Disability Act of 1990 (ADA). If you have a disability and need a reasonable accommodation for equal access to education or services at MTU, please call Dr. Gloria Melton, Dean of Students, (2212). For other concerns about discrimination, you may contact your advisor, department head, or the Affirmative Action Office (3310).''

The following two web sites may provide you with more information:

Disability Services.
Affirmative Programs Office (commonly called the Affirmative Action Office, or AAO)

Other Useful Information

Downloadable Stuffs

Files are in PDF format.

Programming Information: Programming Assignment 1; Programming Assignment 2; Programming Assignment 3; Programming Assignment 4; Programming Assignment 5
Exam Information: Exam 1 Solutions (PDF file); Exam 2 Solutions (PDF file)
Reading Lists

Week 1	Week 2	Week 3	Week 4	Week 5	Week 6	Week 7
Week 8	Week 9	Week 10	Week 11	Week 12	Week 13	Week 14

You are visitor

since July 1, 1998.
Last update: August 29, 2010

Please send comments and suggestions to shene@mtu.edu

CS4411 Introduction to Operating Systems Course Information Page Fall 2010

Happy Holidays