-What's new in Samba 4 alpha17
+What's new in Samba 4 alpha21
=============================
Samba 4.0 will be the next version of the Samba suite and incorporates
support for the Active Directory logon protocols used by Windows 2000
and above.
+
WARNINGS
========
-Samba4 alpha17 is not a final Samba release, however we are now making
+Samba4 alpha21 is not a final Samba release, however we are now making
good progress towards a Samba 4.0 release, of which this is a preview.
-Be aware the this release contains both the technology of Samba 3.6
-(that you can reasonably expect to upgrade existing Samba 3.x releases
-to) and the AD domain controller work previously known as 'samba4'.
-
-While binaries for the stable file server are provided in this
-release, for a stable, supported file server, Samba3 domain or AD
-domain member installation, please run a Samba 3.x release, as we are
-still bedding down the new single build system.
+Be aware the this release contains the best of all of Samba's
+technology parts, both a file server (that you can reasonably expect
+to upgrade existing Samba 3.x releases to) and the AD domain
+controller work previously known as 'samba4'.
Samba4 is subjected to an awesome battery of tests on an automated
basis, we have found Samba 4.0 to be very stable in it's behavior.
However, we still recommend against upgrading production servers from
Samba 3.x release to Samba 4.0 alpha at this stage.
+In particular note that the new default configuration 's3fs' may have
+different stability characteristics compared with our previous default
+file server. We are making this release so that we can find and fix
+any of these issues that arise in the real world. New AD DC installations
+can provision with --use-ntvfs to obtain the previous default file
+server. Existing installations will be unaffected at this stage.
+
If you are upgrading, or looking to develop, test or deploy Samba 4.0
alpha releases, you should backup all configuration and data.
the infamous Kerberos PAC, and include it with the Kerberos tickets we
issue.
-Samba 4.0 alpha ships with two distinct file servers. The file server
-from the Samba 3.x series is 'smbd', and works with the binaries users
-would expect from that series (nmbd, winbindd, smbpasswd).
+Samba 4.0 alpha ships with two distinct file servers. We now use the
+file server from the Samba 3.x series 'smbd' for all file serving by
+default. For pure file server work, the binaries users would expect
+from that series (nmbd, winbindd, smbpasswd) continue to be available.
+
+Samba 4.0 also ships with the 'NTVFS' file server. This file server
+is what was used in all previous alpha releases of Samba 4.0, and is
+tuned to match the requirements of an AD domain controller. We
+continue to support this, not only to provide continuity to
+installations that have deployed it as part of an AD DC, but also as a
+running example of the NT-FSA architecture we expect to move smbd to in
+the longer term.
-Samba 4.0 also ships with a new file server, which is tuned to match
-the requirements of an AD domain controller. Users should not use the
-file server in the 'samba' binary for non-DC related tasks.
+As mentioned above, this change to the default file server may cause
+instability, as we learn about the real-world interactions between
+these two key components.
A new scripting interface has been added to Samba 4, allowing Python
programs to interface to Samba's internals, and many tools and
-internal workings of the DC code is now implemented in python.
+internal workings of the DC code is now implemented in python.
-CHANGES SINCE alpha16
+
+CHANGES SINCE alpha20
=====================
-For a list of changes since alpha 15, please see the git log.
+For a list of changes since alpha20, please see the git log.
$ git clone git://git.samba.org/samba.git
$ cd samba.git
-$ git log release-4-0-0alpha16..release-4-0-0alpha17
+$ git log samba-4.0.0alpha20..samba-4.0.0alpha21
Some major user-visible changes include:
-samba-tool dbcheck
-------------------
-
-We now have an fsck-like tool for Samba's internal sam.ldb database.
-Run samba-tool dbcheck after installation to check your database for
-self-consistency. Any database created with a previous Samba4 alpha
-will have a very large number of consistency errors, which this tool
-can fix.
-
-See also the -H option to point dbcheck at a different database to the
-default, and the --fix and --yes options to make changes and to not
-prompt about those changes.
-
-After upgrading Samba, it is suggested that you do the following:
+For installations that do not need an AD Domain controller, we can now
+build using MIT Kerberos from the local system. This is important for
+some distributors. This is enabled with the new --with-system-mitkrb5
+configure option. A synonym is the new --without-ad-dc option.
- - stop samba
- - take a backup copy of your sam.ldb and sam.ldb.d/* database files
- - run samba-tool dbcheck --cross-ncs --fix
- - use 'all' to say yes to fixing each type of error found
- - after it has finished, run dbcheck again to ensure it reports no
- errors
+The 's3fs' effort has moved to a new stage, with this now being the
+default mode of operation for new provisions.
-There will be a lot of errors fixed, particularly related to
-bad/missing GUID values. This is due to a bug in previous releases
-that left many objects with bad GUID values. These can all be fixed
-using dbcheck with steps above.
+The BIND 9 DLZ plugin has had some stability improvements under BIND reloads.
+The 'samba-tool domain samba3upgrade' tool will now generally import
+all group members, and correctly imports domain password policies.
-New default paths
------------------
+Some major but less visible changes include:
-The configure options for paths have changed again, and the
---enable-fhs option has been reinstated. Packagers should attempt to
-first package Samba using:
+Continued early implementation work on the SMB 2.2 protocol client and server as
+the team improves and develops support these new protocols.
-./configure --enable-fhs --prefix=/usr --sysconfdir=/etc --localstatedir=/var
-and only after examining the location Samba uses with these options
-should further changes be made. Existing packaging scripts are not
-expected to work unmodified, instead the Samba Team's aim is to
-simplify such scripts for the long term.
-
-samba-tool domain samba3upgrade
--------------------------------
+KNOWN ISSUES
+============
-The new samba-tool domain samba3upgrade command is a supported upgrade route from Samba
-3.x domain controllers to Samba 4.0 AD domain controllers. This
-provides a one-time migration of all users, domain members, passwords,
-groups, group members and account polcies.
+- We are making this alpha release to gain real-world use of the 's3fs'
+ file server combination we will use for the Samba 4.0 release.
+ Users should expect some rough edges: in particular, there are
+ warnings about invalid parameters from the two respective parameter
+ parsing engines.
-This tool is still under development and may fail when presented with
-an inconsistant Samba3 database (such as many LDAP configurations).
-We hope to improve the error handling and recovery in these
-situations, so please provide feedback using the samba-technical
-mailing list.
+- There have been improvements to FreeBSD support, but more work is
+ still required to finish this effort
-KNOWN ISSUES
-============
+- upgradeprovision should not be run when upgrading to this release
+ from a recent release. No important database format changes have
+ been made since alpha16.
- Installation on systems without a system iconv (and developer
headers at compile time) is known to cause errors when dealing with
non-ASCII characters.
-- In some situations, group members may not be upgraded by the
- samba-tool domain upgrade_from_s3 script
-
-- The samba-tool domain join script will not join Windows 2000 domains.
-
- Domain member support in the 'samba' binary is in it's infancy, and
is not comparable to the support found in winbindd. As such, do not
use the 'samba' binary (provided for the AD server) on a member
server.
-- There is no printing support in the 'samba' binary (use smbd instead)
-
- There is no NetBIOS browsing support (network neighbourhood) in the
'samba' binary (use nmbd and smbd instead)
git.samba.org / kai / samba.git / blobdiff