A while back I wrote about my various settings in X to get programsworking on my HiDPI display , partly in an attemptto document exactly this for my future use at work. Well, I just wentthrough the exercise of converting from two Dell U2412M 1920x1200displays to two Dell S2721Q 3840x2160 displays, and sadly I found alot of places where I had to make changes other than

Suppose, not hypothetically, that you're exploring what somedevice exposes over SNMP . You're probably using snmpwalk (orperhaps snmpbulkwalk ). Snmpwalk isprobably completely clear to people who use it all of the time, butit's not clear to people like me who touch it only once in a while.So here are some notes from my recent experiences (for future me,among others), assuming general background in reading SNMP .

To start with, many of the interesting snmpwalk options are covered

In the past I have tended to use the term 'IPMI' for several differentthings, in a somewhat confusing and imprecise way (much like how I'vebeen imprecise about terms like 'SSD' and 'NVMe' ). For various reasons I want to straightenthat out in my head, so I'm going to write up my understanding of thewhole area.

A BMC is a "Baseboard management controller", an additional server embeddedin your real server (or server class motherboard). The

Suppose, not hypothetically, that you have some servers of interest which provide interesting information through their BMC's web server that theydon't expose through IPMI in any non-proprietary way . But their BMC does support SNMP , theSimple Network Management Protocol, and perhaps they expose theinformation in SNMP. You would like to peer through the informationthe BMC exposes over SNMP, which requires actually understanding abit of SNMP. Since I went through this today, here are some notes(for a future me if

I just upgraded my office and home desktops to Fedora 35 ( I knowI'm late to the party, but ). Afterward, I noticed something about the Go version :

I guess [the reason] that Fedora 35 (still) has Go 1.16, not Go 1.17,is that 1.17 came out too close to the release freeze. It looks likeFedora 35 branched from Rawhide a week before 1.17, and presumably noone specifically

Over on Twitter, I said something :

Every Linux daemon that refuses to stop during a reboot for "goodreasons" needs to understand that it's delaying the system's returnto service by a minute and a half (systemd's timeout) or more. Whenthat's my desktop, I get quite angry with the daemon. Hi, PackageKit.

When I type ' reboot ' (or invoke the equivalent in a GUI), mymachine immediately goes out of service. My desktop session ends

If you use your system's Python for pipx and then upgrade your system and its version of Python, pipx canhave a bad problem that renders your pipxmanaged virtual environments more or less unrecoverable if you dothe wrong thing. Fortunately there turns out to be a way around it,which I tested as part of upgrading my office desktop to Fedora 35today .

Pipx's problem is that it stashes a bunch of stuff in a~/.local/pipx/shared virtual environment that depends on the

For reasons beyond the scope of this entry , for thepast couple of years I've been running a large commercial anti-spamsystem (and its malware recognition) side by side with what we couldput together with ClamAV and somelow-cost commercial ClamAV signature sources. Since the commercialanti-spam system is on the way out, one of the things I keep an eyeon is what it detects as malware that ClamAV misses (and then I tryto figure out if there's some message signature

A while back I read Jesse Duffield's Go'ing Insane Part Two:Partial Privacy (eventually via ).In this installment, Duffield is frustrated by how Go controlsthe visibility of identifiers outside the package:

Unlike in other languages where privacy is controlled with private or public keywords, Go marks privacy with capitalisation. [...]

I suspect that this is an issue in programming language design thatpeople have strong opinions on, like Python's use of significantindentation; some people will find it appealing