From 58ba502a0580d2fcb3a8198f7ef9e21da7aecc03 Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Thu, 7 May 2026 09:09:15 +0300 Subject: Update content for md --- gemfeed/DRAFT-unveiling-ior-ng-part-1.md | 2 +- gemfeed/DRAFT-unveiling-ior-ng-part-2.md | 2 +- gemfeed/DRAFT-unveiling-ior-ng-part-3.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) (limited to 'gemfeed') diff --git a/gemfeed/DRAFT-unveiling-ior-ng-part-1.md b/gemfeed/DRAFT-unveiling-ior-ng-part-1.md index 21b9f7eb..6f0aaf10 100644 --- a/gemfeed/DRAFT-unveiling-ior-ng-part-1.md +++ b/gemfeed/DRAFT-unveiling-ior-ng-part-1.md @@ -213,4 +213,4 @@ For installing it and the eBPF / CO-RE / static-linking story (why one build run [Part 2: install + compile once, run everywhere](./DRAFT-unveiling-ior-ng-part-2.md) [Part 3: under the hood (schema, probe generator, ClickHouse)](./DRAFT-unveiling-ior-ng-part-3.md) [Source on Codeberg](https://codeberg.org/snonux/ior) -[The full in-repo tutorial](https://codeberg.org/snonux/ior/src/branch/main/demo/TUTORIAL.md) +[The full in-repo tutorial](https://codeberg.org/snonux/ior/src/branch/main/docs/tutorial/tutorial.md) diff --git a/gemfeed/DRAFT-unveiling-ior-ng-part-2.md b/gemfeed/DRAFT-unveiling-ior-ng-part-2.md index 56885fcc..c4b81886 100644 --- a/gemfeed/DRAFT-unveiling-ior-ng-part-2.md +++ b/gemfeed/DRAFT-unveiling-ior-ng-part-2.md @@ -166,7 +166,7 @@ Old I/O Riot (Systemtap) New ior (libbpf + CO-RE) What that buys ior in practice: I ship a single `ior` binary. On any Linux ≥4.18-ish with BTF available (which is almost all of them now — Debian, Ubuntu, Fedora, Arch, RHEL, and ElRepo's `kernel-ml` builds all ship `CONFIG_DEBUG_INFO_BTF=y` by default), it just works. No kernel-debuginfo dependency, no per-kernel build matrix, no DKMS hooks. The first time I tried `scp ior fedora-box:` and it ran without complaint after a 6-month gap I had to double-check it wasn't silently doing nothing. -So the operational shape is: pick one box, do the install dance from the Rocky section above (or the Fedora one in the README) once, build, then distribute the 23 MB binary wherever you want to trace. The build host needs Go and clang and the static libraries. The trace hosts need a BTF-enabled kernel and `sudo`. That's it. +So the operational shape is: pick one box, do the install dance from the Rocky section above (or `docs/build-rocky-linux-9.md` for a native Fedora/RHEL build) once, build, then distribute the 23 MB binary wherever you want to trace. The build host needs Go and clang and the static libraries. The trace hosts need a BTF-enabled kernel and `sudo`. That's it. The runtime shape of a trace pipeline lines up with that: diff --git a/gemfeed/DRAFT-unveiling-ior-ng-part-3.md b/gemfeed/DRAFT-unveiling-ior-ng-part-3.md index 49a17daa..49b52e62 100644 --- a/gemfeed/DRAFT-unveiling-ior-ng-part-3.md +++ b/gemfeed/DRAFT-unveiling-ior-ng-part-3.md @@ -202,4 +202,4 @@ That's the bottom of the stack. For the dashboard surface — what ior looks lik [Part 1: a guided tour](./DRAFT-unveiling-ior-ng-part-1.md) [Part 2: install + compile once, run everywhere](./DRAFT-unveiling-ior-ng-part-2.md) [Source on Codeberg](https://codeberg.org/snonux/ior) -[The full in-repo tutorial](https://codeberg.org/snonux/ior/src/branch/main/demo/TUTORIAL.md) +[The full in-repo tutorial](https://codeberg.org/snonux/ior/src/branch/main/docs/tutorial/tutorial.md) -- cgit v1.2.3