To release Samba 4.0 'as is'

Stefan Gohmann gohmann at
Wed Nov 23 02:08:51 MST 2011

Am Dienstag 22 November 2011 schrieb Andrew Bartlett:
> I would like to propose that we proceed to making a pre-release of Samba
> 4.0 in the next month (ie, before Christmas), and that we propose to
> release Samba 4.0 'as is' regarding major features.
> To be clear, I propose that the DNS server work continue, and we seek a
> resolution of the best approach here over the time between now and a
> release, but we do not block a release on this point.  (I am confident
> however that those involved will have a good solution, and even the
> current flat file is clearly good enough for our many users).
> I also propose that we do not make the major architectural changes
> between now and the release to change file server or winbind
> implementations for the AD DC.  Instead, we continue to build on the
> massive efforts already made here over the next few months, but we will
> not change the default behaviour for a 4.0 release.
> This will give the vendors (Univention and Resara) and our numerous
> users who are building on top of Samba 4.0 alpha releases a stable
> release to move to, based on the current architecture, before we make
> the change to a common file server for Samba 4.1.
> This will mean we continue to ship smbd, nmbd, winbindd, samba etc as
> found in the current alpha releases.
> With this plan, and with the quality brought about by our continuous
> integration approach, I think we can make a Samba 4.0 release in a
> reasonable time-frame, perhaps with a final release in about three
> months time.
> I do wish to be clear that I'm certainly not abandoning the idea of a
> single file server, and I know many others on the team have also
> invested great amounts of their own time in this effort.  It is
> important not only for NAS vendors who wish to add AD to the NAS (an
> idea I raise with every NAS vendor I get the chance to speak to), but
> also our users who still regularly ask for a combined release with the
> AD server, file server and print server all present in the same runtime
> installation.
> What do others think?

+1 from me.

As some of you know, we will ship Samba 4 with the next major release of UCS 
in a few weeks. We made a lot of good progress in the last few month, 
specially with the help of Stefan Metzmacher.

Our status is:

1. The user can choose between Samba 3.5 and Samba 4 in the package selection 
of the UCS installation.

2. We will support multiple Samba 4 DCs in one domain.

3. We won't support a mix with Microsoft AD DCs. This is a very big 
limitation, but we first want to gather in a plain Samba 4 setup.

4. In UCS we have diffrent system roles similar to the Samba roles. For file 
server we will normal use member server and for that we use Samba 3.5 which 
joins into the Samba 4 domain.

5. But we also support a file server on the Samba 4 DC. We start the smbd for 
file and print services and Metze wrote a vfs module for the sysvol share 

6. The bind9 dlz module works fine for us. Windows Kerberos DNS updates are 
working directly.

7. With the S4 Connector we synchronize the data between Samba 4 and OpenLDAP.

8. We write automatically idmap.ldb to get an association between the Samba 
users/groups and the POSIX users/groups.


Stefan Gohmann
Head of Software Engineering 

Univention GmbH
Linux for your business
28359 Bremen
Tel. : +49 421 22232-0
Fax :  +49 421 22232-99

gohmann at

Geschäftsführer: Peter H. Ganten
HRB 20755 Amtsgericht Bremen
Steuer-Nr.: 71-597-02876 

More information about the samba-technical mailing list