sin/samba-mirror
1
0
Fork 0
mirror of https://github.com/samba-team/samba.git synced 2024-12-28 07:21:54 +03:00
Code
63aaa6b782
samba-mirror/source4/ntvfs
History
Simo Sorce 9c66f601f1 r17206: Add a modular API for share configuration. 
Commit the classic backwards compatible module which is the default one
(This used to be commit a89cc346b9)
2007-10-10 14:10:18 -05:00
..
cifs r17206: Add a modular API for share configuration. 2007-10-10 14:10:18 -05:00
cifs_posix_cli r17206: Add a modular API for share configuration. 2007-10-10 14:10:18 -05:00
common r17206: Add a modular API for share configuration. 2007-10-10 14:10:18 -05:00
ipc r17206: Add a modular API for share configuration. 2007-10-10 14:10:18 -05:00
nbench r16834: split the level's of smb_search_first/smb_search_next and the levels 2007-10-10 14:09:49 -05:00
posix r17206: Add a modular API for share configuration. 2007-10-10 14:10:18 -05:00
print r17206: Add a modular API for share configuration. 2007-10-10 14:10:18 -05:00
simple r17206: Add a modular API for share configuration. 2007-10-10 14:10:18 -05:00
sysdep r17206: Add a modular API for share configuration. 2007-10-10 14:10:18 -05:00
unixuid r16980: - make struct smb_notify a union and add levels RAW_NOTIFY_NTTRANS,RAW_NOTIFY_SMB2 2007-10-10 14:10:06 -05:00
config.mk r15716: disable the cifs_posix ntvfs backend as it will not be updated 2007-10-10 14:08:08 -05:00
ntvfs_base.c r17206: Add a modular API for share configuration. 2007-10-10 14:10:18 -05:00
ntvfs_generic.c r17088: add ntvfs mapping function for notify 2007-10-10 14:10:12 -05:00
ntvfs_interface.c r16980: - make struct smb_notify a union and add levels RAW_NOTIFY_NTTRANS,RAW_NOTIFY_SMB2 2007-10-10 14:10:06 -05:00
ntvfs_util.c r16950: remove the smb mid from the ntvfs layer and keep a list of pending 2007-10-10 14:10:02 -05:00
ntvfs.h r17206: Add a modular API for share configuration. 2007-10-10 14:10:18 -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