Check for multiple device mounts overridable by '-o force'.

diff --git a/project/captive/man/mount.captive.pod.html b/project/captive/man/mount.captive.pod.html
index 53c49c4..d7379f5 100644 (file)
--- a/project/captive/man/mount.captive.pod.html
+++ b/project/captive/man/mount.captive.pod.html
@@ -91,6 +91,21 @@ double-dashes (<strong>--</strong>) will be used for <strong>lufs-captivefs</str
 <strong>lufsmount</strong>(1). You may be interested in these unprefixed options:
 </dd>
 <dl>
+<dt><strong><a name="item_force"><strong>force</strong></a></strong><br />
+</dt>
+<dd>
+Force the mount of {<strong>image-file</strong>|<strong>device</strong>} despite it appears to be already
+mounted according to <strong>mtab</strong>(5). You should never mount a device multiple
+times in read-write mode. It is safe to mount it multiple times in read-only
+mode. It is safe to mount it once in read-write mode and multiple times
+in read-only mode although you may encounter filesystem errors by the read-only
+filesystems in such case.
+</dd>
+<dd>
+<p>This is the only option is interpreted by <strong>mount.captive</strong> itself; it is not
+<strong>lufs-captivefs</strong>(7) nor <strong>lufsmount</strong>(1) option.</p>
+</dd>
+<p></p>
 <dt><strong><a name="item_uid%3d500"><strong>uid</strong>=<strong>500</strong></a></strong><br />
 </dt>
 <dd>