http://www.read.cs.ucla.edu/111/ 2009-11-21T23:36:00-08:00 http://www.read.cs.ucla.edu/111/ http://www.read.cs.ucla.edu/111/lib/images/favicon.ico text/html 2007-04-02T00:18:42-08:00 http://www.read.cs.ucla.edu/111/2006fall?rev=1175498322 Lectures TR 2-3:50pm, WG Young 2200 (note room change) Lab Sections F 12-1:50pm, Boelter 9436 (Chandra) F 2-3:50pm, Physics & Astronomy Building (PAB) 1749 (Marino) Instructor Eddie Kohler, Boelter 4531C Office Hours M 9-11am, by appointment, or whenever I'm in my office and available TAs Shyamal Chandra (Office Hours: 10:30-11:30 AM TH in 4428 BH) Dan Marino (Office Hours: M 3:30-4:30pm & W 9:30-10:30am in 4405 BH) * Schedule * On the textbook * Paper report (du… text/html 2006-09-26T11:07:54-08:00 http://www.read.cs.ucla.edu/111/2006spring?rev=1159294074 Lectures TR 2-3:50pm, Boelter 2760 Lab Sections F 2-3:50pm, Boelter 2760 F 4-5:50pm, Boelter 2760 Instructor Eddie Kohler, Boelter 4531C Office Hours M 10-11am, by appointment, or whenever I'm in my office and available TAs Chris Frost and Mike Mammarella * Final: Wednesday, June 14, 3-6pm, WG Young Hall CS76 text/html 2007-09-27T23:10:59-08:00 http://www.read.cs.ucla.edu/111/2007spring?rev=1190959859 Lectures MW 2-3:50pm, Geology 3656 Lab Sections F 2-3:50pm, Boelter 5440 Instructor Eddie Kohler, Boelter 4531C Office Hours MW after class, by appointment, or whenever I'm in my office and available TAs David Jurgens (Office Hours: MW 12pm-1pm, Boelter 4405 [Linux lab]) Dan Marino (Office Hours: TR 11am-12pm, Boelter 4405 [Linux lab]) Final Tuesday, June 12, 3-6pm, Boelter 3400 * Schedule * On the textbook * Final preparation * Preparation questions text/html 2007-06-06T11:32:11-08:00 http://www.read.cs.ucla.edu/111/answers?rev=1181154731 Questions for which these are the answers. Group A Questions in Group A A1. False A2. C. Modularity A3. True A4. C A5. B, D A6. True A7. True A8. False A9. A, D A10. True A11. False A12. True A13. True A14. True A15. False A16. False text/html 2006-10-03T11:49:00-08:00 http://www.read.cs.ucla.edu/111/book?rev=1159901340 Our text, Operating Systems Principles, is a prerelease version of a forthcoming textbook written by Jerry Saltzer (Wikipedia) and Frans Kaashoek. Copies are available from Course Reader Material at 1137 Westwood Blvd. near Lindbrook. This page collects some notes on how we're using the textbook in class. text/html 2007-12-06T08:23:48-08:00 http://www.read.cs.ucla.edu/111/cs111?rev=1196958228 Lectures MW 2-3:50pm, Dodd 146 Lab Sections Lab 1A: F 2-3:50pm, Boelter 5419 Lab 1B: F 8-9:50am, Boelter 9436 Instructor Eddie Kohler, Boelter 4531C Office Hours M4-5pm, T11am-12pm, by appointment, or whenever I'm in my office and available TAs Jacob Lacouture (jacobl at cs dot ucla dot edu) (Office Hours: W 11-12 @ 4405BH, TH 4-5 @ 4405BH) Jonathon Salehpour (jsalehpo at ucla dot edu) (Office Hours: W 4-5 @ 4405BH, F 10-11 @ 4405BH) Final F… text/html 2007-11-19T12:50:48-08:00 http://www.read.cs.ucla.edu/111/design?rev=1195505448 Design problems give CS 111 students the opportunity to create OS features "from scratch" without any skeleton code found in the directed sections of the labs. Each team will be assigned a design problem from one of the four labs assigned throughout the quarter. Once assigned, students may choose from the suggested design problems for that lab or devise their own feature with the approval of their TA. text/html 2006-10-10T20:24:38-08:00 http://www.read.cs.ucla.edu/111/design_groups?rev=1160537078 The table below lists your lab partner and the lab for which your team must complete a design problem. Also listed is the section in which you will give your presentation (might not be your usual section if your partner is in a different section). If we have you listed with the wrong lab partner, or if you don't appear in the list, please email Dan or Shyamal. text/html 2006-12-07T13:15:26-08:00 http://www.read.cs.ucla.edu/111/finaltopics?rev=1165526126 * The systems perspective * System: A set of interconnected components that has a specified behavior observed at the interface with its environment * System characteristics * Emergent properties * Propagation of effects * Incommensurate scaling * Trade-offs text/html 2006-12-18T17:08:17-08:00 http://www.read.cs.ucla.edu/111/grades?rev=1166490497 These graphs are called CDFs, or cumulative distribution function graphs. (Strictly speaking they are empirical CDFs or ECDFs.) The X axis shows the range of grades. The Y axis value for a given grade G shows the percentage of students that had grade <= G. CDFs are super useful, please try to get comfortable with them! text/html 2007-09-28T23:27:54-08:00 http://www.read.cs.ucla.edu/111/lab1a?rev=1191047274 Assigned Friday, September 28 "Due" Friday, October 5 at 11:59pm Download skeleton code from CourseWeb Download skeleton code from this site (no CourseWeb username/password required) Overview Lab 1 is divided into two parts. In this first part of the lab, you will be writing the command line parsing portion of an operating system shell. The shell will be completed in the next part of the lab, and will include support for I/O redirection, pipes, and conditional, sequential, and background e… text/html 2006-04-15T16:45:29-08:00 http://www.read.cs.ucla.edu/111/lab1b-builtin?rev=1145144729 In addition to running programs from the file system, shells have builtin commands that provide functionality that could not be obtained otherwise. Our shell will implement two such builtin commands, to change directories (cd) and to exit the shell (exit). text/html 2007-10-14T19:12:59-08:00 http://www.read.cs.ucla.edu/111/lab1b?rev=1192414379 Due Friday, October 19 Skeleton code available on SEASnet October 14: New lab1b-tester.pl available on SEASnet! Overview In this second part of Lab 1 you will build upon your command line parser to make a complete shell which can actually execute the parsed commands. You'll implement support for all commands that can be parsed, which may use features such as I/O redirection, pipes, and conditional, sequential, and background execution. You'll also implement the two internal commands cd and… text/html 2007-11-05T16:18:59-08:00 http://www.read.cs.ucla.edu/111/lab2?rev=1194308339 Quick links: Useful kernel functions / Getting kernel source Download skeleton code at CourseWeb Download latest Lab 2 tester Please note that we are still making updates to the lab manual. Overview In Lab 2, you'll write a Linux kernel module that implements a ramdisk: an in-memory block device. (A block device is basically a device that acts like a disk, supporting random-access read and write operations of fixed-sized units called sectors. Random-access means the disk can read or wri… text/html 2007-11-06T19:27:57-08:00 http://www.read.cs.ucla.edu/111/lab2functions?rev=1194406077 Descriptions of kernel functions you may be unfamiliar with and may find helpful in implementing your lab. Implementation files are given as a helpful pointer for authoritative information on the workings of the functions, their locations are given relative to a linux kernel source tree, e.g. /usr/src/linux/. You may also find the Linux Cross Reference a helpful reference for Linux types and functions (search: Linux Cross Reference identifier search). text/html 2006-04-28T11:27:31-08:00 http://www.read.cs.ucla.edu/111/lab2kernelsource?rev=1146248851 You can skip this section if you are using a lab machine, or if your own machine has the necessary kernel sources already installed. (Red Hat Fedora, for instance, generally has the necessary parts of the kernel sources installed by default.) To check whether your machine already has the files you need, just try compiling your module as above. If it works, you're all set. Otherwise, read on. text/html 2007-11-06T19:36:52-08:00 http://www.read.cs.ucla.edu/111/lab3?rev=1194406612 Due Wednesday, November 21 Quick link: Getting kernel source / Useful kernel functions (Lab 2) Overview In Lab 2, we used a RAM disk block device to teach you about the Linux kernel setting and about synchronization. In Lab 3, you'll learn about file systems by writing your own file system driver for Linux. text/html 2007-05-30T19:44:02-08:00 http://www.read.cs.ucla.edu/111/lab4-eventdriven?rev=1180579442 Event-Driven Programming The conventional way to serve multiple connections simultaneously is simply to fork: to serve each connection from a different process or thread. You may have done this already in CS 118. The Apache web server uses a forking model. Each Apache server process can handle one request at a time; in order to handle concurrent requests, Apache forks a number of "spare server" processes, to which it forwards requests. Performance isn't as bad as it could be, since the spa… text/html 2007-11-19T12:38:15-08:00 http://www.read.cs.ucla.edu/111/lab4?rev=1195504695 Handin Procedure When you are finished, edit the answers.txt file and add your name(s) and email address(es), student ID(s), any challenge problems you may have done. ALSO REMEMBER TO WRITE THE INFORMATION REQUIRED BY TASKS 2 AND 3, INCLUDING WHICH ROBUSTNESS PROBLEMS YOU FIXED, AND HOW YOU MADE YOUR PEER EVIL! text/html 2006-05-13T02:56:09-08:00 http://www.read.cs.ucla.edu/111/labs?rev=1147514169 * Lab 1A: Shell parsing * Lab 1B: Shell execution * Lab 2: Lockable RAM disk * Lab 3: File systems text/html 2007-10-31T17:26:55-08:00 http://www.read.cs.ucla.edu/111/midtermtopics?rev=1193876815 Definitions System. A set of interconnected components that has a specified behavior observed at the interface with its environment. Emergent properties. The commonly observed system characteristic that some properties of a system are not present in the components, but show up only in the aggregate. text/html 2007-05-16T13:21:06-08:00 http://www.read.cs.ucla.edu/111/qemu?rev=1179346866 May 5, 2007: Please note that we have changed DebOSP.tar.gz and the run-qemu script to support Mac OS X and Cygwin machines. If you would like to run the labs from your Mac or Windows (with Cygwin) machine in the same way that you do from the linux lab, by simply calling "./run-qemu", Download the updated lab 2 run-qemu script and the updated DebOSP.tar.gz. text/html 2007-06-06T15:59:16-08:00 http://www.read.cs.ucla.edu/111/questions?rev=1181170756 These relatively simple questions -- mostly true/false or multiple-choice -- are meant to help you prepare for the final. Unless otherwise stated, the questions concern typical operating systems for PC- and server-class hardware, like the ones we've focused on in class. Multiple-choice questions are "circle all that apply". text/html 2007-05-31T23:47:40-08:00 http://www.read.cs.ucla.edu/111/report?rev=1180680460 Due Wednesday, June 6 at 11:59pm Operating systems are still evolving! This paper report will guide you to explore recent operating systems developments, and help demonstrate how concepts from the course can help you understand modern operating systems technology. text/html 2007-11-19T12:50:12-08:00 http://www.read.cs.ucla.edu/111/schedule?rev=1195505412 Schedule/Syllabus Week Date Topic Assignments Week 0 F 9/28 Lab 1a assigned Week 1 M 10/1 Course introduction Scribe notes W 10/3 Operating systems goals I Scribe notes F 10/5 Lab 1a "due", Lab 1b assigned Week 2 M 10/8 Operating systems goals II Scribe notes W 10/10 Process abstraction & implementation Scribe notes Week 3 M 10/15 Process interaction I Scribe notes T 10/16 WeensyOS 1 due… text/html 2007-10-02T08:41:04-08:00 http://www.read.cs.ucla.edu/111/scribeguidelines?rev=1191339664 Everyone will participate at least once in creating a set of scribe notes for a lecture. Three scribes will be assigned at the beginning of each lecture. Notes are due about a week after the lecture. Over the following week, the three scribes will cooperate to produce a single set of notes. The notes will be posted on the Web for everyone's reference.