Btw: does anybody know what bad things actually happen if there is no metal cage that blocks all the radio?

Noise happens. Could be no problem, or it could hurt your wifi or mobile data connections, or maybe raise a neighbor’s ham radio noise floor. I saw this recently when setting up a pi to run BirdNet-Pi. The USB3 connection to an SSD caused enough noise in the 2.4GHz band that the onboard wifi radio could only connect on the 5GHz band.

To start - moving services from bare metal to rootless Podman containers running via quadlets. It’s something I have had in mind for a while but keep second guessing the distro choice. Long-ish release cadence, systemd-networkd and a recent Podman version in the native repos, well supported, and not Ubuntu.

So far openSUSE Leap seems like the winner. A testing machine is up to install everything, write some deployment scripts, and decide on a storage layout and partitioning scheme.

If anyone has another distro to recommend that checks these boxes let me know!

I like rolling release for the desktop, but only want critical patches in any given month for this server, and a major upgrade no more than every 3-4 years. Or an immutable server distro. But it doesn’t seem like networkd is an option for the ones I’ve looked at (Fedora CoreOS, openSUSE MicroOS), and I am not sure if I want to figure out Ignition/Combustion right now.

Next project - VLANs on Mikrotik.

OP - Navepoint makes good racks for reasonable money. I have a Pro series 9u from them and it went together without any problems. It’s on the wall with a pretty big ups in it.

My understanding of why is that it relates to their change to a scene-referred workflow. Up to v3, darktable used a display-referred workflow like other programs. In that model the image you start with is mapped on a tone curve from the start where 0 is pure black and 1 is pure white, and the midpoint is set to midway between. This is all from the standpoint of what your display can render. The scene-referred workflow in v4 doesn’t do that. All the tones are mapped in an unbounded and uncurved way. So images look flat, but you’ve retained maximum data, so you have more to work with. The developers assume that you want control and maximum fidelity. There’s a better explanation in the intro of the documentation. This impacts everything - especially the color balance.

One of the problems is that all of the display-referred tools remain as modules in the interface, and some are even used in the base processing, but you’re not supposed to use them. At least if you want to do things the ‘right’ way. We created a custom panel that has 90% of what we regularly use (shared UI with my partner). That plus creating some presets that work well with our cameras has made it very quick to get a satisfying output in a minute or less.

Honestly, if you want to do minor tweaks to a RAW and mostly want what the out of camera JPEG looks like, there are much easier tools. If you at least occasionally deal with really challenging photos, or you want to get creative in the processing of some of your RAW images, darktable opens up a lot of possibilities, while being free and open source. So I think it’s worth the effort to learn. Shooting with a colorchecker helped us get the presets we wanted for a variety of shooting conditions.

Same here. DigiKam and darktable.

Getting color balance with raw in darktable took quite a while for us. It was helped by using a Color Checker Passport in a few shooting conditions to use for reference and calibration. Once we got past that darktable has been great.

If you want to keep using networkd, you might want to consider if multiple interfaces are causing the wait. NM doesn’t care, but networkd gives more granular options for dependencies. If you have wired and wireless and only one in use the systemd-networkd-wait-online.service waits for a timeout period. You can find lots of info on it related to boot delays with that service.

Try the --any switch on the systemd-networkd-wait-online.service launch configuration. This will tell the wait-online service that any single routable interface is enough, you don’t need them all.

Run:

sudo systemctl edit systemd-networkd-wait-online.service

That adds the override.conf for the service. Add these lines:

[Service]
ExecStart=
ExecStart=/usr/lib/systemd/systemd-networkd-wait-online --any

The other possibility is if you have virtual .netdev devices configured (VPN, bridging, etc) and some of them are not essential for the machine to be online, you can set RequiredForOnline=no on the ones that aren’t essential.

Interesting!

it wasn’t for dumb people who didn’t know any better

I mean, it kind of was though, wasn’t it?

Just because more knowledgeable people found it interesting and got it for the novelty or to see how it worked doesn’t mean it wasn’t a product intended for people who, Kodak hoped, wouldn’t know any better. That doesn’t mean I’m saying your father didn’t know better.

Hopefully he’s still around and you can ask him about the relative image quality between those formats. If he was interested in quality, he wasn’t going to grab the disc camera. It wasn’t like Betamax where it was superior but lost a battle in the marketplace. Disc film was objectively much worse than even 110 while being much more expensive to buy and process.

It’s not bad to get running, and the alerting is really flexible. You can add Nagios and syslog alerts easily too.

Using it here. Love the flexibility and features.

I’m running NUT on the host os - no container. If that’s an option for you it will probably be much more reliable.

Huh. Losing USB access?

It’s not very exciting, but: Network UPS Tools (NUT).

Keep everything in good shape in the event of a power outage.

Here’s my messy-cabled 9u rack.

It has:

• Fiber gateway out of view on top of the rack.
• Switch, which also powers 2 Ruckus APs and 2 other switches.
• Mikrotik RB5009 router.
• Raspberry Pi x3 all running Debian Bookworm. I have too many pis right now, running Home Assistant, LibreNMS, Log collection, and a read-only NUT server that orchestrates shutdowns and startups on power loss. I need to consolidate these.
• 1L PCs. One is on Debian serving media and files. The other is a test server where I’m trying out Immich on openSUSE. I’m considering moving to that and rootless podman for services. To that end I have another of these 1L boxes on my desk trying other options (MicroOS, Fedora IoT, maybe others).
• HDs. These are backup drives for the 1L server. I keep them powered off except when needed.
• UPS and a managed, switched PDU.

Everything is set up for low energy consumption (~90w), remote admin, and recovery from power loss.

My favorite French borrowings are gentle, genteel and jaunty. All borrowed from gentil (kind, pleasant, nice), but at different times (13th century, late 16th, and 17th, respectively).

The French word is from Latin gentilis, meaning “of the Roman clan.” English borrowed that from Latin as gentile.

So we have 4 English words, all from the same Latin origin. Of them, genteel is probably closest to the Old French pronunciation (but the vowels are still a little bit different).

put the phone to my ear

Clearly you would look more normal if you blast it on the speaker while holding the phone in front of you, like everyone else. /s

It’s funny that there are two unambiguous alternatives to bimonthly, but they both mean 2x/month: fortnightly and semimonthly.

Both German and Dutch distinguish their equivalent words with clear prefixes meaning half- and two-. The English word was unclear after 1066 since the French word bimensuel would have been used by the new bosses. And that means 2x/month. English used bimensual for a while before developing a new, worse word with the Latin origin bi- and the Germanic origin -monthly. And it seems to have been ambiguous from the start. So this has probably been messed up for almost 1050 years.

Maybe we should resurrect the Old English prefix twi- to make a new(old) 1x/2months word twimonthly or more intuitively, twomonthly that we can use in opposition with halfmonthly.

Interesting. I wonder if they vary the cut based on what else is trendy at the time. Or by region.

Edit: yeah, I see your latest. Not surprised tbh.

501 is the style

0126 is the color

32x34 is the size in inches waist x inseam

Levi’s still sell non-stretch 501, and they should fit pretty much the same (although there is a lot more variation from one batch to the next than there used to be). If you can order from Levi’s online you should be able to get similar ones. Or check any shops for 501 32x34 in 100% cotton.

Another option would be to get the original 501 shrink-to-fit (color 000). It’s a process to break them in (not as much as heavier denim), but they should last longer since they’re not stonewashed or otherwise treated to make them soft. Just read up on sizing first.

That and the shrinking ability to grant access to device storage. If that becomes an option only on rooted phones (which seems like the directly Google is heading) it will make the audience for such an app much smaller.