1
0
mirror of https://github.com/samba-team/samba.git synced 2024-12-22 13:34:15 +03:00
samba-mirror/source4/ntvfs
2011-03-21 22:35:17 +01:00
..
cifs source4/ntvfs: Fix prototypes for all functions. 2011-03-19 03:20:05 +01:00
cifs_posix_cli s4-loadparm: 2nd half of lp_ to lpcfg_ conversion 2010-07-16 18:24:27 +10:00
common source4/ntvfs: Fix prototypes for all functions. 2011-03-19 03:20:05 +01:00
ipc libcli/named_pipe_auth Change from 'info3' to auth_session_info_transport 2011-02-10 06:51:06 +01:00
nbench source4/ntvfs: Fix prototypes for all functions. 2011-03-19 03:20:05 +01:00
posix s4:ntvfs/posix: grant SEC_STD_DELETE if the parent grants SEC_DIR_DELETE_CHILD 2011-03-21 22:35:17 +01:00
print source4/ntvfs: Fix prototypes for all functions. 2011-03-19 03:20:05 +01:00
simple s4-loadparm: 2nd half of lp_ to lpcfg_ conversion 2010-07-16 18:24:27 +10:00
smb2 source4/ntvfs: Fix prototypes for all functions. 2011-03-19 03:20:05 +01:00
sysdep source4/ntvfs: Fix prototypes for all functions. 2011-03-19 03:20:05 +01:00
unixuid source4/ntvfs: Fix prototypes for all functions. 2011-03-19 03:20:05 +01:00
ntvfs_base.c s4-server: move the creation of the IPC$ share into ntvfs 2010-11-11 02:57:04 +00:00
ntvfs_generic.c s4-pvfs: move the private ntcreatex flags to private_flags 2010-03-05 16:12:05 +11: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 s4-idl: rename s4 server_id.idl to server_id4.idl 2011-02-18 18:41:00 +11:00
README
wscript_build credentials: Lowercase library name, 2010-11-07 01:48:44 +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