sin/samba-mirror
1
0
Fork 0
mirror of https://github.com/samba-team/samba.git synced 2025-01-04 05:18:06 +03:00
Code
da5cbd0886
samba-mirror/source4/ntvfs
History
Andrew Tridgell 2003ab2598 r2941: added pvfs_flush() implementation to the posix backend 
(This used to be commit dac00ef3b0)
2007-10-10 12:59:50 -05:00
..
cifs r2751: this is a new ntvfs design which tries to solve: 2007-10-10 12:59:30 -05:00
ipc r2751: this is a new ntvfs design which tries to solve: 2007-10-10 12:59:30 -05:00
nbench r2751: this is a new ntvfs design which tries to solve: 2007-10-10 12:59:30 -05:00
posix r2941: added pvfs_flush() implementation to the posix backend 2007-10-10 12:59:50 -05:00
print r2751: this is a new ntvfs design which tries to solve: 2007-10-10 12:59:30 -05:00
simple r2751: this is a new ntvfs design which tries to solve: 2007-10-10 12:59:30 -05:00
unixuid r2934: - changed the unixuid module to use the nt_user_token instead of the server supplied info structure. 2007-10-10 12:59:49 -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 r2751: this is a new ntvfs design which tries to solve: 2007-10-10 12:59:30 -05:00
ntvfs_interface.c r2751: this is a new ntvfs design which tries to solve: 2007-10-10 12:59:30 -05:00
ntvfs_util.c first public release of samba4 code 2003-08-13 01:53:07 +00:00
ntvfs.h r2751: this is a new ntvfs design which tries to solve: 2007-10-10 12:59:30 -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