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
887487851f
samba-mirror/source4/ntvfs
History
Stefan Metzmacher 2ccf5f67a5 s4:ntvfs/ipc: don't echo back the smb2 ioctl input_buffer 
metze
2012-04-27 08:31:37 +02:00
..
cifs s4:libcli/raw: implement on top of smbXcli_conn/req 2011-11-30 15:13:36 +01:00
cifs_posix_cli libcli/util Rename common map_nt_error_from_unix to avoid duplicate symbol 2011-06-20 08:12:03 +02:00
common tdb_wrap: Move to specific directory. 2012-03-10 23:13:01 +01:00
ipc s4:ntvfs/ipc: don't echo back the smb2 ioctl input_buffer 2012-04-27 08:31:37 +02:00
nbench nterr: Add mem_ctx for return string from get_nt_error_c_code() 2011-05-06 07:51:24 +02:00
posix s4-python: Add python wrapper for xattr_tdb format xattr storage 2012-04-18 12:05:00 +10:00
print libcli: move ioctl function field defs to smb_constants 2011-10-19 15:44:29 +02:00
simple libcli/util Rename common map_nt_error_from_unix to avoid duplicate symbol 2011-06-20 08:12:03 +02:00
smb2 s4:ntvfs/smb2/vfs_smb2.c - remove unused variable 2011-06-11 16:26:13 +02:00
sysdep rely on sys/inotify.h for inotify 2012-04-13 21:15:00 +02:00
unixuid s3-waf: add dependency on talloc or it won't build if talloc.h is not in the default include path 2012-02-10 23:27:29 +01:00
ntvfs_base.c Revert making public of the samba-module library. 2011-12-03 08:36:30 +01:00
ntvfs_generic.c s4:ntvfs subsystems - rework it using concrete enum values 2011-06-16 09:05:31 +02:00
ntvfs_interface.c s4:ntvfs: remove socket_address based functions 2010-04-27 13:02:26 +02:00
ntvfs_util.c Fix include paths to new location of libutil. 2008-10-11 21:31:42 +02:00
ntvfs.h librpc/idr Use the Samba3 notify.idl in common. 2011-06-09 12:40:08 +02:00
README
wscript_build Revert making public of the samba-module library. 2011-12-03 08:36:30 +01: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