People. It’s people.

That’s Alyssa Rosenzweig. Lina appeared by vtube stream.

Lina has? Link?

What computer/what hardware? What media?

They wanted to write more drivers in Rust. They sought the approval of one of the key maintainers of part of the Linux kernel even though their approval wasn’t needed. That guy rejected any new Rust code due to personal dislike. Obviously this upset people, and Linus didn’t step in to manage the dispute until the drama had blown up.

Rumored, not confirmed.

Does the non-flatpak one do the same? I know there was some drama over the unofficial flatpak distribution. It might also be that the flatpak one doesn’t have the necessary access.

There’s still microcode and other firmware blobs. Coreboot is just BIOS.

Seriously? It’s the default file manager for KDE since version 4, way back in 2006. If you’ve KDE at all since then, you’ve probably used it.

You assume the shell isn’t compromised.

Yes, but the last times it was just one city, this time it’s a state.

Internet2 too

For basic functionality, yes.

It’s called physical-to-virtual, or p2v. Proxmox uses qemu under the hood, so you should be able to start from their docs to create the VM: https://pve.proxmox.com/wiki/Advanced_Migration_Techniques_to_Proxmox_VE

I would just download them. Already ripped, encoded, and compressed.

What laptop? BIOS option?

I don’t think static linking is that difficult. But for sure it’s discouraged, because I can’t easily replace a statically-linked library, in case of vulnerabilities, for example.

You can always bundle the dynamic libs in your package and put the whole thing under /opt, if you don’t play well with others.

What are the crazy historical reasons? As far as I know, running six ttys and one graphical session, in that order, has been standard.

The really crazy historical way to test for crashes is num/scroll/caps lock. That’s handled by a very low-level kernel driver. If those are responsive, it’s probably just your display (gpu, X, wayland, or something) that’s locked up. If they’re unresponsive, your kernel is locked up. (If you’re lucky, it’s just gotten real busy and might catch up in a minute, but I’ve only seen that happen once.)

Anything that might interfere with sleep. Literally any attached device might have a buggy driver.

I don’t see a list of hardware in your edit.