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
159ca62094
samba-mirror/source4/ntvfs
History
Andrew Tridgell e8788808da s4-pvfs_sys: build on systems without O_NOFOLLOW or O_DIRECTORY
2010-03-05 23:07:32 +11:00
..
cifs s4: fixed some shadowed variable warnings 2009-09-08 11:52:44 +10:00
cifs_posix_cli Change uint_t to unsigned int in source4 2010-02-02 07:18:18 +01:00
common s4-ntvfs: use TYPESAFE_QSORT() in notify code 2010-02-13 22:36:12 +11:00
ipc s4-krb5: propogate errors from a lot more kerberos functions 2010-02-26 13:59:16 +11: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_sys: build on systems without O_NOFOLLOW or O_DIRECTORY 2010-03-05 23:07:32 +11:00
print Have ntvfs_connect() accept union smb_tcon *tcon instead of char* sharename 2009-05-20 13:32:27 +02:00
simple Change uint_t to unsigned int in source4 2010-02-02 07:18:18 +01:00
smb2 Change uint_t to unsigned int in source4 2010-02-02 07:18:18 +01:00
sysdep
unixuid s4: Switch to S3-style id mapping data types. 2010-02-11 23:56:35 +01:00
config.mk s4:ntvfs_ipc: add real named pipe support 2009-09-18 20:34:43 +02:00
ntvfs_base.c
ntvfs_generic.c s4-pvfs: move the private ntcreatex flags to private_flags 2010-03-05 16:12:05 +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
ntvfs.h Have ntvfs_connect() accept union smb_tcon *tcon instead of char* sharename 2009-05-20 13:32:27 +02:00
README

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