summaryrefslogtreecommitdiff
path: root/network/nbd/README
diff options
context:
space:
mode:
Diffstat (limited to 'network/nbd/README')
-rw-r--r--network/nbd/README18
1 files changed, 11 insertions, 7 deletions
diff --git a/network/nbd/README b/network/nbd/README
index 18f1ebcb93..36d4f946df 100644
--- a/network/nbd/README
+++ b/network/nbd/README
@@ -1,8 +1,12 @@
-With NBD you can access block device on remote host just as it was in your
-local /dev. It works with companion with the kernel nbd driver and consists
-of a server and a client. Communication between client and server works over
-TCP/IP networking, but to the client program this is hidden: it looks like
-a regular local file access to a block device special file such as /dev/nd0.
+Network Block Devices (NBD) is used to access a remote block device on a local
+machine over a TCP/IP network. Provided in this package are the userland apps
+nbd-client and nbd-server.
-NBD kernel driver location: Device Drivers -> Block devices -> Network block
-device support The kernel driver needs only to be compiled on client side.
+The nbd-server is used to export a block device over a TCP/IP network to a
+remote client. It defaults to /etc/nbd-server/config for settings.
+See man page nbd-server.
+
+The nbd-client is used to connect to the remote nbd-server block device over
+a TCP/IP network. It requires the nbd kernel module provided by Slackware
+which creates /dev/nbd0 through /dev/nbd15 for local use.
+See man page nbd-client. \ No newline at end of file