samba-mirror

mirror of https://github.com/samba-team/samba.git synced 2025-11-12 04:23:49 +03:00

Files

Stefan Metzmacher 2e57ee884e - we now specify the object files in the subsystems config.m4 file

I plan to convert all objectfile group to use SMB_SUBSYSTEM
  later I'll add a SMB_BINARY() and SMB_LIBRARY(), then there will be no more need
  to touch Makefile.in, because all make rules will be autogenerated by configure

- convert the PROCESS_MODEL subsystem to this new scheme
  and move the pthread test to smbd/process_model.m4

- convert the CHARSET subsystem to this new scheme
  and move the iconv test to lib/iconv.m4

cifs

some DEBUG and comment fixes

ipc

some DEBUG and comment fixes

posix

CVS: ----------------------------------------------------------------------

some DEBUG and comment fixes

reference

- added SMBntrename test suite

simple

some DEBUG and comment fixes

config.m4

- we now specify the object files in the subsystems config.m4 file

ntvfs_base.c

some DEBUG and comment fixes

ntvfs_dfs.c

first public release of samba4 code

ntvfs_generic.c

merged more updates from Jim Myers

ntvfs_util.c

first public release of samba4 code

README

first public release of samba4 code

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