Skip to content
Linux
~/justmeandlinux

Writing/Topics/linux

Linux

How the system actually works underneath the commands: what the kernel is doing, where the filesystem boundary is, and why the thing you just typed behaved the way it did.

27 posts / 69,728 words

/ dc · part 8 / 11 min

Data Center Part 8: The cheat sheet

Everything in this series on one page. Bookmark this one and skip the rest. Vocabulary, in one line each Term What it is U / RU Rack unit. 1.75 in / 44.45 mm of vertical mounting space. Cabinet Enclosed rack with doors and sides. What colo actually sells you…

/ dc · part 7 / 12 min

Data Center Part 7: Directing remote hands

The technician reading your ticket is standing in a cold, loud room, in front of forty identical black boxes, wearing gloves, holding a tablet. They cannot see your monitoring. They do not know your naming scheme. They have another six tickets after yours…

/ dc · part 6 / 10 min

Data Center Part 6: Leaving the cage

Everything up to this point stayed inside your cage. This part is about the handful of strands that leave it, and about the paperwork that governs them — because the paperwork is genuinely the hard part. The chain, end to end Almost all confusion here…

/ dc · part 5 / 10 min

Data Center Part 5: Where the switches live

Your server's NIC cable probably travels about two feet. That fact shapes more of the datacenter than anything else in this series. This part is where switches physically sit, why that choice was made, and what it means for the cabling in your cabinet. The…

/ dc · part 4 / 12 min

Data Center Part 4: Out-of-band access

Every remote hands ticket you do not have to open is a win, and out-of-band access is how you avoid most of them. There is a second computer inside your server. It has its own CPU, its own firmware, its own network stack and its own IP address, it runs on…

/ dc · part 3 / 10 min

Data Center Part 3: Cables, optics and transceivers

"Send me a 3-metre DAC" is a complete, unambiguous, orderable request. "Send me a network cable" is not. This part is about being able to say the first thing. The three ways to connect two ports Every high-speed link in a datacenter is one of three physical…

/ dc · part 2 / 9 min

Data Center Part 2: Power, A-side and B-side

You are sold a 30 amp feed. You can use 24 of them. If you also want redundancy, you can use 12. Power is the part of the datacenter that punishes vagueness hardest, because the failure mode is not a warning in a dashboard — it is a breaker opening and half a…

/ dc · part 1 / 10 min

Data Center Part 1: Anatomy of a rack

A 42U cabinet does not give you 42U of usable space, and the sooner you internalise that the fewer awkward conversations you will have about why the new server does not fit. This part is the physical frame: what the numbers mean, what holds equipment in, why…

/ dc · part 0 / 12 min

Data Center Part 0: The vocabulary

I have never racked a server. I have opened a lot of tickets asking someone else to. That is the normal shape of this job now. You are a competent Linux engineer, you own machines that live in a building you have visited maybe twice, and every physical act on…

/ net · part 7 / 19 min

Linux Networking Part 7: The Cheat Sheet

The whole series on one page. Print it, pin it, put it in your runbook. Parts 0 through 6 explain why each of these works. This is the lookup table for when you don't have time to read. Glossary Term Meaning Interface A network device as the kernel sees it …

/ net · part 6 / 14 min

Linux Networking Part 6: Routing, ARP, Firewalls and Containers

Five parts in, we've covered sockets, counters, packets and latency. There's a gap, and it's the one that eats the most time on modern infrastructure: the packet reaches the box and disappears. No socket sees it. No drop counter moves. tcpdump shows it…

/ net · part 5 / 17 min

Linux Networking Part 5: Latency, Queues, and a Real nginx Hunt

"The site is slow." Three words, and almost no information. Slow where? Slow for whom? Slow by how much, compared to what? Latency work is mostly attribution — cutting the total time into pieces until one piece is obviously the problem. Do that first and the…

/ net · part 4 / 16 min

Linux Networking Part 4: Reading tcpdump

Counters tell you that something is wrong. tcpdump tells you what happened . Most engineers can start a capture. Far fewer can look at forty lines of output and say "the firewall is dropping this" or "the server's accept queue is full" without opening…

/ net · part 3 / 13 min

Linux Networking Part 3: Proving Packet Loss

"We're seeing packet loss." That sentence starts more wasted investigations than any other in infrastructure. It's not a diagnosis. It's a feeling. Packets can be discarded at six different places between the wire and your application, and each one has a…

/ net · part 2 / 12 min

Linux Networking Part 2: Reading Sockets with ss

You have nginx running. Someone says it's broken. You need to know, in the next thirty seconds: who is connected, from where, to which port, and whether anything is stuck. One command answers all of that. Most people run it wrong. This is part 2 of the…

/ net · part 1 / 9 min

Linux Networking Part 1: The Mental Model

Most engineers learn Linux networking backwards. They memorise commands first, then spend years never quite knowing which one to reach for. So they run netstat -an , stare at 4000 lines, and guess. The fix is not more commands. The fix is a map. Once you know…

/ net · part 0 / 15 min

Linux Networking Part 0: The Fundamentals

Somebody says "the app can't reach the database." You have a terminal and no idea where to start. This post is the on-ramp. Vocabulary, then the seven commands that answer "is it reachable, is the port open, is DNS working, is TLS working, and who owns this…

/ 8 min

iptables: the commands you need

Complete iptables firewall guide: tables, chains, rules, real server configuration, troubleshooting, and practical security examples for Linux systems.

/ 26 min

Storage performance testing: what to run and how to read it

Storage Performance Testing: What to Run, What You're Reading, and What It Actually Means Your colleagues are debating RAIDZ2 vs RAID 10. Someone runs a benchmark. Numbers appear. A decision gets made. Half the time the benchmark measured the wrong thing…

/ 25 min

mdadm, LVM, and the Storage Stack Nobody Fully Explains

mdadm, LVM, and the Storage Stack Nobody Fully Explains Most Linux admins learn these tools one crisis at a time. A disk fails, you Google mdadm commands. A volume fills up, you find out about LVM resize. A snapshot corrupts silently, you learn about thin…

Drill it instead

Lessons covering the same ground — asked rather than explained.