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-12-18 15:03:37 -08:00
..
cifs vfs_cifs - Use ntvfs request transport close to close downstream session 2008-12-05 12:52:19 +01:00
cifs_posix_cli Make sure prototypes are always included, make some functions static and 2008-10-20 18:59:51 +02:00
common Fix include paths to new location of libutil. 2008-10-11 21:31:42 +02:00
ipc Make sure prototypes are always included, make some functions static and 2008-10-20 18:59:51 +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 s4: fix LIBEVENTS dependencies and use more forward declarations 2008-12-17 11:04:45 +01:00
print Remove iconv_convenience parameter from simple string push/pull 2008-10-24 03:40:09 +02:00
simple Make sure prototypes are always included, make some functions static and 2008-10-20 18:59:51 +02:00
smb2 Remove use of global_loadparm for SMB2 client connections. 2008-11-02 16:20:00 +01:00
sysdep s4: Fix include path to work with tevent 2008-12-18 15:03:37 -08:00
unixuid Remove unused include param/param.h. 2008-10-24 16:37:56 +02:00
config.mk Use variables for directories in ntvfs smb2 module. 2008-05-28 03:07:42 +02:00
ntvfs_base.c Fix include paths to new location of libutil. 2008-10-11 21:31:42 +02:00
ntvfs_generic.c s4:ntvfs_generic: pass RAW-OPEN again 2008-12-18 13:32:49 +01:00
ntvfs_interface.c Install public header files again and include required prototypes. 2008-04-02 04:53:27 +02:00
ntvfs_util.c Fix include paths to new location of libutil. 2008-10-11 21:31:42 +02:00
ntvfs.h Rename dom_sid.idl -> server_id.idl (since it no longer actually contains the dom_sid). No longer include it from security.idl. 2008-12-16 15:36:18 +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