aboutsummaryrefslogtreecommitdiff
path: root/fs/cifs/README
diff options
context:
space:
mode:
authorMatt LaPlante <kernel1@cyberdogtech.com>2006-10-03 22:36:44 +0200
committerAdrian Bunk <bunk@stusta.de>2006-10-03 22:36:44 +0200
commitcab00891c5489cb6d0cde0a55d39bd5f2871fa70 (patch)
tree0dc810a15ad02dc76939b6ea021a4a24794561bb /fs/cifs/README
parent44c09201a4178e08ed1c8cc37e7aea0683888f0a (diff)
Still more typo fixes
Signed-off-by: Adrian Bunk <bunk@stusta.de>
Diffstat (limited to 'fs/cifs/README')
-rw-r--r--fs/cifs/README6
1 files changed, 3 insertions, 3 deletions
diff --git a/fs/cifs/README b/fs/cifs/README
index 5f0e1bd64fe..432e515431c 100644
--- a/fs/cifs/README
+++ b/fs/cifs/README
@@ -269,7 +269,7 @@ A partial list of the supported mount options follows:
(gid) mount option is specified. For the uid (gid) of newly
created files and directories, ie files created since
the last mount of the server share, the expected uid
- (gid) is cached as as long as the inode remains in
+ (gid) is cached as long as the inode remains in
memory on the client. Also note that permission
checks (authorization checks) on accesses to a file occur
at the server, but there are cases in which an administrator
@@ -375,7 +375,7 @@ A partial list of the supported mount options follows:
the local process on newly created files, directories, and
devices (create, mkdir, mknod). If the CIFS Unix Extensions
are not negotiated, for newly created files and directories
- instead of using the default uid and gid specified on the
+ instead of using the default uid and gid specified on
the mount, cache the new file's uid and gid locally which means
that the uid for the file can change when the inode is
reloaded (or the user remounts the share).
@@ -440,7 +440,7 @@ A partial list of the supported mount options follows:
create device files and fifos in a format compatible with
Services for Unix (SFU). In addition retrieve bits 10-12
of the mode via the SETFILEBITS extended attribute (as
- SFU does). In the future the bottom 9 bits of the mode
+ SFU does). In the future the bottom 9 bits of the
mode also will be emulated using queries of the security
descriptor (ACL).
sign Must use packet signing (helps avoid unwanted data modification