KDE's 'Plasma Login Manager' Stops Supporting FreeBSD - Because Systemd (itsfoss.com)
- Reference: 0180656182
- News link: https://bsd.slashdot.org/story/26/01/26/0135254/kdes-plasma-login-manager-stops-supporting-freebsd---because-systemd
- Source link: https://itsfoss.com/news/plasma-login-manager-drops-freebsd/
> systemd and logind look like hard dependencies of the login manager, which means the software is built to work exclusively with these components and cannot function without them... [3]logind is a component of systemd that is responsible for user session management...
>
> This doesn't mean that KDE has abandoned the operating system altogether. FreeBSD users can [4]still run the KDE Plasma desktop environment and continue using [5]SDDM , the current login manager that works just fine on such systems.
The article argues FreeBSD users "won't really care much for missing out on this as they have plenty of login manager options available."
[1] https://itsfoss.com/news/plasma-login-manager-drops-freebsd/
[2] https://invent.kde.org/plasma/plasma-login-manager/-/merge_requests/42
[3] https://www.freedesktop.org/software/systemd/man/latest/systemd-logind.service.html
[4] https://community.kde.org/FreeBSD/Setup
[5] https://github.com/sddm/sddm
KDE is dead (Score:2)
They stopped supporting BSD and any linux that doesn't support Systemd, Microsoft's infiltration of the Linux ecosystem.
Re: (Score:1)
Stop hyperventilating. KDE still works fine on FreeBSD. Just use one of the many login managers that work on FreeBSD (SDDM, LightDM, etc.)
Re: (Score:2)
It's also likely not a priority. People forget that login managers exist, and they work independently of the desktop environment. I mean, you log into any non-Linux machine graphically and it asks you for a username, password, and what environment you want to boot into - you can often have basic ones like twm or fvwm, full fat KDE and GNOME, even ones like CDE and Java (on Solaris).
You picked when you logged into your machine, not when you installed the OS (e.g., Ubuntu, Kubuntu, etc). Generally speaking t
And where did he go after red hat? (Score:2)
And why did he go there?
This Is How It Starts (Score:5, Insightful)
First it's KDE's login manager. Next, it will be some other portion of KDE due to another dependency, maybe systemd-homed. And other projects are almost certain to follow. This is Red Hat's version of embrace, extend, extinguish (which is likely a big reason why IBM bought Red Hat). They keep making additional modules that are exclusive to SystemD with enticing functionality, they lure downstream projects to integrate those modules, and before you know it the dependencies are so intertwined with this exclusive functionality that the downstream project can no longer support any other init system. Say what you want about all of the other init systems available, but I can't think of another init system that pulled shit like this. They didn't have to implement SystemD like this, but they chose to because it allowed them to exert undue influence on many other downstream projects (and when you're an init system, almost every component is a downstream project). If you like SystemD, fine, but let's not pretend this outcome is incidental, let alone healthy for alternative init systems.
Re: (Score:2)
KDE is under the GPL/LGPL, which is a license expressly designed to stop corporate takeovers. Anyone is free to fork. They can always pivot to a non-systemd DE if Plasma goes all in on systemd - no big deal. But it also begs the question - why don't the BSD folk just create their own DE? Perhaps one under the same permissive BSD license that the OS uses?
Modern desktops have so many inter-dependencies that it makes total sense to develop for a single init system, and have tight integration with it. Otherw
Re: (Score:2)
Out of curiosity I looked up what desktops are on BSD.
Even without Plasma there are several to choose from. I'm not seeing a problem here if you are simply trying to get work done.
[1]https://docs.freebsd.org/en/bo... [freebsd.org]
[1] https://docs.freebsd.org/en/books/handbook/desktop/
Re: (Score:2, Funny)
Oh hell no don't even utter the words of porting systemd to freebsd. KDE can go and fuck off if they want to suck systemd's dick. Mark my words in a decade it won't be the linux kernel anymore. It will be the systemd kernel. Probably all written in python so it takes an I9 with 128GB of ram just to open a txt file in a notepad app.
Re: (Score:2)
No way man.
2036 is the year of the GNU/HURD desktop!
Re: (Score:2, Interesting)
before you know it the dependencies are so intertwined with this exclusive functionality that the downstream project can no longer support any other init system.
This is precisely what has happened with pulse audio. Sure ALSA is still around but good luck finding any project that will support it. I tried to hold out on apluse but it it just isn't feasible anymore. I suspect I will be forced into systemd at some point, but for now, openrc and friends are holding strong.
Re: (Score:2)
perhaps you can write a Boot Script that also is a login manager, and also a UI.
Re: (Score:2)
Starts? This has been ongoing for a long time.
KDE? Who cares? (Score:2, Insightful)
There are tons of desktop environments and a lot of them are better than KDE (or Gnome).
BSD is dead! (Score:3)
KDE confirms it!!! /jk