sin/samba-mirror
1
0
Fork 0
mirror of https://github.com/samba-team/samba.git synced 2024-12-25 23:21:54 +03:00
Code
459a2301a5
samba-mirror/source4/ntvfs
History
Andrew Tridgell 3dc237eb28 r18342: a bit more explanation of these strange values 
(This used to be commit e191f84f24)
2007-10-10 14:18:13 -05:00
..
cifs r17930: Merge noinclude branch: 2007-10-10 14:16:54 -05:00
cifs_posix_cli r17930: Merge noinclude branch: 2007-10-10 14:16:54 -05:00
common r17930: Merge noinclude branch: 2007-10-10 14:16:54 -05:00
ipc r17930: Merge noinclude branch: 2007-10-10 14:16:54 -05:00
nbench r18301: I discovered how to load the warnings from a build farm build into 2007-10-10 14:18:04 -05:00
posix r18342: a bit more explanation of these strange values 2007-10-10 14:18:13 -05:00
print r17206: Add a modular API for share configuration. 2007-10-10 14:10:18 -05:00
simple r17930: Merge noinclude branch: 2007-10-10 14:16:54 -05:00
sysdep r17930: Merge noinclude branch: 2007-10-10 14:16:54 -05:00
unixuid r16980: - make struct smb_notify a union and add levels RAW_NOTIFY_NTTRANS,RAW_NOTIFY_SMB2 2007-10-10 14:10:06 -05:00
config.mk r18213: don't list LIBREPLACE depdendecies explicit and 2007-10-10 14:17:50 -05:00
ntvfs_base.c r17930: Merge noinclude branch: 2007-10-10 14:16:54 -05:00
ntvfs_generic.c r17088: add ntvfs mapping function for notify 2007-10-10 14:10:12 -05:00
ntvfs_interface.c r16980: - make struct smb_notify a union and add levels RAW_NOTIFY_NTTRANS,RAW_NOTIFY_SMB2 2007-10-10 14:10:06 -05:00
ntvfs_util.c r17930: Merge noinclude branch: 2007-10-10 14:16:54 -05:00
ntvfs.h r17206: Add a modular API for share configuration. 2007-10-10 14:10:18 -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