5 ms·
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 th
by geofft 11y ago
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.
- nwmcsween 11y agoRead the slides he had a multitude of issues trying to copy the interfaces due to the tight integration of components.
- simoncion 11y agoWhat's more, I expect that his will forever be an incomplete implementation due to to undocumented or poorly-documented behaviors, edge-case or otherwise.
- generic_user 11y agoIt 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.
- the_why_of_y 11y agoOf 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.
- generic_user 11y agoThe 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.
- esarbe 11y agoWhat you are stating here is not true. Take a look at https://wiki.freedesktop.org/www/Software/systemd/InterfacePortabilityAndStabilityChart/ 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/InterfaceStabilityPromise/ 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.
- generic_user 11y agoI 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.
- yrro 11y ago> 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.
- gillianseed 11y ago>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/InterfacePortabilityAndStabilityChart/ http://www.freedesktop.org/wiki/Software/systemd/InterfacePo... Judging by this chart, ~99% of the intefaces are stable.
- okasaki 11y agoSo where can I read the standard?
- gillianseed 11y agoI googled for systemd api interfaces and this was the first thing I got: http://www.freedesktop.org/wiki/Software/systemd/InterfacePortabilityAndStabilityChart/ http://www.freedesktop.org/wiki/Software/systemd/InterfacePo...
- viraptor 11y agoThat 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.
- gillianseed 11y ago>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'.
- viraptor 11y agoThat'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.
- 11y ago