Shared publicly  - 
kdbus: +Greg Kroah-Hartman +Kay Sievers Why such a strange namespaces design for the API?
The entry points of lower level API (bus) are higher up in the /dev/kdbus hierarchy than the higher level API (namespaces)!
The bus API implementation even seems to had to add the uid to avoid name clashes with namespace API (namely "ns" directory, under which the namespaces are collected).
I.e. why not /dev/kdbus/ns/{namespaces..}/bus/{buses...}/entries/{entries}? This way there may be no clash between the interface and user-affected elements in the API: namespaces and buses would be in directories completely for themselves.
#kdbus #DBUS  
Morgaine Fowle (de la faye)'s profile photo
but programs run inside of a namespace. wouldn't this mean they have to know their own namespace to find the bus for their namespace?
Add a comment...