doc: do not mention modprobe in rbd docs

rbd binary will load rbd.ko itself, with appropriate options. Loading it by hand with default options is undesirable. Signed-off-by: Ilya Dryomov <[email protected]>
sahid · Apr 23, 2014 · 4238ffd · 4238ffd
1 parent 0ba3960
commit 4238ffd
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 12 deletions.
diff --git a/doc/rbd/rbd-ko.rst b/doc/rbd/rbd-ko.rst
@@ -6,13 +6,6 @@
 
 .. important:: To use kernel module operations, you must have a running Ceph cluster.
 
-Load the Ceph RBD Module
-========================
-
-To map a block device image to a kernel module, first load the Ceph RBD module:: 
-
-	modprobe rbd
-
 Get a List of Images
 ====================
 
@@ -24,7 +17,8 @@ Map a Block Device
 ==================
 
 Use ``rbd`` to map an image name to a kernel module. You must specify the 
-image name, the pool name, and the user name. ::
+image name, the pool name, and the user name. ``rbd`` will load RBD kernel
+module on your behalf if it's not already loaded. ::
 
   sudo rbd map {image-name} --pool {pool-name} --id {user-name}
 

diff --git a/doc/start/quick-rbd.rst b/doc/start/quick-rbd.rst
@@ -51,10 +51,6 @@ Configure a Block Device
 
 	rbd create foo --size 4096 [-m {mon-IP}] [-k /path/to/ceph.client.admin.keyring]
 
-#. On the ``ceph-client`` node, load the ``rbd`` client module. ::
-
-	sudo modprobe rbd
-
 #. On the ``ceph-client`` node, map the image to a block device. :: 
 
 	sudo rbd map foo --pool rbd --name client.admin [-m {mon-IP}] [-k /path/to/ceph.client.admin.keyring]