-What's new in Samba 4 alpha16
+What's new in Samba 4 alpha18
=============================
Samba 4.0 will be the next version of the Samba suite and incorporates
WARNINGS
========
-Samba4 alpha16 is not a final Samba release, however we are now making
+Samba4 alpha17 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'.
-No migration path is currently provided between these two sets of
-technology. These missing migration paths will be the focus of
-development between now and a Samba 4.0 release.
While binaries for the stable file server are provided in this
release, for a stable, supported file server, Samba3 domain or AD
internal workings of the DC code is now implemented in python.
-CHANGES SINCE alpha15
+CHANGES SINCE alpha17
=====================
-For a list of changes since alpha 15, please see the git log.
+For a list of changes since alpha 17, please see the git log.
$ git clone git://git.samba.org/samba.git
$ cd samba.git
-$ git log release-4-0-0alpha15..release-4-0-0alpha16
+$ git log release-4-0-0alpha17..release-4-0-0alpha18
-The biggest user-visible change is that binaries from the Samba 3.x
-series of development are now built and installed. These binaries
-(smbd, nmbd, winbindd, net, testparm, etc) operate much as they do in
-the Samba 3.6 release candidates.
+Some major user-visible changes include:
-CHANGES
-=======
+Better IPv6 support
+-------------------
-smb.conf changes
-----------------
+Samba4 was able to run with some IPv6 setup, but during this cycle
+a couple of patches were made to cover more use cases (ie. pure IPv6 interfaces,
+6to4 interfaces, ...). Changes were made in the way IPv6 addresses are looked-up.
+All of this should lead to much better support of IPv6 in Samba, please report any
+remaining problem.
- Parameter Name Description Default
- -------------- ----------- -------
- announce version Removed
- announce as Removed
-Those familiar with Samba 3 can find a list of user-visible changes
-between the two technology sets provided in the NEWS file.
+More Directory replication stability and correctness
+----------------------------------------------------
+
+A couple of patches were made to support correctly the recycled objects and replicate them
+correctly too. Improvement on deleted links pointed to deleted items were made too.
+Also a timeout for the getncchanges was implemented so that we are always sure that a
+getncchanges call will take not more than xx seconds (10 by default but it's a parameter).
KNOWN ISSUES
============
+- 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
- There is no printing support in the 'samba' binary (use smbd instead)
-- There is no NetBIOS browsing support in the 'samba' binary (use nmbd
- and smbd instead)
+- There is no NetBIOS browsing support (network neighbourhood) in the
+ 'samba' binary (use nmbd and smbd instead)
- Clock Synchronisation is critical. Many 'wrong password' errors are
actually due to Kerberos objecting to a clock skew between client
experience issues with DRS replication, as we have fixed many issues
here in response to feedback from our production users.
-- Users upgrading existing databases to Samba4 should carefully
- consult upgrading-samba4.txt. We have made a number of changes in
- this release that should make it easier to upgrade in future.
- Btw: there exists also a script under the "setup" directory of the
- source distribution called "upgrade_from_s3" which should allow a step-up
- from Samba3 to Samba4. It's not included yet in the binary distributions
- since it's completely experimental!
-
RUNNING Samba 4.0 as an AD DC
=============================
git.samba.org / metze / samba / wip.git / blobdiff