1
0
mirror of https://github.com/samba-team/samba.git synced 2024-12-23 17:34:34 +03:00
samba-mirror/source4/ntvfs
2007-12-21 05:50:00 +01:00
..
cifs r26430: require explicit specification of loadparm context. 2007-12-21 05:49:58 +01: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 r26431: Require ndr_push creators to specify a iconv_convenience context. 2007-12-21 05:50:00 +01:00
ipc r26431: Require ndr_push creators to specify a iconv_convenience context. 2007-12-21 05:50:00 +01:00
nbench r25554: Convert last instances of BOOL, True and False to the standard types. 2007-10-10 15:07:55 -05:00
posix r26429: Avoid use of global_smb_iconv_convenience. 2007-12-21 05:49:56 +01:00
print r26429: Avoid use of global_smb_iconv_convenience. 2007-12-21 05:49:56 +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 r25554: Convert last instances of BOOL, True and False to the standard types. 2007-10-10 15:07:55 -05:00
unixuid r26353: Remove use of global_loadparm. 2007-12-21 05:48:57 +01:00
config.mk r26136: Attempt to fix dependencies for auth. 2007-12-21 05:46:18 +01:00
ntvfs_base.c r26403: Make sure ntvfs is only initialized once. 2007-12-21 05:49:34 +01:00
ntvfs_generic.c r25554: Convert last instances of BOOL, True and False to the standard types. 2007-10-10 15:07:55 -05:00
ntvfs_interface.c r25554: Convert last instances of BOOL, True and False to the standard types. 2007-10-10 15:07:55 -05:00
ntvfs_util.c r25554: Convert last instances of BOOL, True and False to the standard types. 2007-10-10 15:07:55 -05:00
ntvfs.h r26353: Remove use of global_loadparm. 2007-12-21 05:48:57 +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