1
0
mirror of https://github.com/samba-team/samba.git synced 2024-12-23 17:34:34 +03:00
samba-mirror/source4/ntvfs
Volker Lendecke 02d4b74701 tdb_wrap: Only pull in samba-debug
Signed-off-by: Volker Lendecke <vl@samba.org>
Reviewed-by: Martin Schwenke <martin@meltin.net>
2014-09-18 20:36:11 +02:00
..
cifs s4: tidy up vfs cifs in regards to using share_string_option 2014-02-24 17:17:03 +01:00
cifs_posix_cli s4: pass down a memory context when performing share_string_option, to allow substitutions 2014-02-20 10:11:00 +13:00
common s4:ntvfs/common: explicitly check the status of imessaging_send() in notify_send() 2014-04-02 09:03:43 +02:00
ipc s4: pass down a memory context when performing share_string_option, to allow substitutions 2014-02-20 10:11:00 +13:00
nbench s4-ntvfs: Cast getpid() result to unsigned int for GNU/Solaris build 2013-03-15 10:38:36 -07:00
posix tdb_wrap: Only pull in samba-debug 2014-09-18 20:36:11 +02:00
print s4:ntvfs: add '_fn' suffix to all ntvfs_ops function pointers 2012-06-13 11:03:15 +02:00
simple s4: pass down a memory context when performing share_string_option, to allow substitutions 2014-02-20 10:11:00 +13:00
smb2 s4: tidy up vfs smb2 in regards to using share_string_option 2014-02-24 19:16:48 +01:00
sysdep s4:ntvfs/sysdep: add sys_notify_inotify_init() prototype to avoid a warning 2014-04-02 09:03:44 +02:00
unixuid s4:ntvfs/unixuid: explicitly use allow_warnings=True 2014-04-02 09:03:46 +02:00
ntvfs_base.c Revert making public of the samba-module library. 2011-12-03 08:36:30 +01:00
ntvfs_generic.c s4:ntvfs: add '_fn' suffix to all ntvfs_ops function pointers 2012-06-13 11:03:15 +02:00
ntvfs_interface.c s4:ntvfs: add '_fn' suffix to all ntvfs_ops function pointers 2012-06-13 11:03:15 +02:00
ntvfs_util.c
ntvfs.h s4:ntvfs: add '_fn' suffix to all ntvfs_ops function pointers 2012-06-13 11:03:15 +02:00
README
wscript_build Introduce system MIT krb5 build with --with-system-mitkrb5 option. 2012-05-23 17:51:50 +03:00

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