sin/samba-mirror
1
0
Fork 0
mirror of https://github.com/samba-team/samba.git synced 2025-01-11 05:18:09 +03:00
Code
1bdd08227e
samba-mirror/source4/ntvfs
History
Andrew Tridgell 1bdd08227e smbpid needs to be 32 bit now to cope with SMB2 
(This used to be commit a2854fd6ea)
2008-06-02 11:03:19 +10:00
..
cifs added support for the output fields of SMB2 close 2008-05-27 16:43:36 +10:00
cifs_posix_cli r25554: Convert last instances of BOOL, True and False to the standard types. 2007-10-10 15:07:55 -05:00
common smbpid needs to be 32 bit now to cope with SMB2 2008-06-02 11:03:19 +10:00
ipc implement the documented SMB2 create blobs in the server 2008-05-28 16:28:37 +10:00
nbench r25554: Convert last instances of BOOL, True and False to the standard types. 2007-10-10 15:07:55 -05:00
posix don't emulate broken SMB2 locking behaviour from windows 2008-05-30 07:28:29 +10:00
print r26443: Remove global_loadparm instances. 2007-12-21 05:50:11 +01:00
simple r25554: Convert last instances of BOOL, True and False to the standard types. 2007-10-10 15:07:55 -05:00
smb2 implemented client side SMB2 signing 2008-05-30 17:03:54 +10:00
sysdep Use variables for source directory in a couple more places. 2008-05-18 19:54:27 +02:00
unixuid Use variables for source directory in a couple more places. 2008-05-18 19:54:27 +02:00
config.mk Use variables for directories in ntvfs smb2 module. 2008-05-28 03:07:42 +02:00
ntvfs_base.c started new vfs_smb2 module 2008-05-15 10:57:22 +10:00
ntvfs_generic.c added support for returning the maximal access MXAC tag in SMB2 create 2008-05-29 19:16:26 +10:00
ntvfs_interface.c Install public header files again and include required prototypes. 2008-04-02 04:53:27 +02:00
ntvfs_util.c Install public header files again and include required prototypes. 2008-04-02 04:53:27 +02:00
ntvfs.h ntvfs: pass down the client capabilities into the ntvfs layer 2008-03-06 16:31:25 +01:00
README first public release of samba4 code 2003-08-13 01:53:07 +00:00

README 

This is the base of the new NTVFS subsystem for Samba. The model for
NTVFS backends is quite different than for the older style VFS
backends, in particular:

- the NTVFS backends receive windows style file names, although they
  are in the unix charset (usually UTF8). This means the backend is
  responsible for mapping windows filename conventions to unix
  filename conventions if necessary

- the NTVFS backends are responsible for changing effective UID before
  calling any OS local filesystem operations (if needed). The
  become_*() functions are provided to make this easier.

- the NTVFS backends are responsible for resolving DFS paths

- each NTVFS backend handles either disk, printer or IPC$ shares,
  rather than one backend handling all types

- the entry points of the NTVFS backends correspond closely with basic
  SMB operations, wheres the old VFS was modelled directly on the
  POSIX filesystem interface.

- the NTVFS backends are responsible for all semantic mappings, such
  as mapping dos file attributes, ACLs, file ownership and file times