vault backup: 2025-03-03 09:07:47

.obsidian/workspace.json

@@ -38,7 +38,7 @@
                 "file": "Concurrent Systems/slides/class 1.pdf",
                 "page": 4,
                 "left": -22,
-                "top": 42,
+                "top": 51,
                 "zoom": 0.7036817102137768
               },
               "icon": "lucide-file-text",
@@ -220,7 +220,8 @@
   },
   "active": "bfdcb298848e6147",
   "lastOpenFiles": [
-    "Pasted image 20250303090135.png",
+    "Concurrent Systems/notes/images",
+    "Concurrent Systems/notes/images/Pasted image 20250303090135.png",
     "Concurrent Systems/slides/class 1.pdf",
     "Concurrent Systems/notes/Lezione1.md",
     "Concurrent Systems/notes",
@@ -265,7 +266,6 @@
     "Biometric Systems/images/Pasted image 20241212093900.png",
     "Biometric Systems/images/Pasted image 20241212084349.png",
     "Biometric Systems/images/Pasted image 20241212094000.png",
-    "Biometric Systems/images/Pasted image 20241212093943.png",
     "Senza nome.canvas"
   ]
 }

Concurrent Systems/notes/Lezione1.md

@@ -61,3 +61,6 @@ While `read()` and `write()` may be considered as atomic, their sequential compo
 
 ![[Pasted image 20250303090135.png]]
 
+#### Mutual Exclusion (MUTEX)
+Ensure that some parts of the code are executed as *atomic*.
+This is needed in competition but also in cooperation.