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

[captive.git] / src / client / lufs / mount.captive.pod.pl.in

diff --git a/src/client/lufs/mount.captive.pod.pl.in b/src/client/lufs/mount.captive.pod.pl.in
index 7c39880..be3676d 100644 (file)
--- a/src/client/lufs/mount.captive.pod.pl.in
+++ b/src/client/lufs/mount.captive.pod.pl.in
@@ -94,6 +94,18 @@ B<lufsmount>(1). You may be interested in these unprefixed options:
 
 =over
 
+=item B<force>
+
+Force the mount of {B<image-file>|B<device>} despite it appears to be already
+mounted according to B<mtab>(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.
+
+This is the only option is interpreted by B<mount.@PACKAGE@> itself; it is not
+B<lufs-@PACKAGE@fs>(7) nor B<lufsmount>(1) option.
+
 =item B<uid>=B<500>
 
 Supply the B<UID> to be the user identification number owning all the files.