Starting the kdbus discussions

[Lennart Poettering]

On Thu, 02.01.14 15:25, Kevin Krammer (krammer at kde.org) wrote:

> On Thursday, 2014-01-02, 14:42:47, Kay Sievers wrote:
> > On Thu, Jan 2, 2014 at 2:12 PM, Kevin Krammer <krammer at kde.org> wrote:
> > > On Thursday, 2014-01-02, 02:03:29, Lennart Poettering wrote:
> > >> Coming back to the original question (or what I think the question was):
> > >> I figure the trusted/untrusted thing is also something that would
> > >> translate to whether people should ship unit files or dbus1 service
> > >> activation files. (That all said, thinking about it, maybe we should
> > >> just drop the requirement for native unit files or the user bus, and
> > >> just keep it in for the system bus).
> > > 
> > > I think that would be nice, though my understanding from your other reply
> > > is that dbus-daemon will handle that as usual anyway, at least for the
> > > not too distant future.
> > 
> > On systemd systems, the current "session bus" will be replaced by one
> > "user bus" per user. All sessions will share the same bus of the user.
> > That bus will be provided by the "systemd --user" instance.
> > 
> > There will be no dbus-daemon running or be used by default. The system
> > bus and the user bus are both created by the systemd binary which also
> > spawns the and manages the services.
> 
> Sorry, I am confused now.

Kay just tried to describe an another facet of the system after a
desktop environment adopted systemd as a service manager: we try to
shift the focus from a session bus to a user bus. This of course is
another politically senstive thing since some people are strongly bound
to the idea that multiple local session of the same user should work. We
kinda put an end to that.

> This seems to contradict what Lennart wrote earlier today: "Our primary focus 
> for now is the system bus, and dbus-daemon can continue to be used for the 
> session bus, even on a system that uses kdbus for the system bus."

Yes, this is correct, however as soon as kdbus and hence systemd is
adopted as service manager by the desktops this also means that the
desktops need to deal with the shift from a session to a user bus. 

The shift is smaller than it might appear I figure, as we simply will
redirect all session traffic to the user bus.

> Right now any application using its services can just make the D-Bus calls and 
> dbus-daemon will launch it if necessary.
> 
> It will either be necessary that this continues to work or that some end user 
> retrievable log or end user runnable diagnostic tool can identify that 
> FooContacts has a .service file but now needs a whatever-is-needed-now-file.

Whatever happens we will certainly make sure that unmodified apps will
continue to work the way they currently do (though possibly are talking
on the user bus rather than the session bus, but they shouldn't really
notice the difference).

Lennart

-- 
Lennart Poettering, Red Hat