diff options
author | Steve French <sfrench@us.ibm.com> | 2006-03-02 03:24:57 +0000 |
---|---|---|
committer | Steve French <sfrench@us.ibm.com> | 2006-03-02 03:24:57 +0000 |
commit | 82940a465829b0c757dea45889aa150c8083e3d9 (patch) | |
tree | 3ef3b38f47d93f07b6b5ebc51a54f301f62ec11a /fs/cifs/README | |
parent | 46c79a645a00e71dbbfd5f52abe0ea7cf2d5daa3 (diff) | |
download | linux-82940a465829b0c757dea45889aa150c8083e3d9.tar.bz2 |
[CIFS] Make POSIX CIFS Extensions SetFSInfo match exactly what we want
not just the posix path feature.
Signed-off-by: Steve French <sfrench@us.ibm.com>
Diffstat (limited to 'fs/cifs/README')
-rw-r--r-- | fs/cifs/README | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/fs/cifs/README b/fs/cifs/README index b0070d1b149d..b2b4d0803761 100644 --- a/fs/cifs/README +++ b/fs/cifs/README @@ -422,6 +422,13 @@ A partial list of the supported mount options follows: nomapchars Do not translate any of these seven characters (default). nocase Request case insensitive path name matching (case sensitive is the default if the server suports it). + posixpaths If CIFS Unix extensions are supported, attempt to + negotiate posix path name support which allows certain + characters forbidden in typical CIFS filenames, without + requiring remapping. (default) + noposixpaths If CIFS Unix extensions are supported, do not request + posix path name support (this may cause servers to + reject creatingfile with certain reserved characters). nobrl Do not send byte range lock requests to the server. This is necessary for certain applications that break with cifs style mandatory byte range locks (and most |