1
0
mirror of https://github.com/samba-team/samba.git synced 2025-01-12 09:18:10 +03:00
samba-mirror/source4/ntvfs
2007-10-10 13:05:31 -05:00
..
cifs r3528: added support for the SMBntcancel() operation, which cancels any 2007-10-10 13:05:28 -05:00
common r3539: much nicer async open delay code. 2007-10-10 13:05:29 -05:00
ipc r3528: added support for the SMBntcancel() operation, which cancels any 2007-10-10 13:05:28 -05:00
nbench r3528: added support for the SMBntcancel() operation, which cancels any 2007-10-10 13:05:28 -05:00
posix r3550: fixed initial attribute on file create (inlusion of FILE_ATTRIBUTE_ARCHIVE) 2007-10-10 13:05:31 -05:00
print r3466: split out request.h, signing.h, and smb_server.h 2007-10-10 13:05:17 -05:00
simple r3528: added support for the SMBntcancel() operation, which cancels any 2007-10-10 13:05:28 -05:00
unixuid r3528: added support for the SMBntcancel() operation, which cancels any 2007-10-10 13:05:28 -05:00
config.m4 r2794: a very simple version of the unixuid NTVFS pass-thru module. In 2007-10-10 12:59:34 -05:00
config.mk r2751: this is a new ntvfs design which tries to solve: 2007-10-10 12:59:30 -05:00
ntvfs_base.c r3466: split out request.h, signing.h, and smb_server.h 2007-10-10 13:05:17 -05:00
ntvfs_dfs.c r3441: some include file cleanups and general housekeeping 2007-10-10 13:05:11 -05:00
ntvfs_generic.c r3531: add support for RAW_OPEN_MKNEW, RAW_OPEN_CREATE and RAW_OPEN_CTEMP in pvfs 2007-10-10 13:05:29 -05:00
ntvfs_interface.c r3528: added support for the SMBntcancel() operation, which cancels any 2007-10-10 13:05:28 -05:00
ntvfs_util.c r3466: split out request.h, signing.h, and smb_server.h 2007-10-10 13:05:17 -05:00
ntvfs.h r3528: added support for the SMBntcancel() operation, which cancels any 2007-10-10 13:05:28 -05: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