5 ms·
It doesn't seem very general purpose unless there are also non kernel implementations, and you can't sanely remote it as it relies on the kernel for authenticat
by justincormack 11y ago
It doesn't seem very general purpose unless there are also non kernel implementations, and you can't sanely remote it as it relies on the kernel for authentication.
- rwmj 11y agoIts purpose is single host communication. If you assume a single host then you don't have to deal with distributing computing problems at all. Not sure why having non-kernel implementations is a problem. Is the fact that there is no non-kernel implementation of Unix sockets / TCP/IP / filesystems / name-most-other-Linux-kernel-features a problem for you? BTW I don't especially care about kdbus, but I do hate that there are no good, featureful communication primitives in Linux.
- justincormack 11y agoThe article was looking for multihost too which is why I mentioned it. There are some non kernel sockets implementations, but it is less of an issue as every kernel implements them, but kdbus is not implemented anywhere yet. It is also not possible to implement correctly in userspace as the security guarantees rely on a kernel, which is inconvenient. It is unlikely eg FreeBSD will ever implement it.