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
d3bcaf66a8
samba-mirror/source4/ntvfs
History
Jelmer Vernooij 10d88a02d7 r13652: Move some more stuff out off include/ 
(This used to be commit 26bf2a393b)
2007-10-10 13:52:04 -05:00
..
cifs r13129: fix the memory hierachie 2007-10-10 13:51:28 -05:00
common r13281: Use TALLOC_CTX * not a void *, and use tmp_ctx as the name for consistancy. 2007-10-10 13:51:42 -05:00
ipc r13652: Move some more stuff out off include/ 2007-10-10 13:52:04 -05:00
nbench r13129: fix the memory hierachie 2007-10-10 13:51:28 -05:00
posix r13099: allow shares that point to / 2007-10-10 13:51:24 -05:00
print r12528: Add seperate proto headers for ntvfs, tdr, smb_server and nbt_server. 2007-10-10 13:47:51 -05:00
simple r13129: fix the memory hierachie 2007-10-10 13:51:28 -05:00
unixuid r13129: fix the memory hierachie 2007-10-10 13:51:28 -05:00
config.mk r13210: Revert my named pipes patch until it passes not just 'make quicktest' but 2007-10-10 13:51:35 -05:00
ntvfs_base.c r13128: init the private_data to NULL 2007-10-10 13:51:28 -05:00
ntvfs_generic.c r13623: - make sure ntvfs_map_qfileinfo isn't used for async replies 2007-10-10 13:52:01 -05:00
ntvfs_interface.c r12838: make the ntvfs function public 2007-10-10 13:50:04 -05:00
ntvfs_util.c r12838: make the ntvfs function public 2007-10-10 13:50:04 -05:00
ntvfs.h r12528: Add seperate proto headers for ntvfs, tdr, smb_server and nbt_server. 2007-10-10 13:47:51 -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