sin/samba-mirror
1
0
Fork 0
mirror of https://github.com/samba-team/samba.git synced 2025-01-11 05:18:09 +03:00
Code
118f3edd27
samba-mirror/source4/ntvfs
History
Stefan Metzmacher 118f3edd27 r1291: rename struct smbsrv_context to smbsrv_connection 
because this is the connection state per transport layer (tcp)
connection

I also moved the substructs directly into smbsrv_connection,
because they don't need a struct name and we should allway pass the complete
smbsrv_connection struct into functions

metze
(This used to be commit 60f823f201)
2007-10-10 12:56:49 -05:00
..
cifs r1291: rename struct smbsrv_context to smbsrv_connection 2007-10-10 12:56:49 -05:00
ipc r1291: rename struct smbsrv_context to smbsrv_connection 2007-10-10 12:56:49 -05:00
nbench r1280: rename struct request_context to smbsrv_request 2007-10-10 12:56:48 -05:00
posix r1286: rename struct tcon_context to smbsrv_tcon 2007-10-10 12:56:49 -05:00
print r1280: rename struct request_context to smbsrv_request 2007-10-10 12:56:48 -05:00
reference r1280: rename struct request_context to smbsrv_request 2007-10-10 12:56:48 -05:00
simple r1280: rename struct request_context to smbsrv_request 2007-10-10 12:56:48 -05:00
config.m4 r862: remove acl and sendfile stuff 2007-10-10 12:56:13 -05:00
config.mk r766: convert ntvfs/* to a config.mk file 2007-10-10 12:53:49 -05:00
ntvfs_base.c r1280: rename struct request_context to smbsrv_request 2007-10-10 12:56:48 -05:00
ntvfs_dfs.c first public release of samba4 code 2003-08-13 01:53:07 +00:00
ntvfs_generic.c r1291: rename struct smbsrv_context to smbsrv_connection 2007-10-10 12:56:49 -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