TOPIC
Linux & Systems
Lessons, explainers, experiments, and implementation notes.
Linux & Systems · 10 min read · 2026-11-06
How did a Finnish student's hobby project become a foundation of modern computing? The story of Linux is also a story about shared knowledge, collaboration, and the invisible infrastructure of civilization.
Linux & Systems · 2 min read · 2026-10-02
The server stays the service anchor while the laptop or desktop can change; the tailnet keeps the relationship stable.
Linux & Systems · 2 min read · 2026-08-22
Containerizing a SIP service added another address and NAT boundary, which made port publishing, advertised addresses and RTP ranges more important rather than less important.
Linux & Systems · 2 min read · 2026-08-14
A process can be alive while the service contract its neighbors depend on is broken.
Linux & Systems · 2 min read · 2026-05-22
A .local name and a Tailscale peer can refer to the same host while depending on different discovery systems.
Linux & Systems · 2 min read · 2026-05-01
Remote deployment is unreliable when host identity, user and access policy are rediscovered every time.
Linux & Systems · 2 min read · 2026-05-01
A second worker is useful only if it knows what the first worker already changed.
Linux & Systems · 2 min read · 2026-04-14
Every extra reverse proxy adds another place for routing, TLS and headers to disagree.
Linux & Systems · 2 min read · 2025-11-02
Swap is sometimes treated as a direct replacement for RAM, but memory moved to storage has to be read back when active work needs it again. Swap creates room while introducing a time cost.
Linux & Systems · 2 min read · 2025-10-12
Private tailnet publishing and public internet publishing are different ingress jobs, even when they reach the same container.
Linux & Systems · 3 min read · 2025-09-29
`dig` gave me a way to separate resolver configuration, authoritative answers, record types and response timing instead of reducing DNS to 'name works' or 'name fails'.
Linux & Systems · 3 min read · 2025-07-22
Ubuntu 18.04 was a good excuse to stop relying on desktop network icons and start reading interface state, routes, sockets and DNS configuration directly from the system.
Linux & Systems · 1 min read · 2025-05-22
Dashboards improved once I stopped collecting attractive metrics and started collecting evidence for specific failure modes.
Linux & Systems · 2 min read · 2025-03-20
I do not use Tailscale as a generic VPN. I use it as the stable identity and reachability layer between my laptop, desktop and home server.
Linux & Systems · 1 min read · 2024-10-08
The difference between a lab box and production infrastructure is not the hardware; it is whether failure has a documented recovery path.
Linux & Systems · 1 min read · 2024-09-20
A protected parent directory can block a perfectly readable child file because directory execute controls traversal.
Linux & Systems · 2 min read · 2024-09-07
On Linux, a high used-memory number does not automatically mean the system is under pressure. Cache consumes memory too and can often be reclaimed. A full-looking memory graph and work actually stalling for memory are different events.
Linux & Systems · 2 min read · 2024-08-17
I choose the networking boundary before I add Tailscale to a Docker stack, because the two patterns create different operational models.
Linux & Systems · 2 min read · 2024-07-20
One reason I like Linux is that its parts can be followed. Behind a command, you can trace processes, files, permissions, and network relationships. You do not need to understand everything at once for the larger system to start opening up.
Linux & Systems · 1 min read · 2024-06-24
Container networking stopped feeling magical when I separated host routing, bridge interfaces, NAT and the application socket.
Linux & Systems · 2 min read · 2024-05-26
Service state, bind failures and restart loops often explained a broken PBX before I needed to inspect a single SIP packet.
Linux & Systems · 2 min read · 2023-10-13
Stopping a service now, preventing automatic startup at boot, and making the service impossible to start are different operational intentions. systemd's stop, disable, and mask reflect those distinctions.
Linux & Systems · 3 min read · 2023-07-12
Once I started reading Linux routes as prefix decisions instead of interface settings, multi-interface hosts and lab gateways became much easier to debug.
Linux & Systems · 3 min read · 2023-07-03
A useful home lab does not need enterprise hardware. A spare PC, a small switch and a few isolated network experiments are enough to learn a lot about real interfaces, routes and services.
Linux & Systems · 2 min read · 2023-06-26
Before opening a full packet capture, sngrep gave me a quick view of call legs, response codes and dialog timing directly on the server.
Linux & Systems · 3 min read · 2022-07-24
Moving from local console access to SSH keys changed the lab from a collection of machines into something I could actually operate and troubleshoot remotely.
Linux & Systems · 3 min read · 2021-12-17
On a headless Linux box, tcpdump was faster than moving captures around blindly. A narrow capture at the right interface often answered the question immediately.
Linux & Systems · 2 min read · 2021-08-18
Joining a machine is easy; making its identity, hostname, access and role predictable is the part that matters later.
Linux & Systems · 1 min read · 2021-08-14
Most operational confusion came from mixing desired configuration, live state and credentials into the same place.
Linux & Systems · 1 min read · 2021-03-17
Logs explain individual failures; metrics show whether the system is drifting before the failures become obvious.
Linux & Systems · 2 min read · 2020-10-06
On a headless PBX, a narrow tcpdump capture often answered the important question faster than a full GUI trace: did the signaling or media packet actually reach the server?