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.
rotopenguin
joined 1 year ago
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.
Sometimes when I go into Desktop Mode, X11 doesn't have any screens. The deck just sits there with a black screen, until I ssh in and kill plasma
It is rare to see a game get this wrong, the last one I saw was a Borderlands. If you look at a game's Steamdb cloud listing, they list Windows's save location, and then Mac/Linux saves are expressed as a rewrite rule.
Cloud saves on PS are handled quite simply - if you didn't pay for your very own PS Plus then go fuck yourself. I have lost dozens of Aloy hours on my brother's PS4.
I think "endurance" cards are where you get something reasonably non-self-destructive, for a modest premium.
You can grab Kate from the Windows Store right now. Get all of the KDE apps, they're pretty much the only good stuff on there.