1
0
mirror of https://github.com/samba-team/samba.git synced 2025-01-11 05:18:09 +03:00
samba-mirror/source4/ntvfs
David Disseldorp 281fc93c6b libcli: move ioctl function field defs to smb_constants
Currently there are a lot of duplicate ioctl function field definitions
between source3 and source4.

Signed-off-by: Stefan Metzmacher <metze@samba.org>
2011-10-19 15:44:29 +02:00
..
cifs s4:ntvfs/cifs: add option to use S4U2Proxy 2011-06-22 18:17:43 +02:00
cifs_posix_cli libcli/util Rename common map_nt_error_from_unix to avoid duplicate symbol 2011-06-20 08:12:03 +02:00
common s4:ntvfs common - remove two outdated function prototypes 2011-09-20 20:16:29 +02:00
ipc libcli: move ioctl function field defs to smb_constants 2011-10-19 15:44:29 +02:00
nbench nterr: Add mem_ctx for return string from get_nt_error_c_code() 2011-05-06 07:51:24 +02:00
posix libcli: move ioctl function field defs to smb_constants 2011-10-19 15:44:29 +02:00
print libcli: move ioctl function field defs to smb_constants 2011-10-19 15:44:29 +02:00
simple libcli/util Rename common map_nt_error_from_unix to avoid duplicate symbol 2011-06-20 08:12:03 +02:00
smb2 s4:ntvfs/smb2/vfs_smb2.c - remove unused variable 2011-06-11 16:26:13 +02:00
sysdep lib/util: consolidate module loading into common code 2011-10-06 07:18:07 +02:00
unixuid s4-auth Move conversion of security_token to unix_token to auth 2011-07-29 04:24:07 +02:00
ntvfs_base.c lib/util: consolidate module loading into common code 2011-10-06 07:18:07 +02:00
ntvfs_generic.c s4:ntvfs subsystems - rework it using concrete enum values 2011-06-16 09:05:31 +02:00
ntvfs_interface.c s4:ntvfs: remove socket_address based functions 2010-04-27 13:02:26 +02:00
ntvfs_util.c Fix include paths to new location of libutil. 2008-10-11 21:31:42 +02:00
ntvfs.h librpc/idr Use the Samba3 notify.idl in common. 2011-06-09 12:40:08 +02:00
README
wscript_build lib/param move source4 param code to the top level 2011-10-11 13:41:34 +11: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