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
42c6a2548a
samba-mirror/source4/ntvfs
History
Andrew Tridgell 42c6a2548a merged more updates from Jim Myers 
(This used to be commit 03bf306596)
2003-12-04 11:01:58 +00:00
..
cifs * patch based on work by Jim Myers to unify the ioctl handling to be 2003-12-04 02:03:06 +00:00
ipc * patch based on work by Jim Myers to unify the ioctl handling to be 2003-12-04 02:03:06 +00:00
posix CVS: ---------------------------------------------------------------------- 2003-11-25 03:15:26 +00:00
print * patch based on work by Jim Myers to unify the ioctl handling to be 2003-12-04 02:03:06 +00:00
reference - added SMBntrename test suite 2003-08-13 16:04:21 +00:00
simple * patch based on work by Jim Myers to unify the ioctl handling to be 2003-12-04 02:03:06 +00:00
config.m4 Initial step at cleaning and splitting up configure.in. 2003-12-02 11:10:56 +00:00
ntvfs_base.c make sure we can expand the critical versions structure without 2003-12-02 09:16:53 +00:00
ntvfs_dfs.c first public release of samba4 code 2003-08-13 01:53:07 +00:00
ntvfs_generic.c merged more updates from Jim Myers 2003-12-04 11:01:58 +00:00
ntvfs_util.c first public release of samba4 code 2003-08-13 01:53:07 +00: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