sin/samba-mirror
1
0
Fork 0
mirror of https://github.com/samba-team/samba.git synced 2024-12-24 21:34:56 +03:00
Code
b6a515aca4
samba-mirror/source4/ntvfs
History
Andrew Tridgell d5d0651bb9 r4244: add more calls to pvfs_xattr_unlink_hook() on file/dir create, to try to beat race 
conditions in the tdb xattr backend
(This used to be commit 3ac8401598)
2007-10-10 13:07:28 -05:00
..
cifs r4055: fixed more places to use type safe allocation macros 2007-10-10 13:06:20 -05:00
common r4054: got rid of Realloc(), replacing it with the type safe macro realloc_p() 2007-10-10 13:06:19 -05:00
ipc r4160: fixed the file_type in ntcreatex reply on a named pipe. NT4 requires this to be right. 2007-10-10 13:07:20 -05:00
nbench r3737: - Get rid of the register_subsystem() and register_backend() functions. 2007-10-10 13:05:48 -05:00
posix r4244: add more calls to pvfs_xattr_unlink_hook() on file/dir create, to try to beat race 2007-10-10 13:07:28 -05:00
print r3971: fix compiler warnings 2007-10-10 13:06:09 -05:00
simple r3737: - Get rid of the register_subsystem() and register_backend() functions. 2007-10-10 13:05:48 -05:00
unixuid r4147: converted from NT_USER_TOKEN to struct security_token 2007-10-10 13:06:31 -05:00
config.mk r3982: split out the sid -> uid/gid mapping routines into a ntvfs_sidmap 2007-10-10 13:06:11 -05:00
ntvfs_base.c r4052: fixed a bunch of code to use the type safe _p allocation macros 2007-10-10 13:06:18 -05:00
ntvfs_generic.c r4173: - new t2open code, that can cope with "create with EAs". Many thanks 2007-10-10 13:07:22 -05:00
ntvfs_interface.c r3528: added support for the SMBntcancel() operation, which cancels any 2007-10-10 13:05:28 -05:00
ntvfs_util.c r3466: split out request.h, signing.h, and smb_server.h 2007-10-10 13:05:17 -05:00
ntvfs.h r3528: added support for the SMBntcancel() operation, which cancels any 2007-10-10 13:05:28 -05: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