sin/samba-mirror
1
0
Fork 0
mirror of https://github.com/samba-team/samba.git synced 2024-12-24 21:34:56 +03:00
Code
2a689f463b
samba-mirror/source4/ntvfs
History
Andrew Tridgell c5e67b8555 r18581: also check for SEC_STD_DELETE, and split out the check into a separate 
static function
(This used to be commit 024ca6a91c)
2007-10-10 14:18:51 -05:00
..
cifs r17930: Merge noinclude branch: 2007-10-10 14:16:54 -05:00
cifs_posix_cli r18570: Fix up function names in cifs unix/posix extensions backend. Enable tiny quick test for torture for them 2007-10-10 14:18:48 -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 r18581: also check for SEC_STD_DELETE, and split out the check into a separate 2007-10-10 14:18:51 -05:00
print r17206: Add a modular API for share configuration. 2007-10-10 14:10:18 -05:00
simple r18568: this warning is not needed now that it is the job of the unixuid ntvfs 2007-10-10 14:18:48 -05:00
sysdep r18370: allow system inotify to be disabled 2007-10-10 14:18:20 -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 r18564: update for cifs unix/posix extensions stub version to build and beginnings of smbtorture test for it 2007-10-10 14:18:47 -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