1
0
mirror of https://github.com/samba-team/samba.git synced 2024-12-22 13:34:15 +03:00
samba-mirror/source4/ntvfs
2021-08-24 18:33:32 +00:00
..
cifs s4:ntvfs: Use cli_credentials_init_server() 2021-04-09 10:46:28 +00:00
common messaging4: Pass fds to messaging handlers 2019-09-18 20:10:24 +00:00
ipc smb.conf: Remove "share backend" option 2021-03-26 03:04:39 +00:00
posix ntvfs: add missing COM/LPT ports that are also reserved names 2021-08-24 18:33:32 +00:00
simple lib: modules: Change XXX_init interface from XXX_init(void) to XXX_init(TALLOC_CTX *) 2017-04-22 01:17:00 +02:00
sysdep s3/wscript: only check for F_SETLEASE being available at compile time 2020-12-07 19:02:33 +00:00
unixuid s4:auth/unix_token: remove unused tevent_context from security_token_to_unix_token() 2017-06-26 08:47:15 +02:00
ntvfs_base.c lib: modules: Change XXX_init interface from XXX_init(void) to XXX_init(TALLOC_CTX *) 2017-04-22 01:17:00 +02:00
ntvfs_generic.c smb: rename NTCREATEX_OPTIONS_PRIVATE_DENY_FCB to NTCREATEX_FLAG_DENY_FCB 2020-10-23 17:44:33 +00:00
ntvfs_interface.c ntvfs: Remove now unused functions 2019-06-26 04:12:32 +00:00
ntvfs_util.c ntvfs: Remove now unused functions 2019-06-26 04:12:32 +00:00
ntvfs.h s4:ntvfs: add '_fn' suffix to all ntvfs_ops function pointers 2012-06-13 11:03:15 +02:00
README
wscript_build s4-ntvfs: Remove untested ntvfs_cifsposix backend 2019-05-22 07:15:43 +00: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