Merge branch 'cs-pub-ro:main' into private

Author: raress04

.checkpatch.ignore

@@ -1,3 +1,4 @@
 # Ignore directories containing third-party files
 chapters/compute/synchronization/drills/tasks/threadsafe-data-struct/support
 content/assignments/async-web-server/src/http-parser
+content/assignments/elf-loader/tests

.github/workflows/lab-archive.yml

@@ -37,6 +37,13 @@ jobs:
             exit 0
           fi
 
+          git config user.name "github-actions[bot]"
+          git config user.email "github-actions[bot]@users.noreply.github.com"
+
+          ls -A *.zip > zip-list
+          git add *.zip
+          git stash
+
           # Create or switch to lab-archives branch
           if git ls-remote --exit-code origin lab-archives; then
             git fetch origin lab-archives
@@ -46,15 +53,12 @@ jobs:
             git rm -rf .
           fi
 
+          # Remove old archives
+          for f in $(cat zip-list); do rm "$f"; git rm "$f"; done
+          git commit -m "Remove outdated lab archives for commit $GITHUB_SHA"
+
           # Copy new zips into branch root
+          git stash pop
           git add *.zip
-
-          # Only commit if there are changes
-          if ! git diff --cached --quiet; then
-            git config user.name "github-actions[bot]"
-            git config user.email "github-actions[bot]@users.noreply.github.com"
-            git commit -m "Update lab archives for commit $GITHUB_SHA"
-            git push origin lab-archives
-          else
-            echo "No changes to commit."
-          fi
+          git commit -m "Update lab archives for commit $GITHUB_SHA"
+          git push origin lab-archives

.gitignore

@@ -15,7 +15,6 @@
 *.war
 *.nar
 *.ear
-*.zip
 *.tar.gz
 *.rar
 

chapters/compute/overview/reading/lab6.md

@@ -0,0 +1 @@
+The contents of the lab are located in the [lab archive](https://github.com/cs-pub-ro/operating-systems/raw/refs/heads/lab-archives/Lab_6_Multiprocess_and_Multithread.zip) and in the [GitHub repository](https://github.com/cs-pub-ro/operating-systems).

chapters/compute/overview/reading/lab8.md

@@ -0,0 +1 @@
+The contents of the lab are located in the [lab archive](https://github.com/cs-pub-ro/operating-systems/raw/refs/heads/lab-archives/Lab_8_Synchronization.zip) and in the [GitHub repository](https://github.com/cs-pub-ro/operating-systems).

chapters/compute/processes/drills/tasks/create-process/README.md

@@ -1,11 +1,12 @@
 # Create Process
 
-Enter the `chapters/compute/processes/drills/tasks/create-process/` directory, run `make skels`, open the `support/src` folder and go through the practice items below.
+Enter the `create-process/` directory (or `chapters/compute/processes/drills/tasks/create-process/` if you are working directly in the repository).
+Run `make` and then enter `support/` folder and go through the practice items below.
 
 Use the `tests/checker.sh` script to check your solutions.
 
 ```bash
-./checker.sh
+./tests/checker.sh
 exit_code22 ...................... passed ... 50
 second_fork ...................... passed ... 50
 100 / 100

chapters/compute/processes/drills/tasks/sleepy/README.md

@@ -2,12 +2,13 @@
 
 ## Higher level - Python
 
-Enter the `chapters/compute/processes/drills/tasks/sleepy` directory, run `make skels`, open the `support/src` folder and go through the practice items below.
+Enter the `sleepy/` directory (or `chapters/compute/processes/drills/tasks/sleepy` if you are working directly in the repository).
+Run `make` and then enter `support/` folder and go through the practice items below.
 
 Use the `tests/checker.sh` script to check your solutions.
 
 ```bash
-./checker.sh
+./tests/checker.sh
 sleepy_creator ...................... passed ... 30
 sleepy_creator_wait ................. passed ... 30
 sleepy_creator_c .................... passed ... 40

chapters/compute/processes/drills/tasks/wait-for-me-processes/README.md

@@ -1,6 +1,7 @@
 # Wait for Me
 
-Enter the `chapters/compute/processes/drills/tasks/wait-for-me-processes/` directory, run `make skels`, open the `support/src` folder and go through the practice items below.
+Enter the `wait-for-me/` directory (or `chapters/compute/processes/drills/tasks/wait-for-me/` if you are working directly in the repository).
+Run `make` and then enter `support/` folder and go through the practice items below.
 
 Use the `tests/checker.sh` script to check your solutions.
 
@@ -10,7 +11,7 @@ wait_for_me_processes ...................... passed ... 100
 ```
 
 1. Run the code in `wait_for_me_processes.py` (e.g: `python3 wait_for_me_processes.py`).
-    The parent process creates one child that writes and message to the given file.
+    The parent process creates one child that writes a message to the given file.
     Then the parent reads that message.
     Simple enough, right?
     But running the code raises a `FileNotFoundError`.

chapters/compute/processes/reading/processes.md

@@ -14,7 +14,7 @@ student@os:~$ file /usr/bin/ls
 ```
 
 When you run it, the `ls` binary stored **on the disk** at `/usr/bin/ls` is read by another application called the **loader**.
-The loader spawns a **process** by copying some of the contents `/usr/bin/ls` in memory (such as the `.text`, `.rodata` and `.data` sections).
+The loader spawns a **process** by copying some contents of `/usr/bin/ls` into memory (for example the `.text`, `.rodata` and `.data` sections).
 Using `strace`, we can see the [`execve`](https://man7.org/linux/man-pages/man2/execve.2.html) system call:
 
 ```console

chapters/compute/synchronization/drills/tasks/apache2-simulator-condition/README.md

@@ -22,8 +22,8 @@ There are a few rules though, such as:
 - The consumer must not retrieve data if the buffer is empty.
 - The producer and the consumer can't access the shared buffer at the same time.
 
-Now enter `chapters/compute/synchronization/drills/tasks/apache2-simulator-condition/` and run `make skels`.
-Look at the code in `chapters/compute/synchronization/drills/tasks/apache2-simulator/support/src/producer_consumer.py`.
+Now enter the `apache2-simulator-condition/` directory of the extracted archive (or `chapters/compute/synchronization/drills/tasks/apache2-simulator-condition/` if you are working directly in the repository) and run `make skels`.
+Look at the code in `support/src/producer_consumer.py`.
 We have one producer and one consumer for simplicity.
 Observe that the producer calls `notify()` once there is data available, and the consumer calls `notify()`, when data is read.
 Notice that this call is preceded by an `acquire()` call, and succeeded by a `release()` call.
@@ -58,7 +58,7 @@ Neat!
 So now we have both synchronization **and** signalling.
 This is what conditions are for, ultimately.
 
-Open `chapters/compute/synchronization/drills/tasks/apache2-simulator/support/src/apache2_simulator_condition.py` and follow the TODOs.
+Open the `apache2-simulator-condition/` directory of the extracted archive (or `chapters/compute/synchronization/drills/tasks/apache2-simulator-condition/` if you are working directly in the repository), then go to `support/src/apache2_simulator_condition.py` and follow the TODOs.
 The code is similar to `apache2_simulator_semaphore.py`, but this time we use condition variables as shown in `producer_consumer.py`.
 
 [Quiz](../../../drills/questions/notify-only-with-mutex.md)