sin/samba-mirror
1
0
Fork 0
mirror of https://github.com/samba-team/samba.git synced 2025-01-12 09:18:10 +03:00
Code
a949db7c6d
samba-mirror/source4/ntvfs
History
Stefan Metzmacher a949db7c6d r14486: remove the need of a stream_connection on a dcesrv_connection, 
and let the transport set callbacks for getting the own and peer
socket_address

metze
(This used to be commit 56fac3ddbb)
2007-10-10 13:57:32 -05:00
..
cifs r14456: don't access the smbsrv_tcon inside the ntvfs modules 2007-10-10 13:57:26 -05:00
common r14464: Don't include ndr_BASENAME.h files unless strictly required, instead 2007-10-10 13:57:27 -05:00
ipc r14486: remove the need of a stream_connection on a dcesrv_connection, 2007-10-10 13:57:32 -05:00
nbench r14256: - rename smb_file -> smb_handle 2007-10-10 13:57:06 -05:00
posix r14464: Don't include ndr_BASENAME.h files unless strictly required, instead 2007-10-10 13:57:27 -05:00
print r14456: don't access the smbsrv_tcon inside the ntvfs modules 2007-10-10 13:57:26 -05:00
simple r14456: don't access the smbsrv_tcon inside the ntvfs modules 2007-10-10 13:57:26 -05:00
unixuid r14173: change smb interface structures to always use 2007-10-10 13:56:57 -05:00
config.mk r14327: Replace MAJOR_VERSION/MINOR_VERSION/RELEASE_VERSION with two parameters: 2007-10-10 13:57:12 -05:00
ntvfs_base.c r14456: don't access the smbsrv_tcon inside the ntvfs modules 2007-10-10 13:57:26 -05:00
ntvfs_generic.c r14256: - rename smb_file -> smb_handle 2007-10-10 13:57:06 -05:00
ntvfs_interface.c r14456: don't access the smbsrv_tcon inside the ntvfs modules 2007-10-10 13:57:26 -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 r14456: don't access the smbsrv_tcon inside the ntvfs modules 2007-10-10 13:57:26 -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