Blogs publish articles, or entries, which are basically the same as Usenet posts – but there’s no widespread mechanism for grouping and replying. We can fix that.

When something goes wrong, especially (but not limited to) at startup, you should log an error message that is as informative as possible. In particular, if your service has parameters that might conflict with any other running process –say, it wants to listen to a particular port– you should have the error message mention all of those details.

It’s even better if the failure does a little diagnostic and tells you what other process is using that port.

This message brought to you by the Campaign for More Informative Error Messages. -30-

There are two kinds of smart home enthusiasts: the kind who buy into a particular cloudy ecosystem and need to buy all new stuff every few years, and the kind who spend all their time tinkering on their in-house systems. Fairly often the tinkers also end up buying all new stuff, but they get to do it in incremental steps where everything works (more or less) during the transitions.

I’m not an enthusiast: I want a return on investment in money, convenience or fun.

When a backup fails to complete, that’s a reliable sign of trouble. Most of the time it’s in the backup mechanism, but the second most likely underlying cause is a problem in the thing which is being backed up.

-30-

This blog is created by Pelican, a static site generator that combines some text files that I write with a layout and some CSS styles to produce the HTML that is rsync’d over to the nginx webserver which answers your requests.

I just upgraded from 4.6 to 4.71, and also from an older python3 release to Debian’s current 3.9 release. Nothing appears to need to be changed, which is nice and relaxing compared to the last few upgrades.

-30-

I just realized that I internalized the O’Reilly house style decades ago, and so I think it’s the proper way to write documentation.

Primary elements: the document, even at book length, takes the form of a precise, pedantic, but informal letter to the audience. The author might reference themself as “I” and tell brief anecdotes to contextualize the material, and frequently encourages the reader in the second person:

You can also reticulate the frobnitz with the ‘–frob-harder’ switch if that feels more natural to you.

As a side effect, this style of technical writing minimizes the number of gendered pronouns, which I always prefer because I don’t know who is reading the work.

-30-

When you stop looking for ways to improve your sound reproduction experience and instead look for new music to listen to, you have begun to recover from audiophilia.

Or at least, I have.

Places in the house with acceptable sound systems:

• my bedroom
• the living room
• the den/theater
• the office
• the other end of the office
• the third system in the office
• two portable systems

Places in the house with marginal sound systems:

• the kitchen
• the dining room

-30-

Twenty-five years ago, approximately, my housemates and I bought office chairs – rolling five-star bases, adjustable arms, comes in a box with an L-shaped hex driver like IKEA stuff – and put them in our dining room around the table. They were cheap and comfortable.

I can’t tell you how many people looked at that arrangement and needed to talk about their sudden feelings.

The Cloud – where did we get that metaphor?

The answer is pretty simple. Imagine you are a techie working on an Internet project in the late 1990s. You are explaining to a less-technical audience how your application is going to be built. You have a whiteboard, and you draw some simple things as you talk:

This is a reminder to myself on how to make the systemd journald relay everything through rsyslogd, so we get useful info in /var/log.

Fun fact of the day: the AT in SATA is a direct reference to the IBM PC/AT launched in 1984.

However, this only works as long as the other party actually internalizes the risk and liability. Since there are no consequences for mishandling data, operating IT services you’re not structurally competent to operate, and eventually having your crown jewels stolen - the contractor doesn’t really internalize risk, has no incentive to mitigate it.

I will assume you have a working DNS server listening on the default port, 53, and that you have certbot or some other means of acquiring SSL certs.

• Install stunnel4

• Create a config file in /etc/stunnel4/dns.conf

pid = /var/run/stunnel4/stunnel.pid

[dns]
accept = 853
accept = :::853
connect = 127.0.0.1:53
cert = /etc/letsencrypt/live/randomstring.org/fullchain.pem
key = /etc/letsencrypt/live/randomstring.org/privkey.pem

Substitute the locations of an appropriate SSL cert and key.

• Start stunnel4.

-30-

My work-issued MacBook Pro (Retina, late 2013) began to break down: the speakers fried, it was running out of memory (8GB), and then it started rebooting spontaneously. I mentioned this and work bought a replacement. Since I’m capable of working around exciting new bugs, they sent me the newest M1 MacBookPro, with an Apple-designed and -produced M1 8 core CPU.

Herewith, a micro-review.