|
|
Log in / Subscribe / Register

clarity of concept

clarity of concept

Posted Nov 6, 2014 22:05 UTC (Thu) by mezcalero (subscriber, #45103)
In reply to: clarity of concept by atai
Parent article: Kdbus meets linux-kernel

sd-bus supports both the classic dbus1 AF_UNIX transport as well as kdbus as backend. Applications written against the library should in most ways not see any difference. A couple of things won't be available on AF_UNIX though. For example, the credentials concept is much more powerful on kdbus than on AF_UNIX and we cannot emulate that on AF_UNIX.

sd-bus as a library should work fine on non-systemd systems too. A couple of things won't be available then though. For example, it offers APIs to connect to the system bus of local running OS containers, and to system busses of remote systems via SSH.

sd-bus is not portable to other kernels however. We make use of a multitude of Linux APIs, and it's not feasable really to port it, like the rest of systemd. And we will not accept patches for that.

However, this shouldn't really be a problem, as libdbus-1 and gdbus are both powerful libraries that are portable, and can also be used to talk to dbus. If portability to other OSes matters to you you can simply opt for one of those libraries.

Lennart


to post comments

clarity of concept

Posted Nov 18, 2014 17:29 UTC (Tue) by nix (subscriber, #2304) [Link]

This encourages user applications to become gratuitously nonportable and seems like a bad move.

Libraries meant for general use should be portable, even if the system as a whole that they are part of is not.


Copyright © 2026, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds