CS 354: Operating Systems Fall 2006 http://www.cs.purdue.edu/homes/fahmy/cs354f06/index.html

• Silberschatz, Galvin and Gagne. Operating system concepts. John Wiley and Sons. 7th edition. 2004. ISBN: 0-471-69466-5. Older editions are okay too.
  We will cover parts of Chapters 1 through 13. On Reserve in the Math library.

  You can find the slides for Silberschatz, Galvin and Gagne here.

• Recommended text: Advanced Programming in the UNIX Environment. W. Richard Stevens. Addison-Wesley. 1993. ISBN: 0-201-56317-7. On Reserve in the Math library.

• Other Useful Books (some of them available in the library):
  • The Linux kernel.
  • The Design of the Unix Operating System. Maurice Bach, 1986.
  • Linux Kernel Internals. Michael Beck et al. Addison-Wesley-Longman, 1998. 2nd edition. ISBN: 0-201-33143-8.
  • Solaris Internals: Core Kernel Architecture. Jim Mauro et al, Sun Microsystems Press, 2001. ISBN: 0-13-022496-0.
  • Solaris Systems Programming. Rich Teer, Pearson Education, 2005. ISBN: 0-201-75039-2.
  • UNIX Network Programming, volumes 1 and 2. Stevens.
  • Internetworking with TCP/IP, Vol. III. Comer and Stevens.
  • Distributed Operating Systems. Tanenbaum.
  • Operating system design: The XINU approach, PC Edition. D. E. Comer and T. Fossum. Prentice-Hall Inc. 1988. ISBN: 0-13-638180-4.

• An introduction to C++ by Tom Anderson | A quick introduction to C by Steve Holmes | Makefile Tutorial

• Class notes from previous semesters:
  • Spring 2006/Fall 2005 (PPT) | Spring 2005 | Spring 2004 | Spring 2003 | Fall 2002 | Spring 2002 | Fall 2001 | Fall 2000 | Spring 2000 | Fall 1999 (Disclaimer: we will cover some different material. Also, there is a number of typos in the notes.)

• Old CS 354 Exams (Disclaimer: our exams will be different in style, content, and format. Also, some of the solutions provided in this directory are incomplete or incorrect.)

• A brief introduction to UNIX and xemacs commands

• Sonia Fahmy, office: LWSN 2142H, e-mail: fahmy@cs.purdue.edu, phone: (765) 49-46183

Office Hours:

• T Th 1:30--2:20 PM, W 11 AM--noon, and by appointment

• Ian Molloy, e-mail: imolloy@cs.purdue.edu, office: LWSN B105, office hours: Tuesdays 2:30-3:30 PM.
• Ardalan Kangarlou-Haghighi, e-mail: akangarl@cs.purdue.edu, office: LWSN B105, office hours: Thursdays 3:00-4:00 PM.

PSOs:

Students are strongly encouraged to attend the PSO sessions on Mondays at 9:30 AM in HAAS G040, or Wednesdays at 1:30 PM in HAAS G040. (PSOs will meet every week, starting Monday August 28th. There are no PSOs the first week of classes.)

If you need to remove a registration schedule conflict, please notify your advisor.

Prerequisites:

CS 250, CS 251, and ability to program in C/C++.

Credit:

03

No makeup exams will be given.

Policies:

Due Dates

All assignments are due on the dates and times specified. It is the student's responsibility to manage their time so that the assignments can be submitted before the deadline.

To accomodate unseen schedule conflicts and difficulties, a student can submit an assignment up to 24 hours later than the due date, with a 10 point (out of 100) reduction in total score. An assignment submitted up to 48 hours late will have 20 point deducted from the total score. Note that submitting an assignment even one second late counts as a late lab.

Any submission that is 48 hours or more later than the specified due date and time will be returned ungraded.

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 your TA or 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 TAs will be inspecting all submitted material to ensure honesty.

Class participation and discussions are strongly encouraged. However, please be considerate to others: avoid coming to class late, leaving early, talking to other students, etc. Please turn off your cell phone before the class starts.

Newsgroup:

Questions should be posted on the newsgroup: news:purdue.class.cs354.
Make sure that you check the newsgroup and your e-mail frequently (at least once or twice per day). Do NOT post answers to the assignments, though general clarifications are OK. Complaints about the assignments or the class should NOT be posted to the newsgroup-- instead, they should be emailed to the instructor/TAs. The instructor and TAs can be reached by email at cs354-ta@cs.purdue.edu.

Useful Links:

• Links to be discussed in class:
  • Airline analogy
  • Transportation analogy (from Philip Greenspun)
  • Executable and Linking Format (ELF)
  • UNIX file descriptors, showing open() and dup() operation
  • Semaphores
  • Priority inversion and priority inheritance
  • mmap() example
  • Tiny OS web page
  • Advice to systems researchers

• Resources from Stanford University, including C references, pointer information, and UNIX tools
• UNIX/sockets/C/C++/PERL/JAVA manuals
• Coding Conventions (from H. Schulzrinne)
• C FAQ
• C++ FAQ
• GNU documentation tree

• SIGOPS- ACM Special Interest Group on Operating Systems
• IEEE Computer Society
  • Technical Committee on Operating Systems (TCOS)
• IEEE Communications Society
  • Technical Committee on Computer Communications (TCCC)
  • Internet Technical Committee (ITC)
• SIGMETRICS- ACM Special Interest Group on Performance Evaluation
• Operating System Links