40 lines
1.3 KiB
Diff
40 lines
1.3 KiB
Diff
Index: nbd-2.9.8/README
|
|
===================================================================
|
|
--- nbd-2.9.8.orig/README
|
|
+++ nbd-2.9.8/README
|
|
@@ -11,16 +11,18 @@ deadlock issues if you do that[1].
|
|
|
|
To install the package, please see the INSTALL file. You'll need to
|
|
install it on both the client and the server.
|
|
|
|
-Using NBD is quite easy. First, on the client, you need to create the
|
|
-device nodes:
|
|
+Using NBD is quite easy. First, on the client, you need to load the nbd
|
|
+kernel module; on modern systems, udev will create the needed device
|
|
+nodes /dev/nbdX.
|
|
+Otherwise, you can create them manually:
|
|
|
|
# cd /dev
|
|
-# ./MAKEDEV nb0
|
|
+# ./MAKEDEV nbd0
|
|
|
|
-(if you need more than one NBD device, repeat the above command for nb1,
|
|
-nb2, ...)
|
|
+(if you need more than one NBD device, repeat the above command for nbd1,
|
|
+nbd2, ...)
|
|
|
|
Since there's a problem with nbd and the (default) cfq I/O scheduler,
|
|
you may want to set it to deadline:
|
|
|
|
@@ -46,9 +48,9 @@ Finally, you'll be able to start the cli
|
|
nbd-client <hostname> <port> <nbd device>
|
|
|
|
e.g.,
|
|
|
|
-nbd-client 10.0.0.1 1234 /dev/nb0
|
|
+nbd-client 10.0.0.1 1234 /dev/nbd0
|
|
|
|
nbd-client must be ran as root; the same is not true for nbd-server (but
|
|
do make sure that /var/run is writeable by the server that nbd-server
|
|
runs as; otherwise, you won't get a PID file, though the server will
|