sin/samba-mirror
1
0
Fork 0
mirror of https://github.com/samba-team/samba.git synced 2024-12-23 17:34:34 +03:00
Code
54eff1435d
samba-mirror/source4/ntvfs
History
Andrew Tridgell 54eff1435d r4942: converted the cifs backend to not use event_context_merge(). Instead, 
is supplies the server event context during the connect.
(This used to be commit 133e67bb1f)
2007-10-10 13:09:08 -05:00
..
cifs r4942: converted the cifs backend to not use event_context_merge(). Instead, 2007-10-10 13:09:08 -05:00
common r4547: - added talloc_new(ctx) macro that is a neater form of the common talloc(ctx, 0) call. 2007-10-10 13:08:20 -05:00
ipc r4690: - add support for async rpc server replies 2007-10-10 13:08:43 -05:00
nbench r3737: - Get rid of the register_subsystem() and register_backend() functions. 2007-10-10 13:05:48 -05:00
posix r4887: removed a bogus cast 2007-10-10 13:09:03 -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 r4547: - added talloc_new(ctx) macro that is a neater form of the common talloc(ctx, 0) call. 2007-10-10 13:08:20 -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 r4608: - use better error codes 2007-10-10 13:08:33 -05:00
ntvfs_generic.c r4549: got rid of a lot more uses of plain talloc(), instead using 2007-10-10 13:08:25 -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