Operating Systems (CIS-4020) Labs

In this course, the labs are relatively long, complicated, and open-ended. In some labs, you will be writing Linux kernel modules. Use this skeleton as a starting point. In some labs, you may want your module to provide a /proc file that "contains" a significant amount of material. Use this skeleton as a starting point.

DevBox and HackBox. Here you will set up and experiment with the virtual machines that we will use for operating system development. Install both DevBox and HackBox in some suitable location and then run through at least some steps in Section 5 of the DevBox and HackBox document. Don't worry if you don't get to all the steps. LaTeX source of the DevBox and HackBox document.

If you are curious, you may also wish to browse over my Compiling Linux document. The bulk of what is described there has already been done for you. However, you may find the information useful if you need to recompile the kernel in some special way. LaTeX source of the document. This document is licensed under the GNU Free Documentation License.
Counting System Calls. In this lab you will modify the kernel to count the number of times each system call is invoked. You will also write a module that creates a /proc file providing access to the count information. Slides describing the lab.
Fork Watcher. In this lab you will modify the Linux kernel to gather information about each fork system call that is executed. As with the counting system calls lab you will also write a module that creates a /proc file providing access to the gathered information. Slides describing the lab.
Scheduling Simulation. In this lab you will write a program that simulates several CPU scheduling algorithms so you can compare their performance.
GenericFS. In this lab you will experiment with the GenericFS file system for Linux. The exact content of this lab varies from year to year depending on the current state of GenericFS. The lab focuses on file system implementation and layout.
— Labs below are subject to change —
Shared Memory. In this lab you will experiment with System V shared memory segments. This exposes you to an important System V IPC facility and also gives you practice thinking about the memory management services provided by the kernel.
Device Drivers. In this lab you will write a simple character mode device driver for QNX. Use the skeleton resource manager discussed in class as the starting point for your driver.

Additional Labs

There are a number of other good topics that could be explored in lab. For example, here are some possibilities.

Kernel Threads. In this lab you will explore Linux kernel thread sychronization by writing a module that creates two threads serving as a producer/consumer pair.
Phoenix. In this lab you will experiment with the Phoenix micro-kernel. The exact content of this lab varies from year to year depending on the current state of Phoenix. The lab focuses on scheduling and process management.
A proper memory management lab.
Install an experimental OS (Plan 9?) and play with it.
Reader/Writer locks as an example of implementing a synchronization primitive from lower level primitives.
Explore one of the less commonly used Linux file systems such as XFS or JFS. Perhaps the performance of the systems should be evaluated.
Something with logical storage management.
Build a small cluster and look at OS issues related to cluster management.
QNX Introduction. In this lab you will explore the basics of the QNX operating system including the kernel's support for message passing.
QNX Serial Driver. In this lab you will write a device driver for the QNX operating system. Support files needed for the lab. 16550 UART datasheet.
A QNX lab that looks at real time issues.
Distributed Mutual Exclusion. In this lab you will implement Lamport's distributed mutual exclusion algorithm. A solution in Java: DMutexDemo.java, DistributedQueue.java. A skeleton solution in C++: DMutexDemo.cpp, DistributedQueue.hpp.