1
0
mirror of https://github.com/samba-team/samba.git synced 2024-12-23 17:34:34 +03:00
samba-mirror/source4/ntvfs
Stefan Metzmacher 75a412a469 pvfs_open: always call odb_can_open() before odb_open_file()
odb_open_file() will later change to not redo the logic of
odb_can_open().

metze
(This used to be commit b09a1461ac)
2008-03-07 19:15:27 +01:00
..
cifs vfs_cifs: disable level2 oplocks if the frontend client doesn't support them 2008-03-07 19:15:19 +01:00
cifs_posix_cli r25554: Convert last instances of BOOL, True and False to the standard types. 2007-10-10 15:07:55 -05:00
common opendb_tdb: pass down struct messaging_context directly to odb_oplock_break_send() 2008-03-07 19:15:21 +01:00
ipc updated SMB2 create operation to match WSPP. 2008-02-13 15:05:44 +11:00
nbench r25554: Convert last instances of BOOL, True and False to the standard types. 2007-10-10 15:07:55 -05:00
posix pvfs_open: always call odb_can_open() before odb_open_file() 2008-03-07 19:15:27 +01:00
print r26443: Remove global_loadparm instances. 2007-12-21 05:50:11 +01:00
simple r25554: Convert last instances of BOOL, True and False to the standard types. 2007-10-10 15:07:55 -05:00
sysdep Remove yet more uses of global_loadparm. 2008-02-21 17:17:37 +01:00
unixuid r26353: Remove use of global_loadparm. 2007-12-21 05:48:57 +01:00
config.mk Move public header accumulation out of the perl code. 2008-02-29 14:23:38 +01:00
ntvfs_base.c ntvfs: pass down the client capabilities into the ntvfs layer 2008-03-06 16:31:25 +01:00
ntvfs_generic.c missed another spot in the SMB2 create conversion 2008-02-13 17:36:41 +11:00
ntvfs_interface.c r25554: Convert last instances of BOOL, True and False to the standard types. 2007-10-10 15:07:55 -05:00
ntvfs_util.c ntvfs: pass down the client capabilities into the ntvfs layer 2008-03-06 16:31:25 +01:00
ntvfs.h ntvfs: pass down the client capabilities into the ntvfs layer 2008-03-06 16:31:25 +01: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