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
Just use docker/podman containers: They’re way easier to use and correctly configure than jails.
Podman quadlets will even spin up containers as systemd services. You could automatically assign solitary confinement containers to new inmates on the fly.
No. 404 media is written by people. I’ve personally been impressed by their reporting over the last year.
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 /
I think this is probably more a copy of various East Asian social media services than anything Reddit-like. Pretty sure TikTok and a bunch of Chinese video streaming services already do this. I think the whole Money -> Gifts -> Rubies -> Money chain is intended to dance around money laundering legislation. The same way that Pachinko machines aren’t technically considered gambling in Japan.
The problem isn’t just that people are making AI slop: It’s also a problem that Zuck has seen the engagement that this trash generates and realized that it’s good for Meta’s metrics. They’re never going to do anything to stop it if the alternative is that investors might realize that Facebook is a rotten log.
If you’re doing activities outdoors: Always bring an extra bottle of water. That is to say, bring a bottle to drink, and then another for when you get thirstier than expected. This season is relatively cool, but you really don’t want to be caught unprepared. Also: Arizona has a law requiring businesses to serve water for free if you ask. Don’t let anyone bullshit you and ask for money.
Keep an eye on the weather reports, and do not hike down washes, ravines, or narrow canyons if there’s a rain storm anywhere nearby. Heavy rainfall several miles away can turn a sunny, dry ravine into a raging torrent that can kill. If you see a road that’s currently flowing with water, don’t try to cross it, even in a big car. You don’t know how deep it really is, and even just a few cms of fast water is enough to sweep a person off their feet and drown them. It doesn’t take much more to get a car stuck.
If you’re going to Northern Arizona, bring warm clothes. People can be caught unprepared when they leave Phoenix for a day trip and it’s 60⁰F, but when they get to Flagstaff 2h later it’s snowing.
If you see a Jumping Cholla:
Don’t get too close. Their spines are longer than they look because they get so thin as to be nearly invisible.
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 that’s elephant garlic, then it’s the wrong amount. That shit is 3x the size with 1/10 the flavor. Fuck that, I’ll peel a whole head of normal garlic myself.
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.
My indie theater has a bright blue pixel in their main screening room.
I complained about it when I first noticed, which was more than a year ago. It was still there the last time I went.
The Grand Nagus has come to earth in search of profit
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:
'Es shot? Dump eet.