Re: Perfect Jessie is something like this...
Le Tue, 04 Nov 2014 01:29:52 +0000,
Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.com> a
écrit :
> Laurent Bigonville:
> > The systemd umbrella project is made of 10+ different executables
> > that have all a specific scope (systemd PID1 used to manage the
> > life cycles of the daemons, systemd-logind manage the user
> > sessions, systemd-journald a logging system,...) and that are all
> > communicating using well defined, stable and documented dbus
> > interfaces that allow one to reimplement the functionalities as
> > long as it exposes the same interfaces (ie. this is what
> > systemd-shim is doing).
>
> Not correct. The "systemd process" D-Bus API is not stable and not
> covered by the interface guarantee. It's exactly this that is part
> of the hoo-hah and part of the problem with systemd-shim over the
> past year or so.
>
> *
> http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/debian-systemd-packaging-hoo-hah.html
These are the "internal" API if I'm not wrong. The external ones are
stable as explained:
http://www.freedesktop.org/wiki/Software/systemd/InterfacePortabilityAndStabilityChart/
http://www.freedesktop.org/wiki/Software/systemd/InterfaceStabilityPromise/
But indeed you are correct, systemd PID1 and logind are tightly coupled
(the "Reimplementable Independently" column) and a project trying to
reimplement only one of them will have to play catch and run with
upstream. But this is NOT preventing to have reimplementations at all
as the external API used by 3rd party are stable. systemd is not alone
when providing stable external API and unstable internal ones.
Also note that this is not a huge issue for distribution like debian
that provides frozen in time stable release as we have a way to
synchronize the version (this is the job of a distribution) shipped to
our users.
Well at least this is my understanding of the matter.
Laurent Bigonville
Reply to: