Lab Tasks
On this page you find the Lab tasks accompanying the Operating-System Construction course. In addition to the task descriptions we also provide a Git repository with partial implementations that you should use as a basis for your own solutions. For many C++ classes, we only provide an empty class body that you must complete; other classes are fully implemented (mostly those that are complicated to implement, but actually do boring things).
You can find the template code in a (read-only) Git repository under this URL: https://os.inf.tu-dresden.de/Studium/OSC/SS2025/oostubs.git
Throughout the semester we will push a new commit for each task to this repository. Clone it (git clone https://os.inf.tu-dresden.de/Studium/OSC/SS2025/oostubs.git) and get the necessary changes for later tasks via git pull (see "Pro Git" for further documentation on Git).
In case you want to host your code on a public repository website like GitHub for collaboration within your team, please do this in a "private" repository.
| # | Short Description | Start | Submission* | Git Tag |
|---|---|---|---|---|
| 1 | Input/Output Functionality | 2025-04-07 | 2025-04-23 | task1 |
| 2 | Interrupt Handling | 2025-04-21 | 2025-05-07 | task2 |
| 3 | Interrupt Synchronization | 2025-05-05 | 2025-05-20 | task3 |
| 4 | Context Switching | 2025-05-19 | 2025-06-04 | task4 |
| 5 | Time-Slice Scheduling | 2025-06-02 | 2025-06-25 | task5 |
| 6 | Events and Synchronization | 2025-06-16 | 2025-07-09 | task6 |
| 7 | Applications for OOStuBS | 2025-06-24 | 2025-07-15 13:00 | task7 |
* You are encouraged to submit before the deadline during Lab hours, especially for the later tasks. This reduces our (and your) stress on the submission date, allows you to fix issues and resubmit if necessary, and gives you more time for preparing your custom task #7 submission.
In order to work on these tasks, you first need to get your development environment working. We also provide a collection of typical mistakes during OOStuBS development, and the symptoms they (may) come with [TODO]. If you encounter mysterious crashes, check this list, maybe it helps.
In case you need an additional challenge, starting with Lab task 3 we also provide template code for MPStuBS, an extension of OOStuBS for multi-processor systems. The accompanying template code can be found in the "mpstubs" branch of the Git repository. This template overwrites a few files; as it bases on solutions of already solved tasks, you definitely will see merge/rebase conflicts. One option to deal with these conflicts is to discard the respective local versions of the affected files.