1
0
mirror of https://github.com/samba-team/samba.git synced 2024-12-25 23:21:54 +03:00
samba-mirror/source4/ntvfs
2008-04-17 13:05:25 +02:00
..
cifs Remove event context tracking from the credentials struct. 2008-04-17 01:03:18 +02:00
cifs_posix_cli r25554: Convert last instances of BOOL, True and False to the standard types. 2007-10-10 15:07:55 -05:00
common Explicitly require event context to be specified. 2008-04-17 01:19:53 +02:00
ipc Specify event_context to ldb_wrap_connect explicitly. 2008-04-17 12:23:44 +02:00
nbench r25554: Convert last instances of BOOL, True and False to the standard types. 2007-10-10 15:07:55 -05:00
posix Merge branch 'v4-0-test' of ssh://git.samba.org/data/git/samba into v4-0-test 2008-04-17 13:05:25 +02:00
print r26443: Remove global_loadparm instances. 2007-12-21 05:50:11 +01:00
simple r25554: Convert last instances of BOOL, True and False to the standard types. 2007-10-10 15:07:55 -05:00
sysdep Require explicit event context rather than looking if it is not specified. 2008-04-17 01:22:39 +02:00
unixuid Use _OBJ_FILES variables in a couple more places. 2008-04-14 17:22:58 +02:00
config.mk Use _OBJ_FILES variables in a couple more places. 2008-04-14 17:22:58 +02:00
ntvfs_base.c Remove prototypes from build.h in preparation of removing build.h 2008-04-14 11:54:50 +02:00
ntvfs_generic.c ntvfs_generic: map SMB2 oplock levels to the generic ones 2008-04-17 03:54:26 +02:00
ntvfs_interface.c Install public header files again and include required prototypes. 2008-04-02 04:53:27 +02:00
ntvfs_util.c Install public header files again and include required prototypes. 2008-04-02 04:53:27 +02:00
ntvfs.h ntvfs: pass down the client capabilities into the ntvfs layer 2008-03-06 16:31:25 +01:00
README first public release of samba4 code 2003-08-13 01:53:07 +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