WHATS NEW IN Samba 2.2.0alpha1
              ==============================

This is the first alpha release of the new 2.2.0 codebase
for Samba. This version must not be run in production.

This code will almost certainly have some bugs and is
intended to help the Samba Team prepare an official 2.2.0
release.

The documentation in this alpha snapshot is not up to date,
there are many new parameters since 2.0.7. This will be
corrected in a later alpha release.

Several significant bugs have been fixed between alpha0
and alpha1, these include :

Fix for level II oplock bug.
Support for detecting version 2/3 printer drivers (from HP).
Samba profiling support (from SGI).
Winbind integration fixes.
Preliminary Win2K PDC support in compatibility mode for Win2K
clients (from JF).
VFS interface updates.
Failover finding of BDC's now works again.
lpq race condition fixes.
utmp fixes.
SWAT username detection fix.

The upcoming 2.2.0 Samba release will include the following
new features: 

Integration with the winbind daemon that provides a single
sign on facility for UNIX servers in Windows NT4/2000 networks
driven by a Windows NT4/2000 PDC.

Support for native Windows NT4/2000 printing RPCs.
This includes support for automatic printer driver
download. This functionality should be complete in
alpha1.

Rewritten internal locking semantics for more robustness.
This alpha supports full 64 bit locking semantics on all
(even 32 bit) platforms. SMB locks are mapped onto POSIX
locks (32 bit or 64 bit) as the underlying system allows.

Conversion of various internal flat data structures to use
database records for increased performance and
flexibility. 

Support for acting as a MS-DFS server 

Compile time option for enabling a VFS layer 

Support for server supported Access Control Lists (ACLs).
This support will require a specific pluggable backend to
be written for each filesystem ACL implementation to be
supported. The stable 2.2.0 release should contain
support for the following filesystems: 
    Solaris 2.6+ 
    HPUX
    SGI Irix 
    Linux Kernel 2.2 with German ACL patch 

Currently in this alpha snapshot (alpha1) this feature
is not enabled - the VFS layer has been modified to allow
it, but the code is still under development and should
be in a later alpha snapshot.

Other platforms will be supported as resources are
available to test and implement the encessary modules. If
you are interested in writing the support for a particular
ACL filesystem, please join the samba-technical mailing
list and coordinate your efforts. 

Support for collection of profile information. A shared 
memory area has been created which contains counters for
the number of calls to and the amount of time spent in
various system calls and smb transactions. See the file
profile.h for a complete listing of the information 
collected. Sample code for a samba pmda (collection agent
for Performance Co-Pilot) has been included in the pcp
directory. 

To enable the profile data collection code in samba, you 
must compile samba with profile support (run configure with 
the --with-profile option). On startup, collection of data
is disabled. To begin collecting data use the smbcontrol
program to turn on profiling (see the smbcontrol man page).
Profile information collection can be enabled for all smbd
processes or one or more selected processes. The profiling
data collected is the aggragate for all processes that have
profiling enabled.

With samba compiled for profile data collection, you may see
a very slight degradation in performance even with profiling
collection turned off. On initial tests with NetBench on an
SGI Origin 200 server, this degradation was not measureable 
with profile collection off compared to no profile collection
compiled into samba. 

With count profile collection enabled on all clients, the 
degradation was less than 2%. With full profile collection 
enabled on all clients, the degradation was about 8.5%. 


=====================================================================

If you think you have found a bug please email a report to :

        samba@samba.org

As always, all bugs are our responsibility.

Regards,

        The Samba Team.