From feb6da1ec3dfaed7abab678790e337e3a88861fa Mon Sep 17 00:00:00 2001 From: Daniel Mack Date: Tue, 27 Jan 2015 18:32:08 +0100 Subject: [PATCH] doc: kdbus.fs.xml cleanups Signed-off-by: Daniel Mack --- doc/kdbus.fs.xml | 49 ++++++++++++++++++++++++++++++++---------------- 1 file changed, 33 insertions(+), 16 deletions(-) diff --git a/doc/kdbus.fs.xml b/doc/kdbus.fs.xml index 75d00f0..fc2d900 100644 --- a/doc/kdbus.fs.xml +++ b/doc/kdbus.fs.xml @@ -22,11 +22,34 @@ File-system Layout - The kdbusfs - pseudo file-system provides access to internal kdbus entities, - including buses and endpoints. Each time you mount it, a new - instance (called domain) will be created - which is independent of the other domains. + + The kdbusfs pseudo file-system provides access to + kdbus entities, such as buses and + endpoints. Each time you mount the filesystem, + a new and isolated kdbus instance will be created which is independent + of the other instances. + + + The system-wide default 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. On 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.bus7, + kdbus.connection7 and + kdbus.endpoint7 + for more details. + Following, you can see an example layout of the kdbusfs file-system: @@ -46,15 +69,13 @@ Mounting instances - In order to get a new and separate kdbus environment, new instance - of kdbusfs can be mounted like this: + + In order to get a new and separate kdbus environment, new instance + of kdbusfs can be mounted like this: + - # mount -t kdbusfs kdbusfs /tmp/new_kdbus/ + # mount -t kdbusfs kdbusfs /tmp/new_kdbus/ - - - Busses created in this new instance will be entirely separated and - not influence any other kdbus instances on the system. @@ -64,10 +85,6 @@ kdbus.bus7 kdbus.connection7 kdbus.endpoint7 - kdbus.item7 - kdbus.message7 - kdbus.names7 - kdbus.pool7 mount8 -- 2.34.1