CSE422S: Operating Systems Organization (Spring 2006)

Department of Computer Science

School of Engineering and Applied Science

Washington University in St. Louis

Instructor

Grader/Consultants

All Graders/Consultants cse422@cec.wustl.edu
Lin Chen lc1@cec.wustl.edu	By appointment
Mark Wood mcw2@cec.wustl.edu	By appointment

Quick Links

• News Group: wu.cse.class.422
• Exam 1 ( Solution and Statistics )
• Old Exam
• Spring 2005 exam and solution
• Latest Assignments
• Homework 8
• Due Date: None
• The assignment ( pdf ), the FAQ , the Full Solution
• Homework 7
• Due Date: Wed, Apr 26, 2006 in class
• The assignment ( pdf ), the FAQ , the Full Solution
• Homework 6
• Due Date: Wed, Apr 19, 2006 in class
• The assignment ( pdf ), the FAQ , the Full Solution
• Project B
• Due Date: Mon, May 8. Electronic copy by midnight. Hardcopy by noon Tue, May 9.
• The assignment ( pdf ), the FAQ
• Documentation Template
• A test script and a script called from within the test script. The script also uses the fib program from Project A.
• test40.C (demo child sends SIGINT to own process group)
• doio.c (demonstrates how to read stdin/write stdout using unbuffered I/O)
• Project A command parser
  This tar file contains a skeleton main and a parser in the file skel.c and a header file stdinc.h. If you saved the tar file as parser.tar, then it can be untarred into a directory that does not already contain a stdinc.h file using: tar xf parser.tar . It uses two STL maps and must be compiled with a C++ compiler like this: g++ -g -o skel skel.c. The skeleton main is not intended to be used directly but is provided as an example of how to call the parser.
• Homework 5
• Due Date: Wed, Apr 5, 2006 in class
• The assignment ( pdf ), the FAQ , the Full Solution
  • npipe.c
  • stdinc.h
• Problem 6 input file (use this if you want)
• Homework 4
• Due Date: Wed, Mar 22, 2006 in class
• The assignment ( pdf ), the FAQ , the Full Solution
• Project A
• The assignment ( pdf ) and the FAQ
• Due Dates:
  • Mid: Mon, 1600 Hours (4 PM), Feb 27 (Electronic submission only)
  • Final: Wed, 2400 Hours, Mar 8 (Electronic submission) and Thur, 1800 Hours (6 PM), Mar 9 (Hardcopy)
  • Final Late Date (20% penalty): Wed, 2400 Hours, Mar 22 (Electronic submission) and Thur, 1800 Hours (6 PM), Mar 23 (Hardcopy)
• Feb 27 status form (aka Feb27-questions.txt)
• Feb27.test This test file refers to fib which you can create from the source file given in the next item.
• Documentation Template
• Grading Form
• Another test
• shar file containing a CPU intensive program. Unpacking this file will produce two files: fib.c and fib-stdinc.c
Suppose you put the shar file in 'fib.shar'.
• To see what is in the shar file: 'less fib.shar'
• To unpack: 'sh fib.shar'
• To compile: 'g++ -o fib fib.c'
  The code may not compile under Solaris. Try uncommenting out one line near the top of the code marked with "uncomment for solaris".
• The Coding Style Guide
• The sample Makefile . You will probably have to modify it to suit your programs.
• test28f.C is a test program that shows how to map to a function. Ignore this if you don't have any experience with <map>.
• Here is the version that just maps to a char *
• Symbol table tar file .
  This is a simple C++ version, but you don't need to know much C++ to use it.. See the file 'SymTbl.h' for usage information.
  NOTE: If you know how to use the STL, then you might be better off using something like <map> from the STL.
  BEWARE: The tar file contains a file called 'Makefile'. Unpacking will destroy any existing file named 'Makefile'.
  Suppose you put the tar file in 'SymTbl.tar'.
  • To see what is in the tar file: 'tar tf SymTbl.tar'
  • To unpack: 'tar xf SymTbl.tar'
  • Read README file.
  • Read SymTbl.h file.
  • To build test: 'make'
  • To run test: 'testSymTbl'
• Perl script which "cleans" your shar file.
  If you are worried that your shar file is bad, you can use the above perl script to see if the file is ok:
  • REMINDER: Do NOT send non-ASCII files (e.g., word documents, binaries).
  • Read the documentation header in the script. NOTE that you may have to change the pathname in the first line of the script to point to the location of your perl interpreter.
  • Make your shar file (suppose it is called A.shar).
  • Then, run "cleanshar.pl A.shar". If it finds anything wrong, it will try to fix it and save the old copy. cleanshar.pl only fixes non-conformant shar files. It can not read your mind.
  • Look at the contents of A.shar using less (more) or an editor. You should see a list of your files.
  • If you are still worried, then email the file to yourself: mail -s "my shar test" YourLogin < A.shar.
  • Read your email and save the email to a file IN A DIRECTORY AWAY FROM YOUR SOURCE CODE (e.g., ~/tmp/A.email).
  • Edit ~/tmp/A.email to remove mail headers, etc. and save it to a file (e.g., A.shar). It's just your files with some Bourne shell stuff surrounding it. There should be a table of contents near the top that lists your files.
  • Extract the files: cd ~/tmp; sh A.shar. The files should be in your ~/tmp directory or whereever you are at this point.
• Homework 3
• Due Date: Mon, Feb 20 in class (NEW DATE)
• The assignment ( pdf ), the FAQ , the Full Solution
• Problem 6 tar file.
  Get the tar file and then untar: tar xf hw3-6.tar
  Or get the files individually here: Makefile, stdinc.h, forkit.c.
  Or get the zip file and unzip it.
• Simple parser for Problem 7
• Problem 7 tar file.
  Get the tar file and then untar: tar xf hw3-7.tar
  Or get the files individually here: Makefile, stdinc.h, t_exec.c.
  Or get the zip file and unzip it.
• Homework 2
• Due Date: Wed, Feb 8 in class
• The assignment ( pdf ), the FAQ , the Full Solution
• An Introduction to Linux, Machtelt Garrels
• Tar file containing Makefile, membench.c, template.gp that uses scripts and gnuplot to give you a "one stop" method of running membench and getting a postscript plot. If you name the tar file membench.tar,
  • The command 'tar tf membench.tar' will list the contents of the tar file.
  • The command 'tar xf membench.tar' will create the 3 files in the current directory.
  • The command 'make' will build the executable and run a sequence of commands that will culminate in the creation of the file generic.ps that is a postscript file containing the plot.
    This file can be printed on a postscript printer or viewed with the 'gv', 'gs' or 'ghostview' utility. If using 'gs', try 'gs -sDEVICE=x11 generic.ps' when trying to view the generic.ps postscript file.
• timeit.c file for Problem 8. You will need to add a few lines to get it to compile and run properly.
• Homework 1
• Due Date: Wed, Feb 1, in class
• The assignment ( pdf ), the FAQ , Problem 1 Code , and the Full Solution
• Example of getopt for processing command-line arguments.
• Latest Lecture Notes and Handouts
• Lecture 18: Hot Topics ( pdf ) and Exam 2 ( pdf ) (Mon, May 1, 2006)
• Lecture 17: Files ( pdf ) (Wed, Apr 26, 2006)
• Lecture 16: Basic I/O ( pdf ) (Wed/Mon, Apr 19/24, 2006)
• Lecture 15: Virtual Memory (Part 2) ( pdf ) (Mon, Apr 17, 2006)
• Lecture 14: Virtual Memory (Part 1) ( pdf ) (Wed, Apr 12, 2006)
• Lecture 13: Memory Management ( pdf ) (Mon, Apr 10, 2006)
• Lecture 12: Project B ( pdf ) (Wed, Apr 5, 2006)
• Lecture 11: Signals ( pdf ) (Mon/Wed, Apr 3/5, 2006)
• Lecture 10: Threads ( pdf ) and Exam 1 ( pdf ) (Wed/Mon, Mar 22/27, 2006)
• Lecture 9: Deadlock ( pdf ) (Mon, Mar 20, 2006)
• Lecture 8: CPU Scheduling ( pdf ) (Wed/Mon/Wed, Mar 1/6/8, 2006) and ( Homework 3 )
• Lecture 7: Classic Synchronization Problems ( pdf ) (Wed/Mon, Feb 22/27, 2006)
• Lecture 6: Synchronization ( pdf ) (Wed/Mon, Feb 15/20, 2006)
• Lecture 5: The Bourne Shell ( pdf ) (Wed/Mon, Feb 8/13, 2006) and ( Homework 2 )
• Lecture 4: Classic Processes ( pdf ) (Mon/Wed, Feb 6/8, 2006)
• Lecture 3: Using an OS ( pdf ) (Mon/Wed, Jan 30/Feb 1, 2006)
• Lecture 2: Computer Architecture ( pdf ) (Mon/Wed, Jan 23/25, 2006) and Computer Architecture Addendum (Mon, Jan 30) ( pdf )
• Assessment 1 (Wed, Jan 18, 2006)
• pdf , and solution
• Lecture 1: Introduction ( pdf ) (Wed, Jan 18, 2006)
• Page With Links To All Other Handouts
• Link to Fall 2005

Course Description

Prerequisites

• CSE 332S (CS 342S) - Object-Oriented Software Laboratory
  

Books

• Required: Modern Operating Systems, Andrew Tanenbaum, Prentice Hall, Latest Edition.
• Optional: Advanced Programming in the UNIX Environment, W. Richard Stevens, Addison-Wesley, Latest Edition.
  (*** A classic for systems programmers)
• Other Books:
• Programming Style
• The Practice of Programming, Brian W. Kernighan and Rob Pike, Addison-Wesley, 1999.
  (*** A must for the serious CS student)
• Operating Systems
• Operating Systems, Fifth edition, by William Stallings
• Distributed Systems, 2nd Edition, edited by Sape J. Mullender, ACM Press.
• The Design and Implementation of the 4.4 BSD UNIX Operating System, S. J. Leffler and M.K. McKusick and M.J. Karels and J.S. Quarterman, Addison-Wesley, 1996.
• The Design of the UNIX Operating System, Maurice J. Bach, Prentice Hall, 1986.
• Inside Windows NT, Helen Custer, Microsoft Press, 1993.
• C and C++ Programming
• The C++ Primer: Second Edition, Stan Lippman, Addison-Wesley, 1991.
• The C++ Programming Language: Second Edition, Bjarne Stroustrup, Addison-Wesley, 1991.
• Effective C++, Scott Meyers, Addison-Wesley, 1992.
• Learning C++, Neil Graham.
• Stephen G. Kochan, Programming in C.
• The C Programming Language: Second Edition, Kernighan and Ritchie, Prentice Hall, 1991.
• A Book on C, Kelly and Pohl.