-What's new in Samba 4 beta1
+What's new in Samba 4 beta2
=============================
Samba 4.0 will be the next version of the Samba suite and incorporates
WARNINGS
========
-Samba4 beta1 is not a final Samba release, however we are now making
+Samba4 beta2 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 the best of all of Samba's
technology parts, both a file server (that you can reasonably expect
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 or join with --use-ntvfs to obtain the
-previous default file server. Existing installations will be
-unaffected at this stage.
+previous default file server. See below how to continue using ntvfs
+in an existing installation.
If you are upgrading, or looking to develop, test or deploy Samba 4.0
beta releases, you should backup all configuration and data.
+
+UPGRADING
+=========
+
+Users upgrading from Samba 3.x domain controllers and wanting to use
+Samba 4.0 as an AD DC should use the 'samba-tool domain
+classicupgrade' command. See the wiki for more details:
+https://wiki.samba.org/index.php/Samba4/samba3upgrade/HOWTO
+
+Users upgrading from Samba 4.0 alpha and beta releases since alpha15
+should run 'samba-tool dbcheck --cross-ncs --fix'. Users upgrading
+from earlier alpha releases should contact the team for advice.
+
+
NEW FEATURES
============
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.
+As DNS is an integral part of Active Directory, we also provide a DNS
+solution, using the BIND DLZ mechanism in versions 9.8 and 9.9.
+During the provision, a configuration file will be generated for bind
+to make it use this plugin. We also have a project to provide a
+minimal internal DNS server from within the Samba process, for easier
+'out of the box' configuration. Note however that this is not yet
+complete (pending addition of secure DNS update support).
+
+To provide accurate timestamps to Windows clients, we integrate with
+the NTP project to provide secured NTP replies.
+Finally, 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.
-CHANGES SINCE alpha21
+CHANGES SINCE beta1
=====================
-For a list of changes since alpha21, please see the git log.
+For a list of changes since beta1, please see the git log.
$ git clone git://git.samba.org/samba.git
$ cd samba.git
-$ git log samba-4.0.0alpha21..samba-4.0.0beta1
+$ git log samba-4.0.0beta1..samba-4.0.0beta2
Some major user-visible changes include:
-The internal DNS server has had some stability improvements, and
-now handles forwarded DNS replies in an async manner.
+The default file server for EXISTING USERS has changed to s3fs. To
+continue to use ntvfs, you must set in your smb.conf:
-The build of libtdb.so and libtalloc.so has been removed from the
-autoconf build. Use the build in lib/talloc and lib/tdb to build
-this software for use across the system.
+ server services = +smb -s3fs
+ dcerpc endpoint servers = +winreg +srvsvc
-The smbclient and nmblookup binaries have been renamed in the top
-level build, so smbclient/nmblookup are now the implementations from
-the Samba 3.x heritage.
+samba-tool dbcheck will now upgrade older databases that are missing
+GUIDs in the schema partition.
-Improved handling of the cleanup of smbd child processes (removing a
-number of scary warnings from our log output).
+The 'samba-tool domain samba3upgrade' command is now called
+'samba-tool domain classicupgrade' and now creates users and groups
+with the posixAccount objectClass and uidNumber and gidNumber values.
+
+The new 'idmap_ldb:use rfc2307' parameter allows these values to be
+used instead of the idmap.ldb, where found in the directory.
+
+Work has continued to make Samba more portable to a wide variety of
+Unix-like systems, and to support --without-ad-dc on systems lacking a
+modern MIT krb5.
+
+Less visible, but very importantly, the work has continued in restructuring
+the smbd file server to implement SMB3.
+
+The TDB2 database library has been changed to ntdb, but will not be
+the default db layer for the 4.0 release. We will continue to use tdb1.
-Much improved support for FreeBSD, including extended attribute
-support on the filesystem for the AD DC.
KNOWN ISSUES
============
-- We are making this beta release to gain real-world use of the 's3fs'
+- This release makes the s3fs file server the default, as this is the
file server combination we will use for the Samba 4.0 release.
- Users should expect some rough edges: in particular, there are
+ Users should still expect some rough edges: in particular, there are
warnings about invalid parameters from the two respective parameter
parsing engines.
experience issues with DRS replication, as we have fixed many issues
here in response to feedback from our production users.
+
RUNNING Samba 4.0 as an AD DC
=============================
git.samba.org / ddiss / samba.git / blobdiff