Overview
In this course we will explore concepts of operating systems both from perspectives of the design side and from the implementation side. The design side will be investigated via lectures (discussions), presentations and reading core system research papers. The implementation side will be realized through several programming projects and homeowork. The programming component will give you a real taste of systems programming and the inner workings of a real-world Operating System.
- Processes.
- Sockets.
- Threads.
- Scheduling.
- Synchronization.
- Deadlock.
- Memory Management.
- Virtual Memory.
- File Systems.
- I/O Systems.
- Mass Storage.
- Distributed Systems.
- Protection & Security.
Topics will be covered either by lecture, reading or both.
Laptops are required. You will need to be able to install a vitual machine on your laptop- such as VMWare or Virtual Box. You will be required to demo projects on your laptop primarily that it compiles and runs. You may use UGA WiFI or mobile network to connect to nike (CS department linux platform) to demonstrate that your programming project compiles and runs appropriately.
The course includes may include 2 movies that we may watch together in class or they may be assigned as homework.
Logististics:
| Date /Time: | Tu/Th: | 2:00 - 3:15 | Dawson Hall 0116 |
| We | 2:30 - 3:20 | Dawson Hall 0116 | |
| Instructor | Th | 3:30 - 4:30 | Maria Hybinette - Office Hours ( ingrid AT uga.edu ) |
| TA (TBD) | Sruthi Palaparthi -- possibly -- ( sruthi.p AT uga.edu ) | ||
| Mailing List | piazza (see schedule when activated) | ||
Course Material & Textbook
The course material covered in class is primarily drawn from two text books: (1) The "Operating System Concepts (9th updated edition - for 2018) by Silberschatz, Galvin and Gagne", or as it is sometimes called the Dinosaur book, and (2) Modern Operating Systems by Andrew Tanenbaum and Woodhull. The second book by Tannenbaum is not required and all its material will be supplied or covered in lectures.
The first textbook, the dinosaur books is required.
The lectures are influenced by additional resources including: William Stallings (previously MIT); Deitel & Deitel’s OS Book and many more, other instructors & colleagues: Andrea & Remzi Arpaci-Dusseau, University of Wisconsin; Andy Wang, (UCLA) now at Florida State University Fred Kuhns, Washington University; Jeff Donahoo, Baylor University (TCP/IP and sockets), Darrell Long, UC Santa Cruz, Chris Kruegel, UC Santa Barbara, students feedback and last but not least Wikipedia.
 |
|
|
Grading Policy and Evaluation:
You are evaluated via exams & quizzes, projects, paper summaries, presentations and implementation of software projects. The distribution is below, but is subject to change.
NOTE: Syllabus & policies are solidified after 3rd week of class - but there still may be minor changes.
Participation : |
10% |
| Exam 1 | 10% |
| Exam 2 (replaced online quizzes) | 10% |
| Final Exam: (take home project, presentation during final exam period & code, report) |
15% |
| Projects (P1-P4) | 30% |
| HW/Summaries (only 2 more for tools talk) | 20% |
| Presentations/Demo (only tool talks remaining) | 05% |
The general grading philosophy is the following (the context is "programs" and "projects" but it should generalize to summaries and to other required elements). See translation from percentage to letter grades finger grade in link further below.
A+ Extraordinary, goes beyond the minimum criteria both in depth and breath. Design is thorough and well thought out, code base and implementation is beautiful- modularized, complete, clear and concise. A well thought out debugging strategy is apparent. Well documented code. The evaluation plan is well executed and well thought out, goes beyond the simple cases and illustrates strong problem solving skills.
A Superior (somewhat less than an A+, almost perfect code, beautiful, concise, minimum criteria met, not as much depth and forethought as an A+ but it is superb), goes beyond meeting the minimum criteria demonstrates depth, can apply solution to a variation of similar problems.
B Good, minimum criteria well executed and well done, shows some depth and understanding, meets most test cases but does not demonstrate as much forethought as an A;
C Fair, minimum criteria met, but could have been executed with more depth and forethought.
We will use the College Board's convention to convert from percent grades to letter grades grades:
(see here).
Late Policy
Assignments, and summaries (if applicable to this class) are due on the date and time specified in the assignment or the day of demonstration (email as a time stamp and hand-in hardcopy the next day). Late homework cannot be accepted.
Homework and Projects Posting
Projects and homework will be posted on the web from the scheduling page (see link top menu bar), and will be accessible from anywhere on the Internet. Assignments may be posted before they are officially assigned; however, you should not assume that an assignment on the schedule page is in final form until the date it is assigned. In other words, assignments are subject to change before the date that they are officially assigned. There may be additional required elements.
The software programming projects are of-course an important component of this course. You'll be making programs of the languages specified in class or on schedule page (e.g., Python, Java, Scala, or C, C++). The programming tools you'll need (game engine, simulation engine, compiler, debugger, etc.) may be denoted on the project page and should be downloaded and installed on your laptop and /or workstation.
Currently the programming languages used in this class are: C and C++ (mostly plain C).
Technical Paper Summaries
You will read/skim at least one technical paper or essay every week. For each week each you will prepare a 1-page summary on one of the presented papers (you may chose any one of the two). This summary must be submitted to the grader before midnight on Friday following the presentation. The summary needs to reflect that you made an effort to read and understand the paper. The summary should address the five questions listed on the slides covering presentations.
The fifth question concerns a brief critique of the delivery of material bu tehe speaker. Here you need to address if pertinent material should have been included, and suggestions on improvements. You may skip up to 2 summaries without a penalty (see reading page link above for specific questions that you need to address). If you submit and cover every week you may be subject to earn bonus points.
Presentations
You will present on 2 topics throughout the semester, each presenter is expected to read additional technical papers (or essays) to ensure breadth of the week's topic. Some suggestions to add "breath" to your theme topic are listed in the reading list, or you may choose your own. You will select the theme, but the specific paper will be assigned (however you may suggest or express interest in particular paper). If we have a large class the presentations may be presented as a group (a group of 2) presentation.
Participation and Attendance
Class attendance is mandatory; we do take attendance frequently, and class participation is 5% of your grade. Excused absences count when taking attendence - we do take it frequently so missing one or two classes should have minor effect on your grade. You may earn bonus points for perfect attendance.
Instructor Enforced Withdrawals
Missing 8 days or more of classes (inclusive of excused absences) is considered excesive absentia and may result in an instructor enforced withdrawal.
Missing 2 scheduled exams (inclusive of excused absences) may result in instructor enforced withdrawal.
Other Class Policies
If you miss class it is your responsibility to find out what you missed if you don't attend class. Please do not email instructor and ask what you have missed - you may ask however after class.
You are required to subscribe to the class email list or forum (Piazza)- and be aware that sometimes homework is assigned or templates are distributed via this forum - or there are some hints posted in the forum - you probably do not want to miss that.
The purpose of the assignments and projects is familiarization of concepts and details of programming.. The assignments & projects are expected to be individual work unless other specified. However, you are encouraged to ask questions of one another, and to respond to other student's questions on the email list.
Direct exchange of code is prohibited, as is line-by-line assistance from anyone or thing (this includes internet copying). This is checked for every assignments. If you do get help from other sources than book, slides, or TA you must acknowledge the source in the material that you turn in -but note still no copying is allowed.
Unless otherwise specified, exams are closed-book and no additional materials may be used. Missing an exam: absence due to serious illness will be an acceptable reason for missing an exam. Doctor's diagnostic note is required (these absences may be confirmed with your doctor). The final grade will be scaled accordingly.
Class Photo: A Previous Class
