From dcc40aee57f9295a3ff7eb1efeecb189bc597602 Mon Sep 17 00:00:00 2001 From: marcel-dempers Date: Sat, 29 Mar 2025 11:00:01 +1100 Subject: [PATCH] chapter 3 refinements --- .../content/operating-systems/linux/monitoring/disk/README.md | 2 ++ .../operating-systems/linux/monitoring/disk/disk.drawio.svg | 4 ++++ .../linux/monitoring/network/network.drawio.svg | 2 +- 3 files changed, 7 insertions(+), 1 deletion(-) create mode 100644 course/content/operating-systems/linux/monitoring/disk/disk.drawio.svg diff --git a/course/content/operating-systems/linux/monitoring/disk/README.md b/course/content/operating-systems/linux/monitoring/disk/README.md index 75be45e..2f2018f 100644 --- a/course/content/operating-systems/linux/monitoring/disk/README.md +++ b/course/content/operating-systems/linux/monitoring/disk/README.md @@ -21,6 +21,8 @@ As a DevOps, SRE or platform engineer, we need to form a basic understanding of As we have learned in our introduction to monitoring, disk is the only long term persistent storage for a computer system
When a server shuts down, all important data, files, applications and configuration files are all retained on disk.
+![diagram](disk.drawio.svg) + ### Applications are just files Applications that developers write are compiled into binaries or executables which are all but files on disk.
diff --git a/course/content/operating-systems/linux/monitoring/disk/disk.drawio.svg b/course/content/operating-systems/linux/monitoring/disk/disk.drawio.svg new file mode 100644 index 0000000..e33131c --- /dev/null +++ b/course/content/operating-systems/linux/monitoring/disk/disk.drawio.svg @@ -0,0 +1,4 @@ + + + +
Basic Disk Usage
DISK
⚙️
Linux loads application into memory
📂
📜
📜
📜
📜

EVERYTHING
in Linux is a file!
⚙️
CPU
⚙️
⚙️
MEMORY
📜
📂
application executed as "tasks" by cpu
data lost
when
computer
shuts
down!
data is persisted
when
computer
shuts
down!
\ No newline at end of file diff --git a/course/content/operating-systems/linux/monitoring/network/network.drawio.svg b/course/content/operating-systems/linux/monitoring/network/network.drawio.svg index 4c5f027..fc99c9e 100644 --- a/course/content/operating-systems/linux/monitoring/network/network.drawio.svg +++ b/course/content/operating-systems/linux/monitoring/network/network.drawio.svg @@ -1,4 +1,4 @@ -

* [IP]:[PORT] 
* 10.0.0.4:1024
Network Components
CLIENT

SERVER


* [IP]:[PORT] 
* 10.0.0.4:443

* [PUBLIC IP]:[PORT]
* 144.0.1.2:1024
* NETWORK DEVICE

* [PUBLIC IP]:[PORT]
* 143.0.1.2:443
* NETWORK DEVICE
ROUTER\MODEM\LOAD BALANCER\GATEWAY
(controls inbound\outbound traffic)
PROCESS
PROCESS
⚙️
⚙️
\ No newline at end of file +

* [IP]:[PORT] 
* 10.0.0.4:1024
Basic NETWORK flow
CLIENT

SERVER


* [IP]:[PORT] 
* 10.0.0.4:443

* [PUBLIC IP]:[PORT]
* 144.0.1.2:1024
* NETWORK DEVICE

* [PUBLIC IP]:[PORT]
* 143.0.1.2:443
* NETWORK DEVICE
ROUTER\MODEM\LOAD BALANCER\GATEWAY
(controls inbound\outbound traffic)
PROCESS
PROCESS
⚙️
⚙️
private network
private network
browser (or program)
STEP 1 
create TCP request
STEP 2 
client sends TCP packet to server
web server or any process
(listening on port 443)
STEP 3 
server processes request
generates TCP response
\ No newline at end of file