kdbus.fs kdbus.fs kdbus.fs 7 kdbus.fs kdbus file system File-system Layout The kdbusfs pseudo filesystem provides access to kdbus entities, such as buses and endpoints. Each time the filesystem is mounted, a new, isolated kdbus instance is created, which is independent from the other instances. The system-wide standard mount point for kdbusfs is /sys/fs/kdbus. Buses are represented as directories in the file system layout, whereas endpoints are exposed as files inside these directories. At the top-level, a control node is present, which can be opened to create new buses via the KDBUS_CMD_BUS_MAKE ioctl. Each bus shows a default endpoint called bus, which can be opened to either create a connection with the KDBUS_CMD_HELLO ioctl, or to create new custom endpoints for the bus with KDBUS_CMD_ENDPOINT_MAKE. See kdbus.bus 7 , kdbus.connection 7 and kdbus.endpoint 7 for more details. Following, you can see an example layout of the kdbusfs filesystem: /sys/fs/kdbus/ ; mount-point |-- 0-system ; bus directory | |-- bus ; default endpoint | `-- 1017-custom ; custom endpoint |-- 1000-user ; bus directory | |-- bus ; default endpoint | |-- 1000-service-A ; custom endpoint | `-- 1000-service-B ; custom endpoint `-- control ; control file Mounting instances In order to get a new and separate kdbus environment, a new instance of kdbusfs can be mounted like this: # mount -t kdbusfs kdbusfs /tmp/new_kdbus/ See Also kdbus 7 kdbus.bus 7 kdbus.connection 7 kdbus.endpoint 7 mount 8