Course Description - CSCI 402, Spring 2013, TuTh Section

Focus		Late Policy		Fairness
Textbooks		Note From A Doctor		Auditing
Syllabus / Topics Covered		Regrade Policy		E-mail
Homework Assignments		Office Hours		Academic Integrity Policy
Projects		Extra Credit		Academic Calendar
Exams		Implicit Student Agreement		Additional Resources
Grading		Student Responsibilities

• T. W. Doeppner, Operating Systems In Depth: Design and Programming, 1st Edition, Wiley, 2010. (Please note that the Kindle Edition of this book is identical to the printed version of this book.)

Recommended resources:

• B. Kernighan and D. Ritchie, C Programming Language, 2nd Edition, Prentice Hall, 1988. (Since the C programming language is a proper subset of the C++ programming language, if you know C++, you pretty much know C already. However, things available in C++, such as strings and streams, are not be available in C. So, you need to know how to do things such as manipulating null-terminated array of characters and performing I/O in C.)

• Scott Chacon, Pro Git (a free online book). You will need to use Git for the programming assignments.

• David Rusling, The Linux Kernel. (This is for your reading pleasure. We will not cover this book in our class.)

• Wk 1-2: Introduction to Operating Systems (OSID Ch 1)
  • A Brief History of Operating Systems
  • A Simple OS
  • Beyond a Simple OS
• Wk 3: Multithreaded Programming (OSID Ch 2)
  • Why Threads
  • Programming with Threads
  • Synchronization
  • Thread Safety
• Wk 4-5: Basic Operating Systems Concepts (OSID Ch 3)
  • Context Switching
  • I/O Architecture
  • Dynamic Storage Allocation
  • Linking and Loading
  • Booting
• Wk 5-6: Operating-System Design (OSID Ch 4)
  • A Simple System
  • Virtual Machines
  • Microkernels
• Wk 7-8: Process Management (OSID Ch 5)
  • Threads Implementations
  • Interrupts
  • Scheduling
• Wk 8-9: File Systems (OSID Ch 6)
  • The Basics of File Systems
  • Crash Resilency
  • Directories and Naming
  • Multiple Disks
  • Flash Memory
  • Case Studies
• Wk 10-11: Memory Management (OSID Ch 7)
  • Memory Management in the Early Days
  • Hardware Support for Virtual Memory
  • OS Issues
• Wk 11-12: Security (OSID Ch 8)
  • Security Goals
  • Security Architectures
• Wk 13: Networking (OSID Ch 9)
  • Network Basics
  • Remote Procedure Call Protocols
• Wk 14-15: Distributed File Systems (OSID Ch 10)
  • NFS Version 2
  • CIFS
  • DFS
  • NFS Version 4

These exercises will not be collected or graded, but students are encouraged to work on them.

All projects will require a fairly strong background in C programming, which you are expected to pick up on your own. There will be 1 to 2 warmup programming assignments at the beginning of the semester to make sure that you are up to speed with C and doing multi-threading in C.

All kernel programming assignments are extremely difficult. You can do these assignments in teams of two or three students. Since the kernel programming assignments are interrelated, you must pick a team at the beginning of the semester and stick with the team till the end of the semester. If you'd prefer, you can do the kernel assignments by yourself.

Please see the projects specifications for details.

Exam Questions

There are two types of exam questions that I usually ask. The first type is a calculation-type question. Pretty much anything that can be calculated/computed by running an algorithm can be asked in an exam. For example, I can ask you to compute a schedule using a particular scheduling algorithm. I can also ask you about what a data structure (e.g., tree, hash table, etc.) would look like after certain operations have been performed on it. Usually, for this type of questions, you must get the answer right and there is not much room for partial credits.

The second type is in the following form: "In N words or less, what is the answer to the following question?"

For this type of question, you can write as many words as you'd like, but I will only read the first N words of your answer! You don't need to count the number of words in your answer, you just need to make sure that the most important part of your answer appears in the first N words! (There is no need to write complete English sentenses when you answer exam questions. Just give me the important stuff!)

The reason I'm doing this is that I don't want a brain dump of everything you know about a topic and tell me that the answer is there and that I have to look for it! I want you to tell me what part of your answer you think is important and you need to distinguish between answers of different quality and put the best answer up front.

Let me give a couple of silly examples (with questions that's not in the scope of any exam).

• "In 20 words or less, for programming assignments (well, this is not our policy, I'm just using this as an example), when is 'plagiarism' considered taking place? If your answer is "when you take someone else's work and claim it to be yours", then you will get full credit. If your answer is, "when you submit someone else's work", you probably will not get full credit.

• "In 20 words or less, what is the fairness policy of this class?" If your answer is, "whatever the instructor offer to one student, he must offer it to the rest of the class," then you will get full credit. If your answer is, "the instructor must be fair to every student," you probably will not get much credit.

In general, better answers may score more points. If you give very high level and generic answer that's generally true or basically just repeat the question, you probably will get very little credit for it! You need to answer a specific question with a specific answer.

If I asked a question straight from the lecture slides, the best/correct answer is the one on the lecture slides. If you disagree with what's on the slides, you must complain when you were studying for the exam, i.e., before the exam. Once the exam starts, it's too late to complain that you don't like the answer on the lecture slides. In an exam, if you give an answer that's different from the lecture slides, you may receive partial credits, at the discretion the TA

Projects:		30%
Midterm Exam:		30%
Final Exam:		40%

Two methods will be used to calculate your final letter grade:

(1)		Use a modified curve (i.e., we won't necessarily assign an equal number of failing grades as passing grades) based on the numeric score calculated above
(2)		Use the following fixed scale (to encourage cooperation and friendly association amongst students): Percentage Letter Grade 90% or higher A 80-90% A- 70-80% B+ 60-70% B 50-60% B- 40-50% C+ 30-40% C 20-30% C- below 20% F

Pleaes also note the following:

• No other methods will be considered. (So, please do not ask the instructor to take how much you have improved since the beginning of the semester into account. You are expected to try your best from the beginning!)

• We will assign grades of C and below to individuals who do not perform satisfactorily (i.e., you should not assume a B- or even C if you perform unsatisfactorily.) However, we hope that everyone will perform well.

• We will not assign incompletes unless it is for a documented illness or family emergency (in accordance with USC policy).

If you are unable to complete a homework or a programming assignment due to illness or family emergency, please see the instructor as soon as possible to get an extension. A doctor's note is required as proof of illness or emergency. In general, when you get sick, it's best to see a doctor and get a note just in case you may need it later.

So, if you visit a doctor at the Student Health Center, please make sure you fill out one of these forms, check the "limited discussion with faculty" checkbox, get it stamped, signed, and dated by someone there (a clerk/receptionist would sign at the "witness" line), and bring it back to me. This would satisfy the "note from a doctor" requirement so that you can get an extension.

If you visit a doctor somewhere else, please either bring a "note from the doctor" or a similar authrozation letter so I can contact them.

For exams, please do not argue abou what you were thinking when you were writing down your answers. We can only grade based on what you wrote on the exam paper. Please write what you meant and meant what you write.

You are welcome to make an appointment to see the instructor outside of office hours. Making an appointment is not a big deal! Just send an e-mail to the instructor and tell him when you are available to meet and go from there.

1. Post good, useful, and insightful answers to the class Google Group in response to questions posted by other students regarding kernel programming assignments.
   • The maximum number of extra credit points you can get is 10 points for each of the kernel assigments (on a 100-point scale).
   • You can lose extra points you have earned if you post something unprofessional to the class Google Group or exhibit poor netiquette. Please always be courteous and professional.
   • The instructor will decide to award extra credit or not at his discretion and will keep track of scores. (Harrassing the TA is considered unprofessional behavior.)
   • If you post something good, it's your responsibility to verify that it has been posted to the Google Group
   • You will not get credit for anything posted to a Google Group for the section you are not registered in.

2. To encourage you to do your programming assignments early, you will get extra credit if you turn in programming assignment 2 or 3 days early. (Please note that this rule does not apply to assignments that are entirely extra credit, i.e., kernel assignment 3.)
   • If your submission is more than 72 hours before the posted deadline, you get an extra 10%, i.e., your actual score will be 1.1 times your graded assignment score.
   • If your submission is between 48 and 72 hours before the posted deadline, you get an extra 5%, i.e., your actual score will be 1.05 times your graded assignment score.
   The figure below summarize the early submission extra credit schemes.

   

Please note that due to my fairness policy, I cannot offere any individual extra credit work.

This policy also holds for programming assignments. In this class, we will use sophisticated automated program checkers to detect cheating. Be aware that the program checkers have demonstrated very good results and are widely used within the academic community. Any student caught cheating will be given zero credit and will be disciplined.

It is the students responsibility to submit their assignments electronically in time.

For students who satisfied the prerequisite at other universities or through work experience, this course assumes that you understand data structures, basic algorithms, and UNIX programming. You should be able to write large programs in C/C++. No special assistance or consideration will be offered if your background is inadequate.

You must keep up with the assigned readings. If you come to class without having read the chapter for the corresponding lecture, you're unlikely to learn anything at all from the lecture. In particular:

1. You are expected to read the relevant textbook chapter thoroughly. Not all details will be covered in class, and the exam may test material covered in the textbook but not discussed in class.
2. I expect you to attend every class meeting. If you do happen to miss a session, you are responsible for finding out what material was covered and if any administrative announcements were made. Also, please be aware that several of the exams are in-class, so you will be expected to at least attend those lectures.

Please do not ask the following types of questions in your e-mail:

• Here is my understanding of X. Am I right (or is this correct)?
  (You can do this for just about everything and in many different ways. I do not have the bandwidth to deal with too many questions like this. However, often times, you should be able to ask a slightly different question and get the same answer that you are looking for. This type of questions is completely appropriate for office hours.)

• I don't understand X. Could you explain X to me?
  (It's your responsiblity to come to lectures and ask questions during lectures if there is something you do not understand. If you did attend lectures, then it is appropriate to ask this during office hours.)

Although this is not related to e-mails, it's a type of question I get often. Please do not ask this types of question:

• Here is what I am thinking of or doing... is it acceptable (or is this okay)?
  

  (What you are really asking is whether you will receive full credit or not. Wouldn't it be great if you can ask this during exams? It's not an appropriate question for assignments for the same reason it is not appropriate for exams. Although there is a difference between programming assignments and exams, but since you are asking about grading, it's inappropriate. If you asking if it's okay to take a shortcut. The answer is always, "No" or "At your own risk.")

Programming:

• C Programming (by Steve Holmes at the University of Strathclyde in Glasgow, England) - includes notes on make, separate compilation, file I/O, etc.
• Makefile tutorial (at Colby College)
• Makefile tutorial (at Indiana University)
• Steve's Software Trek (by Steve Karg) - includes some useful C/C++ source code for string manipulation, INI file manipulation, etc.
• C Examples - lots and lots of sample C code for basic stuff.
• C/C++ at USC from USC ITSWeb

• Ubuntu Linux
• cygwin (BSD system with X11R6 on Windows XP)
• Some Often-used UNIX Commands
• Unix commands (more complete, from University of Utah)
• UNIX Shell Programming (Chapter 2 of this book gives a good introduction to UNIX)
• UNIXhelp for Users from the University of Edinburgh
• UNIX Tutorial for Beginners from the University of Surrey
• Introduction to the Unix Shell from the Canisius College
• Introduction to C Shell Programming from the Canisius College
• C/C++ Documentation (compiling, linking, additional libraries, include files) from USC ITSWeb
• Understanding C by learning assembly
• UNIX Documentation (concepts, commands, X-Windows) from USC ITSWeb
• Editors on most UNIX systems
  • Vi Text Editor Documentation from USC ITSWeb
  • EMACS Text Editor Documentation from USC ITSWeb
  • Pico Text Editor Documentation from USC ITSWeb
• Beej's Quick Guide to GDB
• Richard Stallman's gdb Tutorial
• General information on operating systems, productivity applications, Internet connectivity, e-mail and web publishing at USC, can be found at the ITS software site. You can click on your operating system and download useful software from there. For example, for the Windows platform, you can find things like X-Win32, FileZilla, and PuTTY there.