operating-systems
operating-systems copied to clipboard
Teaching resources (OER) for Operating Systems
Watch course recordings and add diagrams and demos that are not already in.
Currently, slides for the Data chapter are part of a single [`slides.mdpp` file](https://github.com/open-education-hub/operating-systems/blob/master/content/chapters/data/lecture/slides.mdpp). This is inconsistent with the rest of the chapters that use `slides.mdpp` as an index that includes...
File interface and socket interface diagrams present the system components horizontally [1]. It is more intuitive to present components vertically, as they appear in the Software Stack (Application > OS...
The [OS Cloud section](https://open-education-hub.github.io/operating-systems/Lab/Application-Interaction/SO%20Cloud/content/so-cloud) has given students trouble regarding nested virtualisation. The [Prerequisites subsection](https://open-education-hub.github.io/operating-systems/Lab/Application-Interaction/SO%20Cloud/content/so-cloud#prerequisites) only provides details for VirtualBox users on Linux. It should be updated with the following: -...
The I/O chapter presents many communication channels (pipes -- named and anonymous --, sockets -- UNIX and network --, shared memory etc.), but makes no parallel between them. Some images...
Building [the website](https://open-education-hub.github.io/operating-systems/) locally is tedious, takes a very long time, and 20GB+ of disk space. This makes it difficult to test changes to the documentation. The solution is to...
Right now we don't have any issue templates and this leads to the fact that people create issues without all the details and without any labels. It would be nice...
Right now we don't have any PR templates and this leads to the fact that people create PR without a proper description. It would be nice to have some templates...
[Intro] page is empty. It doesn't contain the general information mentioned there. [Intro]: https://open-education-hub.github.io/operating-systems/
There is currently plenty of duplicate code between `support/` and `solution/` directories for labs. The best approach is to only provide the `solution/` folder inside the repository. And the `support/`...