sin/samba-mirror
1
0
Fork 0
mirror of https://github.com/samba-team/samba.git synced 2024-12-25 23:21:54 +03:00
Code
2df2d1b67f
samba-mirror/source4/ntvfs
History
Andrew Tridgell 2df2d1b67f r3461: another place where "open" was used as a structure element 
(This used to be commit 1087ea830e)
2007-10-10 13:05:16 -05:00
..
cifs r3461: another place where "open" was used as a structure element 2007-10-10 13:05:16 -05:00
common r3387: fixed pvfs to pass the NTDENY tests. The tricky bit was 2007-10-10 13:05:04 -05:00
ipc r3461: another place where "open" was used as a structure element 2007-10-10 13:05:16 -05:00
nbench r3461: another place where "open" was used as a structure element 2007-10-10 13:05:16 -05:00
posix r3461: another place where "open" was used as a structure element 2007-10-10 13:05:16 -05:00
print r2751: this is a new ntvfs design which tries to solve: 2007-10-10 12:59:30 -05:00
simple r3461: another place where "open" was used as a structure element 2007-10-10 13:05:16 -05:00
unixuid r3461: another place where "open" was used as a structure element 2007-10-10 13:05:16 -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 r3336: use a struct ntvfs_async_state to be able to do async chaning of ntvfs modules 2007-10-10 13:04:57 -05:00
ntvfs_dfs.c r3441: some include file cleanups and general housekeeping 2007-10-10 13:05:11 -05:00
ntvfs_generic.c r3461: another place where "open" was used as a structure element 2007-10-10 13:05:16 -05:00
ntvfs_interface.c r3461: another place where "open" was used as a structure element 2007-10-10 13:05:16 -05:00
ntvfs_util.c r3336: use a struct ntvfs_async_state to be able to do async chaning of ntvfs modules 2007-10-10 13:04:57 -05:00
ntvfs.h r3461: another place where "open" was used as a structure element 2007-10-10 13:05:16 -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