It’s harder when you can’t even talk about “the 00s” gracefully, though. How do you say that?

The aughts/oughts/noughts/noughties, depending on where you’re from.

I don’t know what TTY7 is, but if I had to guess I’d say Plymouth, which is the graphical loading screen that covers the boot messages.

SDDM is the login screen, but when you’re already logged in it’s not going to display anything. If you reboot your computer SDDM is what you see before you start KDE. If you use Gnome then this will be different because Gnome doesn’t use SDDM.

For comparison here’s the error message KDE displays in the same situation: https://www.reddit.com/r/kde/comments/15477a5/screen_locker_is_broken/

I believe it has no localization support, but the language is clearer and the command it tells you to run is much simpler. A big problem with it is that Ctrl-Alt-F2 does not actually get you to a working TTY on many distros – e.g. on Fedora TTY1 is SDDM and TTY2 is the DE – and the error message is not adjusted based on which TTY is which.

It doesn’t look like this has been conclusively dated. It’s possible that he drew it later in his life, e.g. after finding the report card in a box and reminiscing about his childhood.

What did he pick off the ground?

My understanding is that it is fixable by just implementing a couple of APIs, but Artix barely has the resources to fix their own init system, so they aren’t able to support such compatibility.

No you haven’t. The security is the Jellyfin login prompt, then the Jellyfin container, and if you’re really paranoid, that container won’t be in your LAN.

The funny part is that I can’t tell whether you’re talking about LLMs or the C-suite.

The only real issue I’ve had was that the btrfs partition sometimes shits itself and requires some CLI commands in emergency mode to fix it.

At the risk of stating the obvious, this shouldn’t happen. You haven’t said enough to know what the issue could be, but most of the time when btrfs spontaneously stops booting on you, it’s because it has dropped to read-only mode because it detected a problem with your drive.

To be fair to the internet discussion, Linus’s (and the other maintainers’) communication on this could have been better. Still, it should’ve been pretty obvious from the start that this is a sanctions thing, and people and companies don’t end up on sanctions lists for no reason – though it is easy to end up on the list if you have even indirect ties to the Russian state.

The discussion around this has been physically painful to read. From what I gather, the delisted maintainers are people on sanction lists, i.e. somehow connected to the Russian state, and they have been given the opportunity to prove their innocence by providing some (admittedly unspecified) documents to Linus and the Linux Foundation.

Judging by Linus’s updated comment in that article there are legal concerns involved, as the Linux Foundation is a US-based organization. Though even if they weren’t, it is the morally correct thing to do to give Russian state actors the boot.

No, but I’m not a lawyer, so I’m not going to go into the details that I - and other maintainers - were told by lawyers.

I’m also not going to start discussing legal issues with random internet people who I seriously suspect are paid actors and/or have been riled up by them.