It’s a shame that that the list doesn’t translate well into “what device can I go out and buy”? Every shitty manufacturer has to constantly churn design changes, and hide it all behind the exact same model number.

Is there a reason to install one(1) singular OS across multiple partitions? Is it just because that’s how our ancestors did things?

Partitions are crude buckets that tell Operating Systems that “this lump is a filesystem that you know how to read” or “you don’t know how to read this, leave it alone”. Partitions tell UEFI that it should only use this special FAT32 chunk. A partition is not a good mechanism to set quotas, as you can see from how difficult it is to expand. A bunch of partitions that are all mounted together does little to isolate against failures.

If you want to run an OS across two filesystems that provide different characteristics (one provides atomic snapshots, the other provides ??), that would have to live on different partitions. Would you be better served by putting it all on the more modern FS? Is the older filesystem only kept around because it straddles “what my OS knows” and “what my bootloader knows”? If it’s just for the bootloader’s sake, that’s why we have /boot.

First you have to make a new --user remote. Then you can list your current stuff and install it on the --user side one package at a time, (with --no-pull so it sucks the existing install). Then, you delete the --system copy of packages.

Instead of having an efficient chip monitoring the power button, they integrate that job into some 10nm chip. That chip doesn’t get to power off, so it just pisses away power on gate leakage all day long.

Debian Testing.

ARM systems don’t have the whole ACPI thing to describe what hardware is where. Linux has to bodge together its view of the system with a devicetree instead. If you don’t know what device IP blocks are integrated into the SOC (and locked behind an NDA), good luck blindly guessing. You don’t even get EFI booting, you get shit like “the rpi gpu runs its own proprietary bootloader lol”.

Has Qualcomm ever been helpful?

Lobster was an unbelievably buggy distro. I had no end of sleep and compositor problems, and outright system hangs on it. Minotaur was better, but still give me far too much crap.

I would rather run a “crack monkeys with a sourceforce account” nightly distro than go through Ubuntu’s idea of a beta again.

I think “endurance” cards are where you get something reasonably non-self-destructive, for a modest premium.

I’m somewhere between Kitty and Ptyxis.

The existing buttons are made out of a plastic that wears well when rubbing against their contact-points in the case. The plastics are chosen to be compatible, self-lubricating and “not spalling or rubbing eachother to death”.

I doubt that these metalized buttons have been tested for their long-term wear characteristics.

Wait till you see a Mediatek

The PineTab doesn’t even have a wifi/bt radio that’s supported by its own OS. When you’re an OEM and you’re choosing what chips you’re putting in a design, I think you should stick to chips that are usable. Chips where the manufacturer has written specs and maybe even a driver that transforms “a piece of glass with a lead frame” into something with a purpose.

Anyway, that’s just how I feel.

Go to Desktop Mode, run Plasma Discover, get the Heroic flatpak, run Heroic, log into GoG there, install games.

Heroic is pretty damn good at doing the rest. It’ll install the Linux or Windows version of your games, it’ll add them to Steam, it’ll run them. Heroic will even give Steam some coverart for your games. (Many are missing the logo, tho. DeckyLoader +SteamGridDB plugin fixes that.)

Flatseal is the tool.

(Another benefit to using the flatpak version of Steam is that Steam leaks rather substantial chunks of /dev/shm memory. The flatpak automatically cleans that up. God knows why Valve hasn’t fixed this yet.)

The simplest way to opt out is to “install any other OS instead”.

Hahahaha NO

The hard part is finding a stable identifier, instead of “this interface is know as sink 48 at this exact instant. It will be a completely different number tomorrow. It might even be a potato emoji, who knows?”

Might as well go for Win11, you’re going to have to deal with it next year anyways.

Windows doesn’t do minimal, it does whatever the hell it wants. There are some OOBE tricks to get a local account working.

I have used the privacy.sexy app to strip down some of the most obnoxious Win11 bits - be warned that you have to disable defender to have it work. Is it doing bad things? Is MS doing incredibly shady shit with their detections? Who’s to say? When I turn on Defender afterwards, everything seems “fine”.

There’s no need to get rid of grub, or play games with different boot drives. Get to know how EFI works. Look at efibootmgr’s output - that’s pretty much all that the firmware knows. The firmware has multiple entries consisting of a drive (magic device number), a program path (EFI\grub\grub_x64.efi), and maybe a string to pass along. There is a priority list (0003,0001,0002) which MS occasionally likes to re-arrange.

Power management on “the most boring Intel chip imaginable” is still touch-and-go at times.