KYOCERA ECOSYS P2235DW laser printer
I heartily recommend and endorse the KYOCERA ECOSYS P2235dw Monochrome Laser Printer. According to Amazon, it cost me $462.
I heartily recommend and endorse the KYOCERA ECOSYS P2235dw Monochrome Laser Printer. According to Amazon, it cost me $462.
I upgraded my Debian Bullseye
$6.47/month VPS
from Bullseye (Debian 11) to Bookworm
(Debian 12.15 according to /etc/debian_release contents).
It’s a VPS hosted somewhere in the Kansas City metro area,
I was prepared for the process to not work,
and I’d have to try some difficult recovery method.
It worked! Victory is mine! Science triumphs!
This is a little circuitous, as real life often is. My house has two fiber connections to The Internet. The ISP in question has failed to bill for them since July of 2026. We got a large lump sum bill for the connection that wasn’t paid for via ACH. We canceled it, because I’m retired now and no longer need a dedicated work connection.
A pickup truck crashed into an electric pole just down the road yesterday. The pole fell partway over, held aloft by the power cables. The electrical mains power dropped abruptly. My Dell R530 and Qotom fanless server are powered through an uninterruptible power supply, but only the R530 has the USB connection and runs apcupsd to get notifications that the UPS is running out of energy.
I changed from Arch Linux linux-hardened
to plain linux kernels on my
Dell R530
server.
I have had the Arch Linux
linux-hardened kernel installed on
my Qotom fanless server
since I bought it a couple of years ago.
The Qotom has had kernel panics on the last two
linux-hardened updates.
I changed to the plain linux kernel.
It was pretty easy, even though I had a case of the nerves about it.
As is my habit, I ran pacman -Syu on my
Qotom fanless server
to get all the fresh Arch Linux software updates.
The update included a kernel, moving from “linux-hardened-7.1.3.hardened1-4”
to “linux-hardened-7.1.5.hardened1-1”.
Kernel upgrades are almost always no big deal.
Today, I got a kernel panic!
I used to live in a neighborhood with elderly power and phone infrastructure. The 120V, 60 Hz main power fluctuated during spring and summer. I bought an APC Back UPS 1500 uninterruptible power supply in early June, 2020 to get whatever server I was using back then through the inevitable series of short power losses.
While fiddling with my educational TFTP client code
I noticed an oddity.
Sometimes my client could talk to a TFTP server,
but not vice versa.
The TFTP server, when it condescended to acknowledge a connection,
logged a message like recvmsg(): connection refused.
I used a local TFTP server, running on my laptop,
to avoid these errors,
but the mystery of why the server returned
no TFTP ACKs or DATA packets remained.
My laptop’s /etc/hosts file has entries like this:
fe80::46a8:42ff:fe2d:c255 monarcheno1
# eno2 - 10.0.10.1
fe80::46a8:42ff:fe2d:c256 monarcheno2
# eno4 10.0.20.1
fe80::46a8:42ff:fe2d:c258 monarcheno4
# ens5 10.0.40.1
fe80::6a05:caff:fe4a:8ac7 monarchens5