1
0
mirror of https://github.com/samba-team/samba.git synced 2024-12-22 13:34:15 +03:00
samba-mirror/source4/ntvfs
Andrew Tridgell 7c542406b1 s4-pipes: convert pipe names to lowercase and validate
clients may provide arbitrary names, but we only want lowercase alnum
names
2009-09-18 22:58:03 -07:00
..
cifs s4: fixed some shadowed variable warnings 2009-09-08 11:52:44 +10:00
cifs_posix_cli s4: fixed some shadowed variable warnings 2009-09-08 11:52:44 +10:00
common s4:ntvfs/common: s/private/private_data 2009-02-02 13:08:32 +01:00
ipc s4-pipes: convert pipe names to lowercase and validate 2009-09-18 22:58:03 -07:00
nbench Have ntvfs_connect() accept union smb_tcon *tcon instead of char* sharename 2009-05-20 13:32:27 +02:00
posix no need to shout about getting an oplock 2009-08-12 15:20:02 +10:00
print Have ntvfs_connect() accept union smb_tcon *tcon instead of char* sharename 2009-05-20 13:32:27 +02:00
simple Have ntvfs_connect() accept union smb_tcon *tcon instead of char* sharename 2009-05-20 13:32:27 +02:00
smb2 s4: fixed some shadowed variable warnings 2009-09-08 11:52:44 +10:00
sysdep s4:sysdep/inotify: use tevent_fd_set_auto_close() 2009-01-03 19:58:52 +01:00
unixuid added a uid_wrapper library 2009-08-05 10:51:00 +10:00
config.mk s4:ntvfs_ipc: add real named pipe support 2009-09-18 20:34:43 +02:00
ntvfs_base.c s4:lib/tevent: rename structs 2008-12-29 20:46:40 +01:00
ntvfs_generic.c Upgrade ntvfs_map_*info to ntvfs_map_async_setup/ntvfs_map_async_finish 2009-06-26 14:39:44 +02:00
ntvfs_interface.c Have ntvfs_connect() accept union smb_tcon *tcon instead of char* sharename 2009-05-20 13:32:27 +02:00
ntvfs_util.c Fix include paths to new location of libutil. 2008-10-11 21:31:42 +02:00
ntvfs.h Have ntvfs_connect() accept union smb_tcon *tcon instead of char* sharename 2009-05-20 13:32:27 +02: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