There’s a game which you have probably played in some form, possibly not even knowing that it was a game. It goes like this: an author writes fiction, and the reader comes across an interesting element and asks how it works, in-universe.

And people come up with answers…

About two weeks ago I decided to use parts from a suddenly unused desktop to upgrade the living room media server. The initial plan was to keep the disks, power supply and case of the media server, and use the motherboard, CPU, RAM and video card from the desktop.

Things did not go to plan, of course…

In the spirit of the Joel Scale for software dev, I propose an initial version of a scale for IT and operations folks.

My RSI prevention strategy involves change: I use three different keyboards, four or five pointing devices, and move around to different places. On my main desktop, I mostly use a thumb trackball, with a mouse in second place and a drawing pad in distant third.

On Friday the trackball died in a peculiar way.

I have almost 30 years of professional experience as a sysadmin.

Failure is inevitable. Hardware will fail, software will be discovered to have flaws, reconfiguration will be mistaken.

The antidote is to have reliable recovery mechanisms: everything will eventually break or need to be changed, so in turn you need to be able to recover back to a stable position, so you can try again.

Recovery mechanisms are not all-purpose. I usually describe them in three phases:

I had thought that ‘pareidolia’ referred exclusively to the human tendency to see human faces everywhere – any time you see two dots or circles and a line below them, boom :) it’s a face. It can be triggered by rocks, clouds, shadows, uneven browning on a tortilla or a pancake.

It turns out, though, that pareidolia covers any kind of overactive pattern matching. Humans look for meaningful patterns all the time, without thinking about the search, and when something trips the right thresholds in our brain, we seize upon it. The result can be faces, voices, music or just a cloud that looks like a moose.

Here’s my thesis: the large language models (LLMs) and similar generative software processes that people currently refer to as “AI” – those are exceptionally well-tuned to produce patterns that will trigger threshold recognition in human brains. Not by accident – that’s the goal. They are pareidolia-circuit stimulators.

The problem is that LLM output is exactly as meaningful as any other kind of pareidolia. Every well-formed paragraph is a false-positive error.

And when people repeatedly mistake their overactive pattern recognition for reality, we call that a mental disorder: psychosis.

-30-

If your Debian system is suddenly very slow to login – like, 25 to 90 seconds of apparent inactivity on every new ssh – it’s not DNS.

Check to see if your elogind or systemd/logind is actually running. Look for a log entry in auth.log along the lines of

dbus-daemon[4501]: [system] Failed to activate service 'org.freedesktop.login1'

right after an SSH attempt.

If so, restart the daemon.

-30-

Some people play Wordle to get their brains moving in the morning. I find one of Linked-In’s incredibly stupid “AI”-driven “articles” where they limit you to 750 characters of commentary (times 5-7 article segments) and write a cohesive answer to the whole thing in one block.

Herewith: “How Do You Work With Other IT Departments To Manage Security Risks”

Either your company understands that security is the prime risk assessment and management tool, or it does not. Figure this out first.

Assuming your company cares, get an executive mandate. Bring the IT, Ops, Network Engineering, Security, Software Development, Hardware Engineering, Legal, and all other relevant groups together. Establish a common vocabulary, write a policy, and appoint a committee that has the authority to approve exceptions and change policy.

Policy is implemented in plans, and if your company is large enough, some groups will need their own plans. Write them to a common skeleton, and publicize them internally.

Include Business Continuity and Disaster Recovery as subsets of Security: that’s where they belong. Done in 750.

-30-

This is what I would like you to know about my mother:

She didn’t like what people were doing to the world; she found some ways she could be effective at making things better; she did them.

It is not required of us that we fix the world, but it is required that we try to leave it better than when we came into it. Mom succeeded.

I’m going to tell you the secret (it’s not a secret) to building reliable, operable, debuggable infrastructure. This is going to be terse, but hopefully understandable to someone with just a little experience.

Let’s take a second to remember that copyright is the reason ~every child doesn’t have access to ~every book ever written.