News for hackers. Stuff that matters.
Re:SystemBSD: Custom D-Bus daemons emulating systemd behavio... by geofft on Saturday September 05, 2015 @11:31PM (#10176750)
The systemd folks have been saying all along that it's just a standardized and stable interface and anyone else can implement that interface. I'm glad to see this, because it's testing the claim: if it's true, that means wonderful things for OpenBSD portability, and if it's not true, we should be more cautious about coding to systemd's APIs.
Re:SystemBSD: Custom D-Bus daemons emulating systemd behavio... by generic_user on Sunday September 06, 2015 @01:29AM (#10176879)
The argument that XYZ has a portable interface therefor XYZ is portable is a bit of a head fake argument. OpenGL 4.5 is also a supposedly portable interface, so is the X Server protocol. To implement these takes years of work with large teams of full time engineers. Mesa has over 1.5 million lines of code and has been in constant development for over 10 years.

At last count SystemD has over 40 "Interfaces". These are not publicly versioned standards. So there is no stable interface to even implement and there is no commitment that these "interfaces" will not change at any point in time.

If the project estimate to actually implement XYZ interface takes years of full time engineers and millions of dollars to complete its basically out of the reach of any volunteer open source operating system project.

I just find the argument disingenuous. Everyone making these claims knows that there is practically 0 chance that anyone but RedHat or another big Corporation like Google or Samsung has the resources to Implement something like this.

Re:SystemBSD: Custom D-Bus daemons emulating systemd behavio... by esarbe on Sunday September 06, 2015 @03:34AM (#10177027)
What you are stating here is not true.

Take a look at https://wiki.freedesktop.org/www/Software/systemd/InterfaceP... and you'll see that there are indeed a plethora of systemd service apis. But almost all of them are covered by the systemd stability promise (https://wiki.freedesktop.org/www/Software/systemd/InterfaceS...) and almost all of them are documented.

So, there is a commitment that these interfaces will not change.

Re:SystemBSD: Custom D-Bus daemons emulating systemd behavio... by generic_user on Sunday September 06, 2015 @07:00AM (#10177332)
I am aware of the pages you linked to and have on a few occasions tried to look over things. Having read quite a few rather large standers and APIs my impression the "Portable Interfaces" is rather dim. They are disjoint and unversioned notes not presentable portable interface standards. There are also various internal protocols and interfaces which are not documented from what I have gathered.

In short SystemD is an implementation. And as they say in there own documents there implementation is and never will be a portable implementation.

The "Interface Stability Promise" is referring to the unit configuration file format and the command line interface. This is not stability of the implementation c interfaces.

If you want to see a proper portable specification take a look at the Wayland Protocol Specification. There or perhaps POSIX.

Re:SystemBSD: Custom D-Bus daemons emulating systemd behavio... by yrro on Sunday September 06, 2015 @08:47AM (#10177479)
> The "Interface Stability Promise" is referring to the unit configuration file format and the command line interface. This is not stability of the implementation c interfaces.

This is not true.

Re:SystemBSD: Custom D-Bus daemons emulating systemd behavio... by gillianseed on Sunday September 06, 2015 @03:40AM (#10177035)
>So there is no stable interface to even implement and there is no commitment that these "interfaces" will not change at any point in time.

Isn't this what the systemd 'Interface Stability Promise' does as listed here ?

http://www.freedesktop.org/wiki/Software/systemd/InterfacePo...

Judging by this chart, ~99% of the intefaces are stable.

[dead]
Re:SystemBSD: Custom D-Bus daemons emulating systemd behavio... by geofft on Sunday September 06, 2015 @12:23PM (#10178066)
Regardless of the validity of your point (which seems tenuous), your mockery is not conducive to reasoned, respectful discussion. Perhaps the parent, like me, has read the interface stability promise and found it wanting. Perhaps there was a useful discussion to have had there.
Re:SystemBSD: Custom D-Bus daemons emulating systemd behavio... by vezzy-fnord on Sunday September 06, 2015 @10:14AM (#10177690)
There's also the "Reimplementable independently" column. Rather important.
Re:SystemBSD: Custom D-Bus daemons emulating systemd behavio... by generic_user on Sunday September 06, 2015 @02:57PM (#10178601)
Its quite the opposite. Only after you seriously try to look at the documents and what they provide that you come the conclusion that the "Portable Interfaces" is simply blowing smoke.
Re:SystemBSD: Custom D-Bus daemons emulating systemd behavio... by okasaki on Sunday September 06, 2015 @02:12AM (#10176930)
So where can I read the standard?
Re:SystemBSD: Custom D-Bus daemons emulating systemd behavio... by gillianseed on Sunday September 06, 2015 @03:34AM (#10177026)
I googled for systemd api interfaces and this was the first thing I got:

http://www.freedesktop.org/wiki/Software/systemd/InterfacePo...

Re:SystemBSD: Custom D-Bus daemons emulating systemd behavio... by viraptor on Sunday September 06, 2015 @05:13AM (#10177169)
That documentation / list is interesting. They say that logind is fully documented for example. But if you follow the link, you get things like:

    CreateSession(in  u arg_0,
                    in  u arg_1,
                    in  s arg_2,
                    in  s arg_3,
                    in  s arg_4,
                    in  s arg_5,
                    ...
With no further explanation, apart from one paragraph summary of who shouldn't call it.

I remember someone complaining about that years ago already. Apparently nothing changed.

Re:SystemBSD: Custom D-Bus daemons emulating systemd behavio... by gillianseed on Sunday September 06, 2015 @05:46AM (#10177216)
>With no further explanation, apart from one paragraph summary of who shouldn't call it.

The CreateSession description states that it should never be called from the clients, but instead be handled through PAM, so assume this is why they don't describe the arguments for this one call, while all the other method arguments and return values are described under 'Methods'.

Re:SystemBSD: Custom D-Bus daemons emulating systemd behavio... by viraptor on Sunday September 06, 2015 @05:52AM (#10177224)
That's hardly "fully documented" though, isn't it?

What I mean specifically is that they document the client interface only, not the full interface needed for a complete replacement.

Re:SystemBSD: Custom D-Bus daemons emulating systemd behavio... by gillianseed on Sunday September 06, 2015 @06:12AM (#10177254)
Well since it's one single method that's not documented, and they say you should not call it from a client, I assume they want to make it clear by not exposing the arguments in the client api documentation.

If you want to re-implement logind you will invariably read the logind source code anyway, where the call arguments are described.

You said there been a complaint about this, was there a discussion you can point me to ?

Re:SystemBSD: Custom D-Bus daemons emulating systemd behavio... by simoncion on Sunday September 06, 2015 @05:41PM (#10179149)
> If you want to re-implement logind you will invariably read the logind source code anyway...

1) Does this mean that you consider software's source code to be adequate documentation of an API and its behavioral contracts?

2) There's this saying that goes something like "You never know that you have a good API until you've created three independent implementations of it.". It's very difficult to create an independent implementation of an API if the primary documentation of important parts of that API's behavior is the source code that implements that API.

Re:SystemBSD: Custom D-Bus daemons emulating systemd behavio... by DavidNielsen on Sunday September 06, 2015 @07:28AM (#10177363)
They have very well defined documentation for all the stable parts of the API, their code is modern and quite readable. In addition to this Lennart is good at publishing lengthy explanatory blogposts aimed at system administrators. Finally they have done a truly admirable job building a community and explaining the why's and how's of their project. This is evident in the fact that there is now a systemd conference coming up.

If this fails the test, I suggest that it is a marvelous failure which every project should strive to emulate. To suggest that systemd is poorly documented indicates an insufficient exposure to the sad reality of most Open Source projects where "our unmaintained, outdated, bug riddled code base is the documentation" is the best case answer to the question of documentation.

Re:SystemBSD: Custom D-Bus daemons emulating systemd behavio... by geofft on Sunday September 06, 2015 @12:25PM (#10178072)
Having done distro-maintenance work that needed to be compatible with both systemd and upstart, I've read the explanatory blog posts and found them wonderful, and I've also found the detailed API documentation lacking in spots.

There are a lot of praiseworthy things about systemd and its approach to documentation. The blog posts are definitely one of them. That doesn't mean everything is praiseworthy, that there's no room for improvement, or that complaints about things not being documented are illegitimate or inappropriate.

Re:SystemBSD: Custom D-Bus daemons emulating systemd behavio... by viraptor on Sunday September 06, 2015 @08:44AM (#10177474)
Your first sentence seems to contradict the docs... which still don't describe "all the stable parts".
Re:SystemBSD: Custom D-Bus daemons emulating systemd behavio... by nwmcsween on Sunday September 06, 2015 @01:13AM (#10176858)
Read the slides he had a multitude of issues trying to copy the interfaces due to the tight integration of components.
Re:SystemBSD: Custom D-Bus daemons emulating systemd behavio... by simoncion on Sunday September 06, 2015 @01:21AM (#10176867)
What's more, I expect that his will forever be an incomplete implementation due to to undocumented or poorly-documented behaviors, edge-case or otherwise.
Re:SystemBSD: Custom D-Bus daemons emulating systemd behavio... by the_why_of_y on Sunday September 06, 2015 @08:27AM (#10177441)
Of course the implementation is going to be incomplete in some way, since OpenBSD kernel doesn't have the APIs necessary to actually implement multiple seats, so the implementation won't allow creating more than 1 seat.
Re:SystemBSD: Custom D-Bus daemons emulating systemd behavio... by generic_user on Sunday September 06, 2015 @01:35AM (#10176887)
It was never even considered that this would be a complete implementation. The goal was always to just implement the minimum requirements to get Gnome working. And as far as I know they never even completed that work. They implemented some small subset of there original daemons because the project quickly blew up into a major amount of work.