Right? Late 18th / early 19th century surgery was almost more dangerous than the wounds.

Dr*g?

So, I was at my pharmacy today getting my prescription dr*gs, and afterward stopped by my dealer to pick up some fucking heroin.

You mean, they're mounting something that isn't an SD card to the /sdcard directory? Like something truly evil, such as mount -t btrfs -o subvol=@home / /sdcard? Or do you think there's not anything mounted there; it's just a directory in the root partition? None of that would make any sense.

If they're letting whatever automount tool (eg udevil) do its thing, this is practically impossible. And if they know enough to do it by hand, I think they'd have answered the direct question of "which filesystem" with a filesystem rather than a mount point. Don't you think? We still don't know what filesystem they're working with, since they haven't answered the question.

I agree; it probably didn't occur to them. But it was a fairly common job in IT in the 90's. Not a career or job description, maybe, but a duty you got saddled with.

I can see that, although TBH I almost never have to "admin" EndeavourOS. I just upgrade every once in a while.

Most important to me is being able to find and install whatever software I want, and I have a string preference that it either be installed in my ~, or be managed by the package manager. I really dislike sideloading software globally. And Arch does this better than most. AUR is massive, and packages are trivial to write and install in the rare event something isn't in AUR.

It doesn't matter. FAT filesystems - which are usually the default on SD cards, simply do not support ownership or file permissions. Linux emulates these attributes at mount time, but they apply to the entire SD card. You can mount an SD card and tell Linux to act as if root owns everything on the card; you that you own everything on the card; and it will be so until you unmount it and remount it with a different ownership.

These are filesystem level attributes, not device attributes. If you have a modern internal nvme drive and you format it with vfat, you will not be able to set permissions or ownership at the file level, but only at mount time, for the entire drive.

What they really got wrong was the clothing: so much anime/hentai.

This is a techno-goth.

Base Arch can be fussy, but that's because there's a lot to set up, so many opportunities to forget things and only discover them later.

I ran Artix on a laptop for about a year; that was a constant PITA, although I still value their goals.

But EndeavourOS has been an entirely different matter. It's a "just works" Arch derivative.

I had so many fewer problems with Arch that I went through the effort to convert my 3 personal cloud servers from Debian to it. I went through a lot of work to replace thee default Mint on an ODroid to Arch, and it's been so much better. I put Endeavor on the last two non-servers I installed. So, yes, I personally find out far more reliable and easier to work with than Ubuntu, Debian, or Mint.

That said, I had dad install Mint on a new computer he bought because I had to do it over the phone and he never, ever, upgrades his packages, and almost never installs anything. If all I'm going to do is install it once and then never change anything, Mint is easier. But for a normal use case where I'm regularly updating and installing software, Arch is far easier and more reliable.

Or the Bavarians tell about Austrians.

Lightbulb jokes are universal, only the target changes. The Bavarians have some long-form jokes ("Two Austrians go on vacation to the Sahara...") that I'd never heard before going to Germany.

In case anyone is wondering, the joke (actually) goes:

Two Bavarians go on vacation to the Sahara and quickly find themselves bored. Being German, they decide to do something constructive, and decide to build a bridge from whatever scrap wood they can find. Two weeks pass in happy industry, but as they're flying home, the first slaps his head and says, "We have to go back!" "Why," asks the second. "Because we signed our names on it, and if anyone finds we built a bridge in the desert, we'll never hear the end of it!" says the first.

So they switch planes and head back. As they near the bridge, the first says: "Stay here, and I'll go check the coast is clear," and he heads off over the dunes. A while later, he returns, crestfallen. "We are undone," he cries, "a couple of Austrians found our bridge already!" "What are they doing," asks the second. The first answers:
"Fishing off it."

Oh. I couldn't figure out the joke, and I'm still not sure about the format, but your explanation makes sense.

A studio should be able to afford a good LTO tape drive for at least one backup copy; LTO tapes last over 30 years and suffer less from random bitrot than spinning disks. Just pay someone to spend a month duplicating the entire archive every couple of decades. And every decade you can also consolidate a bunch of tapes since the capacity has kept increasing; 18TB tapes are now available: $/MB it's always far cheaper to use tape.

They could have done that with the drives, but today you'd have to go find an ATA IDE or old SCSI card (of you're lucky) that'll work on a modern motherboard.

But I'd guess their problem is more not having a process for maintaining the archives than the technology. Duplicating and consolidating hard drives once a year would have been relatively cheap, and as long as they verified checksums and kept duplicates, HDs would have been fine too.

F-Droid

Most of the apps I have and use are installed via Droidify. The ones that aren't are company apps, like banking or airline. I could just used the web sites for those; they're only conveniences.

My phone isn't rooted, and I didn't read the article so I don't know how this will affect me. If push comes to shove, I'll simply bite the bullet and get a phone I can install Linux on next time, regardless of how polished for daily driving it is.