sin/samba-mirror
1
0
Fork 0
mirror of https://github.com/samba-team/samba.git synced 2024-12-27 03:21:53 +03:00
Code
1190f385f7
samba-mirror/source4/ntvfs
History
Andrew Bartlett 00b1267468 build: Add missing dep on tdb_compat
2012-09-24 03:51:07 +02:00
..
cifs s4:ntvfs: add '_fn' suffix to all ntvfs_ops function pointers 2012-06-13 11:03:15 +02:00
cifs_posix_cli s4:ntvfs: add '_fn' suffix to all ntvfs_ops function pointers 2012-06-13 11:03:15 +02:00
common UTIL_TDB: lowercase name. 2012-05-03 20:18:22 +02:00
ipc s4:ntvfs: add '_fn' suffix to all ntvfs_ops function pointers 2012-06-13 11:03:15 +02:00
nbench s4:ntvfs: add '_fn' suffix to all ntvfs_ops function pointers 2012-06-13 11:03:15 +02:00
posix build: Add missing dep on tdb_compat 2012-09-24 03:51:07 +02:00
print s4:ntvfs: add '_fn' suffix to all ntvfs_ops function pointers 2012-06-13 11:03:15 +02:00
simple s4:ntvfs: add '_fn' suffix to all ntvfs_ops function pointers 2012-06-13 11:03:15 +02:00
smb2 s4:ntvfs: add '_fn' suffix to all ntvfs_ops function pointers 2012-06-13 11:03:15 +02:00
sysdep rely on sys/inotify.h for inotify 2012-04-13 21:15:00 +02:00
unixuid Replace all uses of setXX[ug]id() and setgroups with samba_setXX[ug]id() calls. 2012-06-28 17:15:16 -07:00
ntvfs_base.c Revert making public of the samba-module library. 2011-12-03 08:36:30 +01:00
ntvfs_generic.c s4:ntvfs: add '_fn' suffix to all ntvfs_ops function pointers 2012-06-13 11:03:15 +02:00
ntvfs_interface.c s4:ntvfs: add '_fn' suffix to all ntvfs_ops function pointers 2012-06-13 11:03:15 +02:00
ntvfs_util.c
ntvfs.h s4:ntvfs: add '_fn' suffix to all ntvfs_ops function pointers 2012-06-13 11:03:15 +02:00
README
wscript_build Introduce system MIT krb5 build with --with-system-mitkrb5 option. 2012-05-23 17:51:50 +03: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