lemmyng

In some cases those were load bearing cables, too

Knocking is usually reads (from the header seeking), brrr is heavy writes.

Obligatory “/laughs in alpine” response.

The prompt says “can boot”, not “is usable with”. If it gets to the kernel and then hangs that still counts.

Using LLM for format conversion is like taking a picture of an electronic document, taking the card out of the camera and plugging it into a computer, printing the screenshots, taking those prints to a scanner with OCR, turning the result into an audio recording, and then dictating it too an army of 3 million monkeys with typewriters.

Open to criminals, of course.

The other responses have so far talked about hardware setup, so I’m not going to do that. Instead I’m looking at your software setup: VMs can be comparatively power inefficient compared to containers, specially for always-on services that idle often.

Well it wasn’t so much paranoia as obsession. The person who found it wasn’t paranoid, they just went “Why is my connection taking a quarter of a second longer than it used to? This is unacceptable!!!”

Does registry still have that problem of making it practically impossible to do garbage collection on old images?

You’re going to start a fight with the doas people.

Missing the -i.

Still not as bad as chmod -R 777.

Is a chicken egg an egg laid by a chicken, or an egg that if fertilized would hatch into a chicken?

Yeah, you’d have a LoadBalancer service for Traefik which gets assigned a VIP outside the cluster.

virtual IP addresses

Yeah, metallb.

The container is reproducible. Container configuration is in version control. That leaves you with the volumes mounted into the container, which you back up like any other disk.

It’s not that Seagate improved (which it may have), it’s more that WD has noticeably declined. It’s not a race to the bottom (yet), but there’s effectively no competition any more, so they aren’t incentivised to improve quality.

I think there’s a mistake, I can’t fit “neovim” into 8 across.

Figure out the uid/gid (numeric) for the user in lxc, then change the data permissions to those.

Use -m and limit the build job’s memory so it doesn’t kill the docker daemon.