summaryrefslogtreecommitdiff
path: root/network/nbd/README
diff options
context:
space:
mode:
authorAndrzej Telszewski <atelszewski@gmail.com>2010-05-11 22:54:58 +0200
committerDavid Somero <xgizzmo@slackbuilds.org>2010-05-11 22:54:58 +0200
commitecac12763b1242e543c315e4b0e3c02e7de071f7 (patch)
treeca19832e661b1e61a77d375e83cd63101253c24c /network/nbd/README
parentc2bfcda4247edf3d70065b1fe91077972017b81d (diff)
downloadslackbuilds-ecac12763b1242e543c315e4b0e3c02e7de071f7.tar.gz
network/nbd: Added to 12.1 repository
Diffstat (limited to 'network/nbd/README')
-rw-r--r--network/nbd/README8
1 files changed, 8 insertions, 0 deletions
diff --git a/network/nbd/README b/network/nbd/README
new file mode 100644
index 0000000000..18f1ebcb93
--- /dev/null
+++ b/network/nbd/README
@@ -0,0 +1,8 @@
+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.
+
+NBD kernel driver location: Device Drivers -> Block devices -> Network block
+device support The kernel driver needs only to be compiled on client side.