📄 http:^^www.eecs.umich.edu^~aprakash^482.html^
字号:
Date: Tue, 26 Nov 1996 19:10:28 GMT
Server: Apache/1.1-dev
Content-type: text/html
Set-Cookie: Apache=gs35934584903542817; path=/
<HTML><HEAD><TITLE>UM-EECS: EECS 482</TITLE></HEAD><BODY BGCOLOR="#FFFFFF"><H2> EECS 482: Fall 1996</H2><B>Introduction to Operating Systems</B><P><B>Professor: Atul Prakash<BR>Class time: TTH 10:30-12:00<BR>Class location: 1500 EECS<BR>Office: 3217 EECS Bldg<BR>Office hours: T 1:30-2:30, TH 2:30-3:30<BR>Phone and voice mail: 763-1585<BR>Email: <!WA0><A HREF="mailto:aprakash@umich.edu">aprakash@umich.edu</A><BR><BR>TA 1: Hengming Zou<BR>Discussions: W 12:30-1:30 3424 EECS, W 2:30-3:30 3427 EECS <BR>Office Hours: W 1:30-2:30 and W 3:30-5:30 (2420 EECS) <BR>Email: <!WA1><A HREF="mailto:zou@eecs.umich.edu"> zou@eecs.umich.edu</A> <BR><BR>TA 2: Wengming Jiang <BR>Discussions: W 11:30-12:30 3433 EECS, TH 3:30-4:30 3433 EECS <BR>Office Hours: T 3:00-4:30, F 10:30-12:00 (2420 EECS) <BR>Email: <!WA2><A HREF="mailto:weijiang@engin.umich.edu"> weijiang@engin.umich.edu </A><BR>TA 3: Shailesh Nalawadi<BR>Discussions: M 11:30-12:30 3433 EECS, M 12:30-1:30 3424 EECS <BR>Office Hours: M 4:00-5:00, F 3:00-5:00 (2420 EECS) <BR>Email: <!WA3><A HREF="mailto:nalawad@engin.umich.edu"> nalawad@engin.umich.edu </A><BR><BR><BR>Newsgroup: <!WA4><A HREF="news:umich.eecs.class.482"> umich.eecs.class.482 </A> <BR><!WA5><A HREF="http://www.eecs.umich.edu/~aprakash/482notes/schedule"> APPROXIMATE SEMESTER SCHEDULE </a> <BR><!WA6><A HREF="http://www.eecs.umich.edu/~aprakash/482notes/index.html"> CLASS NOTES, HANDOUTS, ANNOUNCEMENTS, etc. </a> <BR></B><BR><BR><BR>EECS 482 is an introductory course in operating systems at seniorundergraduate level or first-year graduate level. The objective of the course is to familiarize you with the issues involved in the design and implementationof modern operating systems. The concepts discussed areapplicable to a variety of systems. However, we will discuss manyexamples that are drawn from historically significant and modernoperating systems including Multics, UNIX, Mach, and Windows NT.<P>Topics to be discussed include processes and threads, interprocesscommunication, concurrency and synchronization, deadlockscommunication in distributed systems including remote procedurecalls. CPU scheduling, virtual memory management, input-output systems, disk scheduling, file systems, and protection and security.<P>Students are expected to have extensive programming experience priorto this course. Knowledge of the C/C++ programming language andfamiliarity with Unix is required.<P><B> Prerequisites </B> <BR> <P>Computer Organization (EECS 370) and Data Structures (EECS 380) are essential.<P><B> Class Textbook </B> <BR><P><li> Operating System Concepts, 4th Edition by Silberchatz and Glavin,Addison-Wesley.<li> Supplemental reading material and notes provided during the semester.<P><B> Other Suggested Textbooks </B> <BR><P><li> Advanced Programming in the Unix Environment by Stevens, Addison-Wesley<li> Modern Operating Systems by Tanenbaum, Prentice-Hall<P><B>Assignments<BR></B><P>You will complete four programming projects, working individually orin groups of two (your decision), relating to the implementation ofoperating systems. All the programming will be in the C or C++programming language. You should be prepared to spend substantialamount of time on the readings and on programming projects.<P>There will also be several homework assignments, to be done individually.<P><B>Grading</B> <BR><P>Grades will be based on two exams, four programming assignments, andseveral homeworks according to the following tentative weightage:<P><li> Homeworks: 15% <li> Midterm: 20% <li> Final: 25% <li> Four programming projects: 40%<P>From my experience in teaching software courses in the past, mostpeople do very well on programming projects. So, exams and homeworksend up being the distinguishing factors that determine the grade formost students. On the other hand, doing poorly on the programmingprojects is a sure way to fail the course.<P>Also, note that your grade is only determining your performance duringthe term. It is not determining your future potential, how well youwill be able to apply the course in your employment, etc. And, in theend, how well you do in the future is what really matters. So, it isimportant to not lose sight of the bigger picture beyondgrades. Instead, simply focus on doing the course to the best of yourpotential and making sure to take advantage of TAs any myself to learnthe material. Many employers treat the knowledge of the material inthe course as being a true test of an experienced software practioner!<P><B> Policy on Collaboration<BR></B><P>Unethical behavior such as copying/modifying someone else's projectassignment code, looking into other students' directories for materialwhen they do not expect you to, copying homeworks, etc., is notpermissible.<P>On the other hand, you are encouraged to discuss homework problems andproject assignments with each other. That fosters learning and most ofthe work in computer industry is done as a team effort. In such acase, please write the names of the students you discussed homeworksor projects on your submissions. However, note that the homeworksolutions or actual code must not be shared. Homeworks must be writtenindividually and any code submitted must be yours (unless instructor'spermission is taken and the source acknowledged).<P><B> Class Communication Tools </B><P>We will use a variety of mechanisms to communicate within theclass. Most will have links from the <!WA7><a href="http://www.eecs.umich.edu/~aprakash/482.html"> EECS 482 home page </a> athttp://www.eecs.umich.edu/~aprakash/482.html. Tools willinclude class newsgroup, an experimental Java-based chat facility, and of course email. Also, we will attempt to providemost of the handouts on-line.</BODY></HTML>⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -