Eh, maybe. Back during feudalism, emancipation of serfs was also considered theft from the nobles who owned the land (and thus the serfs who worked it).

Sometimes governments implemented programs to reimburse the nobles for losing “their” serfs, and sometimes not. Now that we’re a couple centuries removed from that drama, we generally accept that the destruction of feudalism was a good thing, regardless of whether it was theft.

There used to be a similar bug in the Roku jellyfin app.

If you can recreate the subtitle issue using test file 5 from this repo, it might be worth submitting a bug report. https://github.com/ietf-wg-cellar/matroska-test-files

Programmable condoms which make the user look like a bad dragon dildo.

I once had a directory in /tmp called etc which contained subdirectories for something I was migrating.

I thought that I was in /tmp when I ran rm -rf etc… I was actually in /

Look up the GPU on these charts to find out what codecs it will support: https://developer.nvidia.com/video-encode-and-decode-gpu-support-matrix-new

NVENC support will tell you what codecs your GPU can generate for client devices, and NVDEC support determines the codecs your GPU can read.

Then compare it with the list of codecs that your Intel can handle natively.

If you want to move your containers to a different location, look into configuring docker’s data-root: https://stackoverflow.com/questions/24309526/how-to-change-the-docker-image-installation-directory

You copy /var/lib/docker to a new location and update /etc/docker/daemon.json

I will say: Moving data-root to an NFS mount isn’t going to work well. I’ve tried it, and docker containers rely on filesystem features to run their overlays. On an NFS, this feature isn’t present, so your services will duplicate the container’s entire filesystem. This will tank your performance and is basically unusable for anything but trivial examples. Docker data-root basically needs to be a “physical” disk.

I’ve had no issues using NFS shares mounted as docker volumes. It’s just the data-root where it’ll fail.

If you’re doing it from scratch, I’d recommend starting with a filesystem that has parity checks and filesystem scrubs built in: eg BTRFS or ZFS.

The benefit of something like BRTFS is that you can always add disks down the line and turn it into a RAID cluster with a couple commands.

Yep, the problem was that docker started before the NFS mount. Adding the dependency to my systemd docker unit did the trick!

isn’t it an annoyance having to connect to your home network all the time?

It’s less annoying than the gnawing fear that my network might be an easy target for attackers.

Proliant G9 is an EoL server that hasn’t been sold since 2018. Meanwhile, Debian bookworm released last year. I’d be surprised if the problem were that your installer gave you a kernel that’s too old.

What is the output of ip addr show?

It might also be worth ruling out low-level issues:

• Check for anything strange in the BIOS related to disks (fwupdmgr can automatically install BIOS updates from a live Linux session. I don’t know if Bazzite does this)
• Try using a different SATA port
• Run some SMART tests on your drives

To be pedantic, Ford’s threat is to “rearrange [the computer’s] memory banks with an axe”

The countdown is until he starts doing it.

A much better idea than when I tried to organize my restaurant with hashtables.

It was too much for the waitstaff, who had to reindex the floor plan every time they added or removed a plate.

On the plus side, delivering the right food was always O(1).

Surely this could be good, right?

If celebrities need to be accessible to their biggest fans, maybe it would induce them to leave the birdsite? And if this is as big a migration as the article suggests, it has the potential to snowball in network effects, giving other influential users one less reason to feel chained to a dumpster fire.

I worked on a product that was only allowed to return 200 OK, no matter what.

Apparently some early and wealthy customer was too lazy to check error codes in the response, so we had to return 200 or else their site broke. Then we’d get emails from other customers complaining that our response codes were wrong.

Not that I was ever interested in being military, but I was at a lunch with two older lifelong army retirees. They kept talking about how military service broke their bodies and politicians won’t cover their medical costs. These injuries were independent of any combat: It’s just expected that you sell every part of yourself when you sign up.

Who wants to be 45 years old with a limp, be unable to hear a quiet conversation, and have horrible back problems?

Yes, OP I highly recommend a GL.iNet device. It’s pocket sized and always does the job.

It’s also great for shitty wifi that tries to limit how many devices you can connect. The router will appear as one MAC and then all your other devices can route traffic through it.

As someone who has owned enterprise servers for self-hosting, I agree with the previous comment that you should avoid owning one if you can. They might be cheap, but your longterm ownership costs are going to be higher. That’s because as the server breaks down, you’ll be competing with other people for a dwindling supply of compatible parts. Unlike consumer PCs, server hardware is incredibly vendor locked. Hell, my last Proliant would keep the fans ramped at 100% because I installed a HDD that the BIOS didn’t like. This was after I spent weeks tracking down a disk that would at least be recognized, and the only drives I could find were already heavily used.

My latest server is built with consumer parts fit into a 2U rack case, and I sleep so much easier knowing I can replace any of the parts myself with brand new alternatives.

Plus as others have said, a 1U can be really loud. I don’t care about the sound of my gaming computer, but that poweredge was so obnoxious that despite being in the basement, I had to smother it with blankets just so the fans didn’t annoy me when I was watching TV upstairs. I still have a 1U Dell Poweredge, but I specifically sought out the generation that still let you hack the fan speeds in IPMI. From all my research, no such hack exists for the Proliant line.

The problem with chromebooks is that the base specs are pretty shit. A lot of them have 4 GiB of RAM and maybe 16GiB of disk if you’re lucky.

They were designed to be thin clients to connect students to the internet, and little else. Maybe they could be hacked into something useful, but I don’t think it’ll ever make a good PC. They were always destined for the landfill.

Meanwhile, the best thinkpads were quality machines back when they came out. IMO, that’s why they’re still so versatile today. Free software can’t fix bad fundamentals.

is it dishonorable to find loopholes in the rules of the honor culture

Dueling culture in 18th and 19th century Europe was commonly organized around concepts of “gentlemanly honor”. Even back then, people recognized the need for loopholes.

Consider the case of two friends who got drunk at a tavern, each one declaring how much they loved the other. Eventually, one friend goes overboard “I love you more than you know!” to which the response is “But that cannot be, for my love of you is infinite!”. Soon this becomes an argument over who loves the other more, and eventually they have to settle their friendship like gentlemen: With swords at dawn. If they’re smart and sober up in time, their seconds will work out a solution before the fight, but there are cases recorded where the friends kill each other because honor trumps love.

There were also loopholes which worked to favor the person that society already deemed more “honorable” (wealthy, connected, liked, etc). It was generally accepted that a gentleman of certain standing could honorably refuse another’s challenge to duel if their social stations were different. Think a “new money” banker’s son challenging a minor nobleman over a loan that’s due. It simply wouldn’t look good to have some commoner slaying an aristocrat, even if said aristocrat was an asshole.