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
4f2058175e
samba-mirror/source4/ntvfs
History
Andrew Tridgell 4f2058175e r2591: fixed two errors in simple backend found with valgrind 
(This used to be commit 1730882b9d)
2007-10-10 12:59:10 -05:00
..
cifs r2561: completely redid the ntvfs module chaining code, You can now do something like: 2007-10-10 12:59:06 -05:00
ipc r2580: fixed an uninitialised byte found by valgrind 2007-10-10 12:59:07 -05:00
nbench r2586: updated the nbench example in the README to reflect the new chaining syntax 2007-10-10 12:59:07 -05:00
posix r2573: - added a configure test for nanosecond time resolution in struct stat 2007-10-10 12:59:06 -05:00
print r2552: Character set conversion and string handling updates. 2007-10-10 12:59:05 -05:00
simple r2591: fixed two errors in simple backend found with valgrind 2007-10-10 12:59:10 -05:00
config.m4 r2573: - added a configure test for nanosecond time resolution in struct stat 2007-10-10 12:59:06 -05:00
config.mk r2573: - added a configure test for nanosecond time resolution in struct stat 2007-10-10 12:59:06 -05:00
ntvfs_base.c r2561: completely redid the ntvfs module chaining code, You can now do something like: 2007-10-10 12:59:06 -05:00
ntvfs_dfs.c first public release of samba4 code 2003-08-13 01:53:07 +00:00
ntvfs_generic.c r2561: completely redid the ntvfs module chaining code, You can now do something like: 2007-10-10 12:59:06 -05:00
ntvfs_util.c first public release of samba4 code 2003-08-13 01:53:07 +00:00
ntvfs.h r2561: completely redid the ntvfs module chaining code, You can now do something like: 2007-10-10 12:59:06 -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