From: Karel Zak <kzak@redhat.com>
Date: Tue, 6 Jan 2009 14:20:37 +0000 (+0100)
Subject: mount: suggest to use blockdev --setro rather than losetup
X-Git-Url: https://err.no/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=a99cb339f6abe42d2d14bb627efbd22c7d9c5bfb;p=util-linux

mount: suggest to use blockdev --setro rather than losetup

Thanks to Christoph Hellwig.

Signed-off-by: Karel Zak <kzak@redhat.com>
---

diff --git a/mount/mount.8 b/mount/mount.8
index a734c7b0..e53b5954 100644
--- a/mount/mount.8
+++ b/mount/mount.8
@@ -413,8 +413,8 @@ Mount the file system read-only. A synonym is
 Note that, depending on the filesystem type, state and kernel behavior, the
 system may still write to the device. For example, Ext3 will replay its journal
 if the filesystem is dirty. To prevent this kind of write access, you may want
-to map the device through a read-only loop device, see command
-.BR losetup (8).
+to set the block device to read-only mode, see command
+.BR blockdev (8).
 .TP
 .B \-w
 Mount the file system read/write. This is the default. A synonym is