sin/samba-mirror
1
0
Fork 0
mirror of https://github.com/samba-team/samba.git synced 2025-01-11 05:18:09 +03:00
Code
ee2fb760af
samba-mirror/source4/ntvfs
History
Andrew Tridgell ee2fb760af r14943: bring the inotify backend up to date with all the strange rename 
semantics
(This used to be commit 74c274ea07)
2007-10-10 14:00:20 -05:00
..
cifs r14736: - the ntvfs subsystem should not know about smb_server.h 2007-10-10 13:59:17 -05:00
common r14939: don't use a void pointer 2007-10-10 14:00:20 -05:00
ipc r14736: - the ntvfs subsystem should not know about smb_server.h 2007-10-10 13:59:17 -05:00
nbench r14736: - the ntvfs subsystem should not know about smb_server.h 2007-10-10 13:59:17 -05:00
posix r14941: a rename of a file (but not a directory) triggers 3 events. The first 2007-10-10 14:00:20 -05:00
print r14736: - the ntvfs subsystem should not know about smb_server.h 2007-10-10 13:59:17 -05:00
simple r14736: - the ntvfs subsystem should not know about smb_server.h 2007-10-10 13:59:17 -05:00
sysdep r14943: bring the inotify backend up to date with all the strange rename 2007-10-10 14:00:20 -05:00
unixuid r14838: fix the build. Looks like I still haven't quite got the hang of the 2007-10-10 13:59:25 -05:00
config.mk r14877: added support for the kernel inotify mechanism. This passes basic 2007-10-10 14:00:11 -05:00
ntvfs_base.c r14736: - the ntvfs subsystem should not know about smb_server.h 2007-10-10 13:59:17 -05:00
ntvfs_generic.c r14736: - the ntvfs subsystem should not know about smb_server.h 2007-10-10 13:59:17 -05:00
ntvfs_interface.c r14736: - the ntvfs subsystem should not know about smb_server.h 2007-10-10 13:59:17 -05:00
ntvfs_util.c r14736: - the ntvfs subsystem should not know about smb_server.h 2007-10-10 13:59:17 -05:00
ntvfs.h r14736: - the ntvfs subsystem should not know about smb_server.h 2007-10-10 13:59:17 -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