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
5c847a00a7
samba-mirror/source4/ntvfs
History
Volker Lendecke a80732cf00 r20983: Two no-mem error returns 
(This used to be commit 79a0cd3a1b)
2007-10-10 14:44:17 -05:00
..
cifs r19598: Ahead of a merge to current lorikeet-heimdal: 2007-10-10 14:25:00 -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 r20983: Two no-mem error returns 2007-10-10 14:44:17 -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 r20897: fix compiler warnings 2007-10-10 14:43:48 -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 r19676: Fix some more dependencies. 2007-10-10 14:25:29 -05:00
ntvfs_base.c r20646: first preparations for cluster enablement. This changes " 2007-10-10 14:37:23 -05:00
ntvfs_generic.c r18835: expand IO limits on SMB2. Samba4 now tops out at 16.7MB IOs. 2007-10-10 14:19:16 -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 r20898: make it work to include ntvfs/ntvfs.h multiple times 2007-10-10 14:43:48 -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