Difference between revisions of "CMSC412 - Operating Systems"
From CS 400 Level Course Wiki
(Created page with "{{ClassPage|CMSC412: Operating Systems (4 credits)|Neil Spring|https://www.cs.umd.edu/class/fall2015/cmsc412/ , for example.|The operating system is always running and has com...") |
|||
| Line 1: | Line 1: | ||
{{ClassPage|CMSC412: Operating Systems (4 credits)|Neil Spring|https://www.cs.umd.edu/class/fall2015/cmsc412/ , for example.|The operating system is always running and has complete power over the entire machine: it chooses which programs to run and when, how to organize files on a disk, which processes should get the most memory, and how different processes can communicate. Your task will be to implement pieces of an operating system including virtual memory, a file system, synchronization primitives (maybe), a device (maybe), fork and pipe (maybe). A bug can be catastrophic and elusive. In understanding how these features are built, you will be able to design code that better exploits the underlying hardware, write lightweight operating system features for embedded hardware, and sharpen your debugging skills.|10-20 hours. It's a four-credit class. The amount of time students spend on the assignments varies widely, and depends largely on their ability to write code that starts with not too many bugs and then the time to reason through any remaining errors.|C|A B or better in 216, or experience in another C-based course (possibly 417) or heavy programming course. Concretely, a student should have no question on whether to use the & operator or the * operator when dealing with pointers and should understand the difference between sizeof() and strlen(). |The past syllabus can be found at https://www.cs.umd.edu/class/fall2015/cmsc412/syllabus.pdf . ~45% exams, ~35% projects, some quizzes, participation, etc. No group work outside class.|Qualified CS students do very well in 412; do not be intimidated by CE's.|0101 TuTh 11:00am - 12:15pm CSI 1121MW 12:00pm - 12:50pm CSI 1121 Discussion | {{ClassPage|CMSC412: Operating Systems (4 credits)|Neil Spring|https://www.cs.umd.edu/class/fall2015/cmsc412/ , for example.|The operating system is always running and has complete power over the entire machine: it chooses which programs to run and when, how to organize files on a disk, which processes should get the most memory, and how different processes can communicate. Your task will be to implement pieces of an operating system including virtual memory, a file system, synchronization primitives (maybe), a device (maybe), fork and pipe (maybe). A bug can be catastrophic and elusive. In understanding how these features are built, you will be able to design code that better exploits the underlying hardware, write lightweight operating system features for embedded hardware, and sharpen your debugging skills.|10-20 hours. It's a four-credit class. The amount of time students spend on the assignments varies widely, and depends largely on their ability to write code that starts with not too many bugs and then the time to reason through any remaining errors.|C|A B or better in 216, or experience in another C-based course (possibly 417) or heavy programming course. Concretely, a student should have no question on whether to use the & operator or the * operator when dealing with pointers and should understand the difference between sizeof() and strlen(). |The past syllabus can be found at https://www.cs.umd.edu/class/fall2015/cmsc412/syllabus.pdf . ~45% exams, ~35% projects, some quizzes, participation, etc. No group work outside class.|Qualified CS students do very well in 412; do not be intimidated by CE's.|0101 TuTh 11:00am - 12:15pm CSI 1121MW 12:00pm - 12:50pm CSI 1121 Discussion | ||
| − | 0102 | + | <br /> 0102 TuTh 11:00am - 12:15pm CSI 1121 MW 1:00pm - 1:50pm CSI 1121 Discussion}} |
