sin/samba-mirror
1
0
Fork 0
mirror of https://github.com/samba-team/samba.git synced 2024-12-23 17:34:34 +03:00
Code
71e2f7d260
samba-mirror/source4/ntvfs
History
Stefan Metzmacher 71e2f7d260 opendb_tdb: enable oplocks per default 
metze
(This used to be commit 225a9852ee)
2008-03-27 10:11:48 +01:00
..
cifs ntvfs/cifs: fix the fnum on RAW_RENAME_NTTRANS 2008-03-12 17:35:03 +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: enable oplocks per default 2008-03-27 10:11:48 +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: set h->have_opendb_entry directly after odb_open_file() 2008-03-15 12:36:20 +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 ntvfs/sysdep: implement linux kernel oplocks based F_SETLEASE 2008-03-12 17:35:06 +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

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