Lines Matching refs:to
16 (CIFS) protocol which is the successor to the Server Message Block
31 client for mounting to CIFS compliant servers. It includes
36 If you need to mount to Samba or Windows from this machine, say Y.
43 mounted by the cifs client to be displayed in /proc/fs/cifs/Stats
50 request timing to be displayed in /proc/fs/cifs/DebugData and also
51 allow optional logging of slow responses to dmesg (depending on the
67 SMB protocol but LANMAN based authentication is needed to
70 Enabling this option allows the cifs module to mount to older
74 have a need to access old SMB servers (and are on a private
75 network) you probably want to say N. Even if this support
78 can be set to required (or optional) either in
81 default in order to reduce the possibility of a downgrade
92 utilities to provide SPNEGO packaged (RFC 4178) Kerberos tickets
93 which are needed to mount to certain secure servers (for which more
104 to SMB/CIFS EAs. EAs are stored on Windows servers without the
107 (used by some filesystems to store ACLs) is not supported at
116 Enabling this option will cause the cifs client to attempt to
120 support for POSIX ACLs (getfacl and setfacl) to servers
129 is handed over to the application/caller. See the man
137 Enabling this option adds helpful debugging messages to
145 to the cifs code which slightly increases the size of
156 Distributed File System (DFS) support is used to access shares
158 moves to a different server. This feature also enables
160 utilities to provide server name resolution (host names to
165 bool "Allow nfsd to export CIFS file system"
168 Allows NFS server to export a CIFS mounted share (nfsd over cifs)
182 options. These protocols are the successors to the popular
189 when mounting to Samba, due to the CIFS POSIX extensions,
192 options are also slightly simpler (compared to CIFS) due
193 to protocol improvements.
209 to be cached locally on disk through the general filesystem cache