samba-mirror

mirror of https://github.com/samba-team/samba.git synced 2025-01-19 10:03:58 +03:00

History

Stefan Metzmacher f848aff0c2 if vfs_cifs want to modify the ntvfs_ops struct, it should

use a temporary copy of the struct!

metze
(This used to be commit 372522c64f2aea76b3fe136752d4da40e61d2bec)

2004-02-03 12:37:54 +00:00

cifs

if vfs_cifs want to modify the ntvfs_ops struct, it should

2004-02-03 12:37:54 +00:00

ipc

some DEBUG and comment fixes

2004-02-02 13:28:29 +00:00

posix

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

2003-11-25 03:15:26 +00:00

some DEBUG and comment fixes

2004-02-02 13:28:29 +00:00

reference

- added SMBntrename test suite

2003-08-13 16:04:21 +00:00

simple

some DEBUG and comment fixes

2004-02-02 13:28:29 +00:00

config.m4

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

2004-02-02 13:43:03 +00:00

ntvfs_base.c

- port AUTH and PASSDB subsystems to new

2004-02-03 11:10:56 +00:00

ntvfs_dfs.c

first public release of samba4 code

2003-08-13 01:53:07 +00:00

ntvfs_generic.c

merged more updates from Jim Myers

2003-12-04 11:01:58 +00:00

ntvfs_util.c

first public release of samba4 code

2003-08-13 01:53:07 +00:00

ntvfs.h

move include/ntvfs.h to ntvfs/ntvfs.h

2004-02-03 11:18:54 +00: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