From: Karel Zak Date: Mon, 3 Jan 2022 12:23:54 +0000 (+0100) Subject: mount: (man) fix example X-Git-Tag: v2.38-rc1~80 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=355d3ef726278e03aa80430acc21d965d5c1566d;p=thirdparty%2Futil-linux.git mount: (man) fix example Fixes: https://github.com/util-linux/util-linux/issues/1539 Signed-off-by: Karel Zak --- diff --git a/sys-utils/mount.8.adoc b/sys-utils/mount.8.adoc index e1b3a78888..f2596b3553 100644 --- a/sys-utils/mount.8.adoc +++ b/sys-utils/mount.8.adoc @@ -227,7 +227,9 @@ This feature is not supported by the Linux kernel; it is implemented in userspac The alternative (classic) way to create a read-only bind mount is to use the remount operation, for example: ____ -*mount --bind* _olddir newdir_ *mount -o remount,bind,ro* _olddir newdir_ +*mount --bind* _olddir newdir_ + +*mount -o remount,bind,ro* _olddir newdir_ ____ Note that a read-only bind will create a read-only mountpoint (VFS entry), but the original filesystem superblock will still be writable, meaning that the _olddir_ will be writable, but the _newdir_ will be read-only.