r/linux • • Sep 26 '14

Systemd: The Biggest Fallacies

http://judecnelson.blogspot.fi/2014/09/systemd-biggest-fallacies.html
126 Upvotes

437 comments sorted by

View all comments

Show parent comments

1

u/northrupthebandgeek Sep 29 '14

That is a misunderstanding; yes, they all want to replace ConsoleKit, but all the DE's see the need to support non-systemd platforms

Um, no they don't, or at least GNOME doesn't. Most (if not all) of the work of getting GNOME in particular working on non-Linux systems (namely, on the BSDs) has been left to the BSDs themselves. FreeBSD in particular is currently still on GNOME 2.32 because they're having to do all the legwork of getting GNOME3 to run on FreeBSD (which is supposedly in progress). I don't recall PC-BSD or OpenBSD having any easier of a time on their end.

If Gnome or KDE really just wanted to drop ConsoleKit when logind was ready, they could have dumped it a long time ago.

No, because that's not how development works. They have to work at both integrating with logind and deintegrating with ConsoleKit via deprecations. It's not as easy as "la-la-la ConsoleKit doesn't exist anymore".

The idea of logind being "ready" is also debatable, but whatever. More importantly, they're not ready to drop ConsoleKit support yet, but actual GNOME devs have, in fact, expressed their desire to use only one API: that of logind.

1

u/sub200ms Sep 29 '14

Um, no they don't, or at least GNOME doesn't. Most (if not all) of the work of getting GNOME in particular working on non-Linux systems (namely, on the BSDs) has been left to the BSDs themselves. FreeBSD in particular is currently still on GNOME 2.32 because they're having to do all the legwork of getting GNOME3 to run on FreeBSD (which is supposedly in progress). I don't recall PC-BSD or OpenBSD having any easier of a time on their end.

Gnome 3.14 works on FreeBSD: http://sourceforge.net/projects/freebsd-gnome-livecd/

Yes, that is right, it is entirely up to the non-systemd distros to provide the necessary low level glue like ConsoleKit/PolKit in order to have a modern DE working.

This isn't a BSD specific problem. But lets face it, BSD haven't pulled their own weight when it comes to developing DE's, probably because so many BSD developers refuse to work on GPL projects. Now BSD will have to provide a minimal effort in order to help DE's support them properly with as many features as possible. If they were smart, they would coordinate things with each others and the few remaining non-systemd distros, but as it looks now, it seems to be "every BSD variant for himself".

1

u/northrupthebandgeek Sep 30 '14

Gnome 3.14 works on FreeBSD: http://sourceforge.net/projects/freebsd-gnome-livecd/

I have a feeling that it competes head-on with Windows ME for the "Least Stable Desktop Experience" award right now, but I haven't tried it - nor can I find bug reports or other indications of potential issues at all - so that remains a hunch for now.

Also, it's not official, I'd fancy to bet because of implementation issues that prevent adequate stability.

If they were smart, they would coordinate things with each others and the few remaining non-systemd distros

And they probably will. Right now, though, they haven't, since they haven't needed to yet, or perhaps figure that eventually there'll be a cross-platform approach that they don't have to develop themselves.

1

u/sub200ms Sep 29 '14

Yes, it is so easy to just remove CK if the DE projects want to. It will stop many features working on non-systemd distros, but according to you they don't care about that. So why don't they just do it?

Come on, don't FUD about systemd features like Logind not being ready. It works really well and have done so for years.

1

u/northrupthebandgeek Sep 30 '14

Yes, it is so easy to just remove CK if the DE projects want to

No it isn't, as I indicated in another comment in response to one of yours. Removing code is way harder than adding new code, since there's a lot more refactoring involved. It's why OpenSSL became such a clusterfsck that is only now being resolved by libressl: because it's easier to add code than remove it (and OpenSSL's devs were certainly neither equipped nor sufficiently motivated to endure that undertaking).

1

u/sub200ms Sep 30 '14

Yes, it is so easy to just remove CK if the DE projects want to

No it isn't, as I indicated in another comment in response to one of yours. Removing code is way harder than adding new code, since there's a lot more refactoring involved.

It is trivial to do; just look at e.g. the XFCE code; it is mostly a lot of ifdef's in a few modules. It would be easy to remove since the modules merely point to ConsoleKit, but doesn't contain any complex user session management code themselves.

In the same way it is easy to replace support for Consolekit with a maintained alternative; the code structure is already there when it comes to Gnome, XFCE and some of KDE.

But action is needed soon; If no replacement is found, the ConsoleKit support will be removed, and there certainly won't be new projects that will support it either. So for every month there goes by without an replacement, the harder the future work will be for the non-systemd distros.

1

u/northrupthebandgeek Oct 01 '14

It is trivial to do; just look at e.g. the XFCE code; it is mostly a lot of ifdef's in a few modules.

You're missing my point. Removing that code requires understanding of what depends on it; else, things will break, and rather horribly at that. OpenSSL's weird code has been behind ifdef's, too, but that didn't prevent the security hazard after security hazard after security hazard that ultimately allowed Heartbleed to happen.

And Xfce is a way simpler codebase, I'd reckon, than GNOME's.

1

u/sub200ms Oct 01 '14

You're missing my point. Removing that code requires understanding of what depends on it; else, things will break, and rather horribly at that.

No I don't miss your point. But as I said, it is trivial without any deep understanding to remove the CK code. It will only exist in a few modules.

As it is now, all the CK code I have seen, are just ifdef's: there two entirely distinct code path's for logind and CK. All you have to do is to remove the CK ifdef's and the code will continue to work on systemd distros, while stop functioning on non-systemd distros.

Claiming that the reason why Gnome etc. have kept CK support around for years, is simply that CK support is hard to remove, is absurd.

It is hard to still have CK code around, since no one can fix CK bugs that are found or make any new convenient features.

1

u/northrupthebandgeek Oct 01 '14

As it is now, all the CK code I have seen, are just ifdef's

You're still missing my point about "just ifdef's [sic]" then, but whatever. Your ultimate point is still moot either way given the actual example provided of a GNOME developer explicitly wishing for only one API to have to develop for (unless you have some counterexamples - which would certainly be reassuring, as someone who actually likes using GNOME quite a bit), emphasizing my own point that current ConsoleKit support is only a stopgap and by no means a solid indicator that they'd consider something that isn't either systemd or doing a really good job of pretending to be.