ApertureUA @ ApertureUA @lemmy.today

Posts

0

Comments

15

Joined

2 wk. ago

display drivers

describes an issue that would be the job of your compositor & window manager

ODF support is in MS Office as well, but if you want to be extra sure you can export as .doc from any office suite (Libreoffice should also tell you if a feature you are using can't be exported).

All foam does, you need a unique property for the name

Oh, see, unlike on x86 where you have the ACPI to detect hardware with minimal device quirks (still a lot of them), everything else doesn't have that. Well, except some Qualcomm chips, but their implementation sucks and basically only works reasonably with Windows and Windows Phone. So you need a device tree blob (DTB) to tell the kernel where everything is. But enabling all of the drivers in a single kernel build makes it not fit (the partition for that is traditionally quite tight), so you make different kernels per device.

AND, on Android in particular, lots of features need device specific configuration for all of the small stuff like the proximity sensor and the cameras (a LOT more complex than webcams). This + the need for OEMs to insert their own spyware and the already existing tradition at the time to make device specific images made the decision stick around. There's GSI, which basically forces the OEM to write drivers and all of that with a stable-ish API to make universal images possible, but it results in a system with lots of tiny inexplicable problems that slowly make you loose your sanity in my experience.

How postmarketOS handles it is that there are basically meta packages per device that depend on the kernel package appropriate to the device (sometimes for a whole platform or SoC, having multiple DTBs inside for each device) that flashes itself to the appropriate partition via a post installation hook, as well as all of the config files for apps that need device specific stuff and don't already have it upstream (like camera apps).

I use MUSL/Linux on a tablet btw

Hello, this is Linus Torvalds, and I pronounce Linux as Linux

1. I
2. Am
3. A
4. Fucking
5. Idiot

It doesn't fit

???

Debian separates out stuff with :[arch] suffixes, and is really flexible in the sense that it even lets you install stuff from completely different architectures for, for example, use with qemu userspace. An i386 package is going to only request i386 dependencies, unless it explicitly specifies an architecture, and vice versa. Arch Linux uses the "lib32-" prefix and I don't really remember how it worked on Fedora but I would imagine something similar. All "gaming focused distros" are merely just their mainstream counterparts with an extra repo for a few packages, it's not going to change fundamentals.

Ah yes, everyone on the internet is American

There's no such thing as "The" in both Russian and Ukrainian, but what I've seen happen is pro-russian people intentionally saying "on (the) Ukraine" (as if "on the edge") instead of "in Ukraine" to piss people off.

As any eastern european would say:

I don't speak woman, purple is purple

And how do I explain my income to federal agencies?

None. It is no longer "cool" to post your entire life onto the internet. Source: I am a kid.

Nobody does personal blogging. Well, except a few specific primates doing so on Xitter. And I've also seen some people with at least half a brain getting a domain and writing blogs there in hopes someone clicks on their link.

Maybe the Arch Linux "ports" RFC will finally be of use...

Also, box64 works better in my experience when all of the depending libraries are installed properly, and they are guaranteed to be there in this scenario given that there's the Steam runtime.