http://www.read.cs.ucla.edu/111/ 2009-11-23T09:05:55-08:00 http://www.read.cs.ucla.edu/111/ http://www.read.cs.ucla.edu/111/lib/images/favicon.ico text/html 2006-09-26T11:37:17-08:00 http://www.read.cs.ucla.edu/111/2006spring/grades?rev=1159295837 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-04-07T12:14:01-08:00 http://www.read.cs.ucla.edu/111/2006spring/lab1a?rev=1144437241 Lab 1A: CS 111, Spring 06 "Due" Friday, April 14th at 12:00 PM Assigned Friday, April 7th 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/2006spring/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:11:00-08:00 http://www.read.cs.ucla.edu/111/2006spring/lab1b?rev=1191431460 Lab 1B: CS 111, Spring 06 Due Friday, April 28th at 12:00 PM Assigned Saturday, April 15th 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 change th… text/html 2006-05-10T23:47:40-08:00 http://www.read.cs.ucla.edu/111/2006spring/lab2?rev=1147330060 Quick links: Useful kernel functions / Getting kernel source Overview In Lab 2, you'll get your hands dirty inside the Linux kernel! You will write a kernel module -- code that can be dynamically downloaded into the kernel -- that implements a ramdisk: an in-memory block device. (A block device is basically a device that acts like a disk.) text/html 2006-05-08T16:16:08-08:00 http://www.read.cs.ucla.edu/111/2006spring/lab2functions?rev=1147130168 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/2006spring/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 2006-09-26T11:38:02-08:00 http://www.read.cs.ucla.edu/111/2006spring/lab3?rev=1159295882 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-05-13T02:56:09-08:00 http://www.read.cs.ucla.edu/111/2006spring/labs?rev=1147514169 * Lab 1A: Shell parsing * Lab 1B: Shell execution * Lab 2: Lockable RAM disk * Lab 3: File systems text/html 2006-05-06T10:28:32-08:00 http://www.read.cs.ucla.edu/111/2006spring/midtermtopics?rev=1146936512 * Operating systems and abstract machines * An OS is software that provides programs with access to an abstract machine * Protection and sharing * Operating system goals * Performance * Robustness (Safety) * Isolation/Protection text/html 2006-06-08T10:35:35-08:00 http://www.read.cs.ucla.edu/111/2006spring/report?rev=1149788135 Due Friday, June 9 at 11:59pm Operating systems are still evolving! This paper report is designed to guide towards recent operating systems developments, and to demonstrate how concepts from the course can help you understand modern operating systems technology. text/html 2006-09-26T11:02:47-08:00 http://www.read.cs.ucla.edu/111/2006spring/schedule?rev=1159293767 Schedule/Syllabus Week Date Topic Background reading Week 1 T 4/4 Course introduction Scribe notes Ch. 3 & 4 R 4/6 OS overview: bootstrapping & files Scribe notes Ch. 2.2-2.3, 3.1-3.2, 6.1-6.4 Week 2 T 4/11 Processes & process implementation Scribe notes Ch. 6.1-6.4 R 4/13 Processes & threads Scribe notes Ch. 6.5-6.8 F 4/14 Lab 1A checkpoint due Week 3 T 4/18 Threads & signals Scribe notes Ch. 7 R 4/20 Sch… text/html 2006-04-17T10:44:55-08:00 http://www.read.cs.ucla.edu/111/2006spring/scribeguidelines?rev=1145295895 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. Over the following week, they will cooperate to produce a single set of notes. The notes will be posted on the Web for everyone's reference.