-What's new in Samba 4 alpha1
-============================
+Release Announcements
+=====================
-Samba 4 is the ambitious next version of the Samba suite that is being
-developed in parallel to the stable 3.0 series. The main emphasis in
-this branch is support for the Active Directory logon protocols used
-by Windows 2000 and above.
+This is the first preview release of Samba 4.4. This is *not*
+intended for production environments and is designed for testing
+purposes only. Please report any defects via the Samba bug reporting
+system at https://bugzilla.samba.org/.
-Samba 4 is currently not yet in a state where it is usable in
-production environments. Note the WARNINGS below, and the STATUS file,
-which aims to document what should and should not work.
+Samba 4.4 will be the next version of the Samba suite.
-Samba4 alpha1 is the culmination of 4.5 years of development under our
-belt since Tridge first proposed a new Virtual File System (VFS) layer
-for Samba3 (a project which eventually lead to our Active Directory
-efforts), and 1.5 years since we first released a Technology Preview,
-we wish to allow users, managers and developers to see how we have
-progressed, and to invite feedback and support.
-WARNINGS
-========
+UPGRADING
+=========
-Samba4 alpha1 is not a final Samba release. We recommend against
-upgrading any production servers from Samba 3 to Samba 4 at this
-stage. If you are upgrading an experimental server, you should backup
-all configuration and data.
+Nothing special.
NEW FEATURES
============
-Samba4 supports the server-side of the Active Directory logon environment
-used by Windows 2000 and later, so we can do full domain join
-and domain logon operations with these clients.
+Flush requests from SMB2/3 clients are handled asynchronously and do
+not block the processing of other requests. Note that 'strict sync'
+has to be set to 'yes' for Samba to honor flush requests from SMB
+clients.
-Our Domain Controller (DC) implementation includes our own built-in
-LDAP server and Kerberos Key Distribution Center (KDC) as well as the
-Samba3-like logon services provided over CIFS. We correctly generate
-the infamous Kerberos PAC, and include it with the Kerberos tickets we
-issue.
+WINS nsswitch module
+====================
-SWAT is now integrated into Samba 4 as the user-friendly interface to
-Samba server management. SWAT provides easy provides access to our
-setup and migration tools. Using SWAT, you can migrate windows
-domains in Samba 4, allowing easy setup of initial user databases.
+The WINS nsswitch module has been rewritten to address memory issues and to
+simplify the code. The module now uses libwbclient to do WINS queries. This
+means that winbind needs to be running in order to resolve WINS names using
+the nss_wins module. This does not affect smbd.
-The new VFS features in Samba 4 adapts the filesystem on the server to
-match the Windows client semantics, allowing Samba 4 to better match
-windows behaviour and application expectations. This includes file
-annotation information (in streams) and NT ACLs in particular. The
-VFS is backed with an extensive automated test suite.
+######################################################################
+Changes
+#######
-A new scripting interface has been added to Samba 4, allowing
-JavaScript programs to interface to Samba's internals.
+smb.conf changes
+----------------
-The Samba 4 architecture is based around an LDAP-like database that
-can use a range of modular backends. One of the backends supports
-standards compliant LDAP servers (including OpenLDAP), and we are
-working on modules to map between AD-like behaviours and this backend.
-We are aiming for Samba 4 to be powerful frontend to large
-directories.
+ Parameter Name Description Default
+ -------------- ----------- -------
+ aio max threads New 100
-CHANGES SINCE TP5
-=================
+CTDB changes
+------------
-In the time since TP5 was released in June 2007, Samba has
-continued to evolve, but you may particularly notice these areas:
+* The CTDB tunable parameter EventScriptTimeoutCount has been renamed
+ to MonitorTimeoutCount
- Group Policy Support: Basic group policies may be defined, and are
- enforced by Windows clients
+ It has only ever been used to limit timed-out monitor events.
- MMC Support: The Active Directory Users and Computers console now
- works, supporting most operations.
-
- Winbind: Kai Blin has been working hard on his Google Summer of
- Code project, creating a winbind implementation for Samba4.
-
- Heimdal update: A Heimdal 1.0 snapshot is now included as the
- internal Kerberos library in Samba4.
-
- In the past few weeks, many small but significant bugs have been
- fixed, particularly thanks to Matthias Dieter Wallnöfer <mwallnoefer@yahoo.de>
-
-These are just some of the highlights of the work done in the past few
-months. More details can be found in our SVN history.
-
-
-CHANGES
-=======
-
-Those familiar with Samba 3 can find a list of user-visible changes
-since that release series in the NEWS file.
+ Configurations containing CTDB_SET_EventScriptTimeoutCount=<n> will
+ cause CTDB to fail at startup. Useful messages will be logged.
KNOWN ISSUES
============
-- Domain member support is in it's infancy, and is not comprable to
- the support found in Samba3.
-
-- There is no printing support in the current release.
-
-- Support for managing groups is currently poor (as the
- memberOf/member linked attributes are not kept in sync).
-
-- Renaming and deleting subtrees (containers) in the the LDB tree will
- have unexpected results.
+Currently none.
-- The Samba4 port of the CTDB clustering support is not yet complete
+#######################################
+Reporting bugs & Development Discussion
+#######################################
-RUNNING Samba4
-==============
+Please discuss this release on the samba-technical mailing list or by
+joining the #samba-technical IRC channel on irc.freenode.net.
-A short guide to setting up Samba 4 can be found in the howto.txt file
-in root of the tarball.
+If you do report problems then please try to send high quality
+feedback. If you don't provide vital information to help us track down
+the problem then you will probably be ignored. All bug reports should
+be filed under the Samba 4.3 product in the project's Bugzilla
+database (https://bugzilla.samba.org/).
-DEVELOPMENT and FEEDBACK
-========================
-Bugs can be filed at https://bugzilla.samba.org/. Please
-look at the STATUS file before filing a bug to see if a particular
-is supposed to work yet.
-Development and general discussion about Samba 4 happens mainly on
-the #samba-technical IRC channel (on irc.freenode.net) and
-the samba-technical mailing list (see http://lists.samba.org/ for
-details).
+======================================================================
+== Our Code, Our Bugs, Our Responsibility.
+== The Samba Team
+======================================================================
git.samba.org / obnox / samba / samba-obnox.git / blobdiff