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-10-10 14:07:00 -05:00
..
cifs r15522: allow cifs:map_trans2 per share 2007-10-10 14:05:46 -05:00
cifs_posix_cli r15387: Fix installation of dcerpc headers, remove more instances of uint_t 2007-10-10 14:05:31 -05:00
common r15613: the snum doesn't identify the tcon, but the brl_context pointer does 2007-10-10 14:07:00 -05:00
ipc r15188: Restore svn rev. 15183, 15184 and 15185, which I inadvertantly clobbered 2007-10-10 14:04:14 -05:00
nbench r15261: Work around AIX defining open as open64 again 2007-10-10 14:04:27 -05:00
posix r15613: the snum doesn't identify the tcon, but the brl_context pointer does 2007-10-10 14:07:00 -05:00
print r15188: Restore svn rev. 15183, 15184 and 15185, which I inadvertantly clobbered 2007-10-10 14:04:14 -05:00
simple r15387: Fix installation of dcerpc headers, remove more instances of uint_t 2007-10-10 14:05:31 -05:00
sysdep r15207: Introduce PRIVATE_DEPENDENCIES and PUBLIC_DEPENDENCIES as replacement 2007-10-10 14:04:18 -05:00
unixuid r15572: Trim build/m4/rewrite.m4 a bit more, remove unused tests. 2007-10-10 14:05:58 -05:00
config.mk r15379: Fix shared library build's unresolved dependencies 2007-10-10 14:05:29 -05:00
ntvfs_base.c r15188: Restore svn rev. 15183, 15184 and 15185, which I inadvertantly clobbered 2007-10-10 14:04:14 -05:00
ntvfs_generic.c r15328: Move some functions around, remove dependencies. 2007-10-10 14:05:17 -05:00
ntvfs_interface.c r14736: - the ntvfs subsystem should not know about smb_server.h 2007-10-10 13:59:17 -05:00
ntvfs_util.c r14736: - the ntvfs subsystem should not know about smb_server.h 2007-10-10 13:59:17 -05:00
ntvfs.h r15387: Fix installation of dcerpc headers, remove more instances of uint_t 2007-10-10 14:05:31 -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