Where to for Samba4?
Stefan (metze) Metzmacher
metze at samba.org
Fri Sep 7 07:49:15 GMT 2007
-----BEGIN PGP SIGNED MESSAGE-----
Andrew Bartlett schrieb:
> On Fri, 2007-09-07 at 08:36 +0200, Stefan (metze) Metzmacher wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>> Andrew Morgan schrieb:
>>> I was under the impression that Samba4 would be the next version of
>>> Samba. After reading this discussion, it almost sounds like there will
>>> be 2 different kinds of Samba:
>>> Samba Active Directory Services - Samba4
>>> Samba File and Print Services - Samba3
>>> I don't care either way so long as they are both maintained, but was
>>> that the intention? :)
>> I really think the final samba4 release should support basicly the same
>> features as samba3. That means samba4 should be a good file and print
>> server! Maybe not supporting all smb.conf options from samba3, but it
>> have to have the same or better quality. Samba4 should support
>> the DC, MEMBER and STANDALONE roles. Also samba4 should provide a
>> really working winbind which provides compatible features/protocols as
>> So the final Samba4 should be able to replace Samba3.
>> But I think it would be a good idea to have a 'samba4dc'
>> project which can run parallel to samba3 and just provides
>> domain controller features (without DRSUAPI replication).
>> I don't think it would be a good idea to name a release
>> "samba 4.0.0" which can't replace any samba 3.x.x release.
> But how do we get there? That's the point I'm trying to make - who can
> help us get there?
> I don't share your view that we must be a print server to be Samba 4.0.0
> - but perhaps that's just because I can't see how we can achieve that
I think it's just a matter of time and patience:-)
Why is there a need to call something 4.0.0 final, when it is not final?
I think the way to go is to isolate yet working feature of samba4 into
separate projects like samba4wins, which can stand on their own parallel
The goals you mentioned in your previews mail perfectly match a project
name of "samba4dc", and it would make a lot of sense to have something
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
More information about the samba-technical