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
dd894d5626
samba-mirror/source4/ntvfs
History
Stefan Metzmacher dd894d5626 r15117: add more comments 
metze
(This used to be commit d76f3e2fb6)
2007-10-10 14:04:09 -05:00
..
cifs r14736: - the ntvfs subsystem should not know about smb_server.h 2007-10-10 13:59:17 -05:00
common r15048: started on the server side implementation of oplocks. The code is not 2007-10-10 14:04:03 -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 r15117: add more comments 2007-10-10 14:04:09 -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 r15029: fixed the detection of inotify 2007-10-10 14:04:02 -05:00
unixuid r14964: - move sidmap code from ntvfs_common to SAMDB 2007-10-10 14:00:47 -05:00
config.mk r14964: - move sidmap code from ntvfs_common to SAMDB 2007-10-10 14:00:47 -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