chapter/io: Restructure IO chapter

This commit restructures the IO chapter according to OpenEdu methodology.
This comprises of:
  - refactoring and changing the order of chapters
  - generating support files from solution
  - breaking arena into smaller sections
  - fixing Makefiles from tasks to be self-contained

Signed-off-by: Mihnea Firoiu <[email protected]>
Signed-off-by: Alex Apostolescu <[email protected]>

solve checkpatch

Author: Alex-deVis

.github/labeler.yml

@@ -8,7 +8,7 @@ topic/compute:
   - 'chapters/compute/**/*'
 
 topic/io:
-  - 'content/chapters/io/**/*'
+  - 'chapters/io/**/*'
 
 topic/app-interact:
   - 'content/chapters/app-interact/**/*'

.vscode/settings.json

@@ -0,0 +1,3 @@
+{
+    "editor.formatOnSave": false
+}

chapters/compute/copy-on-write/drills/tasks/shared-memory/README.md

@@ -1,6 +1,6 @@
 # Shared Memory
 
-As you remember from the [Data chapter](reading/process-memory.md#memory-mapping), one way to allocate a given number of pages is to use the `mmap()` syscall.
+As you remember from the [Data chapter](../../../../../data/process-memory/reading/process-memory.md), one way to allocate a given number of pages is to use the `mmap()` syscall.
 Let's look at its [man page](https://man7.org/linux/man-pages/man2/mmap.2.html), specifically at the `flags` argument.
 Its main purpose is to determine the way in which child processes interact with the mapped pages.
 
@@ -10,10 +10,10 @@ Now let's test this flag, as well as its opposite: `MAP_SHARED`.
 Compile and run the code in `shared-memory/support/shared_memory.c`.
 
 1. See the value read by the parent is different from that written by the child.
-Modify the `flags` parameter of `mmap()` so they are the same.
+   Modify the `flags` parameter of `mmap()` so they are the same.
 
 1. Create a semaphore in the shared page and use it to make the parent signal the child before it can exit.
-Use the API defined in [`semaphore.h`](https://man7.org/linux/man-pages/man0/semaphore.h.0p.html).
+   Use the API defined in [`semaphore.h`](https://man7.org/linux/man-pages/man0/semaphore.h.0p.html).
 
     **Be careful!**
     The value written and read previously by the child and the parent, respectively, must not change.