1
0
mirror of https://github.com/samba-team/samba.git synced 2025-01-04 05:18:06 +03:00
samba-mirror/source4/ntvfs
2007-10-10 13:04:39 -05:00
..
cifs r3106: don't call a tree disconnect in the cifs backend, as during a smbd 2007-10-10 13:02:21 -05:00
common r3189: improved the share_conflict() logic (both in terms of readability and 2007-10-10 13:04:38 -05:00
ipc r3167: Add a member 'endpoint' to the dcerpc_binding struct to use instead of 2007-10-10 13:02:28 -05:00
nbench r3081: several updates to ntvfs and server side async request handling in 2007-10-10 13:01:57 -05:00
posix r3192: make sure we don't call pvfs_can_delete() until after we have confirmed that name->exists 2007-10-10 13:04:39 -05:00
print r2751: this is a new ntvfs design which tries to solve: 2007-10-10 12:59:30 -05:00
simple r3131: - make map_nt_error_from_unix() return NT_STATUS_UNSUCCESSFUL if errno is 0 2007-10-10 13:02:24 -05:00
unixuid r3185: Machines can login with krb5, so we need to allow them to map to a unix account. 2007-10-10 13:04:38 -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 r2751: this is a new ntvfs design which tries to solve: 2007-10-10 12:59:30 -05:00
ntvfs_dfs.c first public release of samba4 code 2003-08-13 01:53:07 +00:00
ntvfs_generic.c r3107: slight tweak to the openx -> ntcreatex mapping routine. This mapping 2007-10-10 13:02:22 -05:00
ntvfs_interface.c r3039: This solves the problem of async handlers in ntvfs backends not being 2007-10-10 13:00:01 -05:00
ntvfs_util.c first public release of samba4 code 2003-08-13 01:53:07 +00:00
ntvfs.h r3039: This solves the problem of async handlers in ntvfs backends not being 2007-10-10 13:00:01 -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