aboutsummaryrefslogtreecommitdiff
path: root/network/nbd/README
diff options
context:
space:
mode:
authorStu Miller <slackbuilds@go4it2day.com>2011-05-31 23:02:28 -0400
committerRobby Workman <rworkman@slackbuilds.org>2011-06-13 01:33:39 -0400
commit2a398cb06beb891b8d5acf8174e550af808dbe98 (patch)
tree2b8f9a4a3483766840fc4a5b56e6e71238d2be9d /network/nbd/README
parentc5137b75f202ae38907001d5e98f1a4d0b13d3c6 (diff)
network/nbd: Updated for version 2.9.21a.
Signed-off-by: dsomero <xgizzmo@slackbuilds.org>
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 18f1ebcb931aa..36d4f946df497 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