I'm not sure if this message will be on time before the release of Slackware 14.1.

I've managed to test upgrade and new deployments based on 14.1rc with samba 4.1 and everything is working well on samba side with internal DNS except the startup.

From the documentation samba4 should be started with "samba" on command line and stopped using smbcontrol (ie: smbcontrol all shutdown).
The actual rc.samba in samba4.1 package seems to work only for samba3, smbd and nmbd complain (in logs) that they cannot be started directly on samba4 and that we should use "samba" on command line (they actually don't start when invoked directly).
A small adaptation of the rc.samba script may be desirable before official release...

Below part is SOLVED
[By the way using the internal Samba4 DNS is OK for small organizations or simple setups ; using Bind DLZ is more appropriate for real life scenarios and better performance. I know it's kinda late for this but why isn't bind package compiled with DLZ ? It would certainly help third parties and samba4 users to have bind DLZ and Samba4 compiled with DLZ in 14.1 release (or at least testing). DLZ should now be included in Bind upstream sources and I don't remember any problem compiling it]

you have to start the samba daemon (and eventually integrate it with bind) if you want to use it as an AD domain controller, but I suppose most of Slackware users don't want to deploy by default a (not so easy to manage) DC to share some files.

and bind's dlz patches are not included in the default bind release...

just my 2c

From version 9.4

bind-9.4.0/CHANGES

ops, sorry, I missed that.

I just read https://wiki.samba.org/index.php/Dns-backend_bind, but still can't be used in Slackware by default, as it doesn't ship any kerberos implementation.

Thanks ponce and wildwizard.

wildwizard you were faster than me
DLZ is integrated from 9.4 and built by default from 9.8 on.

I just checked and it is working already on Slackware 14.1rc3 with samba4 so I'm editing the subject of this thread ; I didn't see that it was included in latest packages.
I tested with my AD setup and zones are updated successfully, no need for external Kerberos libraries.

The only remaining request should be about rc.samba.

For the samba4 startup script, does it work for you as it is when using only "simple" shares ?
AD has become way more simple to setup, especially on 4.1, that I consider migrating to that paradigm only on production servers.

no, it doesn't work for me.

I should follow this

https://wiki.samba.org/index.php/Set...re_file_shares

but I don't like that I have to do it through windows