|Lecture:||Mon 7:10P - 9:00P Weaver CIWW 1302|
|Instructor:||Hubertus Franke, email@example.com, Background of the Instructor|
|TAs/Graders:||Salil Kapur, firstname.lastname@example.org|
|TAs/Graders:||Mi Fang, email@example.com|
[0-9] Hubertus Franke: Mon 6:15 - 7:00 PM Room Weaver 320 and after class
[A-J] Salil Kapur: Thu 3:00 - 4:00 PM CIWW 13th floor (lounge)
[K-Z] Mi Fang: Wed 4:00 - 5:00 PM CIWW 13th floor (lounge)
You can go to any office hour, but grading related stuff you need to talk to your assigned TA. Also, please ask questions on the NYU classes forum to get quick answers. Anybody (Prof, TAs, students) should help answer questions (other than providing code) to make the class a success for everybody.
Common CS knowledge and programming skills.|
Four labs consisting of approximately 500-600 lines of code each (give and take). Expect at least 20hrs per lab, typically spread over 3 weeks. This class is designated as a class to emphasize programming in C/C++ and as most operating systems are written in C this is a perfect opportunity to pick this skill up. As a result all labs will have to be coded in C/C++. Learning how to become proficient in C/C++ is one side goal of this class. Expect to learn C/C++ through self study over the first 3 weeks. If necessary, an extra session will be provided to get you up to speed, which will take place after class ( > 9PM ) [ just let me know a few days in advance ].
Author: Andrew Tannenbaum|
Title: Modern Operating Systems
Edition: 4th (you will also be OK with 3rd)
Publisher: Prentice Hall
ISBN-13: 978-0-12-3591720 or 978-0-13-6006663-2
ISBN-10: 0-13-359172X or 0-13-600663-9
Examples will be from Unix/Linux. Programming assignments will be based on C or C++ as Operatings Systems are implemented that way. You will initially not be required to have C or C++ knowledge, but after the first of four labs you will have to move over to C/C++. Each of the four labs is approximately 600 lines of code.This course does not assume that you have taken an Operating Systems course as an undergraduate, or that you have had extensive experience working with one. In fact, if you have taken such a course or have a fair amount of practical experience with OS internals, this course is probably too elementary for you. Please take a look at the course schedule to get a sense of the topics that will be covered: if you can explain most of the terms contained there, you are likely looking for a more advanced course. We will NOT be "hacking" on an operating system but will have lab assignments that deal with the fundamental elements such as different process schedulers and memory management algorithms and I/O schedulers. It will allow you to get and experiment with the concept rather than spending endless hours debugging tedious operating system code.
Grades are based on the labs, the midterm and final exam, each being important.
The weighting will be:
||Introduction: Computer System Architectures (what does the OS manage)
||Start Learning C/C++
||Introduction: Computer System Architectures and Syscalls)
||Processes and Threads
Processes and Threads
||Chapter 2.3 + 6
||Midterm (1hr) + Memory Management
||Rub your good luck charm
and study of course
Several labs (programming assignments) across the semester will provide practical implementations of operating system concepts such as processor scheduling and memory management. These assignments are accepted in C or C++.
You may solve lab assignments on any system you wish, but ...
Good methods for obtaining help include
|Graduate cs.nyu.edu courses:||http://cs.nyu.edu/webapps/fall2017/courses|
|Graduate cs.nyu.edu schedule:||http://cs.nyu.edu/webapps/fall2017/Graduate/courses|
|Academic integrity policy:||http://cs.nyu.edu/web/Academic/Graduate/academic_integrity.html|