1
0
mirror of https://github.com/samba-team/samba.git synced 2024-12-24 21:34:56 +03:00
samba-mirror/source4/ntvfs
Andrew Tridgell 8a94055deb r8753: fixed directory handling on systems that do not return . and .. as the
first two entries in a directory. This is what caused the FC3 system
shelob in the build farm to fail the RAW-UNLINK and RAW-SEARCH tests.
(This used to be commit f48abaaaca)
2007-10-10 13:30:02 -05:00
..
cifs r7931: fixed a bug in the cifs backend found with the new test code 2007-10-10 13:18:52 -05:00
common r7860: switch our ldb storage format to use a NDR encoded objectSid. This is 2007-10-10 13:18:44 -05:00
ipc r8036: revert rev 8023/8024 as they have a bugs. 2007-10-10 13:19:01 -05:00
nbench r5298: - got rid of pstring.h from includes.h. This at least makes it a bit 2007-10-10 13:09:38 -05:00
posix r8753: fixed directory handling on systems that do not return . and .. as the 2007-10-10 13:30:02 -05:00
print r5500: ntvfs modules that are the final backend needs to set the 2007-10-10 13:10:51 -05:00
simple r7850: Support mkdir() with just one parameter. Patch from 2007-10-10 13:18:42 -05:00
unixuid r5298: - got rid of pstring.h from includes.h. This at least makes it a bit 2007-10-10 13:09:38 -05:00
config.mk r3982: split out the sid -> uid/gid mapping routines into a ntvfs_sidmap 2007-10-10 13:06:11 -05:00
ntvfs_base.c r4608: - use better error codes 2007-10-10 13:08:33 -05:00
ntvfs_generic.c r8107: now that we properly separate DOS and NT status codes all the places 2007-10-10 13:19:08 -05:00
ntvfs_interface.c r3528: added support for the SMBntcancel() operation, which cancels any 2007-10-10 13:05:28 -05:00
ntvfs_util.c r5037: got rid of all of the TALLOC_DEPRECATED stuff. My apologies for the 2007-10-10 13:09:15 -05:00
ntvfs.h r3528: added support for the SMBntcancel() operation, which cancels any 2007-10-10 13:05:28 -05:00
README first public release of samba4 code 2003-08-13 01:53:07 +00:00

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