summaryrefslogtreecommitdiffstats
path: root/mount/mount.8
diff options
context:
space:
mode:
authorKarel Zak2009-01-06 15:20:37 +0100
committerKarel Zak2009-01-06 15:20:37 +0100
commitf0daecf3c52a249bd244890ed53c50e165f2793f (patch)
tree152b724baaf483d2baa66da42d54b37dd4174697 /mount/mount.8
parentmount: add info about semantics of read-only mount to mount.8 (diff)
downloadkernel-qcow2-util-linux-f0daecf3c52a249bd244890ed53c50e165f2793f.tar.gz
kernel-qcow2-util-linux-f0daecf3c52a249bd244890ed53c50e165f2793f.tar.xz
kernel-qcow2-util-linux-f0daecf3c52a249bd244890ed53c50e165f2793f.zip
mount: suggest to use blockdev --setro rather than losetup
Thanks to Christoph Hellwig. Signed-off-by: Karel Zak <kzak@redhat.com>
Diffstat (limited to 'mount/mount.8')
-rw-r--r--mount/mount.84
1 files changed, 2 insertions, 2 deletions
diff --git a/mount/mount.8 b/mount/mount.8
index bbbbd33a8..a4d20ac00 100644
--- a/mount/mount.8
+++ b/mount/mount.8
@@ -428,8 +428,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