Introduction to Operating SystemsProf. Darrell LongComputer Science DepartmentJack Baskin School of [email protected] 2002What the catalog says ...Fundamental principles of operating systems: process synchronization, deadlocks, memory management, resourceallocation, scheduling, storage systems, and [the] study of several operating systems. A major programming projectwill be required. Prerequisites: courses CMPS 101 and CMPE 12C.What we will do ...The course will cover the basics of uniprocessor operating systems, paying particular attention to the performanceaspects. This includes, but is not limited to: processes, interprocess communication, synchronization, scheduling,memory management, swapping, virtual memory, page replacement algorithms, segmentation, file systems, security,protection, input/output, interrupts, device management, resource allocation and deadlocks.As we go along, we will also discuss more advanced topics such as distributed operating systems, storage systems,networks, communications protocols, synchronization, atomicity, remote procedure call, distributed file systems andfault tolerance.What you must read ...The primary source for the course will be the text by Tanenbaum. It covers the main topics of uniprocessor operatingsystems in the early chapters, and then covers distributed systems and other advanced topics in the later chapters. It isin its second edition, and is one of the most up-to-date undergraduate operating system texts available.Andrew S. Tanenbaum, Modern Operating Systems, Second Edition, Prentice Hall, 2001.We will cover all the core operating systems issues, but since we only have ten weeks, we will have to skip somelater chapters (for example, the case studies). Additional material, primarily from the research literature, will bepresented when appropriate.What you really ought to read ...If you have some spare time (and spare money), or just want to learn more about operating systems, then the followingtexts may be helpful. The first is a standard introduction to operating systems and contains some material not in theTanenbaum text.Abraham Silberschatz, Peter B. Galvin and Greg Gagne, Operating System Concepts, Sixth Edition, John Wiley& Sons, 2001.Marshall Kirk McKusick, Keith Bostic and Michael J. Karels, The Design and Implementation of the 4.4BSDOperating System, Addison-Wesley, 1996.E. G. Coffman and P. J. Denning, Operating Systems Theory. Prentice-Hall: Englewood Cliffs, 1973 (out ofprint).1Keeping in touch ...You are expected to read your electronic mail daily. It is your primary means of communication with the instructorand with the teaching assistant.You are expected to read (and contribute to) the class news group ucsc.class.cmp111 on a daily basis. Discus-sions of the material and announcements to the entire class appear in this group. Alternatively, you may subscribe tothe class mailing list (http://www.soe.ucsc.edu/mailman/listinfo/cmps111), which is the preferred method if youaccess from off-campus.Programs, Examinations & Exercises ...There will be weekly exercises worth a total of 10% of your total grade. These questions taken from the primarytext and are intended to make sure that you is reading it and to test your understanding of the material from eachchapter.There will be four programming assignments due approximately every two or two and a half weeks, each worth10% of your total grade. You will be implementing several components of an operating system kernel runningatop a simulated DLX processor.There will be a midterm examination at approximately halfway through the quarter that will be worth 20% ofyour grade.There will be a comprehensive final examination worth 30% of your grade.Note: You must average above 50% on the programming assignments and on the examinations in order to passthe source. A score lower than 50% on either portion of the class will result in a failing grade regardless of the totalscore.All examinations and quizzes are closed book. You may bring one   single-sided sheet of notes (the fontmay not be smaller than 10 point) with you. You may not share this sheet with you friends and neighbors.Academic Honesty ...This really should not be an issue, but recent events have made the following necessary. The bottom line is that youare expected to conduct yourself as a person of integrity.You are expected to adhere to the highest standards of academic integrity. This means that plagiarism1in any formis unacceptable. As a (soon to be) computing professional, I encourage you to consult the code of ethics appropriateto your discipline.2Plagiarism will be assumed, until disproved, on work that is essentially the same as that of other students. Thisincludes identically incorrect, off-the-wall, and highly unusual duplicate answers where the probability of a sheercoincidence is extremely unlikely. All parties to this unacceptable collaboration will receive the same (zero) score. Azero score on either examinations or on a segment of the programming project is grounds for failing the course.Your work must be your own. This refers to examinations, written assignments and programming projects. Shouldyou be found to be cheating, at a minimum, you will fail that assignment and a letter will be sent to your Department,the School of Engineering, and to your Provost and academic preceptor. The instructor reserves the right to strongeraction should the situation warrant it.You should bring a picture identification with you to all examinations and be prepared to show it upon request.You may discuss programming projects with your friends, but you are expected to abide by the Gilligan’s Island3rule. The only thing you may bring to such a discussion is you, and no notes may be taken away from the meeting.The copying of code is strictly forbidden.The bottom line is: if you cheat, you will fail the course.1plagiarize vt. [L. plagiarius, kidnaper] to steal and pass off as one’s own (the ideas or words of another) to present as one’s own an idea orproduct derived from an existing source – plagiarizer n. (source: Webster’s New World Dictionary)2The Association for Computing Machinery is http://www.acm.org/, the IEEE is http://www.ieee.org/ and the IEEE Computer Society ishttp://www.computer.org/.3The Gilligan’s Island rule states that following a discussion of the project, a break must be taken for at least a half hour