|Instructor(s)||Shacklette, Mark (jmshackl)|
|Meeting Times||Friday 5:30pm - 8:30pm|
Texts: Required (get the latest (i.e., currently published) editions of the following)
The Linux Programming Interface: A Linux and UNIX System Programming Handbook, Michael Kerrisk, No Starch Press, 2010, ISBN: 1593272200
(2 copies on Ready Reserve in Eckhart)
Understanding Unix/Linux Programming: A Guide to Theory and Practice, Molay, Prentice Hall, ISBN: 0130083968 (1 copy on Ready Reserve in Eckhart)
Advanced Programming in the UNIX(R) Environment , Richard Stevens, Addison-Wesley, ISBN: 0201563177 (2 copies on Ready Reserve in Eckhart)
UNIX Network Programming, Volume 1: Networking APIs - Sockets and XTI (2nd Edition), Richard Stevens, Prentice Hall, ISBN: 013490012X (2 copies on Ready Reserve in Eckhart)
Programming with POSIX Threads, Butenhof, Addison-Wesley, ISBN: 0201633922 (2 copies on Ready Reserve in Eckhart)
C Language Instruction
Knowledge of C is required. If you need some review of C, we recommend either of:
The C Programming Language, 2nd ed. Kernighan & Ritchie. ISBN: 0131103628
C: A Reference Manual (5th Ed.), Harbison & Steele; Prentice Hall (2002). ISBN: 013089592X
Expert C Programming--Deep C Secrets, van der Linden, Prentice Hall (1994). ISBN: 0131774298
Introductory C, Petersen; Morgan Kaufmann Publishers; ISBN: 0125521421 ; 2nd edition (January 15, 1997)
C Programming: A Modern Approach, King; W.W. Norton & Company; ISBN: 0393969452 ; (April 1996)
General Unix C Programming:
Beginning Linux Programming, 4th Ed., Matthew & Stones, Wrox Press, 2008. ISBN: 9780470147627
Managing Projects with Make , Andy Oram and Steve Talbott, O'Reilly, 1991
Unix Systems Programming with SVR 4, David Curry, O'Reilly, 1996
Linux Socket Programming By Example, Warren Gay
Pthreads Programming, Nichols et. al, O'Reilly, 1996
The Unix Programming Environment, Kernighan & Pike, Prentice Hall, 1984
Advanced Unix Programming, Rochkind, Prentice Hall, 1985
Interprocess Communications in UNIX: The Nooks & Crannies , Gray, Prentice Hall, 1988
Unix Distributed Programming, Brown, Prentice Hall, 1994
Power Programming with RPC, Bloomer, O'Reilly, 1992
Using C on the UNIX System, Curry, O'Reilly, 1989
Learning the UNIX Operating System , 4th Edition , Peek, et. al., Orielly, 1997
A Practical Guide to Linux , Mark Sobell, Addison-Wesley, 1997
Portable Shell Programming , Bruce Blinn, Prentice Hall, 1996
UNIX Power Tools, Peek et. al., O'Reilly, 1993
Learning the Bash Shell, 2nd. Ed., Newham & Rosenblatt, O'Reilly, 1998
General Operating Systems:
Modern Operating Systems, 2nd. Ed., Tanenbaum, Prentice Hall, 2001
Operating System Concepts, 5th Ed., Silberschatz & Galvin, Addison-Wesley, 1998
UNIX Internals: The New Frontiers, Vahalia, Prentice Hall, 1996
UNIX Internals: A Practical Approach, Pate, Addison-Wesley, 1996
Texts: Ready Reserve Reading List
The Unix Philosophy, Gancarz
1. Knowledge of C Programing is required.
2. All students should have taken the CSPP Unix Bootcamp or the MacLab Unix Course prior to the first day of class (or have the requirement waived). Those who have not completed this requirement will need approval of the instructor, which will require hands-on experience working within a Unix environment.
Basic familiarity with a Unix source code editor (vi, emacs, nedit, pico, gedit, etc.) will be necessary.
III. COURSE DESCRIPTION
CSPP 51081 is systems programming course which explores topics in systems programming on Unix. Topics to be covered in detail will include:
Unix History and Philosophy
Unix File I/O
Static and Shared Libraries
Processes and Signals (fork, exec, etc.)
Pipes (unnamed and FIFOs)
System V IPC (semaphores, message queues, shared memory)
Berkeley Socket programming
POSIX pThread programming
Various tools used in developing software in C on Unix will be covered in class and/or tutorial, including gcc, gdb, ddd, gprof, cvs, etc.
IV. LEARNING OBJECTIVES
Upon completion of this course the student will::
A. Understand advanced UNIX operating system concepts and terminology.
B. Develop a command of the Unix Shell environment, including advanced Unix commands and utilities.
C. Become acquainted with the basic tools used to develop software in C on the Unix platform.
D. Become familiar with basic IPC issues and techniques in Unix programming
E. Become familiar with socket programming using the Berkeley socket API
F. Become familiar with both the theory and practice of making Remote Procedure Calls in Unix
G. Become familiar with multithreaded programming in C using POSIX pThreads on Unix
V. ACADEMIC INTEGRITY
Students are expected to have read and understood the University's policy on Academic Integrity. This policy is detailed in the Student Manual of University Policies and Regulations, available online at http://studentmanual.uchicago.edu/ .
VI. METHOD OF INSTRUCTION
Methods include lecture and homework assignments.
VII. OTHER COURSE INFORMATION
No formal attendance taken. There may be information presented in class that is not in the texts. You will be responsible for all information discussed in class and assigned in the required readings.
If you miss an exam or quiz, you will need to speak with the instructor ASAP. Prepare for unhappiness.
Students are expected to read the assigned texts before class in order to be able to full participate in the discussions.
VIII. METHOD OF EVALUATING STUDENT PROGRESS
Assigned work evaluated as follows:
Assigned work will be evaluated as follows:
|8 Labs (12 points each)||96 pts|
|1 Mid-Term||402 pts|
|1 Final Exam (or option below)||502 pts|
NB: The end of the quarter is the time at which the final grade you have earned through your work in the quarter is recorded with the registrar. It is not the time at which you begin negotiations with Professor Shacklette for extra credit opportunities. There is no extra credit offered in this course, either at the beginning or at the end.
Students may, with the prior permission of the instructor, opt to do either of the following in lieu of the final exam:
1. Write a 20-30 page page research paper, double spaced with 1 inch margins, including bibliography and footnotes, detailing the internal activities and interfaces of some substantial portion of the Linux kernel (process management, memory management, virtual memory, file system, scheduling, etc.) The quality of the paper should be targeted as publishable. You will need to demonstrate full command of the topic in detail through both the paper as well as possible oral review of its content with the instructor. The approval process requires a 2 page detailed research topic statement including a proposed outline of contents, resources, etc. Plagarism, in any form, will result in an F for the course.
2. Define a non-trivial systems programming project and implement it. The approval process requires a 2 page statement of the project, detailing the project scope, deliverable, and tools to be used. Delivery of the project involves a makefile that builds the software and supporting libraries, etc., and will be open to possible oral review with the instructor. If you choose this option, you may tailor the labs to support the ongoing development of the project (where relevant) and with the approval of the instructor or TA. Your project should include multiple topics of the course, for instance, multiple threads, thread concurrency controls, sockets, IPC, etc. An example of a non-trivial programming project might be a multithreaded web server written in C that supports multiple simultaneous clients and basic HTML delivery and implements some subset of the HTTP protocol. Plagarism, in any form, will result in an F for the course and reporting to the program director.
1. You must obtain the instructor's approval, via email, for either of these options by 11:59 pm, Friday, February 10th, 2017. There will be no exceptions to this.
2. Plagarism in any form will result in a final grade of 'F' for the course and notification of the program director for disciplinary action.
3. Both options carry the same total point availability as the final exam.
4. You may not work together on either of these options. Both options must be completed on an individual basis.
The due dates for labs are on the syllabus schedule below. All labs are required.
Lab assignments, when completed, should be tarballed up into a single gzipped tarball and sent to the graders directly (NOT to the instructor or TA(s)). The graders will post instructions on submitting labs.
For each part of the lab assignment there are detailed descriptions of what you should turn in. You should include ALL supporting files (source files, data files, etc.) as attachments to the submission email (a single message). Please send only UNIX-readable (text) files (that is, no MS Word documents!!!). Word documents will be considered a personal affront to the instructor and will result in ignominy and public humiliation. All work is evaluated and graded on the LINUX CLUSTER (not solaris, hpux, irix, aix, etc.)
FAILURE TO PROVIDE AND DELIVER TO THE GRADERS ALL SCRIPTS, ALL COMMANDS, AND ALL SUPPORTING FILES, TEXT OR SOURCE, YOU USED TO DELIVER AND PRODUCE THE SOLUTION WILL RESULT IN A LOSS OF POINTS. IF THE GRADERS, WORKING SOLELY ON THE LINUX CLUSTER, CANNOT REPRODUCE YOUR SOLUTION OR ANY PART OF YOUR SOLUTION FROM THE SET OF INFORMATION YOU PROVIDE, YOU WILL LOSE PARTIAL OR FULL CREDIT.
Note: Labs are due as scheduled below.
All assignments are due as specified on this syllabus and supporting lab pages. Students who turn in work late, regardless of the reason, will receive 2 points off from the first day the assignment is due (calculated as the first 24 hour period following the due date and time), and continuing for 6 days. Assignments turned in more than 6 days late from the original due date will not be accepted and the student will receive a 0 on the assignment. All late deliveries, regardless of cause will still incur the penalty. It is assumed that you will have plenty of time to work on each assignment, and that an individual penalty or two will have little overall effect on a student's final grade, unless lateness is chronic or other grades are poor, in which case, of course, the penalty will be more cumbersome. If you are late with a delivery and therefore receive a penalty (which you will if you are late for any reason) and it's an isolated incident and the rest of your work is excellent, the penalty should be innocuous.
The instructor reserves the right to alter the course contents, dates, times or percentage of credit based on time allowed and class progress through the course material. The instructor also reserves the right to curve grades if he deems it in the best interest of the majority of students.
IX. COURSE SCHEDULE
NB: The Instructor reserves the right to alter the schedule as class progress dictates.
The following abbreviations reference the following works:
|LPI||Linux Programming Interface|
|BLP||Beginning Linux Programming|
|UNP1||UNIX Network Programming, Volume 1 (optional)|
|PPT||Programming with POSIX Threads (optional)|
|APUE||Advanced Programming in the UNIX Environment (optional)|
|UULP||Understanding Unix/Linux Programming (optional)|
NOTE: Numbers besides the references are chapter numbers. Odd numbers like APUE 14.1-14.5 mean sections 1 through 5 of chapter 14 of APUE.
Tuesday, January 3
|Introduction & syllabus review
Historical Introduction to UNIX
|Class 2||January 15
|Tools and Compilation:
C compiler, compiling & linking
Introduction to make
Unix File I/O
|LPI 3-5; 13-18
|Class 3||January 20||Creating and using static libraries
Creating and using shared libraries
Introduction to Unix Processes
|LPI 6; 12; 41-42
[APUE 3,4,5,7, 10]
|Class 4||January 27
||Unix Processes & Signals
Process Creation: fork & exec
[APUE 7, 8, 10]
|Class 5||February 3||Problem Children: Orphans and Zombies
Introduction to Interprocess Communication:
|LPI 26-27, 43-44
[APUE 9, 14.1-14.5]
FAQ 5 LAB 5
|Class 6||February 10
||MID TERM EXAM (Written & Live)
Mid Term Study Guide
|Class 7||February 17
||System V Interprocess Communication (IPC):
|Class 8||February 24||C Socket Programming||LPI 56-61
|Class 9||March 3||Sun RPC
Multithreaded Programming on Unix with POSIX pThreads
|LPI 51, 29-33
PPT 1-5, 8
FAQ 9 LAB 9
( Due dates on lab page )
|Class 10||March 10||FINAL EXAM: (Written (Cumulative) & Live (Classes 7, 8 & 9 only))
Final Exam Study Guide
|Class 11||March 17||Advanced topics in Unix|
B or above in MPCS 51040 C Programming. For students who have not taken and passed MPCS 51040, there will be a UNIX C Programming qualifying test. Details on how to sign up for the qualifying exam will be sent to the student mailing list.
All students must have attended the Fall UNIX Bootcamp, or must have taken the UNIX waiver exam.
This class is scheduled at a time that does not conflict with any other classes this quarter.