Lecture 1:Lecture 1:Course IntroductionCourse IntroductionCSE 120: Principles of Operating SystemsAlex C. SnoerenLab 0 Due Tuesday 10/03CSE 120 – Lecture 1: Course Introduction 2Lecture 1 OverviewLecture 1 Overview Class overview What is an operating system? Operating systems and hardware Operating systems and applicationsCSE 120 – Lecture 1: Course Introduction 3PersonnelPersonnel Instructor: Alex C. Snoeren◆ Office hours Thursdays 2-3pm or by appointment◆ EBU3B 3114 Discussion TA: Vikram Mavalankar◆ Discussion Wed 12-12:50pm in HSS 1330◆ Office hours Wed 1-2pm◆ Homework grader Project TA: John Fisher Ogden◆ Lab hours TBD, email◆ EBU3B 3262◆ Project graderCSE 120 – Lecture 1: Course Introduction 4CSE 120 Class OverviewCSE 120 Class Overview Course material taught through class lectures,textbook readings, and handouts Course assignments are◆ Homework questions (mostly from the book)◆ Three large programming projects in groups Discussion sections are a forum for asking questions◆ Lecture material and homework◆ Additional OS topics (e.g., how does an OS boot?) Other forums◆ Mailing list ([email protected])◆ Discussion board (http://webboard.ucsd.edu)CSE 120 – Lecture 1: Course Introduction 5HomeworksHomeworks There will be 4-5 homeworks throughout the quarter◆ Reinforce lecture material…no better practice Collaboration vs. cheating◆ You should discuss homework problems with others» You can learn a lot from each other◆ But there is a distinction between collaboration and cheating◆ Rule of thumb: Discuss together in library, walk home, andwrite up answers independently◆ Cheating is copying from other student’s homeworks orsolution sets, searching for answers on the Web, etc.◆ Suspicious homeworks will be flagged for reviewCSE 120 – Lecture 1: Course Introduction 6TextbookTextbook Silberschatz, Galvin, and Gagne, Operating SystemConcepts, John Wiley and Sons, 7th Edition, ISBN 0-471-69466-6CSE 120 – Lecture 1: Course Introduction 7Nachos ProjectNachos ProjectCSE 120 – Lecture 1: Course Introduction 8NachosNachos Nachos is an instructional operating system◆ It is a user-level operating system and a machine simulator» Not unlike the Java runtime environment» Will become abundantly clear (or not so clear) very soon◆ Programming environment will be C++ on Unix (Linux/Solaris)◆ The projects will require serious time commitments» Waiting until the last minute is not an option You will do three projects using Nachos◆ Concurrency and synchronization◆ Multiprogramming◆ Virtual memory You will work in groups of 1-4 on the projects◆ Start identifying partners nowCSE 120 – Lecture 1: Course Introduction 9LabsLabs We will use the uAPE (B230) lab in the basement ofthe CSE/EBU3B building◆ Linux running on Intel machines You can also use your home machine◆ The project source will work on Solaris (but not Windows)◆ Graders will test on uAPE machines◆ Be sure to test your projects there as wellCSE 120 – Lecture 1: Course Introduction 10ExamsExams Midterm◆ Tuesday, October 24th◆ Covers first half of class Final◆ Tuesday, December 5th◆ Covers second half of class + selected material from first part» I will be explicit about the material covered No makeup exams◆ Unless dire circumstances (we all want to start vacation early) Crib sheet◆ You can bring one double-sided 8.5x11” page of notes toeach exam to assist you in answering the questions◆ Not a substitute for thinkingCSE 120 – Lecture 1: Course Introduction 11GradingGrading Homeworks: 20%◆ Think of these collectively as a take-home midterm Midterm: 20% Final: 30% Projects: 30%◆ Each Nachos project is 10% of your final gradeCSE 120 – Lecture 1: Course Introduction 12How How No tNo t To Pass CSE 120 To Pass CSE 120 Do not come to lecture◆ It’s nice out, the slides are online, and the material is in thebook anyway◆ Lecture material is the basis for exams and directly relates tothe projects Do not do the homework◆ It’s only 20% of the grade◆ Excellent practice for the exams, and some homeworkproblems are exercises for helping with the project◆ 20% is actually a significant fraction of your grade (differencebetween an A and a C)CSE 120 – Lecture 1: Course Introduction 13How How No tNo t To Pass (2) To Pass (2) Do not ask questions in lecture, office hours, or email◆ Professor is scary, I don’t want to embarrass myself◆ Asking questions is the best way to clarify lecture material atthe time it is being presented◆ Office hours and email will help with homeworks, projects Wait until the last couple of days to start a project◆ We’ll have to do the crunch anyways, why do it early?◆ The projects cannot be done in the last couple of days◆ Repeat: The projects cannot be done in the last couple of days◆ Some groups last time learned that starting early meantfinishing all of the projects on time…and some didn’tCSE 120 – Lecture 1: Course Introduction 14Class Web PageClass Web Pagehttp://www. cs.ucs d.edu/ classes/fa06 /cse12 0/ Serves many roles…◆ Course syllabus and schedule (updated as quarterprogresses)» Lecture slides◆ Announcements◆ Homework handouts◆ Project handouts (tons of info on Nachos, start now)CSE 120 – Lecture 1: Course Introduction 15QuestionsQuestions Before we start the material, any questions about theclass structure, contents, etc.?San DiegoSan DiegoOctober 4-7, 2006October 4-7, 2006 Over 1,000 women in computing Events for undergraduates considering careers andgraduate school Events for graduate students Parties, company representatives, and more!The Anita Borg Institute for Women and Technology and the Association for Computing Machinery Present Volunteers Needed!Volunteers Needed!http://www.cs.ucsd.edu/~bsimonhttp://www.cs.ucsd.edu/~bsimonFree registration!Free registration!CSE 120 – Lecture 1: Course Introduction 17WiC WiC Keynote SpeakersKeynote Speakers Shirley Tilghman,President, Princeton University Sally Ride,former NASA astronaut andUCSD professor Helen Greiner,President, iRobotCSE 120 – Lecture 1: Course Introduction 18Why Operating Systems?Why Operating Systems? Why are we making you sit here today, having tosuffer through a core course in operating systems?◆ It’s not like everyone will become OS developers, after all Understand what you
View Full Document