@@ -278,7 +278,9 @@ A partial list of the supported mount options follows:
278
278
(such as Windows), permissions can also be checked at the
279
279
client, and a crude form of client side permission checking
280
280
can be enabled by specifying file_mode and dir_mode on
281
- the client
281
+ the client. Note that the mount.cifs helper must be
282
+ at version 1.10 or higher to support specifying the uid
283
+ (or gid) in non-numberic form.
282
284
gid If CIFS Unix extensions are not supported by the server
283
285
this overrides the default gid for inodes.
284
286
file_mode If CIFS Unix extensions are not supported by the server
@@ -345,7 +347,10 @@ A partial list of the supported mount options follows:
345
347
client system. It is typically only needed when the server
346
348
supports the CIFS Unix Extensions but the UIDs/GIDs on the
347
349
client and server system do not match closely enough to allow
348
- access by the user doing the mount.
350
+ access by the user doing the mount, but it may be useful with
351
+ non CIFS Unix Extension mounts for cases in which the default
352
+ mode is specified on the mount but is not to be enforced on the
353
+ client (e.g. perhaps when MultiUserMount is enabled)
349
354
Note that this does not affect the normal ACL check on the
350
355
target machine done by the server software (of the server
351
356
ACL against the user name provided at mount time).
@@ -368,15 +373,21 @@ A partial list of the supported mount options follows:
368
373
setuids If the CIFS Unix extensions are negotiated with the server
369
374
the client will attempt to set the effective uid and gid of
370
375
the local process on newly created files, directories, and
371
- devices (create, mkdir, mknod).
376
+ devices (create, mkdir, mknod). If the CIFS Unix Extensions
377
+ are not negotiated, for newly created files and directories
378
+ instead of using the default uid and gid specified on the
379
+ the mount, cache the new file's uid and gid locally which means
380
+ that the uid for the file can change when the inode is
381
+ reloaded (or the user remounts the share).
372
382
nosetuids The client will not attempt to set the uid and gid on
373
383
on newly created files, directories, and devices (create,
374
384
mkdir, mknod) which will result in the server setting the
375
385
uid and gid to the default (usually the server uid of the
376
386
user who mounted the share). Letting the server (rather than
377
- the client) set the uid and gid is the default. This
378
- parameter has no effect if the CIFS Unix Extensions are not
379
- negotiated.
387
+ the client) set the uid and gid is the default. If the CIFS
388
+ Unix Extensions are not negotiated then the uid and gid for
389
+ new files will appear to be the uid (gid) of the mounter or the
390
+ uid (gid) parameter specified on the mount.
380
391
netbiosname When mounting to servers via port 139, specifies the RFC1001
381
392
source name to use to represent the client netbios machine
382
393
name when doing the RFC1001 netbios session initialize.
@@ -418,6 +429,13 @@ A partial list of the supported mount options follows:
418
429
byte range locks).
419
430
remount remount the share (often used to change from ro to rw mounts
420
431
or vice versa)
432
+ sfu When the CIFS Unix Extensions are not negotiated, attempt to
433
+ create device files and fifos in a format compatible with
434
+ Services for Unix (SFU). In addition retrieve bits 10-12
435
+ of the mode via the SETFILEBITS extended attribute (as
436
+ SFU does). In the future the bottom 9 bits of the mode
437
+ mode also will be emulated using queries of the security
438
+ descriptor (ACL).
421
439
422
440
The mount.cifs mount helper also accepts a few mount options before -o
423
441
including:
0 commit comments