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
857e76ef6b
samba-mirror/source/ntvfs
History
Andrew Tridgell e7c53ad185 dcerpc server output now copes with the client blocking part way 
through a read. This happens to also avoid a memcpy on output for
dcerpc over tcp.
0001-01-01 00:00:00 +00:00
..
cifs remove a useless assignment 0001-01-01 00:00:00 +00:00
ipc dcerpc server output now copes with the client blocking part way 0001-01-01 00:00:00 +00:00
posix CVS: ---------------------------------------------------------------------- 0001-01-01 00:00:00 +00:00
print * patch based on work by Jim Myers to unify the ioctl handling to be 0001-01-01 00:00:00 +00:00
reference - added SMBntrename test suite 0001-01-01 00:00:00 +00:00
simple the next step in the dcerpc server code. Added the link between the 0001-01-01 00:00:00 +00:00
config.m4 Initial step at cleaning and splitting up configure.in. 0001-01-01 00:00:00 +00:00
ntvfs_base.c This patch adds a better dcerpc server infastructure. 0001-01-01 00:00:00 +00:00
ntvfs_dfs.c first public release of samba4 code 0001-01-01 00:00:00 +00:00
ntvfs_generic.c merged more updates from Jim Myers 0001-01-01 00:00:00 +00:00
ntvfs_util.c first public release of samba4 code 0001-01-01 00:00:00 +00:00
README first public release of samba4 code 0001-01-01 00:00:00 +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