On Mon, 14.04.14 14:16, Ryan Lortie (de...@desrt.ca) wrote:
Before we realised that this bug was a problem, however, having the bus
driver was clearly closer to classic dbus-1.
Yupp, and we do revisit what we do from time to time and do change our
opinions after consideration, which any
On 04/14/2014 08:16 PM, Ryan Lortie wrote:
hi,
Hi,
On Mon, Apr 14, 2014, at 12:08, Lennart Poettering wrote:
Au contraire. I am pretty sure that with handling the driver client side
makes things much simpler and closer to classic dbus1.
I agree. No races, after all, in practice.
Before
Lukas, Ryan,
just wanted to let you know that I am working to get rid of the bus
driverd in systemd after all, for kdbus. The reason is that leaving it
in, as it is now, is very racy, and not just theorectically, but
IRL. Ryan, you might remember the mouse cursor bug when running gnome
on kdbus,
On 04/14/2014 08:39 AM, Lennart Poettering wrote:
Lukas, Ryan,
Hi Lennart, Ryan
just wanted to let you know that I am working to get rid of the bus
driverd in systemd after all, for kdbus. The reason is that leaving it
in, as it is now, is very racy, and not just theorectically, but
IRL.
On Mon, 14.04.14 10:48, Ryan Lortie (de...@desrt.ca) wrote:
I will now remove the entirety of the driver daemon, not just
AddMatch/RemoveMatch as all but two of those calls are subject to
similar (theoretical...) races.
It's always been somewhat clear to me that kdbus is not a
