Responses to Coming changes in impending MX 25 release.

[rambo919]

Two years is a long time in the software world and there are a bunch of updates that people have either waited patiently up until now to get pushed upstream or have had to contort their machines to run, through Flatpaks and AppImages and Nix, oh my.

Arch users don't have to develop this kind of patience. Debian users appreciate that brief two- or three-month window of time when they can apt-get something they want and the version installed isn't ancient. For one sweet moment, Debian is both relatively stable and relatively up-to-date. It's nice. It's understandable that folks are eager to have that experience again, however brief it may be.

I am actually oddly comfy by now.... my major curiosity is about how KDE6 is and what fabulous new bugs it will have to annoy me with.... have gotten used to the old ones hahaha.

[AK-47]

It's just funny to me how eager everyone is to finally escape DB12.

Coming from older versions of Windows I can appreciate software that doesn't radically change for a few years. However I moved my main laptop away because I found the KDE wayland session (back then) to be severely lacking and full of bugs, despite it performing substantially and noticeably better than the X11 session.
I have become quite used to new software on my machine that I run Fedora on it. I still run MX but on VMs and build machines, and a Debian base is perfect in applications that require some degree of API/ABI stability and support.

I am actually oddly comfy by now.... my major curiosity is about how KDE6 is and what fabulous new bugs it will have to annoy me with.... have gotten used to the old ones hahaha.

Upgrading from 5.27 (the last of the 5.x releases) to 6.0 there wasn't much of a difference in the UI other than the floating panel by default (which I'm not keen on, I turned it off). It was much more stable with the Wayland session and smoother and felt more refined. The KDE Wayland code split didn't occur until 6.4 so Debian's version will miss out on that change for the time being. There are some big internal changes expected soon (for instance, replacing SDDM with their own login manager) but won't make it into Debian 13 or MX Linux until at least 2027.

tl;dr don't expect any wow-factor features with v6.3.4, but I expect it will be much more stable.

[LU344928]

Thanks anyway.

I wonder how Slackware users will cope. KDE's been default for some time and Slackware's been opposed to systemd from the very start of the affair. Then again, Patrick is quite a wizard so he may find a work around.

@LU344928 I booted up AlienBob's latest Slackware15 -current live ISO (Aug 5th 2025) but they are still on KDE 5.27

Apparently Eric is still working on getting his tooling up to date for KDE 6. Someone else has already gotten a repo ready in the meantime though.

[LU344928]

Sure there are better alternatives out there, but at this stage, practically anything seems better than sysvinit.

The year is 2095. You show up at the annual Devuan developers' conference with a burning question: is SysVinit finally obsolete?

The small group of programmers, most of whom are sporting long white beards, seem taken aback by the question and give confused glances at each other. Finally one of them speaks:

"At the beginning of this century Debian abandoned its roots to switch to systemd. We, the steadfast, the true, decided to stick to what was elegant and simple and right and Unix, even though this decision often came at high personal and professional cost. Although Debian describes itself as the 'universal operating system', even today there are several models of vintage toasters that are not compatible with systemd. Our tradition has paid off in many respects, but none greater than this: we can now hold claim to being a more universal operating system than the 'universal operating system' while offering the world init freedom, and our source code is much simpler to boot. (And need I even mention the ThornWorm debacle of 2074, from which SysVinit users were completely immune?) While other legends like Gentoo and the BSDs died out decades ago, we persist and continue the tradition. So no, SysVinit is NOT obsolete; in fact, it is more important than ever!"

The programmers burst into applause and start patting each other on the back as they head off to lunch. You are left alone in the room with the unshakable feeling that perhaps these odd wizard-like people are right...


https://www.reddit.com/r/linux/comments ... _favor_of/

[asqwerth]

@BitterTruth Point of clarification - antiX is completely systemd-free unlike MX which seeks to have both inits co-exist (until MX25). Your earlier post made it look like MX and antiX were the same in having both systemd and sysV.

But antiX is different from Devuan in that antiX is actually still directly using Debian's repos, but with a separate nosystemd repo of their own.

[AK-47]

The year is 2095. You show up at the annual Devuan developers' conference

when you suddenly sober up and discover you are actually in the middle of a cemetery?

(And need I even mention the ThornWorm debacle of 2074, from which SysVinit users were completely immune?)

Or the ShellShockSuppository trojan of 2079, which only affected SysVinit users but not systemd users?

On a more realistic note, who is to say Linux will even survive that long? There could be a better OS out there by then altogether which is better adapted to that technological climate.

[AVLinux]

Not to mention pretty much everyone participating in this thread will quite likely be dead.. Makes the init system issue seem kinda ephemeral.

[rambo919]

On a more realistic note, who is to say Linux will even survive that long? There could be a better OS out there by then altogether which is better adapted to that technological climate.

The year is 2030, Debian is completely woke and non-conformists are being purged.

The year is 2035, after a brief war Devuan has been purged of the Debian 5th column seeking to subvert it's pure dedication to code over ideology and the great Linux cold war is undeniable. The brothers continue to diverge in code parity as the conflict intensifies and Devuan is forced to ideologically develop to more effectively defend itself.

The year is 2050, Linux is dead. The cold war had turned hot as activists of both sides increasingly turned to physical means of persuasion. The corporations had briefly held a position of dominance and had almost consolidated their once unspoken of power, then disaster struck as worldwide mass eruptions of discontent led to corporate disinvestment, due to the sudden lack of funding only national Distributions were left standing and authorities had heavily cracked down on all non-Government groups as a public order measure. A international body aiming to govern the code is formed in the new United Empires Board which had replaced the defunct United Nations after WW3 (which could be called the AI wars but this is still debated) led to the Imperial Renaissance that had gradually rendered the idea of Nationhood obsolete as the new empires absorbed most of the surviving countries.

[Adrian]

People who use the word "woke" in a non self-referential way usually don't know what it means (or they think it means whatever they imagine it means)
Also, in my experience the Venn diagram of people who are upset they can no longer use the n-word and the people who use "woke" in this manner is almost a circle.

I would stay away from that word...

[rambo919]

People who use the word "woke" in a non self-referential way usually don't know what it means (or they think it means whatever they imagine it means)
Also, in my experience the Venn diagram of people who are upset they can no longer use the n-word and the people who use "woke" in this manner is almost a circle.

I would stay away from that word...

Any response to that would get someone banned.....