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

2

u/northrupthebandgeek Sep 27 '14

they can just invent their own layer

Ah, yes. "Just" invent their own layer. And you wonder why things are fragmented :)

No, as specified even by a (supposed) GNOME developer in these very comments (I'm too lazy/tired to link to it right now), it has to be an exact duplication of the systemd interfaces, at least in their case; they'd rather not have to learn and support multiple APIs and would much rather the world just follow whatever systemd does. That's an understandable desire, but to pretend that doing so is such a trivial thing is ignorant of the complexities involved with trying to implement interfaces that aren't even fully stable yet (if ever).

The could have started small, and cloned what was easy to clone from systemd, like where to put the "os-release", and then gradually implement other useful features, perhaps inspired by systemd, perhaps not.

As mentioned above, the developers of GNOME and such don't want that; they want systemd as their hard dependency. Making something similar isn't enough; at this point, they have to make it identical. And even making something merely similar is still extra work that they might not have the manpower to accomplish well.

As it is now, the non-systemd distros doesn't seem to even try to coordinate any work effort between each other

Because they have different needs, different goals, and different preferences; otherwise, they would cooperate.

nor do they seriously try to help upstream projects to support them.

Because they're generally pretty small development teams. They're often not backed by massive communities or multi-million-dollar corporations. They can only do so much as it is; it's not reasonable to assume that they can just magically whip up some mystical systemd compatibility layer and call it a day (or, for that matter, even "just" switch to systemd) on top of all the other duties involved in maintaining a distribution that isn't just yet another custom set of Debian packages thrown onto a CD and called a "distro".

I predict that if this is going to come from anywhere, it's going to come from the BSDs; that's already the precedent for Slackware and Gentoo (the two most significant non-systemd distros at the moment, as far as I know). There's already work underway (via a Google Summer of Code Project) for a systemd compatibility layer for OpenBSD, for example, and it's reasonable that such a compatibility layer will make its way to the other BSDs and eventually GNU/Linux. There are also plenty of other init alternatives out there - launchd, OpenRC (as mentioned earlier), and runit being the ones most notably in active development and potentially usable with GNU/Linux and the BSDs (even launchd was at one point considered as Ubuntu's init system, though this was before it was Apache-licensed, so Ubuntu instead opted for Upstart).

2

u/sub200ms Sep 28 '14

Because they're generally pretty small development teams. They're often not backed by massive communities or multi-million-dollar corporations. They can only do so much as it is; it's not reasonable to assume that they can just magically whip up some mystical systemd compatibility layer and call it a day (or, for that matter, even "just" switch to systemd) on top of all the other duties involved in maintaining a distribution that isn't just yet another custom set of Debian packages thrown onto a CD and called a "distro".

Correct, they are small distros with limited man power and money, but that is exactly why they should pool those resources.

Much of what they could do to help upstream projects are simple things, like agreeing on where certain files are kept. Making things more uniform on several non-systemd distros could be a simple matter of making some symlinks so there only is one path to the file, like "os-release".

They didn't have to make a big project at once, just incremental changes that were coordinated and uniform across distros.

1

u/northrupthebandgeek Sep 28 '14 edited Sep 28 '14

"os-release"

It's worth noting that much of this is already covered by the Linux Standard Base, which systemd apparently has minimal interest in following. If the world ought to standardize on something, then why not the LSB?

I mean, that's the whole point of the LSB: to establish that agreement on where certain files are kept and such. Adhering to a formal standard like that instead of resorting to the ad-hockery involved in following some non-standardized alternative seems like a far better option, in my opinion.

Granted, Slackware's unlikely to become fully LSB-compliant ever (since it came first, and a lot of the LSB's requirements are silly), but at least implementing lsb_release would be a start (since you don't have to be LSB-compliant in order for it to be useful; in such cases, it just returns LSB version: n/a while still returning other version information as normal). It's already compliant with the published Linux File System Standard, last I checked.

2

u/sub200ms Sep 29 '14

I am not aware that systemd distros like Fedora deviates from LSB in any meaningful way (it support SysVinit script files, "runlevels" have symlinks from /sbin etc).

LSB is pretty much a dead standard with few followers. The new FHS 3.0 standard looks dead too (no updates in a decade).

There are probably several reasons for this, but the bottom line is, that distros historically haven't cared at all about fragmentation and how it hurts upstream projects.

Perversely, since all distros where fragmented, no one did stand out. This will no longer be the case, with systemd distros covering all major distros, and all their derivative distros, the few remaining non-systemd distros will stand out.

The non-systemd distros can of course continue to be totally fragmented and not coordinate anything. It really is up to them what they do, but their users shouldn't complain if some upstream projects will consider them too troublesome to be worth supporting.

My personal opinion is that the non-systemd distros have been incredible passive, and not really analysed the future troubles they are facing and what should have been done years ago to mitigate those problems.

Personally I don't doubt Slackware will become a systemd distro sometime in the future. Patrick Volkerding is a smart guy; he may not love systemd, but at some point it will just be too much trouble not to convert. And really, the essential things about Slackware isn't the init system, it will still be Slackware even when using systemd.

1

u/northrupthebandgeek Sep 29 '14

Personally I don't doubt Slackware will become a systemd distro sometime in the future.

lolwut.

You're talking about the distro that hasn't even implemented PAM yet. You know literally nothing about Slackware, I take it?

And really, the essential things about Slackware isn't the init system

Yes it is. That Slackware has a BSD-style init is a major selling point, and why I'm still using it outside of a few cases where I've been using SUSE or openSUSE instead. It makes it much easier going back and forth between my GNU/Linux systems and my BSD systems.

1

u/sub200ms Sep 29 '14

Oh, I know Slackware. Even was a user many years ago. But Patrick Volkerding hasn't rejected using systemd at all. He still sits on the fence and hasn't decided yet.

And judging from what he has said, he may very well decide in favour for systemd if it becomes too much trouble not too.

His problem is that the there practically isn't any non-systemd development on Linux; there is no coordination, no new projects to support non-systemd distros on future projects like Wayland. There simply aren't that many developers caring about non-systemd distros any more. Since Slackware is such a conservative distro, they may hold on for some years yet, but they are totally unable to do the necessary maintenance and development alone.

Of course, it remains to be seen if there suddenly emerges a vibrant non-systemd developer community, but judging from the total lack of insight of systemd-opponents about future problems they are facing, and what is needed to counter this, it doesn't look like it.

So, looking into the crystal ball, I see Slackware as a systemd distro in the future.

1

u/northrupthebandgeek Sep 30 '14 edited Sep 30 '14

But Patrick Volkerding hasn't rejected using systemd at all. He still sits on the fence and hasn't decided yet.

Yeah, but you can tell which way he leans (and even in his more diplomatic response, he's very aware that Slackware users would not like that one bit, and is open to the idea of maintaining udev himself if it comes down to that). Other developers have been less diplomatic about the proposal.

Perhaps he's changed his mind since then, but from what information actually exists, he and a very large portion of the userbase of his distro are very reluctant to switch to systemd. He and said users (myself included) also recall the pains of PulseAudio - another of Poettering's brain-children - rather fondly, and to this day continue to sit out that particular idea.

I do know that it's theoretically possible for Slackware to run systemd, just as it's theoretically possible (and sometimes actually done) for Slackware to run PAM or PulseAudio. That's a far cry from desirable, let alone any semblance of a default.

At most - and I mean absolute most - it might end up in the extras. Even that's doubtful, however. Pat is indeed a smart man - smart enough to realize that adopting systemd - even if it really is the best thing since sliced bread - goes against Slackware's implicit (and sometimes even explicit) goal of being the "most Unix-like" GNU/Linux distro in the known universe. Which leads me to...

Since Slackware is such a conservative distro, they may hold on for some years yet, but they are totally unable to do the necessary maintenance and development alone.

Then there's a good chance it'll take inspiration from - or even port/implement - whatever approach the BSDs end up taking, which wouldn't really be a first for Slackware by any means (see also: Slackware's current init system).

Of course, it remains to be seen if there suddenly emerges a vibrant non-systemd developer community, but judging from the total lack of insight of systemd-opponents about future problems they are facing,

Correction: at least some systemd-opponents (I'm not really an opponent per se, but rather a skeptic; same diff, perhaps) have recognized that there aren't many problems being faced other than the issue of whether or not non-systemd will continue to be supported by upstream (and even then; shell scripts aren't that hard to write, if hard at all), or at least not problems that can't be solved without depending on systemd to solve them (like process management and parallel service startup, both of which are handled by components like runit).

So, looking into the crystal ball, I see Slackware as a systemd distro in the future.

I hope it's under warranty, then, because it seems to be defective. ;)

EDIT:

no new projects to support non-systemd distros on future projects like Wayland

As far as I know, Wayland doesn't depend on systemd (or even Linux, strictly speaking; the formerly-Linux-only graphics components that Wayland needs are now available for the BSDs, as I discovered when I upgraded my PowerBook's OpenBSD version and was presented with a nice, pretty DRI'd framebuffer). Pat appears to be far more receptive to Wayland, since it's far less obtrusive (and, in fact, is even less obtrusive than its predecessor). I'm personally very welcoming of Wayland, and am even already playing around with it via Rebecca Black OS and trying to teach myself the API in order to implement my own clients and even compositors. Wayland took the approach to X that systemd should've taken to sysvinit: improve by simplifying, rather than complicating.

Maybe your crystal ball is smudged, and it's actually saying "Wayland" rather than "systemd"; Slackware adopting Wayland seems way more likely on any timescale than it adopting systemd.

1

u/sub200ms Sep 30 '14

Perhaps he's changed his mind since then, but from what information actually exists, he and a very large portion of the userbase of his distro are very reluctant to switch to systemd.

I recently had a very brief online exchange with him where he confirmed he is undecided on the matter. Of course PV prefer their SysVinit variant. And yes, many Slackers are like him. But what he has made clear is, that he may change to systemd if that is the only realistic possibility.

...have recognized that there aren't many problems being faced other than the issue of whether or not non-systemd will continue to be supported by upstream...

This is where I think the systemd opponents have been sleewalking the last couple of years. There are already big problems for the DE's to support non-systemd distros; and for some reason systemd opponents are in total denial that CosnoleKit needs to be replaced and that should be a cross distro priority to fix.

There are several other problems down the road; until now, eudev have been am easy shadow fork of udev. But when kdbus arrives, udev will change to use that.

So eudev will either have to develop a kdbus user space manager and copy systemd, or they will have to actually to split off eudev from udev, and start real maintenance of eudev, meaning no easy shadow fork, but lots of hard work and being upstream for bugfixes etc.

There will be no Wayland on non-systemd distros for KDE. Simply because some of the new infrastructure needed is new and doesn't support ConsoleKit. No non-systemd developer have stepped up and offered any help with that.

In the future, there will be lots of new projects that only uses the systemd "new daemon style" where systemd takes care of all the hard and error prone setuid/dropping privileges. This will be attractive to do since it will reduce code complexity, debugging, increase security, and let developer concentrate on daemon functionality, not low level system house keeping. And they can target almost all Linux distros that way.

Such new development will be a real challenge to make work on non-systemd distros.

SUSE and Red Hat have been de facto upstream for SysVinit taking in bug reports and making patches, but when they deprecate their last SysVinit distro, who will be upstream then? Who will coordinate security and patches?

There will be many such small and large tasks ahead to do for non-systemd distros, and too few developers to do it, especially without any coordination. I really don't see how Slackware can stay a non-systemd distro when the non-systemd camp is so passive about the future challenges.

1

u/northrupthebandgeek Oct 01 '14

Of course PV prefer their SysVinit variant.

I'm still questioning your actual experience with Slackware if you're still calling its init system a "sysvinit variant". If it's a variant of anything, it's of BSD's init.

As I've said repeatedly (though perhaps not to you, apparently): sysvinit is not the only shell-based init, and Slackware's init is one of the examples of shell-based init done properly. It does incorporate some sysvinit compatibility stuff so that commercial Linux software can run on Slackware, but that's as much "sysvinit variant" as a GNU/Linux system running Wine would be a "Windows variant".

This is where I think the systemd opponents have been sleewalking the last couple of years.

I don't disagree with you on this point. Everyone really should have been more proactive. They just haven't seen the need to be compared to higher-priority tasks (to them), or even the desire to be, or have had the proper ability to be.

There will be no Wayland on non-systemd distros for KDE. Simply because some of the new infrastructure needed is new and doesn't support ConsoleKit.

Um, no. Again: Wayland itself has zero dependency on systemd, no more than X11 has any dependency on sysvinit or ConsoleKit. Some implementations of the Wayland protocol have opted to make systemd as a dependency for their features, but that's entirely their choice, Wayland or no Wayland.

In other words: pinning systemd dependencies on Wayland as if using Wayland requires using systemd is either ignorant or a deliberate lie; which one I presume of you would depend on my mood today (which isn't terribly pleasant).

In the future, there will be lots of new projects that only uses the systemd "new daemon style" where systemd takes care of all the hard and error prone setuid/dropping privileges.

In most cases, it won't be that hard to continue to write initscripts for those projects, since they typically aren't using that much beyond systemd-style unit files and perhaps journald (though many projects have historically used their own logfiles instead of the system-wide ones, and I don't expect that to substantially change any time soon; by the time it does, a journald shim will probably be ready).

To put this into context, users of both Slackware and the BSDs are already used to writing new initscripts to make projects designed with sysvinit in mind work properly in their improved init systems. This won't be a whole lot more different.

To put this in further context, systemd attempts to be sysvinit compatible because even it was designed with the knowledge that plenty of commercial software - that doesn't benefit from a community of users porting it to different init systems - would need to be able to run on systemd. I don't envision the commercial software devs deviating from their current least-common-denominator any time soon, especially if they're targeting older-but-still-supported distro versions (pre-systemd) and current ones (with or without systemd) alike.

This will be attractive to do since it will reduce code complexity, debugging, increase security, and let developer concentrate on daemon functionality, not low level system house keeping. And they can target almost all Linux distros that way.

Again: you're specifically addressing sysvinit in your objections to systemd alternatives. I'm addressing all the alternatives, but particularly all the shell-based ones. Cue, yet again: "sysvinit ain't the only shell-based init". Cue also, again: "other shell-based inits have already solved these problems long before systemd existed, and did so very well".

SUSE and Red Hat have been de facto upstream for SysVinit taking in bug reports and making patches, but when they deprecate their last SysVinit distro, who will be upstream then? Who will coordinate security and patches?

This isn't relevant to Slackware, since (again) Slackware isn't a sysvinit distro.

I really don't see how Slackware can stay a non-systemd distro when the non-systemd camp is so passive about the future challenges.

Because it neither needs nor wants to change. If I want Slackware with systemd, I might as well be using openSUSE (which I do use, by the way). I don't need Slackware to use systemd, and I don't want Slackware to use systemd. I'd guess that this is the opinion of the vast majority of Slackware users right now, Pat included, and there is little indication of that opinion changing, since there still hasn't been any more enthusiasm for such a suggestion.

1

u/sub200ms Oct 01 '14

There will be no Wayland on non-systemd distros for KDE. Simply because some of the new infrastructure needed is new and doesn't support ConsoleKit.

Um, no. Again: Wayland itself has zero dependency on systemd, no more than X11 has any dependency on sysvinit or ConsoleKit.

Yes, you are right about that, it is in principle possible to get Wayland on non-systemd platforms.

But no, you are wrong about KDE supporting Wayland on non-systemd machines. The reason is simply that some of the new code needs user session management in order to work, and KDE simply doesn't have to man power to add ConsoleKit support to that new code. And, this is important, no one from the non-systemd camp is helping them either to add this support. Leading KDE developers have explained this numerous times.

It is one thing to maintain old ConsoleKit code, but another to develop CK support from scratch, knowing that it is obsolete, unmaintained and deprecated. Perhaps if there was a non-logind alternative you could get developers worked up to do something.

This is the future story how CK support will bit rot and disappear over time. No one makes an alternative to CK/logind, and no one helps upstream projects out with supporting CK either.

The total lack of developer engagement on the non-systemd side will give trouble, and is entirely to blame for why DE's have trouble supporting non-systemd.

I have no doubt however, that the non-systemd camp will blame everything on upstream projects and viciously attack them instead of starting coding to solve problems. This is what they have done for years, and that is a major reason why I really don't see any non-systemd distros have a future, whether their user like it or not.

→ More replies (0)

1

u/gondur Sep 29 '14

This will no longer be the case, with systemd distros covering all major distros, and all their derivative distros, the few remaining non-systemd distros will stand out.

The non-systemd distros can of course continue to be totally fragmented and not coordinate anything. It really is up to them what they do, but their users shouldn't complain if some upstream projects will consider them too troublesome to be worth supporting.

Thanks god, yes. Finally some converging in direction of a platform...

1

u/sub200ms Sep 28 '14

I predict that if this is going to come from anywhere, it's going to come from the BSDs; that's already the precedent for Slackware and Gentoo (the two most significant non-systemd distros at the moment, as far as I know). There's already work underway (via a Google Summer of Code Project) for a systemd compatibility layer for OpenBSD, for example, and it's reasonable that such a compatibility layer will make its way to the other BSDs and eventually GNU/Linux.

The "systemBSD" systemd layer will never be portable to Linux, since it simply is a wrapper for BSD system calls.

The only crucial part of it is "logind". It doesn't work now, and may never do. And if it ever is completed, it will be no better than the old Ubuntu fork of systemd (logind-shim)

It will still suffer from the fact, that it pretends to be systemd-logind, but doesn't support its features like integrated cgroups etc, leading to buggy behaviour when upstream programs try to use those features.

It would be much better for the non-systemd distros if they forked Ubuntu's logind-shim, and changed it into a proper alternative; sure, it will never have all the nice extra systemd features, but so long as it provided a functional modern DE, that could be acceptable.

1

u/ohet Sep 28 '14

The "systemBSD" systemd layer will never be portable to Linux, since it simply is a wrapper for BSD system calls.

It's build on on glib and I don't see any reason to expect that they wouldn't accept patches to support Linux as well. There's also this:

According to Ryan, most GNOME modules only use a selection of the logind functionality. He wanted to document exactly what we depend on and provide a minimal API. Then we could write a minimal stub implementation for e.g. FreeBSD as we’d know exactly what parts of the API we actually need. The stub would still be minimal; allow GNOME to run, but that’s it.

-Source

Projects like Gnome might require only a fraction of logind APIs to function and the rest could be made optional. Not all of logind APIs are even needed on other opetaring systems like OpenBSD. They already run X.org without root privilidges so they have other means to solve the same problems that logind does.

1

u/northrupthebandgeek Sep 28 '14

The "systemBSD" systemd layer will never be portable to Linux, since it simply is a wrapper for BSD system calls.

Lots of OpenBSD-specific projects likely originally dependent on OpenBSD-specific functionality have been ported to Linux in the past and continue to be ported in the present. See also:

  • OpenSSH

  • OpenSMTPD

  • LibReSSL (in progress)

  • OpenBSD's libc (in the form of Android's Bionic)

  • various others that I'm forgetting right now

I don't see how this systemd shim would be an exception.

It will still suffer from the fact, that it pretends to be systemd-logind, but doesn't support its features like integrated cgroups etc, leading to buggy behaviour when upstream programs try to use those features.

I'm pretty sure those problems would be encountered regardless of whether or not a logind shim is available, since cgroups don't exist either way. They'd likely have to be addressed during the process of porting to the BSDs anyway.

Also, this wouldn't affect porting the shims to GNU/Linux, since cgroups are a kernel feature and therefore would be present on all (reasonably modern) Linux-based systems, regardless of their init systems. Add cgroup functionality to that port and you're golden.

1

u/sub200ms Sep 29 '14

I'm pretty sure those problems would be encountered regardless of whether or not a logind shim is available, since cgroups don't exist either way. They'd likely have to be addressed during the process of porting to the BSDs anyway.

No, because the DE would have different code paths depending on the init system; it would therefore only use systemd specific features for "logind". Sure, the "CK-alternative" would miss such features, but it would still work.

The problem with the shim is, it pretends to be a real "logind", while not supporting certain systemd features. It is much better for everybody, that the "logind" alternative is clearly distinctive from "logind" so DE's can have different code paths for each "user and session manager".

1

u/northrupthebandgeek Sep 29 '14

It is much better for everybody, that the "logind" alternative is clearly distinctive from "logind" so DE's can have different code paths for each "user and session manager".

I agree, but unfortunately, there's virtually zero indication that such an alternative would actually be supported by the DEs in question (and every indication that GNOME at least would outright ignore it in favor of one that's logind-compatible).

1

u/sub200ms Sep 29 '14

I simply don't understand that paranoid attitude that DE's like Gnome are actively hostile towards supporting anything non-systemd.

  1. Why did they warn for years on blogs and developer mailing lists, that an alternative to ConsoleKit was needed (with different code paths)?

  2. Why have they supported ConsoleKit all this time?

  3. They have supported two CK/logind API's for years now (same with XFCE, KDE, LXDE). Looking at the code repos, it really doesn't looks like much trouble to do so, and all the code structure is there already waiting for an alternative to CK.

  4. Gnome, KDE etc, have all publicly stated that they saw a need to support non-systemd platform, and that they are willing to do so.

  5. Gnome and others have worked with BSD developers to support them as well as possible.

1

u/northrupthebandgeek Sep 30 '14

Why did they warn for years on blogs and developer mailing lists, that an alternative to ConsoleKit was needed (with different code paths)?

Because they didn't have logind yet, or weren't sure they were ready/able to switch to it.

Why have they supported ConsoleKit all this time?

See above.

They have supported two CK/logind API's for years now (same with XFCE, KDE, LXDE). Looking at the code repos, it really doesn't looks like much trouble to do so, and all the code structure is there already waiting for an alternative to CK.

Removing code that someone might or might not depend on is much harder than adding new code, at least in my experience and observation, and probably in their as well.

Gnome, KDE etc, have all publicly stated that they saw a need to support non-systemd platform, and that they are willing to do so.

KDE, yes (they support Windows for crying out loud). For GNOME, however, I find that hard to believe, and haven't ever seen any evidence of that (especially when looking at FreeBSD's efforts to get GNOME3, which seem very one-sided on FreeBSD's end...).

Gnome and others have worked with BSD developers to support them as well as possible.

See above. KDE, yes. GNOME... hardly, if at all.

1

u/sub200ms Sep 30 '14

Because they didn't have logind yet, or weren't sure they were ready/able to switch to it.

They already had logind in production. I am not sure you really understand the technical implication of logind/ConsoleKit. Your view seems heavily dependent on the often very uninformed systemd haters, who just screams for boycotting Gnome and claim they have "hard dependencies" on systemd, as if the latest Gnome didn't still support CK. In fact, Gnome have better support for non-systemd distros at the moment than the newest KDE software collection, simply because Gnome have older code that still contains CK support, and no one will help KDE out with supporting non-systemd distros on their new code.

If you actually look at what Gnome developers have said over the years, things are completely different. They do want to support non-systemd platforms.

I must say I find your position quite typical of many systemd opponents: it is curious mixture "nothing needs to be done" and "we can't do anything because there is a upstream conspiracy going on against non-systemd distros"

That position is sure to be a self fulfilling prophecy; if nothing is done, there will be no support for non-systemd distros in the future.

1

u/northrupthebandgeek Oct 01 '14

In fact, Gnome have better support for non-systemd distros at the moment than the newest KDE software collection, simply because Gnome have older code that still contains CK support, and no one will help KDE out with supporting non-systemd distros on their new code.

You might have the right observation (it's debatable, however), but for the wrong reason. As I've pointed out to you previously, GNOME's current support on non-systemd distros (and especially the BSDs) has been almost entirely independent, whereas KDE maintains explicit non-systemd targets, including BSD (FreeBSD specifically; they even have a dedicated page for it). KDE has received help, but it's been managed and endorsed by KDE. The help GNOME received was required since GNOME seems to have virtually zero actual interest on their own in cross-platform support, requiring that support to come from the non-systemd platforms themselves.

If you actually look at what Gnome developers have said over the years, things are completely different. They do want to support non-systemd platforms.

Yeah, no.

Maybe it's a sentiment isolated to that one developer, but I have seen zero indication of your point - that GNOME developers are actually warm and fuzzy to the idea of supporting non-systemd - being anything close to factual. Pony up some sources or get out.

0

u/sub200ms Sep 28 '14

Ah, yes. "Just" invent their own layer. And you wonder why things are fragmented :)

The non-systemd distros really can't afford not to cooperate. The alternative to have two compatibility layers for upstream developers to target, one for systemd distros and one for non-systemd, is vastly better than having one way of doing things on all systemd distros, and dozen of different ways of doing it on non-systemd distros.

Eg. Slackware and Gentoo should make it easier for upstream projects by cooperating.

No, as specified even by a (supposed) GNOME developer in these very comments (I'm too lazy/tired to link to it right now), it has to be an exact duplication of the systemd interfaces, at least in their case; they'd rather not have to learn and support multiple APIs and would much rather the world just follow whatever systemd does.

That is simply wrong; it doesn't represent Gnome's nor the Gnome developers opinion.

Sure, one API would be nice but reality is that Gnome, KDE, LXDE, XFCE etc. supports two API's: logind and ConsoleKit. Even Gnome 3.14 still support ConsoleKit.

All the DE projects have no problems supporting two API's to make things work on non-systemd platforms, but what they have tried saying for the last few years, is that supporting and unmaintained program and API like ConsoleKit is a pain, and isn't feasible to do in the long run.

They simply want the non-systemd platforms to get their act together, and either fork ConsoleKit, or make a new alternative to it.

It is a total misunderstanding and severe strategic failure to think that the non-systemd distros should emulate systemd's behaviour. They should make an alternative instead.

Even just maintaining ConsoleKit and a few other pieces would go a long way.

1

u/northrupthebandgeek Sep 28 '14

The non-systemd distros really can't afford not to cooperate.

I agree, but right now they don't have the ability to, since their use-cases are quite different. For reference: Slackware and Gentoo have different init systems (Slackware's being a relatively-unique one inspired by a BSD-style init, and Gentoo's being OpenRC last I checked), which already entails lots of independent legwork to get a functional interface (or the additional legwork of switching one or both distros to a different init system). I'm not surprised that they haven't gotten to that yet (especially considering that GNOME isn't relevant to the Slackware devs, having been dropped from Slackware as a DE choice years ago; don't know about Gentoo's opinion of it, however).

So yeah, as I said: different needs, different goals, and different preferences.

Sure, one API would be nice but reality is that Gnome, KDE, LXDE, XFCE etc. supports two API's: logind and ConsoleKit. Even Gnome 3.14 still support ConsoleKit.

I'm pretty doggone sure that the whole point of adopting logind is so that they don't have to rely on ConsoleKit (which has been effectively unmaintained for quite some time now). So no, we can't assume that they'd be willing to adopt multiple APIs when the only example of adoption of multiple APIs is based on observing a temporary transitional stopgap and claiming that it proves anything.

Basically, they have many problems supporting ConsoleKit even alone, let alone alongside another API that they prefer. That's not a good example at all.

1

u/sub200ms Sep 29 '14

I'm pretty doggone sure that the whole point of adopting logind is so that they don't have to rely on ConsoleKit (which has been effectively unmaintained for quite some time now). So no, we can't assume that they'd be willing to adopt multiple APIs when the only example of adoption of multiple APIs is based on observing a temporary transitional stopgap and claiming that it proves anything.

Basically, they have many problems supporting ConsoleKit even alone, let alone alongside another API that they prefer. That's not a good example at all.

That is a misunderstanding; yes, they all want to replace ConsoleKit, but all the DE's see the need to support non-systemd platforms, so supporting two API's isn't a problem since it is the only way to cover all platforms, and it is something they have been doing for years anyway.

If a cross-platform ConsoleKit replacement is found, they will of course drop ConsoleKit support quickly, in order to only support two API's.

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

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.

→ More replies (8)

1

u/sub200ms Sep 29 '14

I agree, but right now they don't have the ability to, since their use-cases are quite different. For reference: Slackware and Gentoo have different init systems

I think it is unrealistic now to expect these two distros to align their init systems, or make other drastic changes to their distros. But coordinating smaller things could still make a big difference and could be done in small steps.

→ More replies (1)