You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 7a8a976
Browse filesBrowse the repository at this point in the historyBrowse files
docs: professional-voice sweep across all chapters
Recast ~2700 em dashes to colons, parentheticals, semicolons, and sentence
splits across all 57 _docs chapters (bodies, figure captions and alt text,
Tools-used callouts, bullet lists, front-matter title/description, status
footers). Also cleared confessional (honest/plainly), defensive contrast
(genuine/real/on-purpose/for-free), meta-narration (worth naming, rest-of-the-
book), generated tells (load-bearing/earns-its-keep), school framing, and
filler; trimmed deliberately to at most one reasoned instance per chapter.
Applied the repo's lie-rule (keep machine-subject 'lie'/the --lie flag/recorded
output; recast work-subject). Kept the Go debugger tool name 'delve'/'dlv'.
Front-matter values quoted where a recast introduced a colon. Seven parallel
executors, validated centrally. Jekyll build clean (no YAML exceptions).
Copy file name to clipboardExpand all lines: _docs/00-outline.md
+12-12Lines changed: 12 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,26 +2,26 @@
2
2
title: "Outline"
3
3
order: 0
4
4
part: "Setting Up"
5
-
description: "The full arc of this book — fourteen parts, forty-nine chapters, six programs that grow with you, three languages the whole way."
5
+
description: "The full arc of this book: fourteen parts, forty-nine chapters, six programs that grow with you, three languages the whole way."
6
6
---
7
7
8
-
This book teaches Linux systems programming three times at once — in modern
9
-
**C++23**, **Go**, and **Rust** — for developers who already program and want to
8
+
This book teaches Linux systems programming three times at once, in modern
9
+
**C++23**, **Go**, and **Rust**, for developers who already program and want to
10
10
understand what their code asks of the kernel. Every hands-on chapter ships a
11
11
runnable example implemented idiomatically in all three languages, presented in
12
12
switchable code tabs, and every example doubles as a standalone demo.
13
13
14
14
{% include excalidraw.html
15
15
file="00-course-map"
16
16
alt="Course map: four journey stages - Foundations, Core systems, Operating context, and Mastery - shown as bands containing the fourteen parts with their chapter ranges, and the six artifacts fwatch, shmkv, chatterd, pmon, bugfarm, and sysagent along the bottom, each with an arrow to the part where it grows."
17
-
caption="Figure 0.1 — the course at a glance." %}
17
+
caption="Figure 0.1: the course at a glance." %}
18
18
19
19
Two threads run through the whole book and never stop:
20
20
21
-
-**Errors, three ways** — how `errno` becomes `std::expected`, a wrapped Go
21
+
-**Errors, three ways**: how `errno` becomes `std::expected`, a wrapped Go
22
22
`error`, or a Rust `Result`, and what a *policy* for `EINTR`, `EAGAIN`, and
23
23
partial failure looks like in each language.
24
-
-**The concurrency lens** — which of the three concurrency models each
24
+
-**The concurrency lens**: which of the three concurrency models each
25
25
chapter's example leans on (`std::jthread` and atomics, goroutines and
26
26
channels, ownership and `Send`/`Sync`), and why.
27
27
@@ -34,7 +34,7 @@ artifacts that grow chapter by chapter:
|`sysagent`| a metrics agent reading /proc, /sys, and cgroups, exporting OpenTelemetry | 36 → 38, 41 |
40
40
|`bugfarm`| a corpus of seeded bugs for learning gdb, valgrind, sanitizers, and eBPF tools | 28 → 31 |
@@ -54,25 +54,25 @@ artifacts that grow chapter by chapter:
54
54
|**Debugging**| gdb and remote debugging, valgrind vs sanitizers vs miri, eBPF observation tools, per-language toolbelts | 28–31 |
55
55
|**Containers and Virtualization**| namespaces and cgroups, seccomp and Landlock, our programs in containers, KVM and the isolation spectrum | 32–35 |
56
56
|**Observability**| /proc and /sys by hand, the USE method, OpenTelemetry into Grafana/Loki/Tempo/Mimir | 36–38 |
57
-
|**Performance and Low Latency**| benchmarking without self-deception, pinned-core fast paths, the capstone fleet | 39–41 |
57
+
|**Performance and Low Latency**| benchmarking without self-deception, pinned-core fast paths, the final project fleet | 39–41 |
58
58
|**Deep Dives**| embedding Lua, Rust macros for systems code, the Go runtime | 42–44 |
59
59
|**Appendices: Tooling**| Cockpit, SystemTap, and PCP; the C++, Go, and Rust toolboxes | 45–48 |
60
60
|**Compendium: C++ Concurrency**| concurrency vs parallelism, pthreads, std threading, Boost.Thread, C++20 coroutines, Boost.Fiber, Boost.Asio, and a measured comparison of all six | 49–56 |
61
61
62
62
## Where things run
63
63
64
64
Examples run **locally** on your Fedora 44 machine unless they need root, kernel
65
-
observation, or a second host — those run in the disposable KVM lab
65
+
observation, or a second host; those run in the disposable KVM lab
66
66
(`systems-target`, and `systems-peer` for two-host networking) that Chapter 2
67
67
provisions. Observability chapters use a local Podman LGTM stack (Grafana,
68
68
Loki, Tempo, Mimir) plus Performance Co-Pilot from its container image. Nothing
69
69
experimental ever runs un-snapshotted on your workstation.
70
70
71
-
> **Note** — every example section carries a verification status. A demo is
71
+
> **Note**: every example section carries a verification status. A demo is
72
72
> marked *verified* only when it has produced its claimed observable effect on
73
-
> the stated environment — never merely because it compiled. That claim is
73
+
> the stated environment, never merely because it compiled. That claim is
74
74
> enforced by machinery, not habit: the runner, `scripts/test-all-examples.py`,
75
75
> builds each example in all three languages and then executes the example's own
76
76
> Lua `verify.lua` harness, which must observe the behavior to report a PASS. If
77
77
> the VM lab or the LGTM stack an example depends on is down, the runner reports
0 commit comments