sin/samba-mirror
1
0
Fork 0
mirror of https://github.com/samba-team/samba.git synced 2025-01-05 09:18:06 +03:00
Code
5052c65fd3
samba-mirror/source4/ntvfs
History
Andrew Tridgell 0becf4d683 thanks to ntfsd and some google searches I worked out what the unknown 
fields in level 261 and level 262 of directory search are, plus the
names of the levels

the unknown fields are a 64bit unique file id, and match the 64 bit
number from the internal_information qfileinfo level
(This used to be commit b69f54eb02)
2003-09-02 04:37:33 +00:00
..
cifs - added SMBntrename test suite 2003-08-13 16:04:21 +00:00
ipc - added SMBntrename test suite 2003-08-13 16:04:21 +00:00
posix first public release of samba4 code 2003-08-13 01:53:07 +00:00
print first public release of samba4 code 2003-08-13 01:53:07 +00:00
reference - added SMBntrename test suite 2003-08-13 16:04:21 +00:00
simple thanks to ntfsd and some google searches I worked out what the unknown 2003-09-02 04:37:33 +00:00
ntvfs_base.c first public release of samba4 code 2003-08-13 01:53:07 +00:00
ntvfs_dfs.c first public release of samba4 code 2003-08-13 01:53:07 +00:00
ntvfs_generic.c thanks to ntfsd and some google searches I worked out what the unknown 2003-09-02 04:37:33 +00:00
ntvfs_util.c first public release of samba4 code 2003-08-13 01:53:07 +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