Default files/directories to at least 0444/0555 mode.

[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 02e01db..aca3fd4 100644 (file)
--- a/src/client/lufs/mount.captive.pod.pl.in
+++ b/src/client/lufs/mount.captive.pod.pl.in
@@ -32,7 +32,7 @@ mount.@PACKAGE@ - B<mount>(8) interface for NTFS disk access
 
 =head1 SYNOPSIS
 
-B<mount.ntfs> {B<image-file>|B<device>} B<mountdir>
+B<mount.@PACKAGE@-ntfs> {B<image-file>|B<device>} B<mountdir>
 [B<-n>] [B<-v>] [B<-o> B<options>]
 
 B<mount> B<-t> B<@PACKAGE@-ntfs>
@@ -43,7 +43,7 @@ B<mount> B<-t> B<@PACKAGE@-ntfs>
 =head1 DESCRIPTION
 
 B<mount.@PACKAGE@>(8) provides B<mount>(8) interface to B<lufs-@PACKAGE@fs>(7)
-by calling B<lufsmount>(1) with appropriate arguments. You should never call
+by calling B<lufsd>(1) with appropriate arguments. You should never call
 this command directly - use B<mount>(8) instead.
 
 B<mount.@PACKAGE@>(8) (B<@PACKAGE@> filesystem type) is never used - this command
@@ -81,22 +81,64 @@ B</etc/mtab> is modified notwithstanding.
 
 =item B<-v>
 
-Enable verbose mode. Command B<lufsmount>(1) being called is shown.
+Enable verbose mode. Command B<lufsd>(1) being called is shown.
 
 
 =item B<-o> B<options>
 
-Custom options passed to B<@PACKAGE@>(7). See its manpage for details.  Options
-double-dashes (B<-->) can be omitted for B<lufs-@PACKAGE@fs>(7) or
-B<mount.captive>(8).
+Custom options passed to B<@PACKAGE@>(7) separated by comma (B<,>).
+See the B<@PACKAGE@>(7) manpage for details on options prefixed by
+double-dashes (B<-->) will be used for B<lufs-@PACKAGE@fs>(7) /
+B<mount.captive>(8). Options without double-dashes (B<-->) will be used for
+B<lufsd>(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<lufsd>(1) option.
+
+=item B<private>
+
+B<mount.captive>(8) defaults to filesystem files B<644> - read-write for system
+root (or the regular user owner) and read-only for others. You can force the
+mode B<600> by this option (read-write for the owner, inaccessible for others).
+Mode B<755> or <700> applies to directories. Options B<fmask>/B<dmask> will
+be OR-ed to the private/public permissions set by this option.
+
+=item B<fmask>=B<666>
+
+Octal mask to be OR-ed on file permissions (minimum file permissions).
+
+=item B<dmask>=B<777>
+
+Octal mask to be OR-ed on directory permissions (minimum directory
+permissions).
+
+=item B<uid>=B<500>
+
+Supply the B<UID> to be the user identification number owning all the files.
+
+=item B<gid>=B<500>
+
+Supply the B<GID> to be the group identification number owning all the files.
+
+=back
 
 =back
 
 
 =head1 SEE ALSO
 
-B<lufs-@PACKAGE@fs>(7), B<lufsmount>(1)
+B<lufs-@PACKAGE@fs>(7), B<lufsd>(1)
 
 
 =head1 AUTHOR