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
4490c816a9
samba-mirror/source4/ntvfs
History
Andrew Tridgell 0e6799177c r2252: don't register the same name twice 
(This used to be commit fdb675bbad)
2007-10-10 12:58:35 -05:00
..
cifs r2249: got rid of some more mem_ctx elements in structures 2007-10-10 12:58:34 -05:00
ipc r2249: got rid of some more mem_ctx elements in structures 2007-10-10 12:58:34 -05:00
nbench r2249: got rid of some more mem_ctx elements in structures 2007-10-10 12:58:34 -05:00
posix r2252: don't register the same name twice 2007-10-10 12:58:35 -05:00
print r2249: got rid of some more mem_ctx elements in structures 2007-10-10 12:58:34 -05:00
reference r1983: a completely new implementation of talloc 2007-10-10 12:58:14 -05:00
simple r2249: got rid of some more mem_ctx elements in structures 2007-10-10 12:58:34 -05:00
config.m4 r862: remove acl and sendfile stuff 2007-10-10 12:56:13 -05:00
config.mk r1470: Get the smb_trans2 structure out of the rap_cli_call struct. 2007-10-10 12:57:33 -05:00
ntvfs_base.c r1355: Add const (I missed this when I changed the function prototype earlier) 2007-10-10 12:56:52 -05:00
ntvfs_dfs.c first public release of samba4 code 2003-08-13 01:53:07 +00:00
ntvfs_generic.c r2249: got rid of some more mem_ctx elements in structures 2007-10-10 12:58:34 -05:00
ntvfs_util.c first public release of samba4 code 2003-08-13 01:53:07 +00:00
ntvfs.h r1280: rename struct request_context to smbsrv_request 2007-10-10 12:56:48 -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