http://www.read.cs.ucla.edu/111/ 2009-11-22T16:58:08-08:00 http://www.read.cs.ucla.edu/111/ http://www.read.cs.ucla.edu/111/lib/images/favicon.ico text/html 2006-12-12T18:35:03-08:00 http://www.read.cs.ucla.edu/111/2006fall/answers?rev=1165977303 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/2006fall/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 2006-12-10T18:13:08-08:00 http://www.read.cs.ucla.edu/111/2006fall/design?rev=1165803188 For which lab am I assigned a design problem? 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 (Shyamal Chandra or Dan Marino). text/html 2006-10-10T20:24:38-08:00 http://www.read.cs.ucla.edu/111/2006fall/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/2006fall/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/2006fall/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 2006-10-01T18:50:43-08:00 http://www.read.cs.ucla.edu/111/2006fall/lab1a?rev=1159753843 "Due" Monday, October 9 at 11:59 PM Assigned Saturday, September 30 Download skeleton code 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 execution. text/html 2006-04-15T16:45:29-08:00 http://www.read.cs.ucla.edu/111/2006fall/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-03T10:10:07-08:00 http://www.read.cs.ucla.edu/111/2006fall/lab1b?rev=1191431407 Due Friday, October 20 at 12:00 noon Assigned Friday, October 6 Skeleton code 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 exit, which c… text/html 2006-11-03T00:39:53-08:00 http://www.read.cs.ucla.edu/111/2006fall/lab2?rev=1162543193 Quick links: Useful kernel functions / Getting kernel source Update, 11/2/2006 Some of you have noticed that Linux can block some open attempts before your code gets control. This behavior will help out your bounded wait implementation! However, we want your bounded wait implementation to work independently, so you'll get partial credit if you depend on this behavior. You can avoid some of this behavior (but not all of it) by adding the following lines right at the top of osprd_open: text/html 2006-11-02T09:24:22-08:00 http://www.read.cs.ucla.edu/111/2006fall/lab2functions?rev=1162488262 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/2006fall/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-10-31T16:24:36-08:00 http://www.read.cs.ucla.edu/111/2006fall/lab3?rev=1193873076 Quick link: Getting kernel source 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 2006-11-28T13:26:46-08:00 http://www.read.cs.ucla.edu/111/2006fall/lab4?rev=1164749206 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, and any other information you'd like us to have. You must also include an example URL that crashed the original ospweb with a buffer overflow. Then run make tarball, which will generate a file lab4-yourusername.tar.gz inside the lab4 directory. Upload this file to CourseWeb using a web browser to turn in the project. text/html 2006-05-13T02:56:09-08:00 http://www.read.cs.ucla.edu/111/2006fall/labs?rev=1147514169 * Lab 1A: Shell parsing * Lab 1B: Shell execution * Lab 2: Lockable RAM disk * Lab 3: File systems text/html 2006-11-04T10:04:50-08:00 http://www.read.cs.ucla.edu/111/2006fall/midtermtopics?rev=1162663490 * 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-11T18:43:06-08:00 http://www.read.cs.ucla.edu/111/2006fall/questions?rev=1165891386 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 2006-11-29T15:09:04-08:00 http://www.read.cs.ucla.edu/111/2006fall/report?rev=1164841744 Due Wednesday, December 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-04-02T00:19:58-08:00 http://www.read.cs.ucla.edu/111/2006fall/schedule?rev=1175498398 Schedule/Syllabus Textbook chapters are best if read before the class, but may be read after as well. Week Date Topic Textbook chapters Week 0 R 9/28 Course introduction Scribe notes Ch. 1 Week 1 T 10/3 Interfaces & abstractions Scribe notes Ch. 2 (Notes) R 10/5 Virtualization & threads Scribe notes Ch. 4 pp 1-15, Ch. 5 pp 1-13 (Notes) Week 2 M 10/9 Lab 1A checkpoint due T 10/10 Process implementation Scribe notes Ch. 5 pp 61-7… text/html 2006-09-29T02:32:25-08:00 http://www.read.cs.ucla.edu/111/2006fall/scribeguidelines?rev=1159522345 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.