On Fri, 15 Jul 2011 13:48:04 -0500 Shirish Pargaonkar <[email protected]> wrote:
> On Fri, Jul 15, 2011 at 1:30 PM, Jeff Layton <[email protected]> wrote: > > On Fri, 15 Jul 2011 12:37:35 -0500 > > [email protected] wrote: > > > >> From: Shirish Pargaonkar <[email protected]> > >> > >> Manpage contents for cifs mount option cifsacl > >> > >> > >> Signed-off-by: Shirish Pargaonkar <[email protected]> > >> --- > >> mount.cifs.8 | 33 +++++++++++++++++++++++++++++++++ > >> 1 files changed, 33 insertions(+), 0 deletions(-) > >> > >> diff --git a/mount.cifs.8 b/mount.cifs.8 > >> index 7e0f117..082adcd 100644 > >> --- a/mount.cifs.8 > >> +++ b/mount.cifs.8 > >> @@ -272,6 +272,39 @@ Do not allow POSIX ACL operations even if server > >> would support them\&. > >> The CIFS client can get and set POSIX ACLs (getfacl, setfacl) to Samba > >> servers version 3\&.0\&.10 and later\&. Setting POSIX ACLs requires > >> enabling both XATTR and then POSIX support in the CIFS configuration > >> options when building the cifs module\&. POSIX ACL support can be disabled > >> on a per mount basis by specifying "noacl" on mount\&. > >> .RE > >> .PP > >> +cifsacl > >> +.RS 4 > >> +This option is used to map CIFS/NTFS ACLs to/fro Linux permission bits, > > ^^^^^^ > > to/from ... ditto for the other > > places in this entry > > > > Jeff, not sure I understand this change. Replace map with to/from? > No, replace "to/fro" with "to/from"... Another thought occurs to me as well...the ID mapping code is very new, but the cifsacl option has been around for a while. It would be good to clarify that here so that someone can have a reasonable expectation of the behavior they'll see when they enable this on a given kernel version. -- Jeff Layton <[email protected]> -- To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
