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
86497db611
samba-mirror/source4/ntvfs
History
Stefan Metzmacher 86497db611 r14157: - pass a struct ntvfs_request to the ntvfs layer 
(for now we just do #define ntvfs_request smbsrv_request,
   but it's the first step...)
- rename ntvfs_openfile() -> ntvfs_open()
- fix the talloc hierachie in some places in the ntvfs_map_*() code

metze
(This used to be commit ed9ed1f48f)
2007-10-10 13:56:55 -05:00
..
cifs r14157: - pass a struct ntvfs_request to the ntvfs layer 2007-10-10 13:56:55 -05:00
common r13924: Split more prototypes out of include/proto.h + initial work on header 2007-10-10 13:52:24 -05:00
ipc r14157: - pass a struct ntvfs_request to the ntvfs layer 2007-10-10 13:56:55 -05:00
nbench r14157: - pass a struct ntvfs_request to the ntvfs layer 2007-10-10 13:56:55 -05:00
posix r14157: - pass a struct ntvfs_request to the ntvfs layer 2007-10-10 13:56:55 -05:00
print r14157: - pass a struct ntvfs_request to the ntvfs layer 2007-10-10 13:56:55 -05:00
simple r14157: - pass a struct ntvfs_request to the ntvfs layer 2007-10-10 13:56:55 -05:00
unixuid r14157: - pass a struct ntvfs_request to the ntvfs layer 2007-10-10 13:56:55 -05:00
config.mk r13960: Generate makefile rules for installing/removing shared modules. 2007-10-10 13:52:32 -05:00
ntvfs_base.c r14157: - pass a struct ntvfs_request to the ntvfs layer 2007-10-10 13:56:55 -05:00
ntvfs_generic.c r14157: - pass a struct ntvfs_request to the ntvfs layer 2007-10-10 13:56:55 -05:00
ntvfs_interface.c r14157: - pass a struct ntvfs_request to the ntvfs layer 2007-10-10 13:56:55 -05:00
ntvfs_util.c r14157: - pass a struct ntvfs_request to the ntvfs layer 2007-10-10 13:56:55 -05:00
ntvfs.h r14157: - pass a struct ntvfs_request to the ntvfs layer 2007-10-10 13:56:55 -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