CSCI 3500 - Operating Systems

schedule.yml loaded into PHP:
'; //print_r($data); //echo ''; //echo $data['ClassType']; //echo "\r\n"; //echo $data['ClassTime']; //echo "\r\n"; //echo $data['Semester']; //echo "\r\n"; //echo $data['Schedule'][1]['topics'][0]['text']; //These values are used verbatim on the website $CourseNum = $data['CourseNum']; $CourseName = $data['CourseName']; $CourseWebsite = $data['CourseWebsite']; $ClassTime = $data['ClassTime']; $Semester = $data['Semester']; $MidtermTime = $data['MidtermTime']; $FinalTime = $data['FinalTime']; //These values control how the schedule generator works $ClassType = $data['ClassType']; $SchedColor1 = $data['SchedColor1']; $SchedColor2 = $data['SchedColor2']; $SchedHeaderColor = $data['SchedHeaderColor']; $StartDateString = $data['StartDate']; $StartDate = new DateTimeImmutable($StartDateString); $hours = $data['LinkActivationHours']; $holidays = $data['Holidays']; for( $i = 0; $i < count($holidays); $i++ ){ $holidays[$i]['datetime'] = new DateTimeImmutable($holidays[$i]['date']); } //The printCell function expects an Item Array, described below in the comments, // and prints its content inside a tag, applying anchor tags and CSS styles // as indicated function printCell( $itemArray, $itemDate, $activationDate ){ //echo implode( "|", $itemArray); $styles = getStyles( $itemArray ); if( empty($styles) ){ echo "\t"; } else { echo "\t\r\n"; } for( $i = 0; $i < count($itemArray); $i++ ){ if($i > 0 ){ echo "
\r\n"; } if( $itemArray[$i]['link'] == "" or $itemDate > $activationDate){ echo $itemArray[$i]['text']; } else { echo "{$itemArray[$i]['text']}"; } } echo "\r\n"; } //The style of each line function getStyles( $item ){ $styles = array(); foreach( $item as $i ){ if( $i['class'] != "" ) $styles[] = $i['class']; } return $styles; } //Takes two DateTimeImmutable objects and returns whether they //refer to any time on the same day function isSameDay( $x, $y ){ if( $x->format('Y-m-d') == $y->format('Y-m-d') ){ return true; } return false; } //Takes a DateTimeImmutable object and the holidays list and returns //which specific holiday the DateTimeImmutable is, or NULL otherwise function whichHoliday( $date, $holidays ){ for( $i = 0; $i < count($holidays); $i++ ){ if( isSameDay( $date, $holidays[$i]['datetime'] ) ){ return $i; } } return NULL; } ?> CSCI 3500 - Operating Systems

- Class Page

Instructor	David Ferry, Homepage
Course Web Site
Course meeting times
Midterm exam
Final exam
Office hours	See my schedule
Contact	You may contact me in person during office hours or during class time, or you may email me at dferry@slu.edu. I am also available to meet by appointment, see my schedule.

Contents

Course Description
Prerequisites
Lecture
Studios
Labs
Course Schedule
SLU Git Repository
Textbooks and Other Resources
Grading
Attendance
Academic Integrity
Title IX Statement
Academic Support
Disability Services
Writing Center
Basic Needs Security

Course Description

Operating systems are the bridge between computer hardware and the software programs we create and use. As a concept, operating systems are one of the oldest software disciplines, yet they continue to adapt and reinvent themselves as the computing landscape evolves. Modern operating systems must tackle the same challenges of the original mainframes, but must also meet the varied needs of personal computers, severs, mobile/embedded devices, and virtualized systems.

The four elements of this course are lectures, studios, labs, and exams. Studios are short assignments intended to be completed primarily within class time and to augment lecture topics. Labs are longer assignments that will ask students to apply and analyze OS mechanisms. Most class periods will be a mix of questions and answers over lecture material, deep-dives into one or more of the lecture topics or practical demonstrations. Expect a lab assignment approximately every two weeks.

Topical outline:

The operating system, system libraries, and user applications
System calls and interrupts
User programs, processes, and threads
Processor sharing and operating system scheduling
Race conditions, locks, and mutual exclusion
The address space abstraction and virtual memory address translation
Virtual memory via paged memory and historical approaches
File systems and disk organization
7-layer OSI and 4-layer TCP/IP networking models
Sockets programming
Read, write, and execute permissions and institutional access models

Assessment Objectives- at the completion of this course, students will be able to:

Describe how operating systems facilitate and interact with system libraries and user space programs
Describe the purpose and implementation of major operating system abstractions: processes, threads, virtual memory, and the network stack
Identify the presence/absence of race conditions and resolve race conditions with locking
Write simple concurrent and multi-threaded programs (e.g. with fork() and Pthreads)
Write simple networked programs (e.g. with sockets programming)

Catalog Description:Theory and practice of operating systems, with emphasis on one of the UNIX family of operating systems. File organization and database systems. Focus on a multi-user system in the client-server model. Hands-on experience.

Prerequisites

CSCI 2100 - Data Structures
One of: CSCI 2400 - Computer Architecture or ECE 3217 - Computer Architecture and Organization
Some experience: C or C++
Some experience: object-oriented programming
Studios and lab assignments are constructed around the Linux terminal, prior experience is beneficial but not required

Please see the instructor if you're missing a prerequisite or uncertain about your preparation for this course.

Studios

Computer science is an eminently practical discipline, and studios are daily assignments intended to complement and reinforce lectures through practice. Studios will be completed in a team of two students. Students from different teams may discuss studios, but sharing of code or solutions is strictly prohibited.

Studios will be submitted via the Git repository. Every student should have a copy of their studio solutions in their own repository, even if you work with a group.

Studios are due Friday of the week after they are assigned. The midterm exam and other cirumstances may modify this, see the complete course schedule below.

Studios will be graded on a trimodal scale: complete, partial credit, or no credit. Studios that are turned in late or not turned in at all will receive no credit, studios graded as partial will receive 60% credit.

Labs

There will be five lab assignments for this course. These are programming assignments whose purpose is to apply course concepts and to analyze operating system mechanisms. As such, each lab will require a written report detailing your findings in addition to a code submission.

Some labs will require a team of two students, while others are individual projects. Students from different teams may discuss the lab assignments only during course meeting times. Students from the same team are of course encouraged to discuss and work on lab assignments at any time.

Labs submitted on time (as determined by electronic time stamp) are eligible for full credit. Labs submitted up to 24 hours late will be given a ten percent penalty. Labs submitted between 24 and 48 hours late will be given a twenty percent penalty. Labs submitted after 48 hours late will not be given credit, except in the case of extenuating circumstances pre-approved by the instructor.

Course Schedule

A tentative course schedule is below. Note that this schedule may change over the course of the semester. When changes occur, students will be given enough advance notice so that readings and other preparation may be accommodated. add($activateInterval); $bgColor = $SchedColor1; for( $i = 0; $i < count($schedule); $i++ ){ $a = $schedule[$i]; if( $currDate->format('D') == "Fri" ){ echo "\r\n"; if( $bgColor == $SchedColor1 ){ $bgColor = $SchedColor2; } else { $bgColor = $SchedColor1; } } else{ echo "\r\n"; } $isHoliday = whichHoliday( $currDate, $holidays ); if( !is_null($isHoliday) ){ $i--; //The day is incremented below, so we "redo" the for loop for the correct school day echo "\t\r\n"; //Print Month, Day echo "\t\r\n"; //Print Day Of Week echo "\t\r\n"; } else { echo "\t\r\n"; //Print Month, Day echo "\t\r\n"; //Print Day Of Week printCell( $a["topics"], $currDate, $activationDate); printCell( $a["readings"], $currDate, $activationDate); printCell( $a["studios"], $currDate, $activationDate); printCell( $a["labs"], $currDate, $activationDate); } $currDate = $currDate->add(new DateInterval('P2D')); if($currDate->format('D') == "Sun"){ $currDate = $currDate->add(new DateInterval('P1D')); } echo "\r\n"; } ?>

Date	Day	Topic	Readings	Studios	Labs
" . $currDate->format('M d') . "	" . $currDate->format('D') . "	" . $holidays[$isHoliday]['text'] . "	" . $currDate->format('M d') . "	" . $currDate->format('D') . "
Dec 14	Wed	Final Exam

SLU Git Repository

All studios and labs will be submitted via individual course Git repositories that are housed at SLU. You will find your repository already has a directory structure that provides a place for all lab and studio assignments. Your work must be in the appropriate location for the instructor to find it and count it for credit.

A short guide to using SLU's git resources

Textbook and Class Resources

Reccomended Course textbook: Modern Operating Systems by Tanenbaum and Bos. Either the 3rd or 4th Edition works fine. A classic computing textbook on the fundamentals of operating systems, with a bent towards Unix-like operating systems. This book is not required for the course, rather it is a secondary source of information that provides a more comprehensive and textbook-like presentation of the material for students who prefer this. I will not be assigning homework from the book or taking test questions from the book. Access to the book's companion website is not required and will not be used during this course.

Linux skills references:

References for Linux software development.

Software resources:

Secure Shell: My favorite terminal client- runs through the Chrome browser on nearly any platform. Gives a great, consistent interface between Windows, Mac, and Linux. If you've only ever used PuTTY you should really try something else!
Google Search for Shell Emulators: Find something that works for you!
WinSCP: Easily transfer files between your Windows machine and the departmental Linux machines.
scp manual page: Transfer files between your Mac/Linux machine and the departmental Linux machines.

Linux kernel hacking references:

We aren't doing any kernel hacking in this course, but these are great references if you're interested.

Linux Kernel Development by Robert Love, 2010. This is an excellent, compact, and inexpensive text that gives the reader a good understanding of kernel design and critical kernel source code. Written by a Linux kernel veteran.
Understanding the Linux Kernel by Bovet and Cesati, 2006. This is a more exhaustive reference to the kernel than Love's book, covering many data structures and code snippets in detail. Available online for free through the university's subscription to the O'Riley Safari service.
Linux Device Drivers by Corbet, Rubini, and Kroah-Hartman, 2005. The definitive book on hardware device drivers for Linux. Contains some useful reference material over kernel modules, kernel development, kernel locking, timing, and other topics. Available online for free through lwn.net.
LWN.net is a news and information outlet for the open source community. They often run very high quality articles about kernel development, kernel architecture, and kernel mechanisms. When I can't find any good references, searching for "LWN (my_topic)" is usually helpful.
Linux Journal is a magazine covering the Linux community. They often run very high quality articles about kernel development, kernel architecture, and kernel mechanisms. Similar to above, searching for "Linux Journal (my_topic)" often yields good results.
Linux Cross Reference by free-electrons.com This tool easily allows you to browse the Linux source code as well as search for identifiers.
kernel.org the go-to website for Linux kernel source code.

Grading

There are three activities for which you will receive credit in this course: studios, labs, and exams. Studios are daily guided assignments primarily designed to familiarize students with course concepts and development tools (i.e. knowledge and comprehension tasks). Lab assignments will ask students to apply general course concepts and analyze OS design alternatives. A midterm and final exam will evaluate your technical understanding of course concepts.

Studios are graded on the following scale: complete, partial credit, or no credit. Studios will not be turned back with detailed comments. Labs and exams will be graded on a points scale and will be turned back with comments. My goal is to return lab assignments to you within nine days of the deadline, which is an additional 48 hours for late submissions plus one week for grading time. Similarly, my goal is to return exams to you within one week.

Extensions on labs and studios are generally not granted aside from major unexpected events. You have at least a week to complete and submit any studio in this course, and at least two weeks for any lab assignment- it is assumed that this is sufficient for you to work around things such as sporting events or academic conferences on your own time. Please note the automatic 48-hour late policy for lab assignments.

I am happy to work with you on rescheduling exams if you are away from campus for slu-sponsored travel, but you must notify me at least two weeks ahead of time (and note that the exam dates are provided as of the first day of class). Make up exams outside of this policy will only be given for severe and documented reasons.

Your grade will be determined as follows:

Activity	Grade Percentage
Studios	20%
Labs	50%
Midterm	15%
Final	15%

Grading is done on a straight scale (uncurved). The following scores are guaranteed. The grading scale may be curved upwards (in your favor) at the discretion of the instructor.

93% guarantees an A
90% guarantees an A-
87% guarantees a B+
83% guarantees a B
80% guarantees a B-
77% guarantees a C+
73% guarantees a C
70% guarantees a C-
60% guarantees a D

Most work assigned in this course, other than exams and some labs, is expected to be completed collaboratively. Student teams may change from assignment to assignment, but the sharing of written work or significant portions of code between teams is strictly prohibited.

Some specific guidelines for this course:

Code you submit as solutions to the programming assignments must be written by you or your team. You are not allowed to copy code from other students.
Copying pieces of code from in-class examples is allowed, but you must cite the source of such code with a comment denoting the start and finish of the copied section.
Copying small pieces of code from man pages, online references or other sources is generally acceptable, but to be safe you should check with me first. Code from such sources must be cited with a comment denoting the start and finish of the copied section. Knowing how to use online references effectively is an essential skill for modern software developers and I don't want to discourage you from using such sources for understanding APIs and how to call complex functions. It is often the case that there is an expected "right way" to accomplish a specific task such as creating a pThreads thread or binding a socket to an address- lookups of this nature are equivalent to using a textbook or language reference and are fine. Looking up "How do I write my own malloc()" or "How to build my own shell" on the other hand is cheating. If you are in doubt, ask first!
Copied code that is not cited will be considered plagiarism and will be treated as cheating. Citing your code protects you from this. However, copying large portions of code is still grounds for a reduction in grade, even if it is not cheating. Please check with the instructor if you are copying more than a line or two of code!

Attendance

Successful students attend all or mostly all class sessions. This is true in my experience and has been demonstrated in large scale studies as well. In that study, even students who attended nine out of ten class periods had measurably lower class performance than those who attended all classes. However, there is no attendance requirement for this class, and you do not need to get permission when you do miss class. You are an adult and have the freedom to manage your time in whatever way you feel is most useful. Job interviews, conferences, tests in other courses, etc. are all reasonable cases for being absent.

Note that in-class assignments such as tests or quizes cannot be made up outside of class without prior approval from the instructor. All such activities will be listed course schedule with ample time to prepare (i.e. there are no "pop quizes").

If you do miss class you should refer to the course schedule to see what was missed and arrange to get course notes from another student. I am always happy to answer questions but I do not repeat full class periods in office hours.