samba-mirror

mirror of https://github.com/samba-team/samba.git synced 2025-01-10 01:18:15 +03:00

History

Stefan Metzmacher 2986c5f08c r890: convert samba4 to use [u]int8_t instead of [u]int8 metze		2007-10-10 12:56:16 -05:00
..
cifs	r890: convert samba4 to use [u]int8_t instead of [u]int8	2007-10-10 12:56:16 -05:00
ipc	r889: convert samba4 to use [u]int16_t instead of [u]int16	2007-10-10 12:56:16 -05:00
nbench	make sure the tags in the NBENCH test match the tags in the generated	0001-01-01 00:00:00 +00:00
posix	r312: let ntvfs posix backend return NT_STATUS_ACCESS_DENIED in the connect hook	2007-10-10 12:51:20 -05:00
print	some DEBUG and comment fixes	0001-01-01 00:00:00 +00:00
reference	r889: convert samba4 to use [u]int16_t instead of [u]int16	2007-10-10 12:56:16 -05:00
simple	r889: convert samba4 to use [u]int16_t instead of [u]int16	2007-10-10 12:56:16 -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	- port AUTH and PASSDB subsystems to new	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	r873: converted samba4 to use real 64 bit integers instead of	2007-10-10 12:56:14 -05:00
ntvfs_util.c	first public release of samba4 code	0001-01-01 00:00:00 +00:00
ntvfs.h	move include/ntvfs.h to ntvfs/ntvfs.h	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