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
33188999b5
samba-mirror/source4/ntvfs
History
Andrew Tridgell b3115f5cdc s4-ntvfs: win7 does not check for the NONE smb2 lock flag on unlock
2009-11-27 19:42:10 +11:00
..
cifs s4: fixed some shadowed variable warnings 2009-09-08 11:52:44 +10:00
cifs_posix_cli s4: fixed some shadowed variable warnings 2009-09-08 11:52:44 +10:00
common s4-ntvfs: move valid lock range test from smb2 layer to generic code 2009-11-27 19:42:10 +11:00
ipc s4:vfs_ipc - fix "ipc_open" for NTTRANS create requests 2009-11-07 20:53:28 +01:00
nbench Have ntvfs_connect() accept union smb_tcon *tcon instead of char* sharename 2009-05-20 13:32:27 +02:00
posix s4-pvfs: fixed access check failure in SFILEINFO test 2009-11-27 16:05:06 +11:00
print Have ntvfs_connect() accept union smb_tcon *tcon instead of char* sharename 2009-05-20 13:32:27 +02:00
simple s4: fix various warnings (not "const" related ones) 2009-10-02 15:33:48 +02:00
smb2 s4: fixed some shadowed variable warnings 2009-09-08 11:52:44 +10:00
sysdep s4:sysdep/inotify: use tevent_fd_set_auto_close() 2009-01-03 19:58:52 +01:00
unixuid s4:ntvfs Don't attempt to follow NULL in unixuid_setup_security() 2009-10-02 12:44:58 +02:00
config.mk s4:ntvfs_ipc: add real named pipe support 2009-09-18 20:34:43 +02:00
ntvfs_base.c s4:lib/tevent: rename structs 2008-12-29 20:46:40 +01:00
ntvfs_generic.c s4-ntvfs: win7 does not check for the NONE smb2 lock flag on unlock 2009-11-27 19:42:10 +11:00
ntvfs_interface.c Have ntvfs_connect() accept union smb_tcon *tcon instead of char* sharename 2009-05-20 13:32:27 +02:00
ntvfs_util.c Fix include paths to new location of libutil. 2008-10-11 21:31:42 +02:00
ntvfs.h Have ntvfs_connect() accept union smb_tcon *tcon instead of char* sharename 2009-05-20 13:32:27 +02: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