Add multilingual language and systems learning tracks
This commit is contained in:
1 parent
07338189fc
commit
d8d1c40118
844 files changed
+6061
No files matched your search
@@ -0,0 +1,9 @@
|
||||
# Server OS Engineering · 1
|
||||
|
||||
[Agila University track](https://edu.agilaos.com/track.php?track=24&lang=en)
|
||||
|
||||
About 15 minutes per lesson. Predict, run, change, explain, then complete the check in University.
|
||||
|
||||
- [Lesson 1: What makes a server operating system?](lesson-1/lesson.html)
|
||||
- [Lesson 2: Service state and recovery](lesson-2/lesson.html)
|
||||
- [Lesson 3: Accounts and least privilege](lesson-3/lesson.html)
|
||||
@@ -0,0 +1 @@
|
||||
<!doctype html><html lang="en"><meta charset="utf-8"><title>What makes a server operating system?</title><h1>What makes a server operating system?</h1><p>15-minute session: read for 3 minutes, trace for 3, experiment for 7, and complete the check for 2. Spend longer whenever you need.</p><p>A server OS combines a kernel with boot and service management, storage, networking, accounts, updates, and recovery. Building a server distribution is different from writing a new kernel. Choose which goal your project has. Draw the request path from a network interface through a service to storage, and mark every trust boundary.</p><p><strong>Practice and evidence:</strong> Predict the example or draw its state transitions. Change one assumption, test the boundary, and record the actual result. Explain what this small model does not establish about a production system.</p><h3>Practice and evidence</h3><p>Keep three notes: your prediction, the actual result, and why they match or differ. The completion check grades understanding; the practice task builds skill.</p></html>
|
||||
@@ -0,0 +1,3 @@
|
||||
<!doctype html><html lang="en"><meta charset="utf-8"><title>Service state and recovery</title><h1>Service state and recovery</h1><p>15-minute session: read for 3 minutes, trace for 3, experiment for 7, and complete the check for 2. Spend longer whenever you need.</p><p>A service can be stopped, starting, ready, failed, or restarting. Readiness means it can serve its intended workload, not merely that a PID exists. A restart policy needs backoff and a limit to avoid an endless crash loop. Model startup failure and a dependency becoming available.</p><p><strong>Practice and evidence:</strong> Predict the example or draw its state transitions. Change one assumption, test the boundary, and record the actual result. Explain what this small model does not establish about a production system.</p><pre><code class="language-python">delays=[min(2**attempt,30) for attempt in range(6)]
|
||||
print(delays)
|
||||
</code></pre><p><strong>Expected result:</strong> <code>[1, 2, 4, 8, 16, 30]</code></p><h3>Practice and evidence</h3><p>Keep three notes: your prediction, the actual result, and why they match or differ. The completion check grades understanding; the practice task builds skill.</p></html>
|
||||
@@ -0,0 +1,2 @@
|
||||
delays=[min(2**attempt,30) for attempt in range(6)]
|
||||
print(delays)
|
||||
@@ -0,0 +1,6 @@
|
||||
<!doctype html><html lang="en"><meta charset="utf-8"><title>Accounts and least privilege</title><h1>Accounts and least privilege</h1><p>15-minute session: read for 3 minutes, trace for 3, experiment for 7, and complete the check for 2. Spend longer whenever you need.</p><p>Give each service only the files and capabilities it needs. Separate administrator access from application identity. Authentication asks who is calling; authorization asks which action that identity may perform. Test a student trying to read another student’s record. A hidden button is not an access-control check.</p><p><strong>Practice and evidence:</strong> Predict the example or draw its state transitions. Change one assumption, test the boundary, and record the actual result. Explain what this small model does not establish about a production system.</p><pre><code class="language-python">def can_read(caller,owner):
|
||||
return caller==owner
|
||||
assert can_read(7,7)
|
||||
assert not can_read(7,8)
|
||||
print("Passed")
|
||||
</code></pre><p><strong>Expected result:</strong> <code>Passed</code></p><h3>Practice and evidence</h3><p>Keep three notes: your prediction, the actual result, and why they match or differ. The completion check grades understanding; the practice task builds skill.</p></html>
|
||||
@@ -0,0 +1,5 @@
|
||||
def can_read(caller,owner):
|
||||
return caller==owner
|
||||
assert can_read(7,7)
|
||||
assert not can_read(7,8)
|
||||
print("Passed")
|
||||
Reference in new issue
Block a user