From 67e02014c415502d3916f5302b8e04f4f388bd80 Mon Sep 17 00:00:00 2001 From: douyali Date: Tue, 22 Dec 2020 09:34:07 +0000 Subject: [PATCH] fix a number error in docs The qemu-nbd command generate file is /dev/nbd0. the ls command should view /dev/nbd0* Change-Id: Ic16d0e6cf5b99bd7794f88388087f621b778968e --- doc/image-guide/source/modify-images.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/image-guide/source/modify-images.rst b/doc/image-guide/source/modify-images.rst index 484acc5cbf..8b132dfb3d 100644 --- a/doc/image-guide/source/modify-images.rst +++ b/doc/image-guide/source/modify-images.rst @@ -402,7 +402,7 @@ there should be one new device created for each partition: .. code-block:: console - $ ls -l /dev/nbd3* + $ ls -l /dev/nbd0* brw-rw---- 1 root disk 43, 48 2012-03-05 15:32 /dev/nbd0 brw-rw---- 1 root disk 43, 49 2012-03-05 15:32 /dev/nbd0p1 brw-rw---- 1 root disk 43, 50 2012-03-05 15:32 /dev/nbd0p2 @@ -412,7 +412,7 @@ there should be one new device created for each partition: If the network block device you selected was already in use, the initial :command:`qemu-nbd` command will fail silently, and the - ``/dev/nbd3p{1,2,3}`` device files will not be created. + ``/dev/nbd0p{1,2,3}`` device files will not be created. If the image partitions are not managed with LVM, they can be mounted directly: @@ -420,7 +420,7 @@ they can be mounted directly: .. code-block:: console # mkdir /mnt/image - # mount /dev/nbd3p2 /mnt/image + # mount /dev/nbd0p2 /mnt/image When you are done, clean up: