With my face pasted against the window. After a while, all those tiny clouds look like a field of sheep 💤

A towel

I know what I said. Linux upholds the “don’t break userspace” contract pretty well: most kernels, particularly those from generalistic distros built with modules, are compatible with whatever userspace binaries you throw at them. Major version changes in glibc (or equivalent) is where incompatibilities start, but those happen quite rarely, and you can often still force multiple glibc versions to run side by side.

What @exi@feddit.de said. Switching .deb based distros is little more than changing sources, maybe some pinning, doing an upgrade, and optionally a cleanup pass to remove any stranglers.

My main Linux box is a Debian-Ubuntu-Debian upgrade, that hasn’t seen a proper reinstall for like 15 years (switched all the hardware several times, still no clean reinstall).

Switching between non-deb distros is also possible, with a chroot. Like, Gentoo to Fedora. As long as the kernel is compatible with the glibc, it’s basically like running containers, just on slightly hard mode.

Not really, I’m not new to containers.

This might blow yours though: I once booted up from a Tomsrtbt disk, installed Debian, added some RedHat packages, and topped it up with some pinned downgrades from Ubuntu.

On bare metal, no containers, no rebooting.

I want GDPR export.

Next, GDPR import of the same data (aka, account migration)

Debian would not create and maintain a “core debian” variant just to be installed then receive the extra packages

Debian server minimal, is kind of a “core Debian”. There are netinst versions that can be even smaller. The Debian base image for Docker is even smaller than all that.

There is also an Ubuntu minimal install that you could call “core Ubuntu”.

But more importantly, and I can’t stress this enough: YOU CAN SWITCH DISTROS WITHOUT REINSTALLING. Might need to do some cleanup afterwards, but it’s perfectly doable, more so between Debian based ones.

Could you link some examples?

Also keep in mind that people can release their work under multiple licenses, so they may upload the same work with a different license (like a privative one) to other markets.

Probably can’t be libel if they don’t make it public, just stuff that happens behind closed doors and they can say “no comment”. Would be different if Reddit had a public modlog like Lemmy.

My guess is, after 10 years without a problem, someone around 2 years ago might have marked me for takedown for whatever reason. I always tried to be respectful, but didn’t start self-censoring until they suspended me for “violent content” without even referencing what was the supposed content. I kind of hoped that using Power Delete Suite to blank the account history, and avoiding most polemic topics from then onwards, would keep it safe, but apparently not.

Ironically, an alt account I created to participate in more polemic topics, got zero problems… but they now banned it along the main one, so bye Reddit, so long and thanks for all the fish.

I got suspended for “sexualization of minors”. Appealed that I did no such thing, and in response got permanently suspended for “repeated violations”.

So when “they” say you did it, you better believe it, because claiming otherwise is an additional violation 🤦

the karma accumulated could be used to improve the rate of exchange for Reddit gold into real-world money (possibly USD)

Oh, so all those people with 10+ year accounts, with tons of karma accumulated over the years, and who deleted their accounts in protest for the API changes… are actually a “good thing” so Reddit doesn’t have to pay top rates for their comments?

Nice move, very nice… /s

My main account got permabanned for “sexualization of minors” after I made a comment criticizing a guy talking about what he’d do to 4th graders. Sent an appeal… and got permabanned on ALL of my accounts for “recurring offense”.

Maybe spez wants to turn all of Reddit into jailbait again.

[pi@raspberry]# sudo su

Just saying, not everyone needs session management…

Xorg, or X11, “used to” do the “minimum necessary” for a remote display system… in the 80s. Graphics tech has changed A LOT in the last 40 years, with most of the stuff getting offloaded to GPUs, so the whole X11 protocol became more and more bloated as it kept getting new and optional features without dropping backwards compatibility.

The point against Wayland, was dropping support for remote displays, while kind of having an existential crysis for several years during which it didn’t know what it wanted to become. Hopefully that’s clear now.

OpenRC and runit are indeed working alternatives, but OpenRC is kind of a hack over init.rd, while runit relies a bit too much on storing all its status in the filesystem. Systemd has a cleaner approach and a more flexible service configuration.

“do one thing well”

Arguably, Systemd does exactly that: orchestrate the parallel starting of services, and do it well.

The problem with init.d and sys.v is they were not designed for multi-core systems where multiple services can start at once, and had no concept of which service depended on which, other than a lineal “this before that”. Over the years, they got extended with very dirty hacks and tons of support functions that were not consistent between distributions, and still barely functional.

Systemd cleaned all of that up, added parallel starting taking into account service dependencies, which meant adding an enhanced journaling system to pull status responses from multiple services at once, same for pulling device updates, and security and isolation configs.

It’s really the minimum that can be done (well) for a parallel start system.