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 275f32ae2d fill in unknown fields in SMB2 READ call
(This used to be commit 9b686c1380)
2008-04-14 11:31:17 +02:00
..
cifs Install public header files again and include required prototypes. 2008-04-02 04:53:27 +02: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 Install public header files again and include required prototypes. 2008-04-02 04:53:27 +02: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 ntvfs: Use wbclient for pvfs_acl and pvfs_acl_nfs4 2008-04-02 23:07:27 +02: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 ntvfs: Use wbclient in vsf_unixuid, not sidmap 2008-04-02 23:07:17 +02:00
config.mk Reduce the number of installed headers. 2008-04-02 13:41:10 +02:00
ntvfs_base.c Install public header files again and include required prototypes. 2008-04-02 04:53:27 +02:00
ntvfs_generic.c fill in unknown fields in SMB2 READ call 2008-04-14 11:31:17 +02:00
ntvfs_interface.c Install public header files again and include required prototypes. 2008-04-02 04:53:27 +02:00
ntvfs_util.c Install public header files again and include required prototypes. 2008-04-02 04:53:27 +02: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