sin/samba-mirror
1
0
Fork 0
mirror of https://github.com/samba-team/samba.git synced 2024-12-28 07:21:54 +03:00
Code
4c5a4a7e02
samba-mirror/source4/ntvfs
History
Jelmer Vernooij 4c5a4a7e02 r11244: Relative path names in .mk files 
(This used to be commit 24e1030090)
2007-10-10 13:45:06 -05:00
..
cifs r10878: Reply to some comments by tridge and metze: 2007-10-10 13:39:39 -05:00
common r10810: This adds the hooks required to communicate the current user from the 2007-10-10 13:39:32 -05:00
ipc r9794: r11627@blu: tridge | 2005-08-30 22:55:27 +1000 2007-10-10 13:35:02 -05:00
nbench r5298: - got rid of pstring.h from includes.h. This at least makes it a bit 2007-10-10 13:09:38 -05:00
posix r11244: Relative path names in .mk files 2007-10-10 13:45:06 -05:00
print r5500: ntvfs modules that are the final backend needs to set the 2007-10-10 13:10:51 -05:00
simple r10456: More SCons fixes: 2007-10-10 13:38:48 -05:00
unixuid r11244: Relative path names in .mk files 2007-10-10 13:45:06 -05:00
config.mk r11244: Relative path names in .mk files 2007-10-10 13:45:06 -05:00
ntvfs_base.c r4608: - use better error codes 2007-10-10 13:08:33 -05:00
ntvfs_generic.c r10138: Fix the mapping table (as tested in smbtorture). EXEC_ACCESS 2007-10-10 13:38:02 -05:00
ntvfs_interface.c r9074: cope with a null ntvfs context in disconnect, so the destructor that 2007-10-10 13:31:14 -05:00
ntvfs_util.c r5037: got rid of all of the TALLOC_DEPRECATED stuff. My apologies for the 2007-10-10 13:09:15 -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

README 

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