sin/samba-mirror
1
0
Fork 0
mirror of https://github.com/samba-team/samba.git synced 2024-12-29 11:21:54 +03:00
Code
0e6773525f
samba-mirror/source4/ntvfs
History
Jelmer Vernooij 61ffa08f4c r24712: No longer expose the 'BOOL' data type in any interfaces. 
(This used to be commit 1ce32673d9)
2007-10-10 15:02:54 -05:00
..
cifs r23792: convert Samba4 to GPLv3 2007-10-10 14:59:12 -05:00
cifs_posix_cli r23792: convert Samba4 to GPLv3 2007-10-10 14:59:12 -05:00
common r24712: No longer expose the 'BOOL' data type in any interfaces. 2007-10-10 15:02:54 -05:00
ipc r24075: As suggested by metze, match the behaviour of ntvfs_posix, and remove 2007-10-10 15:01:22 -05:00
nbench r23792: convert Samba4 to GPLv3 2007-10-10 14:59:12 -05:00
posix r24712: No longer expose the 'BOOL' data type in any interfaces. 2007-10-10 15:02:54 -05:00
print r23792: convert Samba4 to GPLv3 2007-10-10 14:59:12 -05:00
simple r23792: convert Samba4 to GPLv3 2007-10-10 14:59:12 -05:00
sysdep r23792: convert Samba4 to GPLv3 2007-10-10 14:59:12 -05:00
unixuid r23792: convert Samba4 to GPLv3 2007-10-10 14:59:12 -05:00
config.mk r22406: this dependencies should also be private 2007-10-10 14:51:15 -05:00
ntvfs_base.c r23792: convert Samba4 to GPLv3 2007-10-10 14:59:12 -05:00
ntvfs_generic.c r23792: convert Samba4 to GPLv3 2007-10-10 14:59:12 -05:00
ntvfs_interface.c r23792: convert Samba4 to GPLv3 2007-10-10 14:59:12 -05:00
ntvfs_util.c r23792: convert Samba4 to GPLv3 2007-10-10 14:59:12 -05:00
ntvfs.h r24712: No longer expose the 'BOOL' data type in any interfaces. 2007-10-10 15:02:54 -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